{"id": "nist_00000", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control OC-01 in The NIST Cybersecurity Framework (CSF) 2.0? (Part 8) Control OC-01: firmware, operating systems, applications), and services of physical and virtual platforms are managed consistent with the organization's risk strategy to protect their confidentiality, integrity, and availability - o PR.PS-01: Configuration management practices are established and applied - o PR.PS-02: Software is maintained, replaced, and removed commensurate with risk - o PR.PS-03: Hardware is maintained, replaced, and removed commensurate with risk - o PR.PS-04: Log records are generated and made available for continuous monitoring - o PR.PS-05: Installation and execution of unauthorized software are prevented - o PR.PS-06: Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle - Technology Infrastructure Resilience (PR.IR): Security architectures are managed with the organization's risk strategy to protect asset confidentiality, integrity, and availability, and organizational resilience - o PR.IR-01: Networks and environments are protected from unauthorized logical access and usage - o PR.IR-02: The organization's technology assets are protected from environmental threats - o PR.IR-03: Mechanisms are implemented to achieve resilience requirements in normal and adverse situations - o PR.IR-04: Adequate resource capacity to ensure availability is maintained ## DETECT (DE): Possible cybersecurity attacks and compromises are found and analyzed - Continuous Monitoring (DE.CM): Assets are monitored to", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, csf, fips. General security reference material without sensitive content. Source: The NIST Cybersecurity Framework (CSF) 2.0."}]}
{"id": "nist_00001", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector? (Part 111) Control AM-1: | | Associated Test Case | PACS-1 | | Associated Cybersecurity Framework Subcategories | PR.AC-1, PR.AC-7 | | Preconditions | \uf0a7 PACS-1 test case produces successful results that prove the PACS created patient studies and the VNA stored the studies. \uf0a7 A Microsoft Azure storage account exists.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector."}]}
{"id": "nist_00002", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Guidance for First Responder Mobile and Wearable Devices say about B.1.4 Test 4: Obtaining Vulnerability Information from OS version and known databases? (Part 4) According to Security Guidance for First Responder Mobile and Wearable Devices, B.1.4 Test 4: Obtaining Vulnerability Information from OS version and known databases: are administered at the discretion of the first responder and/or mobile ISP service provider. It is recommended to check for device software updates regularly and apply those patches when available. Note that not all CVEs may apply to a specific device, nor may it be possible to address or patch the CVE. OS and patch-level information should be readily available to the device user at any time of inquiry. Figure 6 - CVE reference in National Vulnerability Database <!-- image --> Using one of the CVE's found in Figure 5, Figure 6, cross-references the CVE-2018-9497 ID in the NIST National Vulnerability Database to obtain more information about the unpatched vulnerability [23]. Detailed information can be used to determine if a patch is available or if further action is needed to mitigate the risk. Benefits: Analysis of known vulnerabilities informs the user of potential threats that the device may incur. CVE analysis allows the users to determine the next steps to secure the device, such as if the device can be updated, if further protections are necessary, or supplemental mitigation mechanisms must be employed.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, cve-. Contains technical security guidance that could inform defensive posture. Source: Security Guidance for First Responder Mobile and Wearable Devices."}]}
{"id": "nist_00003", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD) say about The uplink port? (Part 1) According to Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD), The uplink port: The uplink port auto eth enp1s0 iface eth0inet dhcp v. Confirm that the bridge entry contains an ovs_bridge_uplink_port line referring to the uplink interface as seen in the config below: auto brmn001 allow-ovs brmn001 iface brmn001 inet manual ovs_type OVSBridge ... # This is the port that's connected to the Internet ovs_bridge_uplink_port enp1s0 ... vi. Reboot the gateway to apply the changes to the /etc/network/interfaces file by executing the following command: sudo reboot Create a gateway configuration file for the Micronets Gateway to register for the subscriber: Copy and save the MAC addresses and corresponding interface names output by execut- ing the following command: ifconfig NIST SP 1800-15C: Securing Small-Business and Home Internet of Things Devices 175 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Navigate to the /etc/network/interfaces file on the gateway, and copy the subnets con- figurations, which will be used for the gateway configuration file in the following steps: sudo vim /etc/network/interfaces Copy and save the subnet and ranges associated with the interfaces identified in the previous step from this file. (Note: these are at the bottom of the file.) NIST SP 1800-15C: Securing Small-Business and Home Internet of Things Devices 176 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Create the gateway config file by entering the following command: sudo vim gateway-config-001.json Modify the following configuration to include your gateway\u2019s MAC address and subnets as seen below, and copy them into the gateway-config-001.json file.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_00004", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-8(5) in Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management? (Part 28) Control CM-8(5): | The defect check to assess whether this sub-capability is operating effectively is defined as follows: | Defect Check ID | Defect Check Name | Assessment Criteria Summary | Assessment Criteria Notes | Selected | |-------------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| | HWAM-Q04 | Poor timeliness metric | Frequency of update (timeliness) of the actual inventory collection is lower than an [organization- defined-threshold].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management."}]}
{"id": "nist_00005", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT) provide? (Section 58) itionally, if a component fails, it should fail in a manner that does not generate unnecessary traffic on IoT or other networks, or does not cause another problem elsewhere, such as a cascading event. IoT system should also allow for graceful degradation such as moving from 'normal operation' with full automation to 'emergency operation' with operators more involved and less automation to 'manual operation' with no automation. - \uf0a7 Restoring the system after an incident. Incidents are inevitable, and an incident response plan is essential. A major characteristic of a good security program is how quickly an IoT system can be recovered after an incident has occurred. For the purposes of this report, risk is a measure of the extent to which an entity is threatened by a potential circumstance or event and is typically a function of: (i) the adverse impacts that would arise if the circumstance or event occurs; and (ii) the likelihood of occurrence. For example, information security risks are those that arise from the loss of confidentiality, integrity, or availability of information or information systems. Information security risks reflect the potential adverse impacts to organizational operations (i.e., mission, functions, image, or reputation), organizational assets, individuals, other organizations, and the Nation. Risk assessment is the process of identifying, estimating, and prioritizing risks. Assessing risk requires the careful analysis of threat and vulnerability information to determine the extent to which circumstances or events could adversely impact an organization and the likelihood that such circumstances or events will occur [21]. The proliferation and increased ubiquity of IoT components are likely to heighten the risks they present; particularly as cyber criminals work to develop new generations of malware dedicated to exploiting them. For instance, Dyn, a company that monitors and routes Internet traffic, was a victim of a DDoS attack in October 2016.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit, malware. Contains technical security guidance that could inform defensive posture. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_00006", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain REFERENCES according to NIST Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, REFERENCES: Source Control: MA-04 Supporting Publications: SP 800-63-3 [27], SP 800-88 [50]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_00007", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control say about Identity Function? (Part 29) According to Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control, Identity Function: For example, the | [NIST-SP800-53r5] PM-30, SA-9, SR-1, SR-2, SR-3, SR-5 [NIST-SP800-161] | | Subcategory | Applicability to the Ground Segment | References | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------| | organizational stakeholders.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control."}]}
{"id": "nist_00008", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Operational Technology (OT) Security provide? (Section 78) d information security program. However, information security programs typically focus on the confidentiality, integrity, and availability \u2013 in that order \u2013 of information for the entire organization. Information security programs do not necessarily address all of the specific security and operational needs of an OT environment, which instead prioritizes safety, followed by availability, integrity, and confidentiality. This difference in focus and priorities between IT and OT security programs should be kept in mind. NIST SP 800-100, Information Security Handbook: A Guide for Managers [SP800-100], provides a broad overview of information security program elements to assist in establishing and implementing an information security program in an organization. The lifespan of an OT system can exceed 20 years. As a result, many legacy systems may contain hardware and software that are no longer supported by vendors and cannot be patched or updated to protect against new vulnerabilities. In that case, the security program should be tailored to the unique characteristics of the legacy system to determine whether the controls are applicable. When security controls are not supported by the legacy OT system, compensating controls should be considered. For example, anti-malware software may not be available for systems such as PLCs and DCS, which means that malware protection requirements cannot be applied to these endpoints. In this case, a compensating control should be considered, such as using a firewall with a deep packet inspection capability that can monitor and block advanced threats like malware. The primary purpose of investing in a cybersecurity program is risk management. Risk to operations exists because of the potential of threat actors exploiting the vulnerabilities in the applications and infrastructures.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, threat actor, malware. Contains technical security guidance that could inform defensive posture. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_00009", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-7 in Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments? (Part 191) Control CM-7: the following command: Get-VM \"VM Name\" | Get-AdvancedSetting -Name isolation.tools.autoInstall.disable If isolation.tools.autoInstall.disable does not exist or is not set to true, this is a finding. | TRUE | | CCE ID | Configur ation(s) | Built-In/ Enhanced | Prod- uct | Audit Procedure | Recommended Parameter Value | |---------------|---------------------------------|----------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| | CCE- 8433 6-7 | NIST800 53-VI- ESXI- CFG- 00099 | Enhanced | vCent er | From a PowerCLI command prompt, while connected to the ESXi host or vCenter server run the following command: Get-VM \"VM Name\" | Get-AdvancedSetting -Name tools.setinfo.sizeLimit If tools.setinfo.sizeLimit does not exist or is not set to 1048576, this is a finding. | 1048576 | | CCE- 8433 7-5 | NIST800 53-VI- ESXI- CFG- 00100 | Enhanced | vCent er | From a PowerCLI command prompt, while connected to the ESXi host or vCenter server run the following command: Get-VM \"VM Name\" | Get-AdvancedSetting -Name isolation.device.edit.disable If isolation.device.edit.disable does not exist or is not set to true, this is a finding.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments."}]}
{"id": "nist_00010", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is References according to NIST_SP_800-53r5_Security_Privacy_Controls? References: [OMB A-130], [FIPS 140-3], [SP 800-61], [SP 800-83], [SP 800-92], [SP 800-94], [SP", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00011", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Exchanging Event Tickets and Coupons : according to NIST A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems According to A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems, Exchanging Event Tickets and Coupons :: This use case considers a system to issue and manage transferable event tickets and coupons (e.g., for concerts, conferences). The system is owned by a ticketing company that controls initial identity proofing and user registration. Once registered, event organizers can issue transferable tickets to registered users (in the form of non-fungible tokens). Although the initial registration is controlled by the system owner, users can transfer tickets on their own without any further approval from the system owner. For instance, a ticket owner may be able to exchange the ticket for one on another date, give it to a friend, or sell it. After attending a concert, an individual may keep the digital ticket as a souvenir and add an attestation of it on social media to connect with other attendees and artists. The system also implements a loyalty program to earn rewards and attend other events. It periodically distributes redeemable coupons (in the form of a Merkle airdrop of non-fungible tokens) to the customer base that can then be used to claim discounts to attend new events. While these coupons have an expiration date and were issued to a certain group of individuals, they too can be made transferable. For example, an individual that receives a coupon but prefers to give it to a friend can do so, thus allowing the event organizers to reach a wider target audience.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: identity management, token. Contains security framework guidance for authentication systems. Source: A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems."}]}
{"id": "nist_00012", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RA-1 in Securing Wireless Infusion Pumps in Healthcare Delivery Organizations? (Part 77) Control RA-1: data reporting and analysis to add safety, efficiency, and value Provides an interface capability to help the hospital biomedical engineering department effectively manage their infusion pump fleet. The drug library publishing module helps the hospital pharmacy effectively distribute and enforce medication safety rules. A virtual server platform that provides two-way wireless communication with Alaris PC units Manages drug libraries, firmware updates, and configurations of intravenous pumps NIST SP 1800-8C: Securing Wireless Infusion Pumps 31 Vendor Name Product Name Operating Platform Description Smiths Medical PharmGuard Server Microsoft Windows Manages drug libraries, firmware updates, and configurations of Hospira intravenous pumps for Smiths Medical Pumps NCCoE installed the pump servers in the network in the VLAN 1400. To do so, we prepared a virtual machine in the VMware with the operating system and network, as specified in the vendor installation manual. Because one or more database is associated with the infusion pump server for storing the data, the installation and configuration of the database are parts of the pump server installation procedure. After the installation, we implemented a basic configuration: the user account setup, reporting template configuration, security hardening, license installation, pump metadata installation. T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P 1 8 0 0 - 8 . . We have not included the pump server setup because the vendor performs this activity.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Wireless Infusion Pumps in Healthcare Delivery Organizations."}]}
{"id": "nist_00013", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Study of OSI Key Management provide? (Section 213) describing the Internet suite of protocols and related experiments. Responder: A service user that responds to a connection or association. RFC: See Request for Comments. QOS: See Quality of Service. Quality of Service: The desired or actual characteristics of a service; typically, but not always, those of the network service. SAP: See service access point. SDU: See service data unit. Service access point: An artifact modeling how a service is made available to a user. Service data unit: User-data passed through a service access point. Service primitive: An artifact modeling how a service is requested or accepted by a user. Session layer: That portion of an OSI system responsible for adding control mechanisms to the data exchange. Transfer syntax: A description of an instance of a data structure that is expressed as string of bits. Transport layer: That portion of an OSI system responsible for reliability and multiplexing of data across network (over and above that provided by the network layer) to the level required by the application. TSAP: Transport service access point. In this section security terms and abbreviations used in this paper are defined. The terms and abbreviations are compiled mainly from [ISO 7498-2], [ISO/SC21 6693] and [BARK91]. Access Control: The prevention of unauthorized use of a resource, including the prevention of use of a resource in an unauthorized manner. Asymmetric cryptographic algorithm: A cryptographic algorithm that uses two related keys. At least one of the two keys is the cryptographic inverse of the other. CA: (Certification Authority. Confidentiality: The property that information is not made available or disclosed to unauthorized individuals, entities, or processes. Connection confidentiality: This service provides for the protection of (N)-user-data on an (N)-connection. Connectionless confidentiality: This service provides for the confidentiality of all (N)-user-data in a single connectionless (N)-SDU.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, key management, sso. Contains security framework guidance for authentication systems. Source: A Study of OSI Key Management."}]}
{"id": "nist_00014", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-6 in NIST_SP_800-37r2_Risk_Management_Framework? (Part 231) Control AM-6: MANAGEMENT PROCESS he following sections describe the roles and responsibilities of key participants involved in an organization's risk management process.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_00015", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does IT Asset Management say about 5.3.4.11 AssetCentral? According to IT Asset Management, 5.3.4.11 AssetCentral: AssetCentral is a Web-based IT asset management and data center management solution. Information on all physical IT assets used in the ITAM project was entered into AssetCentral. This information includes make, model, serial number, barcode, room, rack, and owner. This information is then used to provide a complete picture of the state of an asset. Splunk Enterprise utilizes a direct SQL database query to gather information from AssetCentral.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IT Asset Management."}]}
{"id": "nist_00016", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Notional Supply Chain Risk Management Practices for Federal Information Systems provide? (Section 55) ssue or adverse supply chain event. - c) Establish policies and procedures that require identification methods to support provenance in the event of a supply chain issue or adverse supply chain event. - d) Define, design, and implement roles that limit privilege and create redundancy throughout the element life cycle to mitigate the risk of a single role being able to, intentionally or unintentionally, create adverse consequences. - e) Require protection and safeguarding of authentication mechanisms. - a) Implement unique identification requirements for elements and systems by applying policies, procedures, and means of identification to the supply chain. - b) Apply unique identifiers to design, test, and evaluation activities, including design tools (hardware and software), drawings and diagrams, bills of material, and tools used to protect the design, test, and evaluation processes. - c) Integrate mechanism(s) to uniquely identify system-critical hardware elements, such as a physical identifier or authenticator to the hardware. This makes unauthorized substitutions more detectable. This can include etched bar codes, holograms, or other unique identification technologies. None - a) Assess the effectiveness of acquirer and integrator identity management and access control policies, procedures, and practices in limiting exposure of, or access to, elements or element processes. - b) Assess implementation of the acquirers' and integrators' assignment of tasks and activities to roles. - c) Employ tools and techniques to determine if authenticators are sufficiently strong to resist attacks intended to discover or compromise authenticators. - d) Perform audits on unique identification deficiencies within acquirer system/environment and report up the supply chain for corrective action. - e) Check for robustness of the acquirer and integrator infrastructure that manages both identities and labels.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, identity management. Contains security framework guidance for authentication systems. Source: Notional Supply Chain Risk Management Practices for Federal Information Systems."}]}
{"id": "nist_00017", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research say about 4.8.5 Microsoft VSC Technology? (Part 1) According to Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research, 4.8.5 Microsoft VSC Technology: 4.8.5 Microsoft VSC Technology The Microsoft Windows 8.1 VSC is a multi-factor X.509-based cryptographic device. 29 The system's TPM protects the DPC's cryptographic key that is activated through a second authentication factor (e.g., PIN). Authentication is accomplished by proving possession of the device and control of the key. All private key cryptographic functions occur within the TPM. Cryptographic message digests occur within the OS's Cryptographic Service Provider (CSP). VSCs utilizing a TPM support three main security principles: - Non-exportability: Since all private information on the VSC is encrypted by using the host machine's TPM, it cannot be used on a different machine with a different TPM. Additionally, TPMs are designed to be tamper-resistant and non-exportable themselves, so an adversary cannot reverse engineer an identical TPM or install the same one on a different machine. - Isolated cryptography: TPMs provide the same properties of isolated cryptography offered by conventional smart cards, and this is utilized by VSCs. When used, unencrypted copies of private keys are loaded only within the TPM and never into memory accessible by the OS. All cryptographic operations with these private keys occur inside the TPM. - Anti-hammering: If a user enters a PIN incorrectly, the VSC responds by using the antihammering logic of the TPM, which rejects further attempts for a period of time instead of blocking the card. This is also known as lockout. ADCS supports TPM attestation, 30 which provides the ability for the issuing CA to confirm that the key in the certificate request is protected by a known TPM.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor. Contains security framework guidance for authentication systems. Source: Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research."}]}
{"id": "nist_00018", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Threshold Schemes for Cryptographic Primitives_ Challenges and Opportunities in Standardization and Validation of Threshold Cryptography provide? (Section 8) ficult to reach a state where the number of contemporaneous compromised shares surpasses the compromise threshold. Separating the analysis of different security aspects can sometimes lead to pitfalls. To avoid such problems it is important to use appropriate formal models of security. At the same time, it is relevant to assess potential tradeoffs that a threshold cryptographic scheme induces across different security properties. A system model is also important to characterize different types of attack that a system may be subject to. Specific attacks in the real world exploit differences between conventional implementations and their idealized versions. Threshold schemes can be used to improve resistance against some of these specific attacks that breach specific security properties (e.g., confidentiality of a key) or sets thereof. An abstract security model is not enough to assess the effects of placing a threshold scheme in an adversarial environment. One also needs to characterize implementation aspects whose variation may affect security. Such characterization helps distinguish, possibly across different application contexts, the resistance provided against certain classes of attacks. To this end, this document proposes that a basis for discussion and comparison of threshold schemes should include the description of several characterizing features. These include the types of threshold, the communication interfaces, the target computing platforms, and the setup and maintenance requirements. The examples in the document illustrate how security properties can vary depending on high-level features, on assumed attack vectors and on the type of adversarial goals and capabilities. On one hand, this helps prevent a possible misconception that a higher threshold directly means higher security. On the other hand, it also intends to convey that threshold schemes can be used to implement cryptographic primitives in a more secure way.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, attack vector. Contains technical security guidance that could inform defensive posture. Source: Threshold Schemes for Cryptographic Primitives_ Challenges and Opportunities in Standardization and Validation of Threshold Cryptography."}]}
{"id": "nist_00019", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Technology Assessment_ Methods for Measuring the Level of Computer Security say about Siiat\\_skiiis\\_aEe\\_Eeeded\\_tQ\\_siiQQessfull3z\\_u\u00a3e\\_it?? According to Technology Assessment_ Methods for Measuring the Level of Computer Security, Siiat\\_skiiis\\_aEe\\_Eeeded\\_tQ\\_siiQQessfull3z\\_u\u00a3e\\_it?: An auditor with ADP skills is needed to carry out the methodology. As the hook notes, \"Evaluation of control strengths and weaknesses is a highly subjective process. No pat formula or procedures exist to give the answers or even to make it easy. This is the process which most requires professional skills of the auditor\" [p. 181].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technology Assessment_ Methods for Measuring the Level of Computer Security."}]}
{"id": "nist_00020", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain &lt;question&gt; according to NIST Specification for the Extensible Configuration Checklist Description Format (XCCDF) According to Specification for the Extensible Configuration Checklist Description Format (XCCDF), &lt;question&gt;: This element specifies an interrogatory string with which to prompt the user during tailoring. It may also be included into a generated document. Note that this element may not contain any XCCDF child elements nor may it contain XHTML formatting elements. Multiple instances may appear with different xml:lang attributes. Content: string Cardinality: 0-n Parent Elements: Group, Rule, Value Attributes: xml:lang Child Elements: none For Rule and Group objects, the question text should be simple binary (yes/no) question, because tailoring for Rules and Groups is for selection only. For Value objects, the question should reflect the designed data value needed for tailoring.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Specification for the Extensible Configuration Checklist Description Format (XCCDF)."}]}
{"id": "nist_00021", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report_ Authentication Diary Study say about A.1.2.3 Frequency? According to Report_ Authentication Diary Study, A.1.2.3 Frequency: Let's look at a couple of episodes where you marked that you were very frustrated. [ Walk through the data from the form, if you have it, up to the point of describing the problem. After you read their description, ask: ] What happened here? - What was frustrating about it? [or, continue, if needed:] Why did you become frustrated? - What did that event cost you?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report_ Authentication Diary Study."}]}
{"id": "nist_00022", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Q. In what time frame must systems and data be recovered and restored when a disruption occurs? according to NIST Information Security Handbook_ A Guide for Managers According to Information Security Handbook_ A Guide for Managers, Q. In what time frame must systems and data be recovered and restored when a disruption occurs?: - A. When a disruption occurs, a recovery strategy must be implemented within the recovery time objective (RTO) period.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_00023", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Interoperability according to Card Technology Developments and Gap Analysis Interagency Report? Interoperability: Card Operating System level - Interoperability of card ICs from different manufacturers that have a microprocessor can also be achieved through the use of a common operating system. Even to the point where it's certainly technically feasible to port the operating systems from the contact card world to a contactless card IC. The protocol obviously, the transmission protocol, has to be different. Currently, these microprocessor based ICs are available that conform to all four parts of ISO14443 or they're becoming available.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Card Technology Developments and Gap Analysis Interagency Report."}]}
{"id": "nist_00024", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges say about TRAININGGLYPH&lt;c=2,font=/HAAAAA+HKGrotesk-Bold&gt; COMPLIANCEGLYPH&lt;c=2,font=/HAAAAA+HKGrotesk-Bold&gt;? According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges, TRAININGGLYPH&lt;c=2,font=/HAAAAA+HKGrotesk-Bold&gt; COMPLIANCEGLYPH&lt;c=2,font=/HAAAAA+HKGrotesk-Bold&gt;: While organizations most often use learning management systems to track RBT completion, over a third use a manual system for tracking. Participants selected all methods that their organization utilizes to track RBT completion (Figure 6). Over half (54%) of survey participants use a Department-wide learning management system (LMS). Over a third (37%) utilize a spreadsheet or other type of manual method to track RBT completion. Only 7% indicated that their organization does not track RBT completion. 29% of survey participants use more than one method to track. Figure 6. Tracking RBT completion (n = 82) <!-- image --> Most organizations do not experience challenges tracking RBT completion, but training tracking for contractors is more challenging than for federal employees. Survey participants rated the level of challenge their organizations face when tracking federal and contractor employee completion of RBT (Figure 7). 19% of participants indicated that it was very or moderately challenging to track federal employee completion of RBT. Over a quarter (29%) said it was very or moderately challenging to track contractor completion of RBT. <!-- image --> 'We've explored self-paced training options, but ensuring compliance and tracking completion is challenging there.' (Q72) Figure 7. Tracking federal and contractor employee RBT completion (n = 76) <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges."}]}
{"id": "nist_00025", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Test Personal Identity Verification (PIV) Cards Version 2 say about Subject Key Identifier :? According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Subject Key Identifier :: A7:16:70:77:ED:C6:C9:30:6F:BC:A3:C3:D1:BA:D5:C5:40:25:47:43", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_00026", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does PIV Data Model Test Guidelines provide? (Section 221) | 1. Set cardHandle := <<valid card handle>> cate from 2. Set OID := <<Digital Signature Certifi (2.16.840.1.101.3.7.2.1.0)>> 3. Call pivGetData w/ \u2022 (IN) cardHandle \u2022 (IN) OID \u2022 (OUT) data 4. Extract the value of the keyUsage extension field the certificate | |--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Expected Result(s) | The digitalSignature and nonRepudiation bits have been set. | | Purpose | Con exists in the certificate corresponds to the p firms that the public key that rivate key on the card. | |--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Reference(s) | 1. FIPS201, Section 5 2. AS07.02.07 | | Precondition | 1. A valid PIV card is inserted into the contact reader. 2. n exists between the test application and er. 3. ion is currently connected to the card application nt on A valid PC/SC connectio the contact read The test applicat which is accessible through card handle. 4. A digital signature key and corresponding certificate are prese the PIV card. | | Test Steps | 1. Take an arbitrary stream of data 2. Hash the data using a hash algorithm 3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_00027", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders say about 3.5.1 PSFR Risks? According to Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders, 3.5.1 PSFR Risks: As PSFR communities adopt mobile platforms and applications, organizations should consider potential risks that these new devices and ecosystems introduce that may negatively affect PSFR organizations and the ability of PSFR personnel to operate. These are some of the risks: - \uf0a7 The reliance on passwords alone by many PSFR entities effectively expands the scope of a single application/database compromise when users fall back to reusing a small set of easily remembered passwords across multiple applications. - \uf0a7 Complex passwords are harder to remember and input to IT systems. Mobile devices exacerbate this issue with small touchscreens that may not work with gloves or other PSFR equipment, and with three separate keyboards among which the user must switch. In an emergency response, any delay in accessing information may prove critical to containing a situation. - \uf0a7 Social engineering, machine-in-the-middle attacks, replay attacks, and phishing all present real threats to password-based authentication systems. - \uf0a7 Deterministic, cryptographic authentication mechanisms have security benefits, yet come with the challenge of cryptographic key management. Loss or misuse of cryptographic keys could undermine an authentication system, leading to unauthorized access or data leakage. - \uf0a7 Biometric authentication mechanisms may be optimal for some PSFR personnel, yet organizations need to ensure that PII, such as fingerprint templates, is protected. - \uf0a7 Credentials exposed to mobile applications could be stolen by malicious applications or misused by nonmalicious applications. Previously, it was common for native applications to use embedded user-agents (commonly implemented with web views) for OAuth requests. That approach has many drawbacks, including the host application being able to copy user credentials and cookies, as well as the user needing to authenticate again in each application.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, single sign-on. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_00028", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1.3 Organization according to NIST A Framework for Designing Cryptographic Key Management Systems According to A Framework for Designing Cryptographic Key Management Systems, 1.3 Organization: Section 1 Introduction provides an introduction to the Key Management Framework and the motivation behind it. Section 2 Framework Basics covers basic concepts of this Framework and provides an overview of the Framework. Section 3 Goals defines the goals of a robust CKMS. Section 4 Security Policies discusses the structure, typical contents, and need for information management, information security, CKMS security, and other related security policies. Section 5 Roles and Responsibilities presents the roles and responsibilities that support a CKMS. SP 800-130 August 2013 Section 6 Cryptographic Keys and Metadata covers the most critical elements of a CKMS: keys and metadata, by enumerating and defining possible key types; key metadata; and key and metadata management functions, along with access control considerations, security issues and recovery mechanisms. Section 7 Interoperability and Transitioning considers the need for interoperability and the ability to easily make transitions in CKMS capabilities in order to accommodate future needs. Section 8 Security Controls describes security controls applicable to a typical CKMS. Section 9 Testing and System Assurances describes security testing and assurances. Section 10 Disaster Recovery deals with disaster recovery in general and of a CKMS specifically. Section 11 Security Assessment discusses the security assessment of a CKMS. Section 12 Technology Challenges briefly discusses the technical challenges provided by new attacks on cryptographic algorithms, key establishment protocols, CKMS devices, and quantum computing. Appendix A enumerates and describes useful references. Appendix B consists of a glossary of terms used in this Framework. Appendix C provides a list of acronyms used in this Framework.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, key management. Contains security framework guidance for authentication systems. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_00029", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guidelines on Electronic Mail Security? (Part 276) Control ES-1: the internal network from the mail server and vice versa | ## Appendix G-Acronym List | 3DES | Triple Data Encryption Standard | |--------|---------------------------------------------------| | ACL | Access Control List | | AES | Advanced Encryption Standard | | API | Application Programming Interface | | ARP | Address Resolution Protocol | | ARPA | Advanced Research Project Agency | | ASCII | American Standard Code of Information Interchange | | BCP | Best Current Practice | | CA | Certificate Authority | | CIO | Chief Information Officer | | CMVP | Cryptographic Module Validation Program | | CPU | Central Processing Unit | | CRAM | Challenge-Response Authentication Mechanism | | CSE | Communications Security Establishment | | DDoS | Distributed Denial of Service | | DMZ | Demilitarized Zone | | DNS | Domain Name System | | DNSBL | Domain Name System Blacklist | | DoD | Department of Defense | | DoS | Denial of Service | | DSA | Digital Signature Algorithm | | DSN | Delivery Status Notification | | DSS | Digital Signature Standard | | ESMTP | Extended Simple Mail Transfer Protocol | | FIPS | Federal Information Processing Standards |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, certificate authority. Contains security framework guidance for authentication systems. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_00030", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SA-11(01) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control SA-11(01): DEVELOPER TESTING AND EVALUATION | STATIC CODE ANALYSIS POTENTIAL ASSESSMENT METHODS AND OBJECTS:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00031", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IA-02(10) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control IA-02(10): a single sign-on capability is provided for <IA-02(10)_ODP system accounts and services>. POTENTIAL ASSESSMENT METHODS AND OBJECTS:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00032", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendations for Federal Vulnerability Disclosure Guidelines say about Abstract? According to Recommendations for Federal Vulnerability Disclosure Guidelines, Abstract: Receiving 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendations for Federal Vulnerability Disclosure Guidelines."}]}
{"id": "nist_00033", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Identity and Access Management for Electric Utilities say about Java Application? (Part 75) According to Identity and Access Management for Electric Utilities, Java Application: agement for Electric Utilities 247 Figure 13-6 Ozone Import Group from Directory T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 Select the Schedule, Publication Points, and Distribution Points, as shown in Figure 13-7. . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . NIST SP 1800-2C: Identity and Access Management for Electric Utilities 248 Figure 13-7 Ozone New Proof Information T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 Click the Administrators tab, as shown in Figure 13-8. Click the Add Administrators button. Select the users who will administer the proof. Select Add Entities. . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . NIST SP 1800-2C: Identity and Access Management for Electric Utilities 249 Figure 13-8 Ozone New Proof Administrators T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . Click Save. Create the Ozone Server Configuration: Select Configuration > Ozone Server > New\u2026. Click Add proof from tree\u2026. Select a proof that the Ozone Server should use for authorizations, as shown in Figure 13-9. . NIST SP 1800-2C: Identity and Access Management for Electric Utilities 250 Figure 13-9 Ozone Peer Proofs T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . Set the number of proof references (depth) that the proof may follow to authorize a credential, as shown in Figure 13-10. Ensure that the locations where the Ozone Server will retrieve the proof are correct. .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_00034", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)? (Part 164) Control PD-12: | [FIPS 201-2], Section 4.3.1 - Activation by Cardholder | | IAT = Processes | IAT = Processes | IAT = Processes | IAT = Processes | |--------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| | Authorization Focus Area | Identifier | Issuer Control | Source | | | AI-6 | The PIV Card is valid for no more than six years.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_00035", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is This publication is available free of charge from according to Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security? This publication is available free of charge from: ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security."}]}
{"id": "nist_00036", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DS-3 in Cryptographic Key Management Workshop Summary -- June 8-9, 2009? (Part 7) Control DS-3: , is needed; a collection of generic building blocks of security that can be integrated into a system and methods to analyze the resulting system are needed in creating a good key management platform. ## 2.1.8 Future Key Management Methods: David McGrew, Cisco - The focus of the talk was from a manufacturer's perspective and included the challenges of the equipment distribution problem and creating a manufacturer's device certificates. A manufacturer often ships devices to customers with a hardwired private key, device certificate, and device identifier. This would give the capability for devices to authenticate each other from a distance, but would not solve the authorization problem. - Threshold cryptography was discussed (i.e., M out of N keys must be available to perform an operation), as well as manufacturing certificates, automating manual key distribution, and a symmetric key generation system. - Threshold cryptography is useful for encrypted data storage access (e.g., a minimum number of people must cooperate in order to retrieve sensitive, stored information. - There is a problem with replacing the keys and updating revocation lists. We need to be able to streamline the distribution process and replace manual key distribution with a minimal impact process. - We need an automated CKM system that can be implemented in existing systems. - Requirements include: the authenticated/authorized distribution of keys, keys must persist over a long term, a system that replaces/updates keys when needed, key creation should not be centralized, minimal operational impact, and the CKM should be interoperable with Multipoint Key Distribution (MKD). Candidates for this type of KM system would be Kerberos (for session keys), OASIS (for storage keys) or GDOI (for group key management).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, key management. Contains security framework guidance for authentication systems. Source: Cryptographic Key Management Workshop Summary -- June 8-9, 2009."}]}
{"id": "nist_00037", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? (Part 81) Control HA-1: stablishes trust relationships, either mutual or unilateral as required, between the users and providers. Note that CIA service does not make any authorization decisions for the providers. It is left to the providers themselves to make their authorization decisions based on the provided authentication information. CIA is not necessary if two parties can mutual authenticate each other by other means, for example, through the portal login authentication of a trusted portal. No matter whether it works implicitly or explicitly, the CIA service is designed to address the trust bootstrap problem in an XPOLA-enabled Grid community. To make it better understood, let's walk through one of the use scenarios as a provider, X , of service A , and a service A 's user, Y . Suppose X first creates the service A on a remote host. Upon being created, the service A registers itself to a persistent registry. The provider then wants to distribute the service to other people including the user Y . Through a Capman service, he generates a set of capability tokens which contain detailed authorization policy and protected by X 's signature. We will dissect the capability token later, but here we just need to know that the identity of Y is included in the policy as one of the users. Now X advertises his service to Y , who will to use A . When Y tries to access A , his token agent contacts the Capman service for the required capability token. If available, the token is fetched and sent along with the service request to A , where the capability is to be verified. Thus the user Y is served by A , if the request matches what the capability allows. ## 3.2 Attack Analysis Figure 3 can be simplified as Figure 4 to reflect the trust relationships between the main entities, namely the capability authority, the clients, the service instances, and an optional CIA service.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_00038", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Version according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case, Version: | Version | Date | Description | Author | |-----------|------------|------------------------------------|------------| | 1 | 02-22-2018 | Initial Draft | Supervisor | | 2 | 04-21-2018 | Major changes to the initial draft | Supervisor |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case."}]}
{"id": "nist_00039", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Cloud Computing Forensic Science Challenges say about Table 1: Cloud forensic challenges? (Part 45) According to NIST Cloud Computing Forensic Science Challenges, Table 1: Cloud forensic challenges: ction | Jurisdiction | Many cloud systems operate in multiple countries and regions, and each jurisdiction has specific legal frameworks governing the release, protection, and acceptable use of data. While various international bodies have attempted to adopt treaties for law enforcement to collect and exchange forensic data, there is no universal agreement between countries that addresses jurisdictional issues when cloud data is stored in multiple countries. | If this challenge were overcome, there would be mechanisms in place that provide agreements between jurisdictions, thereby empowering investigators and law enforcement officers to obtain necessary data pertaining to their investigations.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Cloud Computing Forensic Science Challenges."}]}
{"id": "nist_00040", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Cryptographic Standards and Guidelines Development Process say about Federal Stakeholders? (Part 3) According to NIST Cryptographic Standards and Guidelines Development Process, Federal Stakeholders: ort, and to assure that NIST's standards and guidelines are complementary and compatible with those employed for the protection of national security systems and information contained in those systems. Beyond this statutory requirement calling for NIST to consult with other agencies, the NSA, in particular, has significant expertise in cryptography. Their cooperation with NIST is governed by an MOU between the two agencies and technical staff meet monthly to discuss ongoing collaborative work and future priorities. As part of NSA and other agencies' collaboration with NIST, their staff may assist in the development of new standards and guidelines. This may take the form of coauthoring publications with NIST staff, providing comments on draft documents, or submitting cryptographic algorithms for consideration by NIST. All contributions that significantly affect the content of any standard or guideline - particularly normative statements - will be clearly and publicly acknowledged. In accordance with NIST's authorship policy, NIST will identify the names of any authors of standards or guidelines. If a NIST standard or guideline contains an algorithm that was designed by another agency's employees, NIST will acknowledge that agency as the designer, even though NIST may not be able to list specific individuals. 2 As is the case with private sector organizations, NIST will consider and acknowledge other agencies' comments, whether they are provided during the formal public comment period or other stages of development. That includes information that may be provided during monthly NIST meetings 2 The names of some NSA staff cannot, by law, be publicly revealed. 50 U.S.C. \u00a7402 note. Freedom of Information Act (FOIA) requests for documents involving any NIST-NSA collaboration are normally reviewed by both organizations and exempted or excluded information, which may include the names of specific NSA participants as noted, may be redacted. NISTIR 7977 with NSA.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Cryptographic Standards and Guidelines Development Process."}]}
{"id": "nist_00041", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance say about IoT Device Use Risk Descriptors:? According to Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance, IoT Device Use Risk Descriptors:: - Non-Critical: Devices the customer may regularly use but does not rely upon. Loss of functionality for short periods has minimal impact on the customer organization's operations. The device does not collect any sensitive data. These devices do not introduce significant risk to systems and/or data beyond being a connected product. - Environment: Devices that can have an impact on the physical environment in which the equipment is used but do not pose physical safety risks. These devices are not relied upon for accomplishing core mission functions. The impact on the physical environment introduces additional risk for customer organizations. - Mission/Operation: Devices that the customer relies on for their operations and interference with function or unauthorized data disclosure can introduce significant risk for the customer organization. - Safety: Devices that can impact safety, which can introduce significant risk for the customer organization.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance."}]}
{"id": "nist_00042", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IA-4 in IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog? (Part 14) Control IA-4: (e.g., service-oriented architectures) that rely on: - a. run-time access control decisions facilitated by dynamic privilege management. - b. organizationally-defined actions to access/use device. 8. Ability to allow information sharing capabilities based upon the type and/or role of user attempting to share the information. 9. Ability to restrict access to IoT device software, hardware, and data based on user account roles, used with proper authentication of the identity of the user to determine type of authorization. ## (LDU) Limitations on Device Usage Description: Ability to establish restrictions for how the device can be used. Discussion: Aspects of how the IoT device can be used by internal and external users may have to be limited by the organization to comply with security and organizational requirements. In some instances, limitations may have to apply to all who interact with the device, but in others the limitation may change based on various factors. ## Related SP 800-53 Rev. 5 Controls: AC-10, AC-21(2) Requirements that may be necessary: 1. Ability to establish pre-defined restrictions for information searches within the device. 2. Ability to establish limits on authorized concurrent device sessions for: - a. User accounts - b. Roles - c. Groups - d. Dates - e. Times - f. Locations - g. Manufacturer established parameters ## (XCN) External Connections Description: Ability to support external connections. Discussion: Complexities of how system resources are distributed and managed by organizations may require them to securely make external connections to comply with and support security controls. Related SP 800-53 Rev. 5 Controls: AC-10, AC-20(1), AC-21, SC-8 Requirements that may be necessary: 1. Ability to securely interact with authorized external, third-party systems. 2.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog."}]}
{"id": "nist_00043", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Codes for Identification of Federal and Federally-Assisted Organizations say about 5600 Central Intelligence Agency? (Part 5) According to Codes for Identification of Federal and Federally-Assisted Organizations, 5600 Central Intelligence Agency: 3L | Center for Air Force History | | 573M | Air Force Elements, U.S. Southern Command | | 573N | Air Force Elements, U.S. Atlantic Command | | 573O | Air Force Elements, U.S. Pacific Command | | 573Q | Air Force Elements, U.S. Strategic Command | | 573R | Air Force Elements, U.S. Readiness Command | | 573S | Headquarters, U.S. Space Command and NORAD | | 573T | Air Force Elements U.S. Transportation Command | | 573V | Air Force Elements, Other than Europe | | 573W | Air Force Center for Environmental Excellence | | 573Y | Air Force Frequency Management Center | | 573Z | Joint Services Survival, Evasion, Resistance and Escape Agency | | 574Z | Air National Guard | | 57NG | Air National Guard Units (Title 32) | | 57ZG | U.S. Special Operations Command (ANG Title 32) | | 57ZS | U.S.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Codes for Identification of Federal and Federally-Assisted Organizations."}]}
{"id": "nist_00044", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.2.3 Identify the Objectives according to NIST Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities According to Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities, 5.2.3 Identify the Objectives: The objectives of any functional exercise should be validating the content of the IT plan, validating participants' roles and responsibilities as documented in the plan, validating the interdependencies documented in the plan, and providing an opportunity for participants to get hands-on practice in executing their functions. An additional objective for some exercises is meeting regulatory and other such requirements associated with exercising plans, such as the requirement in NIST SP 800-53 for Federal agencies to conduct exercises or tests for their systems' contingency plans at least annually. Specific objectives should be documented and clearly articulated to exercise participants.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities."}]}
{"id": "nist_00045", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is one of the following PARAMETER VALUES is selected according to Assessing Security and Privacy Controls in Information Systems and Organizations? one of the following PARAMETER VALUES is selected: {real-\ue000me; near real-\ue000me};", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00046", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PM-8200 in Cell Phone Forensic Tools_ an Overview and Analysis Update? (Part 73) Control PM-8200: More information can be found in Appendix B: Device Seizure Results.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis Update."}]}
{"id": "nist_00047", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about Determine if:? According to Assessing Security Requirements for Controlled Unclassified Information, Determine if:: A.03.17.03.ODP[01]: security requirements to protect against supply chain risks to the system, system components, or system services and to limit the harm or consequences from supply chain-related events are defined . A.03.17.03.a[01]: a process for identifying weaknesses or deficiencies in the supply chain elements and processes is established. A.03.17.03.a[02]: a process for addressing weaknesses or deficiencies in the supply chain elements and processes is established. A.03.17.03.b: the following security requirements are enforced to protect against supply chain risks to the system, system components, or system services and to limit the harm or consequences of supply chain-related events: &lt;A.03.17.03.ODP[01]: security requirements&gt; .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00048", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 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 say about A . Government: Rights of Data Subjects? (Part 1) 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 , A . Government: Rights of Data Subjects: A . Government: Rights of Data Subjects - 1 . The Fifth and Fourteenth Amendments to the Constitution prohibit Federal and State and local governments from depriving a person of \"life, liberty, or property\" without \"due process of law.\" The procedures required by the courts in applying this principle are designed to assure that the individual has a reasonable opportunity to challenge the proposed deprivation. At a minimum, there must be notice and a hearing at which the factual basis of the decision is subject to scrutiny. See Mullane v. Central Hanover Bank &amp; Trust Co., 337 U.S. 306, 314 (1950); Greene v. McElroy, 360 U.S. 474, 496-497 (1959); Goldberg v. Kelly, 397 U.S. 254, 269-271 (1970). 2. The Administrative Procedure Act sets out detailed procedures for Federal agencies' conduct of administrative hearings required by the Constitution or by statute. The Act's provisions prescribe, for example, how notice is to be given and how evidence may be collected, presented, and evaluated. 5 U.S.C. \u00a7\u00a7 551, 554-558. 3. The Privacy Act requires agencies, on request, to provide individuals with access to records pertaining to them and an opportunity to correct or challenge the contents of the records. 5 U.S.C. \u00a7 552a. 4. The Freedom of Information Act provides individuals with access to many types of records that are exempt from access under the Privacy Act, including many categories of personal information. 5 U.S.C. 552. - \u00a7 5. Most of the State fair information practice statutes allow individuals to inspect and challenge information about them held by the State; many also require some type of registry or inventory of State-maintained data bases. See . e . q . Va. Code \u00a7 2.1-377; Mass. Gen. Laws ch. 66A; Ark. Stat. \u00a7 16-804; Cal. Civ. Code \u00a7 1798; Colo. Rev. Stat. \u00a7\u00a7 24-72-204 (3 )( a) , 24-90-119; Conn. Gen. Stat. \u00a7 4-190; 111. Stat. ch. 116 \u00a7 43.5; Ind. Code \u00a7\u00a7 5-14-3-1, 4-1-6-3; Ky. Rev. Stat. \u00a7 61.884; Mo. Stat. \u00a7 182.817; Nev. Rev. Stat. \u00a7 229.013; N.Y. Pub.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. 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 ."}]}
{"id": "nist_00049", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does IT Asset Management say about 4.6.2.1 INSTALL ACTIVE DIRECTORY CERTIFICATE SERVICES (AD CS)? According to IT Asset Management, 4.6.2.1 INSTALL ACTIVE DIRECTORY CERTIFICATE SERVICES (AD CS): 1. Go to Server Manager and click Add Roles and Features Wizard . 2. Click Next . Select Role-based or feature-based installation . Click Next . 3. Select your server on the next screen and click Next . 4. Select the Active Directory Certificate Services and Add Features when prompted. 5. Click Next when you see .NET 4.5 framework and other default selections. 6. Click Next on informational screens. 7. On the Role Services for AD CS , select all checkboxes and click Next . 8. When you are prompted to install the IIS web service, click Install . 9. Click Close when the installation completes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IT Asset Management."}]}
{"id": "nist_00050", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does User's Guide to Telework and Bring Your Own Device (BYOD) Security say about User's Guide to Telework and Bring Your Own Device (BYOD) Security? According to User's Guide to Telework and Bring Your Own Device (BYOD) Security, User's Guide to Telework and Bring Your Own Device (BYOD) Security: Murugiah Souppaya Computer Security Division Information Technology Laboratory Karen Scarfone Scarfone Cybersecurity Clifton, VA This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800-114r1 July 2016 <!-- image --> U.S. Department of Commerce Penny Pritzker, Secretary National Institute of Standards and Technology", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: User's Guide to Telework and Bring Your Own Device (BYOD) Security."}]}
{"id": "nist_00051", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for the Secure Deployment of IPv6 provide? (Section 321) ions and accreditations; with a dual stack environment only a single certification and accreditation may be required. The goal should be to achieve security as good as or better than the IPv4 network. The operations phase often begins concurrently with the implementation phase. During operations, the focus is the secure operation of a dual stack or mixed IPv6/IPv4 environment. One of the most difficult challenges facing the operations staff in a mixed IPv6/IPv4 environment is keeping the two environments synchronized. When operations makes changes to security controls such as firewall rule sets, access control lists, and IDS signatures, they must ensure the change occurs on both the IPv4 and IPv6 networks. Rules and signatures must be translated between IPv4 and IPv6 syntax and deployed as a single coordinated process. If strict change control is not followed, the two environments will have non-overlapping protections. In a dual stack environment, the physical topologies of the equipment are the same, but the logical topologies can be very different. Configuration changes can have unpredictable or unforeseen consequences. Configuration management controls should be structured to prevent configuration changes on IPv4 or IPv6 networks that affect the other network. Organizations should manage and monitor their IPv4, IPv6, and dual stack environment as a single environment. A migration from IPv4 to IPv6 results in displacement or retirement of equipment. Some equipment does not support IPv6 and is retired, while other equipment is transferred to IPv4 islands or to other organizations. Organizations must plan for the secure disposition of this obsolete equipment, ensuring that no confidential data is released. Organizations place themselves at great risk for exposing confidential information when disposing of obsolete equipment. A key decision concerning sanitization is whether the equipment is planned for reuse or retirement.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_00052", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Electronic Health Records on Mobile Devices say about puppet will install here? (Part 98) According to Securing Electronic Health Records on Mobile Devices, puppet will install here: onic Health Records on Mobile Devices 17 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P . 1 8 0 0 - 1 . NIST Cybersecurity Framework v1.1 Sector-Specific Standards & Best Practices Security Characteristics Function Category Subcategory Person or entity authentication Protect (PR) Identity Management, Authentication and Access Control (PR.AC) PR.AC-1: Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users and processes PR.AC-3: Remote access is managed NIST SP80 0-53 Rev 4 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 AC-1, AC-17, AC-19, AC-20, SC-15 IEC/ISO27002 20 Critical Security Controls 8.3.3, 11.2.1, 11.2.2, 11.2.4, 15.2.1, 11.4.3 CSC-5, CSC-9, CSC-11 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.2.2, 9.2.3, 10.6.1, 11.2.1, 11.2.2, 11.2.4, 11.3.2, 11.4.4 HIPAA Security Rule [2] 45 C.F.R. \u00a7\u00a7 164.308(a)(3)(ii)(B), 164.308(a)(3)(ii)(C), 164.308(a)(4)(i), 164.308(a)(4)(ii)(B), 164.308(a)(4)(ii)(C), 164.312(a)(2)(i), 164.312(a)(2)(ii), 164.312(a)(2)(iii), 164.312(d) 45 C.F.R. \u00a7\u00a7 164.308(a)(4)(i), 164.308(b)(1), 164.308(b)(3), 164.310(b), 164.312(e)(1), 164.312(e)(2)(ii) NIST SP 1800-1D: Securing Electronic Health Records on Mobile Devices 18 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P . 1 8 0 0 - 1 .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, identity management. Contains security framework guidance for authentication systems. Source: Securing Electronic Health Records on Mobile Devices."}]}
{"id": "nist_00053", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to Security and Privacy Controls for Information Systems and Organizations? Discussion: Remote access is access to organizational systems (or processes acting on behalf of", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00054", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Threshold Schemes for Cryptographic Primitives_ Challenges and Opportunities in Standardization and Validation of Threshold Cryptography say about 4.2 Types of attack? (Part 3) According to Threshold Schemes for Cryptographic Primitives_ Challenges and Opportunities in Standardization and Validation of Threshold Cryptography, 4.2 Types of attack: nto particular zones of a circuit (which requires close proximity), to change an internal state (e.g., a lock bit [AK96]) and thereby inducing a change of behavior. Conventional vs. threshold-related. While threshold schemes may be designed to mitigate the effectiveness of some attacks on conventional applications, the actual implementation of a threshold design may be the cause of new inherent vulnerabilities. For example, an attack may be able to exploit some vulnerability in the communication network that intermediates several nodes, where such a network would not even exist in a conventional implementation. We characterize an attack as threshold-related if the attack vector is inherently allowed by the threshold design. Complementary, there are conventional attacks that can be considered similarly with respect to each component of a threshold scheme. In the latter case, it is still relevant to consider, for example, if an attacker is able to choose whether to attack the nodes/platform in parallel or sequentially. Tolerance to compromise can be useful even in scenarios of non-intentional adversaries. For example, some systems may be constrained to satisfy auditability requirements that warrant taking down components for audit. If a service is supported on a multi-party threshold scheme with tolerance to compromise, then the audit of components can be done without affecting the overall availability.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit, attack vector. Contains technical security guidance that could inform defensive posture. Source: Threshold Schemes for Cryptographic Primitives_ Challenges and Opportunities in Standardization and Validation of Threshold Cryptography."}]}
{"id": "nist_00055", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management provide? (Section 65) and outbound remote connections are encrypted. \u2022 Laptops with proprietary facility information do not have full-disk encryption. \u2022 Email systems are configured to provide limited data loss prevention. | \u2022 External adversary (who has gained network access may quickly recognize and exfiltrate unencrypted, sensitive information in databases or within cleartext network traffic) \u2022 Internal user (may unintentionally send sensitive records without encryption, while data loss prevention tools might impede that error) | | DE.CM | Security Continuous Monitoring | \u2022 Physical security is monitored through cameras and access log reviews. \u2022 Information security logs are aggregated and stored securely. \u2022 Intrusion Detection products monitor for risks. | \u2022 Internal User (steals valuable equipment due to a lack of diligent video and log monitoring) \u2022 External User (is not quickly detected and thwarted due to ineffective monitoring) | | RS.RP | Response Planning | \u2022 Response processes and procedures are executed and maintained. \u2022 Supply chain partners have not been included in planning or exercises. | \u2022 Supply Chain Partner (is not able to provide the Security Operations Center with system log information and is unable to restore data to a known-good recovery point) | | RC.RP | Recovery Planning | \u2022 Incident recovery processes are included in response plans.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: adversary, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management."}]}
{"id": "nist_00056", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers say about 2.1 StrongKey CryptoEngine FIDO U2F Server? According to Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers, 2.1 StrongKey CryptoEngine FIDO U2F Server: This section of the guide provides installation and configuration guidance for the SKCE, which provides FIDO authentication services.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_00057", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Derived PIV Application and Data Model Test Guidelines say about 7.3.1 X.509 Certificate for Derived PIV Authentication? (Part 2) According to Derived PIV Application and Data Model Test Guidelines, 7.3.1 X.509 Certificate for Derived PIV Authentication: | | 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). | \u2022 [PROF], Worksheet titled - Derived PIV Authentication Certificate Profile | | DTR-07.03.01.05 | The keyUsage extension shall assert only the digitalSignature bit. No other bits shall be asserted. | \u2022 [PROF], Worksheet titled - Derived PIV Authentication Certificate Profile | | DTR-07.03.01.06 | The policyIdentifier field in the certificatePolicies must assert id-fpki- | \u2022 [PROF], Worksheet titled - Derived PIV | | DTR No: | DTR Description | Spec.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_00058", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Report on the Privilege (Access) Management Workshop provide? (Section 46) formation Security and Privacy Series, Second Edition, ISBN 13: 9789-1-59693-113-8, ARTECH HOUSE, INC., 68 Canton Street, Norwood, Massachusetts 02062. - [FERR-07b] Ferraiolo, D. F., V. Atluri, and S. Gavrila, 2007, The Policy Machine: A StandardsDriven Enterprise-Wide Access Control Enforcement Mechanism , pages 87-92, Defense Standardization Program Journal, Defense Standardization Program Office, 8725 John J. Klingman Road, Stop 6233, Fort Belvoir, VA 22060-6221. - [FICAM-09] Identity, Credential, and Access Management (ICAM) Subcommittee, June 15, 2009, Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance , DRAFT Version 0.2, Federal Information Security &amp; Identity Management Committee (ISIMC). - [GREG-07] Gregory, M., March 14, 2007, A Mechanism for Risk Adaptive Access Control (RAdAC) , Presentation in PDF format, National Information Assurance Research Laboratory (NIARL). - [HENG-05] Hengartner, U., 2005, Access Control to Information in Pervasive Computing Environments , ADA457117, DoD-XA. - [HU-01] Hu, V., D. A. Frincke, and D. F. Ferraiolo, 2001, The Policy Machine for Security Policy Management , pages 494-503, Computational Science -- ICCS 2001, ISBN 3-54042233-1, Springer-Verlag Berlin, Heidelberg, New York. - [ILLI-07] Illinois University, June 1, 2007, PolicyMorph: Interactive Policy Transformations for a Logical Attribute-Based Access Control Framework , ADA482461, Illinois University at Urbana-Champaign, Department of Computer Science. - [McGR-UN] McGraw, R. W., undated, Risk-Adaptable Access Control (RAdAC) , Presentation in PDF format, publisher not indicated; available 12-9-2009 at - [McGR-09] McGraw, R. W., September 2009, Risk Adaptable Access Control (RAdAC) , Presentation in PDF format, Information Assurance Architecture and Systems Security Engineering Group, National Security Agency, Ft. Meade, Maryland.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, identity management. Contains security framework guidance for authentication systems. Source: A Report on the Privilege (Access) Management Workshop."}]}
{"id": "nist_00059", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-512 in Computer Security Division 2009 Annual Report? (Part 54) Control HA-512: ludes several proof-ofconcept implementations of security mechanisms suited for the capabilities and limitations of such devices. Detailed descriptions can be found on the project website (see below). This past year we published an additional conference paper on the design and implementation of an authentication mechanism that uses wireless security beacons to provide location data and control device behavior. We also finalized NIST SP 800-124, Guidelines on Cell Phone and PDA Security . This publication provides an overview of security issues with mobile devices and offers insights into making informed security decisions. It includes details about the threats and technology risks involved and the available safeguards to mitigate them. Users of cell phones and other business-oriented mobile devices, as well as security professionals and officials responsible for information technology security in government and elsewhere, should find the information useful. Prior work at NIST in the mobile device forensics area examined the quality and use of forensic tools and identified ways to remove impediments to the practice of cell phone forensics. During FY2009, our work has progressed along both fronts. We improved our methodology for validating the correct functioning of forensic tools quickly and accurately. The approach, called identity module programming, automatically populates devices with reference test data that serves as baseline reference material for validating the correct functioning of related forensic tools. An application and set of reference test data was developed that illustrates the methodology for identity modules of certain classes of cell phones. The distribution package can be found at the project website.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2009 Annual Report."}]}
{"id": "nist_00060", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Digital Identity Guidelines_ Federation and Assertions provide? (Section 193) that they expect to be in the transaction with in the first place. Different techniques provide different degrees of assurance, depending on the federation protocol in use and the needs of the system. For example, the Authorization Code Flow of [OIDC] allows the RP to register a shared secret or private key with the IdP prior to the transaction, allowing the IdP to strongly authenticate the RP's request in the back channel to retrieve the assertion. In addition, the Proof Key for Code Exchange protocol in [RFC7636] allows the RP to dynamically create an unguessable secret that is transmitted in hashed form in the front channel and then transmitted in full in the back channel along with the assertion reference. These techniques can be combined for even greater assurance. Federation authorities can also facilitate the authentication process. If the RP registers its public key and identifier with the federation authority, the IdP only needs to retrieve the appropriate verification keys from the federation authority instead of requiring the RP to register itself ahead of time. Technical profiles of specific federation protocols are out of the scope of these guidelines, but high-security profiles such as [FAPI] provide extensive guidelines for implementers to deploy secure federation protocols. - 9.13. Cloud Wallet An agency's CSP allows its subscribers to issue attribute bundles to a cloud-hosted wallet service. In this scenario, the CSP onboards the cloud wallet service on behalf of the subscriber through a dedicated onboarding process. The subscriber authenticates to the cloud wallet and initiates the onboarding process of the cloud wallet at the CSP. The subscriber authenticates to the CSP and authorizes the issuance of attribute bundles to the cloud wallet. The CSP generates and delivers these attribute bundles to the cloud wallet, the cloud wallet stores the attribute bundles on behalf of the subscriber.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Digital Identity Guidelines_ Federation and Assertions."}]}
{"id": "nist_00061", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS) say about SOME THOUGHTS ON DATA INTEGRITY? According to Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS), SOME THOUGHTS ON DATA INTEGRITY: Data can be said to have integrity when it is as good as we think it is. [Courtney] That is to say, when it agrees with our expectation. Data can be said to have integrity when it agrees with that which it intends to describe. For example, inventory data can be said to have integrity when it tells us accurately and completely just what quantity of which items we have. Of course, it never does that, but as long as it does it well enough to support the decisions that we want to make, then it is probably good enough.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)."}]}
{"id": "nist_00062", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Privacy Controls for Information Systems and Organizations provide? (Section 268) s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ may need to be taken offline, or replicated to the extent feasible, before testing can be conducted. If systems must be taken offline for testing, the tests are scheduled to occur during planned system outages whenever possible. If the testing cannot be conducted on operational systems, organizations employ compensating controls. Related Controls: None. (3) CONFIGURATION CHANGE CONTROL | AUTOMATED CHANGE IMPLEMENTATION Implement changes to the current system baseline and deploy the updated baseline across the installed base using [Assignment: organization-defined automated mechanisms]. Discussion: Automated tools can improve the accuracy, consistency, and availability of configuration baseline information. Automation can also provide data aggregation and data correlation capabilities, alerting mechanisms, and dashboards to support risk-based decision-making within the organization. Related Controls: None. (4) CONFIGURATION CHANGE CONTROL | SECURITY AND PRIVACY REPRESENTATIVES Require [Assignment: organization-defined security and privacy representatives] to be members of the [Assignment: organization-defined configuration change control element]. Discussion: Information security and privacy representatives include system security officers, senior agency information security officers, senior agency officials for privacy, or system privacy officers.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00063", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does U.S. Department of Energy Risk Assessment Methodology say about DEPARTMENT OF ENERGY ADP SYSTEM RISK ASSESSMENT? (Part 9) According to U.S. Department of Energy Risk Assessment Methodology, DEPARTMENT OF ENERGY ADP SYSTEM RISK ASSESSMENT: ^/ yj V yj 4 4 | | INTENTIONAL HUMAN THREATS: | INTENTIONAL HUMAN THREATS: | INTENTIONAL HUMAN THREATS: | INTENTIONAL HUMAN THREATS: | INTENTIONAL HUMAN THREATS: | | TERRORIST INCIDENT BOMBING RIOT/CIVIL DISORDER STRIKES kTONARRfl^ ASSAULT | V V V *T < | \u20224 yi yj V V | V r * V | 4 4 4 4 V 4 | | UNINTENTIONAL HUMAW THREATEs | UNINTENTIONAL HUMAW THREATEs | UNINTENTIONAL HUMAW THREATEs | UNINTENTIONAL HUMAW THREATEs | UNINTENTIONAL HUMAW THREATEs | | ACCIDENTS OPERATIONAUPROCEDURAL ERRORS EMOTIONAL MENTAL HEALTH PROBLEMS | | V | >/ V | , v , X3l | | HEATINQCOOUNG SYSTEM FAILURE POWER OUTAGE structural FAILUR8 | | >/ | | 4 | <!-- image --> | DEPARTMENT OP ENERGY ADP SYSTEM RISK ASSESSMENT | THREATS TO AND VULNERABILITIES INFORMATION, AND (DATA) | OP DATA, EMISSIONS | STEP 4 RESOURCE TABLE R4.3a | |----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|----------------------|-------------------------------| | INFORMATION AND DATA DAMAGE | DESTRUCTION | DISCLOSURE | DENIAL | | NATURAL THREATS; .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: U.S. Department of Energy Risk Assessment Methodology."}]}
{"id": "nist_00064", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to Computer Security Division 2011 Annual Report? http: //csrc.nist.gov/publications/PubsSPs.html Contacts:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2011 Annual Report."}]}
{"id": "nist_00065", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography say about 7.2.1.3 RSASVE Recovery Operation (RSASVE.RECOVER)? According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography, 7.2.1.3 RSASVE Recovery Operation (RSASVE.RECOVER): RSASVE.RECOVER recovers a secret value from ciphertext using an RSA private key. Once recovered, the secret value is considered to be a shared secret.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography."}]}
{"id": "nist_00066", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case say about 4.3.5.4 Additional Information? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case, 4.3.5.4 Additional Information: Video tutorials 58 are available on the CSET YouTube Channel to help you better understand how to use this tool.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case."}]}
{"id": "nist_00067", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CP-02(04) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control CP-02(04): CONTINGENCY PLAN | RESUME ALL MISSION AND BUSINESS FUNCTIONS [WITHDRAWN: Incorporated into CP-02(03).]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00068", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain APPENDIX E: COMPUTER SECURITY AREA AND SOW-SPECIFIC REFERENCES according to NIST Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out According to Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out, APPENDIX E: COMPUTER SECURITY AREA AND SOW-SPECIFIC REFERENCES: The following are federal requirements or guidance used as references for each SOW. These are the basic references used to ensure that the tasks conducted, recommendations made, and products delivered are consistent with government requirements. These references are not intended to be all inclusive. Individual organization computer security directives should be identified, added to a SOW, and complied with, where applicable. For a description of many of the references listed below, please see Appendix A. See note at the end of this section regarding definition and usage of computer security terms. The following abbreviations are used: - o FIPS PUB - Federal Information Processing Standards Publication - o NBS - National Bureau of Standards - o NBSIR - National Bureau of Standards Information Report - o NCSC - National Computer Security Center - o (N)CSL - (National) Computer Systems Laboratory - o NIST - National Institute of Standards and Technology - o NISTIR - National Institute of Standards and Technology Information/Internal Report - o NIST SP NIST Special Publication - o OMB - Office of Management and Budget - o OPM - Office of Personnel Management - o PCMI - Presidents Council on Management Improvement", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out."}]}
{"id": "nist_00069", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure provide? (Section 152) ---------------------------------------------------------------------------------------------------------------------------------------| | DS-4: Adequate capacity to ensure availability is maintained. | Ecosystem: Measures to augment capacity may include: \u2022 Formal procedures and activities to monitor system performance \u2022 Redundant transmission systems \u2022 Alternate transmission systems (such as radio frequency (RF), wired or optical systems) Methods such as load balancing address abnormal server loads due to elevated traffic from user activity, incorrect server configurations, or cybersecurity events. | [NIST-SP800-53r5] AU-4, CP-2, CP-6, CP-7, PE-11, SC-5 [NIST-SP800-160V1] Appendix F.4 IEC62439-3 4, 5, Appendix P.2.3, 4.6, 4.8, 4.9, 4.12, 4.13 NERC CIP 009-6-R1 | | DS-4 | EV | This may include availability of the EV infrastructure that manages networks, processing, and storage capacities. | [NIST-SP800-53r5] CP-2, CP-6, CP-7 [NIST-SP800-160V1] Appendix F.4 | | DS-4 | XFC/EVSE | This may include availability of the XFC/EVSE charging network, supporting processes for charging, and information from EV owners, EV/XFC partners, and suppliers/vendors. | [NIST Handbook 44] 3.40 S.3.4 (c) ISA/IEC 62443-3- 3:2013 SR 7.1, SR 7.2 OIML G22:2022 4.4.9.2.2 OIML D31:2019 | | DS-4 | Cloud/Third-Party | This may include information from EV owners, EV/XFC partners, customers, and cloud and payment processing vendors. Cloud and third-party system providers may consider implementing high-availability networks with the required redundancy of gateways, servers, etc.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure."}]}
{"id": "nist_00070", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers provide? (Section 101) [5] FIDO Alliance. (n.d.). FIDO\u00ae Certified [Online]. Available: https://fidoalliance.org/certification/fido-certified-products/. - [6] Splunk Inc. (n.d.). [Online]. Available: https://www.splunk.com/. - [7] International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC). (Oct. 2013). ISO/IEC 27001:2013: Information technology-Security techniquesInformation security management systems-Requirements [Online]. Available: - [8] National Institute of Standards and Technology (NIST). (Apr. 16, 2018). NIST Cybersecurity Framework, Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1 [Online]. Available: - [9] NIST Special Publication (SP) 800-30 Rev. 1, Guide for Conducting Risk Assessments. (Sept. 2012). [Online]. Available: - [10] NIST SP 800-37 Rev. 1, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach. (June 5, 2014). [Online]. Available: - [11] NIST SP 800-53 Rev. 4, Security and Privacy Controls for Federal Information Systems and Organizations. (Apr. 2013). [Online]. Available: - [12] NIST SP 800-63-3, Digital Identity Guidelines. (June 2017). [Online]. Available: https://pages.nist.gov/800-63-3/. - [13] NIST SP 800-63A, Digital Identity Guidelines, Enrollment and Identity Proofing. (June 2017). [Online]. Available: https://pages.nist.gov/800-63-3/. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ - [14] NIST SP 800-63B, Digital Identity Guidelines, Authentication and Lifecycle Management. (June 2017). [Online].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, risk management framework. General security reference material without sensitive content. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_00071", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain C O M P U T E R S E C U R I T Y according to NIST Personal Identity Verification Demonstration Summary According to Personal Identity Verification Demonstration Summary, C O M P U T E R S E C U R I T Y: Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD, 20899-8940 August 2006 <!-- image --> U.S. Department of Commerce Carlos M. Gutierrez, Secretary National Institute of Standards and Technology William A. Jeffrey, Director", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Personal Identity Verification Demonstration Summary."}]}
{"id": "nist_00072", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Section 177) | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | INTENDED EFFECT | IMPACT ON RISK | EXPECTED RESULTS | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Scrutinize Analyze threat events and artifacts associated with threat events-particularly with respect to patterns of exploiting vulnerabilities, predisposing conditions, and weaknesses-to inform more effective detection and risk response.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_00073", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Secure Data Network Systems (SDNS) Key Management Documents provide? (Section 112) an Estat KPDU to the responder, then the connection is terminated and the TEK generated is discarded by both parties. The KMASE K-TEK-ATTRIBUTES service provides the attribute negotiation activities. The K-TEK-ATTRIBUTES service verifies the cryptographic compatibility with the TEK, negotiates the communication and security attributes associated with the TEK, and exchanges Compromised Key List (CRL) numbers. Additionally, K-TEK-ATTRIBUTES allows a KMAP to associate the attributes of a previous TEK with a new TEK. The K-TEK-ATTRIBUTES parameters are illustrated in Table 1. Table 1 - K-TEK-ATTRIBUTES parameters | Parameter Name | Req | ind | rsp | cnf | |------------------|-------|----------|-------|--------| | init-kid | | | M | M( = ) | | resp-kid | M | M( = ) | | | | proposed-options | U | U( = ) | | | | selected-options | | | M | M( = ) | | add-info | U | U( = ) | U | U( = ) | | old-resp-kid | U | U{ = ) | | | | cri-ver | M | IVI( = ) | | | | result | | | M | M( = ) | Legend: blank - not applicable M - presence is mandatory U - presence is user option = - p value is semantically equal to value to its left in the table This K-TEK-ATTRIBUTES parameter is required on the response primitive. It is passed on the confirm primitive. It contains the identifier the initiator KMAP associates with the TEK. This service parameter is specified in SDN.902, and its KPDU ASN.l specification described in SDN.903. This K-TEK-ATTRIBUTES parameter is required on the request primitive, and passed on the indicate primitive. It contains the identifier the responder KMAP associates with the TEK. This service parameter is specified in SDN.902, and its KPDU ASN.l specification described in SDN.903.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_00074", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3 say about Appendix B: Existing Standards in Relation to the Security and Privacy Fabric? (Part 69) According to NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3, Appendix B: Existing Standards in Relation to the Security and Privacy Fabric: | 'Person or organization having responsibility for the development, procurement, integration, modification, operation and maintenance, and/or final disposition of an information system.' | | Technical Privacy Security Controls | CNSSI-4009 | See also Technical Reference Model adapted for Privacy | 'Security controls (i.e., safeguards or countermeasures) for an information system that are primarily implemented and executed by the information system through mechanisms contained in the hardware, software, or firmware components of the system.' | | Privacy - Threat definition, analysis, assessment, event, scenario, source | NIST SP 800-27, CNSSI-4009 | | | | Tracking cookie | NIST SP 800-83 | | | | Traffic Analysis | NIST SP 800-24, NIST SP 800-98 | Highly applicable to privacy in IoT | 'A form of passive attack in which an intruder observes information about calls (although not necessarily the contents of the messages) and makes inferences, e.g., from the source and destination numbers, or frequency and length of the messages.' | | Trusted Agent TBD | See trusted identification forwarding and related terms | Earliest or most responsible (TBD) direct digital connection to a person whose data is private | | | Term | Sources | Security and Privacy Fabric | Comments", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3."}]}
{"id": "nist_00075", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Secure Domain Name System (DNS) Deployment Guide? (Part 5) Control HA-1: ous command options (parameters) denote the following: -a option: the name of the hashing algorithm that will use the key (HMAC-SHA256 is preferred, but may not be available in older implementations. Use of HMAC-SHA1 is allowed, but migration to HMAC-SHA256 should be done when available) ``` -b option: the length of the key (here - a minimum of 112 bits) -n option: the type of key (in this case, the HOST) last parameter: the name of the key (ns1-ns2.example.com) ``` The dnssec-keygen program generates the following files, each containing the key string: ``` Kns1-ns2.example.com.+157+34567.key Kns1-ns2.example.com.+157.34567.private ``` When the program is generating a pair of keys (one public and the other private), the file with the extension key will contain the public key string and the file with extension private will contain the private key. Because in this case only the secret key is being generated, the key strings in both files will be the same for the TSIG implementation. The key string from any of these files is then copied to a file called the key file. This file is then referenced using an include statement within the key statement. ## 8.2.2 Defining the Keys in the Communicating Name Servers The key generated by using the dnssec-keygen utility has to be defined within the named.conf configuration file of the two communicating servers (generally one primary name server and one secondary name server). This is accomplished by using the key statement of BIND: ``` key 'ns1-ns2.example.com.' { algorithm hmac-sha256; include '/var/named/keys/secretkey.conf'; }; ``` where the file secretkey.conf will contain the keyword secret and the actual key string (in this example): ``` secret 'MhZQKc4TwAPkURM=='; ``` ## 8.2.3 Defining the Keys in a NSD Configuration File In NSD, declaring a TSIG key is very similar to the example above, with some minor syntax changes: ``` key: name: ns1-ns2.example.com.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Domain Name System (DNS) Deployment Guide."}]}
{"id": "nist_00076", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about Interview? According to Assessing Security Requirements for Controlled Unclassified Information, Interview: [SELECT FROM: personnel with boundary protection responsibilities; personnel with information security responsibilities; system developers; system administrators]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00077", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives provide? (Section 25) | 56 | | | A.2 | Technology lenses & adoption curve ............................................................ | 57 | | | A.3 | Win/win and production possibility frontier .................................................... | 60 | | | A.4 | Intermediation, disintermediation, classic make/buy.....................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives."}]}
{"id": "nist_00078", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Usability and Security Considerations for Public Safety Mobile Authentication provide? (Section 9) dios (LMRs) without authentication for voice communication, they should not be required to authenticate in order to use mission-critical communication services on their next-generation mobile devices. - In order to mitigate the usability issues identified, research should be prioritized by focusing on authentication methods rated as readily feasible, then by investigating other less feasible authentication methods. - Research is needed on the associated enterprise policies guiding mobile authentication implementation and deployment. For example, research on timeout policies and SSO implementation is necessary. For first responders in the field, the timeout policy would ideally be lifted, such that a single authentication event would suffice for an entire shift or incident, especially since their mobile devices would remain on their person. SSO will allow first responders to authenticate one time and receive access to multiple applications, systems, and domains within a variety of authentication mechanisms [24]. | Executive Summary..................................................................................................... iii | Executive Summary..................................................................................................... iii | Executive Summary.....................................................................................................", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Usability and Security Considerations for Public Safety Mobile Authentication."}]}
{"id": "nist_00079", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-3 in Data Integrity_ Recovering from Ransomware and Other Destructive Events? (Part 4) Control IP-3: | ## 1 Summary Businesses face a near-constant threat of destructive malware, ransomware, malicious insider activities, and even honest mistakes that can alter or destroy critical data.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Recovering from Ransomware and Other Destructive Events."}]}
{"id": "nist_00080", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Attribute-based Access Control for Microservices-based Applications using a Service Mesh provide? (Section 27) y a label that is a name/value pair. A node is a physical or virtual machine that houses a set of pods as well as the interfaces necessary to run the housed pods. The set of nodes is called a cluster. The control plane's components make global decisions about the cluster (for example, scheduling), as well as detecting and responding to cluster events (for example, starting up a new pod when workload increases). Some key control plane components include: Kubernetes API (application programming interface) server, a key/value store, a scheduler, and a set of controllers. The node controller is one such controller that manages various aspects of nodes. To ensure adequate performance and continued availability, it is imperative to have some clusterlevel mechanisms for the clusters that are configured using the hosts of the application components (i.e., microservices). Considering a scenario where the host is a node of a Kubernetes platform cluster and the application components are running inside of a container with a pod (i.e., a group of containers) as a deployment artifact, the following cluster-level mechanisms are required. For example, one of the most well-known features of Kubernetes is pod-level horizontal scaling . This means that when services receive more traffic, more instances will be generated across machines that grow or shrink on demand. Kubernetes supports auto-vertical scaling on the pod level. Thus, a cluster could be configured to scale the machine on which a pod runs up or down to more accurately fit the anticipated power needs of any microservice. For example, if certain subsets of nodes saw spikes in traffic at key times, with the right usage analysis, one could potentially reschedule those jobs across machines in order to save costs and optimize performance [7]. Similarly, Kubernetes offers features to monitor the health of the microservices (e.g., check the status and readiness).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Attribute-based Access Control for Microservices-based Applications using a Service Mesh."}]}
{"id": "nist_00081", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2014 Annual Report provide? (Section 172) t conferences and research labs; and a joint development of enhanced fault location tools with Johns Hopkins University Applied Physics Lab. http:/ /csrc.nist.gov/groups/SNS/acts/ Mr. Rick Kuhn (301) 975-3337 kuhn@nist.gov Dr. Raghu Kacker (301) 975-2109 raghu.kacker@nist.gov Modern computing devices consist of various hardware, firmware, and software components at multiple layers of abstraction. Many security and protection mechanisms are currently rooted in software that, along with all underlying components, must be trusted and not tampered with. A vulnerability in any of those components could compromise the trustworthiness of the security mechanisms that rely upon those components. Stronger security assurances may be possible by grounding security mechanisms in roots of trust. Roots of trust are highly reliable and secure hardware, firmware, and software components that perform specific, critical security functions. Because roots of trust are inherently trusted, they must be secure by their design. As such, many roots of trust are implemented in hardware or protected firmware so that malware cannot tamper with the functions they provide. Roots of trust provide a firm foundation from which to build security and trust. NIST CSD's work aims to encourage the use of roots of trust in computers to provide stronger security assurances. A focus area for this work has been securing mobile devices, using roots of trust to provide device integrity, data and application isolation, and protected storage. As part of this work, CSD is revising SP 800-164, Guidelines on HardwareRooted Security in Mobile Devices, based on the public comments that were received on the draft. A revised draft will be released in FY 2015.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, malware. Contains technical security guidance that could inform defensive posture. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_00082", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Telehealth Remote Patient Monitoring Ecosystem say about C-4 Threats? (Part 1) According to Securing Telehealth Remote Patient Monitoring Ecosystem, C-4 Threats: C-4 Threats In this practice guide, the NCCoE identified a threat taxonomy for the entire system. Threats may manifest differently to the system depending on the domain in which they appear. Environments that may have resources to maintain security tools and procedures may have mitigating circumstances that reduce the likelihood of attack and minimize impact based on pervasive controls. This practice guide considers scenarios where patient homes may have less resource and capability to minimize threats when compared with telehealth platform providers and HDOs. Also, for the purposes of this practice guide, some threats may target HDOs to a greater extent than patient homes or telehealth platform providers, given a more target-rich data set that may attract threat actors. The following tables describe events and consider the likelihood of variation based on this context. Note that the assigned values are notional. Practitioners who perform similar exercises may determine different assignments. For purposes of this exercise, likelihood is categorized using a range that extends from very low to very high, consistent with a model described in Appendix G of NIST 800-30 [9]. An abstract of the table appears below. The qualitative values from the Table C-2 describes threat likelihood. Table C-2 Assessment Scale: Likelihood of Threat Event Initiation | Qualitative Values | Frequency (derived from nonadversarial table) | Description (derived from adversarial table) | |----------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------| | very high | Error, accident, or act of nature is almost certain to occur or occurs more than 100 times per year. | Adversary is almost certain to initiate the threat event.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: threat actor, adversary. Contains technical security guidance that could inform defensive posture. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_00083", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Note according to Automation Support for Security Control Assessments_ Software Vulnerability Management? Note: Since any given vulnerability scanner might only check for a portion of known vulnerabilities, each scanner defines the desired state differently.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Vulnerability Management."}]}
{"id": "nist_00084", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Information Security Handbook_ A Guide for Managers provide? (Section 170) risk and magnitude of harm resulting from the loss, misuse, or unauthorized access to or modification of the information in the application. Minor applications are typically included as part of a GSS. 53 See NIST SP 800-37, Guide for the Security Certification and Accreditation of Federal Information Systems , and Chapter 11, Certification and Accreditation, of this guide for additional guidance on the C&amp;A process. 54 Caution should be exercised when one individual fills multiple roles in the security planning process to ensure that the individual retains an appropriate level of independence and remains free from conflicts of interest. 55 See Chapter 2, Governance, Chapter 5, Capital Planning, Chapter 11, Certification, Accreditation, and Security Assessments, and Chapter 14, Configuration Management, of this guide for additional guidance on roles and responsibilities. 56 When an agency has not designated a formal CIO position, the Federal Information Security Management Act (FISMA) requires the associated responsibilities to be handled by a comparable agency official. - Designating an SAISO who shall carry out the CIO's responsibilities for system security planning; - Developing and maintaining information security policies, procedures, and control techniques to address system security planning; - Managing the identification, implementation, and assessment of common security controls; - Ensuring that personnel with significant responsibilities for system security plans are trained; - Assisting senior agency officials with their responsibilities for system security plans; and - Identifying and developing common security controls for the agency. The information system owner 57 is the agency official responsible for the overall procurement, development, integration, modification, and operation and maintenance of the information system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_00085", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? (Part 239) Control HA-1: tions on Previous Work All of the existing IBE systems have their own limitations. Shamir's system signed but did not encrypt. Cocks's system needs care to avoid an adaptive chosen ciphertext attack. It is also inefficient, but still efficient enough for use on reasonable communications paths. While others have proofs of security, there is a notoriously poor relationship between proofs of security and actual system security. Security proofs can show where a system is safe, but not protect against new assumptions that an adversary can bring to bear against the system nor against uses of a system that its creators did not think of which may be outside of the scope of the original threat model. Still other subtle problems have shown up on other systems, such as the ability in early HIBE systems for colluding users to determine the PKG's master key. With the exception of Shamir's system, IBE systems rely on new public-key cryptosystems, most often Weil pairing. Consequently, they are not compatible with existing systems that use RSA, Elgamal, or DSA. This limits their practical application, since there are many existing systems built upon these cryptosystems. Also, experience and comfort with the security of these established systems is high. A key advantage that Shamir's system has over all those that follow it is that it was based on established public key cryptography, and thus (had it been successful in being both a signing and encrypting system) interoperable with non-IBE systems. Had Shamir's system been successful at encrypting, an RSA-based IBE system would likely be the dominant IBE system today, if for no other reason than its interoperability with deployed systems. This is an important observation - if we can construct an IBE system that uses traditional, integer-based, public key cryptography, the barriers to adoption of IBE systems might be lowered. The value that IBE has can be fully realized if it can be made to work with these established systems.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_00086", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Other Compressed Archive Formats according to PDA Forensic Tools_ an Overview and Analysis? Other Compressed Archive Formats: Not Applicable - When compressed files (i.e., . tar , . tar . gz , . tgz , . rar and . exe ) are transferred to the Palm device via the Quick Install protocol, the files are automatically uncompressed before being uploaded to the device.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PDA Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_00087", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2009 Annual Report say about SCAP? (Part 1) According to Computer Security Division 2009 Annual Report, SCAP: SCAP SCAP is a suite of specifications that use the eXtensible Markup Language (XML) to standardize the format and nomenclature by which security software products communicate information about software flaws and security configurations. SCAP includes software flaw and security configuration standard reference data, also known as SCAP content . This reference data is provided by the NVD (The National Vulnerability Database can be found at http:// nvd.nist.gov/), which is managed by NIST and sponsored by the Department of Homeland Security (DHS). SCAP is a multi-purpose protocol that supports automated vulnerability checking, technical control compliance activities, and security measurement. The U.S. Government, in cooperation with academia and private industry, is adopting SCAP and encourages its use in support of security automation activities and initiatives. Draft NIST SP 800-126 is the SCAP technical specification (http:// csrc/publications/drafts/sp800-126/Draft-SP800-126.pdf.) CSD plans to publish SP 800-126, The Technical Specification for the Security Content Automation Protocol (SCAP): SCAP Version 1.1 , in final form in the first quarter of FY2010.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2009 Annual Report."}]}
{"id": "nist_00088", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does PIV Data Model Test Guidelines provide? (Section 283) 1: | 11.4.2.3: Verify FASC-N | The tester shall validate the presence of the FASC-N in the subjectAltName extension in the card authentication certificate issued by the vendor. | | TE07.04.10.01 | 11.4.1.7: Verify interim status extension | The tester shall validate that the piv-interim extension by the vendor. is present in the card authentication certificate issued | | TE 07.04.11.01 | 11.4.2.1: Verify public key size | The tester shall validate that the public key size is in accordance with Table 3-1 of SP 800-78. | | TE07.04.12.01 | ymmetric 11.4.2.2: Verify as key pair | The tester shall validate that the public key present in the card authentication certificate is part of the key pair corresponding to the private key on the PIV card. | | TE07.04.13.01 | ASC-N 11.4.2.3: Verify F | The tester shall validate that the FASC-N in the subjectAltName field in the card authentication CHUID in the PIV card. certificate is the same as the FASC-N present in the | | TE0 7.04.14.01 | 11.4.2.4: Verify RSA exponent | exponent size is greater than or equal to 65,537.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_00089", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector say about SOLUTION? According to Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector, SOLUTION: This practice guide demonstrates how an organization may implement a solution to mitigate identified cybersecurity and privacy risks. The reference architecture features technical and process controls to implement: - \uf0a7 a defense-in-depth solution, including network zoning that allows more granular control of network traffic flows and limits communications capabilities to the minimum necessary to support business function - \uf0a7 access control mechanisms that include multifactor authentication for care providers, certificate-based authentication for imaging devices and clinical systems, and mechanisms that limit vendor remote support to medical imaging components - \uf0a7 a holistic risk management approach that includes medical device asset management, augmenting enterprise security controls, and leveraging behavioral analytic tools for near realtime threat and vulnerability management in conjunction with managed security solution providers The NCCoE sought existing technologies that provided the following capabilities: - \uf0a7 role-based access control - \uf0a7 microsegmentation - \uf0a7 behavioral analytics - \uf0a7 data security - \uf0a7 cloud storage While the NCCoE used a suite of commercial products to address this challenge, this guide does not endorse these particular products, nor does it guarantee compliance with any regulatory initiatives. Your organization's information security experts should identify the products that will best integrate with your existing tools and IT system infrastructure. Your organization can adopt this solution or one that adheres to these guidelines in whole, or you can use this guide as a starting point for tailoring and implementing parts of a solution.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector."}]}
{"id": "nist_00090", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2004 Annual Report say about AUTHORIZATION MANAGEMENT AND ADVANCED ACCESS CONTROL MODELS? (Part 1) According to Computer Security Division 2004 Annual Report, AUTHORIZATION MANAGEMENT AND ADVANCED ACCESS CONTROL MODELS: AUTHORIZATION MANAGEMENT AND ADVANCED ACCESS CONTROL MODELS A ccess control is the administrative and automated process of defining and limiting which system users can perform which system operations on which system resources. These limitations are based on business rules or policies of a specific host organization. The ability to enforce policy can be of great economic and mission importance to an organization. Although often specified in terms of protection, the ability of an organization to enforce policy enables the sharing of greater volumes of data and resources to a greater and more diverse user community. Access control policies are enforced through a mechanism consisting of access control functions and access control data that together map a user's access request to a decision whether to grant or deny access. Today access control mechanisms come in a wide variety of forms, each with distinct policy advantages and disadvantages. Although each may meet specific access needs, the resulting technology has disappointed the marketplace. This is due to the reality that a given access control mechanism may meet the policy requirements within a particular market domain, while being completely inappropriate in another. The reality is that access control policies can be as diverse as the business applications that need to enforce them. This rigidity creates a problem when the protection required of an application/organization/agency is different from the policy(ies) built into the mechanism at hand.This problem is exasperated when there is a mission need to share and coordinate information among operational units. The ability of an organization to enforce its access control policies directly impacts its ability to execute its mission - by determining the degree to which its volumes of resources may be protected and shared among its user community.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Computer Security Division 2004 Annual Report."}]}
{"id": "nist_00091", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-09 in A Report on the Privilege (Access) Management Workshop? (Part 42) Control AM-09: retrieval, and definition of resource attributes. In the area of access control methods, this report concludes that a formal standardized definition of attribute-based access control (ABAC) is needed. Although there has been much socialization of the term ABAC, there are still many variations in its description. Toward the end of standardizing its meaning, a definition of ABAC was offered as a starting point. There are three access control methods that are clearly distinguishable from one another: identity-based access control (IBAC), role-based access control (RBAC), and attribute-based access control (ABAC). Although policy-based access control (PBAC) does not need to be considered a separate access control method, the ideas associated with views of it make it clear 15 Privilege management is the definition and management of attributes and policies that are used to decide whether a user's request for access to some resource should be granted. that full realization of ABAC's potential requires better attribute and policy management capabilities at the enterprise level. An organization should consider the many factors regarding requirements for its access control system that are briefly described in Table 1 above. Policy capabilities for applications supporting both federal government and commercial enterprises are a key element for effective privilege management at the enterprise level. Policy developers should carefully consider what attributes are needed to implement the policies, gain an understanding of users and of the characteristics of the data involved, and consider whether there is a need to accommodate unanticipated users. ## Recommendations Based on the view of privilege management captured in this report, the following recommendations are made: - \uf0b7 Privilege Management Workshop Convene the second workshop on Privilege Management, a follow-up to the NIST-NSA Privilege (Access) Management Workshop.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: A Report on the Privilege (Access) Management Workshop."}]}
{"id": "nist_00092", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain validation according to NIST Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control According to Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control, validation: Confirmation (through the provision of strong, sound, and objective evidence and demonstration) that requirements for a specific intended use or application have been fulfilled and that the system, while in use, fulfills its mission or business objectives while being able to provide adequate protection for stakeholder and mission or business assets, minimize or contain asset loss and associated consequences, and achieve its intended use in its intended operational environment with the desired level of trustworthiness. [NIST-SP800-160V1, Adapted]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control."}]}
{"id": "nist_00093", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) provide? (Section 70) upports a security policy that is consistent with its higher-level policies (e.g., its Information Management Policy and Information Security Policy) and other applicable U.S. Government requirements. A Federal organization that is considering the procurement of a CKMS or the services of a CKMS provider should review the security policy of each candidate CKMS and verify that the CKMS has the necessary capabilities. An appropriate FCKMS Security Policy should then be created. The FCKMS Security Policy should specify the rules that can assure the availability, confidentiality, and integrity of the organization's cryptographic keys and bound metadata that will be used to protect the sensitive information to be protected by the FCKMS. An FCKMS service-using organization should verify that its security policies are consistent with, and can be supported by, an FCKMS service provider, both administratively and technically. The FCKMS Security Policy should specify how to protect each type of key and its associated metadata throughout their lifecycles, including when they are stored, transported, or used. An FCKMS service-using organization should assist in adopting, supporting, and enforcing its own security policies and implementation rules by providing for tutorials to new managers and users on how services should be managed and used. If a user can select and initiate security services for an application or category of information, then the FCKMS serviceproviding organization should assist in selecting appropriate security services by informing the user of the rules and how the rules can and should be followed. The FCKMS should be configured so as to minimize the likelihood that a user could select an inappropriate option. FR:4.1 The CKMS design shall specify the CKMS Security Policy, including the configurable options and sub-policies that it is designed to enforce.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_00094", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain II. Project Methodology according to NIST Notional Supply Chain Risk Management Practices for Federal Information Systems According to Notional Supply Chain Risk Management Practices for Federal Information Systems, II. Project Methodology: This project developed a tool to assess cyber-supply chain risk management capabilities by consolidating the collective inputs of the set of public and private actors engaged in supporting Initiative 11. The Department of Commerce (NIST and Bureau of Industry and Security, BIS), the Department of Homeland Security (DHS); the Department of Defense (DOD/CIO and DOD/NSA); and the Government Services Administration all provided formal inputs to design the assessment tool. Representatives from Safe Code and Tech America's SCRM sub-committee also contributed valuable inputs. This tool was then distributed to and validated with a sample of vendors of IT systems, software, hardware, and services. Our target participants included: small to mediumsized IT vendors traditionally under-represented in IT surveys; Chief Information Officers/Chief Security Officers nationally and in the Washington DC region; and Directors of Supply Chain. There were 131 respondents who completed the survey from beginning to end. This means our survey response rate equaled the 1% industry benchmark for Third Party IT Surveys (source: IDG List Services). This is especially impressive given the absence of official survey distribution; the length of time it takes to fill in the survey (approximately 30 minutes); the newness of the subject discipline; and the difficulties some companies reported in routing the survey to appropriate person(s) in the organization. An additional 159 respondents completed one or more sections of the survey. In total, 290 surveys were either partially or fully completed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Notional Supply Chain Risk Management Practices for Federal Information Systems."}]}
{"id": "nist_00095", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Electronic Health Records on Mobile Devices say about puppet will install here? (Part 249) According to Securing Electronic Health Records on Mobile Devices, puppet will install here: EMR3222 NIST SP 1800-1E: Securing Electronic Health Records on Mobile Devices 72 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 1 . . Appendix C References [1] K. Marchesini, Mobile Devices Roundtable: Safeguarding Health Information: Real World Usages and Real World Privacy & Security Practices, The Office of the National Coordinator for Health Information Technology, U.S. Department of Health & Human Services, March 16, 2012. https://www.healthit.gov/sites/default/files/onc_ocpo_mobile_device_roundtable_slides_3_16 _12.pdf [accessed 5/3/18]. [2] [3] [4] [5] [6] [7] [8] Mobile Devices \u2013 Secure Exchange of Electronic Health Information, Final draft, National Cybersecurity Center of Excellence, National Institute of Standards and Technology, Gaithersburg, Maryland. [accessed 5/3/18]. Guide for Conducting Risk Assessments, NIST Special Publication 800-30 Revision 1, National Institute of Standards and Technology, Gaithersburg, Maryland, September 2012, 15 pp. [accessed 5/3/18]. Guide for Conducting Risk Assessments, NIST Special Publication 800-30 Revision 1, National Institute of Standards and Technology, Gaithersburg, Maryland, September 2012, 29 pp. [accessed 5/3/18]. Guide for Conducting Risk Assessments, NIST Special Publication 800-30 Revision 1, National Institute of Standards and Technology, Gaithersburg, Maryland, September 2012, Table I-5: Template \u2013 Adversarial Risk, I-3 \u2013 I-4 pp. [accessed 5/3/18].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Electronic Health Records on Mobile Devices."}]}
{"id": "nist_00096", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 2017 NIST_ITL Cybersecurity Program Annual Report provide? (Section 105) ment and a collaboration with Intrinsic ID, Inc. - a company with complementing technology for constructing the initial key on the client side by extracting it from SRAM memory cells. The team also established a collaborative relationship with Crypto4A and 2Keys Corp. from Canada on developing a common protocol for EaaS. The team coordinated with the research team working on the NIST Beacon for developing common back-end components for the two services. The team plans to leverage these common components in the NIST EaaS implementation. Dr. Apostol Vassilev (301) 975-3221 apostol.vassilev@nist.gov The engine for many of the techniques in CSD's cryptographic toolkit is a block cipher algorithm, such as the Advanced Encryption Standard (AES) algorithm. A block cipher transforms some fixedlength binary data (i.e., a 'block' of data) into seemingly random data of the same length. The transformation is determined by the choice of some secret data called the 'key.' The same key is used to reverse the transformation and recover the original block of data. A cryptographic technique (e.g., for encryption and/or authentication) that is constructed from a block cipher is called a 'mode of operation.' Several modes of operation have been specified in the SP 800-38 series of publications. The latest installment in the series, Special Publication 80038G, Recommendation for Block Cipher Modes of Operation: Methods for Format-Preserving Encryption , was published in 2016. It specifies two AES modes of operation, called FF1 and FF3, for 'format-preserving encryption' (FPE), based on proposals that were submitted from the private sector, specifically, the payments industry. Recently, two academic researchers, Vaudenay and D\u00fcrak, developed a cryptanalytic attack on the FF3 mode.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_00097", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Output : according to NIST Recommendation for Block Cipher Modes of Operation_ Methods for Key Wrapping According to Recommendation for Block Cipher Modes of Operation_ Methods for Key Wrapping, Output :: Plaintext P or indication of inauthenticity, FAIL .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Block Cipher Modes of Operation_ Methods for Key Wrapping."}]}
{"id": "nist_00098", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control WE-1000 in Hardware Security Failure Scenarios_ Potential Hardware Weaknesses? (Part 38) Control WE-1000: ph with memory-related weaknesses highlighted <!-- image --> ## 7. Software Assurance Trends Categories In addition to the views previously presented, there is a Software Development view (CWE699). Figure 25 shows the View-699 CWEs that overlap with the complete HW CWEs graph (from Fig. 1). This overlap is shown in olive green. Fig. 25. View-699 CWEs that overlap with View-1194 highlighted <!-- image --> Only 12 CWEs are both in View-1194 and View-699. Organized by the View-699 categories, they are: - CWE View-699&gt; CWE Category: Permission Issues - (CWE-275) - o CWE-276: Incorrect Default Permissions - CWE View-699&gt; CWE Category: Cryptographic Issues - (CWE-310) - o CWE-325: Missing Cryptographic Step - CWE View-699&gt; CWE Category: Behavioral Problems - (CWE-438) - o CWE-440: Expected Behavior Violation - CWE View-699&gt; CWE Category: Documentation Issues - (CWE-1225) - o CWE-1053: Missing Documentation for Design - o CWE-1110: Incomplete Design Documentation - o CWE-1111: Incomplete I/O Documentation - o CWE-1112: Incomplete Documentation of Program Execution - o CWE-1118: Insufficient Documentation of Error Handling Techniques - CWE View-699&gt; CWE Category: Authorization Errors - (CWE-1212) - o CWE-1220: Insufficient Granularity of Access Control - CWE View-699&gt; CWE Category: Information Management Errors - (CWE-199) - o CWE-319: Cleartext Transmission of Sensitive Information - CWE View-699&gt; CWE Category: Cryptographic Issues - (CWE-310) - o CWE-1240: Use of a Cryptographic Primitive with a Risky Implementation - o CWE-1241: Use of Predictable Algorithm in Random Number Generator Figure 26 provides a separate view of these 12 CWEs. Fig. 26. The 12 CWEs in both View-1194 and View-699 <!-- image --> ## 8. Conclusion Historically held notions that hardware is invulnerable have been shown to be incorrect.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Hardware Security Failure Scenarios_ Potential Hardware Weaknesses."}]}
{"id": "nist_00099", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is FR according to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)? FR: 4.4 The CKMS design shall specify other related security policies that support the CKMS Security Policy.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_00100", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1.4 Document Conventions according to NIST Representation of PIV Chain-of-Trust for Import and Export According to Representation of PIV Chain-of-Trust for Import and Export, 1.4 Document Conventions: Throughout this document key words are used to identify requirements. The key words 'optional', 'required', 'shall', 'shall not', and 'should' are used. These words are a subset of the IETF Request For Comments (RFC) 2119 [RFC2119] key words, and have been chosen based on convention in other normative documents. In addition to the key words, the words 'need,' 'can,' and 'may' are used in this document, but are not intended to be normative.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Representation of PIV Chain-of-Trust for Import and Export."}]}
{"id": "nist_00101", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories say about Privacy Information? (Part 2) According to Guide for Mapping Types of Information and Information Systems to Security Categories, Privacy Information: ired to conduct Privacy Impact Assessments (PIAs) before developing IT systems that contain personally identifiable information or before collecting personally identifiable information electronically. The impact of privacy violations should consider any adverse effects experienced by individuals or organizations as a result of the loss of PII confidentiality. Examples of adverse effects experienced by individuals may include blackmail, identity theft, discrimination, or emotional distress. Examples of adverse effects experienced by organizations may include administrative burden, financial losses, loss of public reputation and confidence, and the penalties associated with violation of the relevant statutes and policies. Categorizations should be reviewed to ensure that the adverse effects of a loss of PII confidentiality have been adequately factored into impact determinations. The confidentiality impact level should generally fall into the moderate range.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories."}]}
{"id": "nist_00102", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST say about B, Computer familiarity? According to Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST, B, Computer familiarity: . Do you currendy make frequent use of a computer for your lab work? If so, what kind is it? Is it attached to the NIST Local Area Network? . Would you feel comfortable using a computer-based electronic notebook? . Are you comfortable working in a Windows environment on the computer? If not, please explain why.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST."}]}
{"id": "nist_00103", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control MP-4 in Control Baselines for Information Systems and Organizations? (Part 9) Control MP-4: protection needs, and assessments of risk. The combination of control baseline selection and control tailoring processes can help organizations satisfy their stated security and privacy requirements. ## 1.2 TARGET AUDIENCE This publication is intended to serve a diverse audience, including: - Individuals with system, information security, privacy, or risk management and oversight responsibilities, including authorizing officials, chief information officers, senior agency information security officers, and senior agency officials for privacy - Individuals with system development responsibilities, including mission owners, program managers, system engineers, system security engineers, privacy engineers, hardware and software developers, system integrators, and acquisition or procurement officials - Individuals with logistical or disposition-related responsibilities, including program managers, procurement officials, system integrators, and property managers - Individuals with security and privacy implementation and operations responsibilities, including mission or business owners, system owners, information owners or stewards, system administrators, and system security or privacy officers - Individuals with security and privacy assessment and monitoring responsibilities, including auditors, Inspectors General, system evaluators, control assessors, independent verifiers and validators, and analysts - Commercial entities, including industry partners, who produce component products and systems and develop security and privacy technologies ## 1.3 ORGANIZATIONAL RESPONSIBILITIES Organizations have the responsibility to choose a control selection approach in accordance with [SP 800-37].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Control Baselines for Information Systems and Organizations."}]}
{"id": "nist_00104", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Virtual Network Configuration for Virtual Machine (VM) Protection say about 2.5.2 Disadvantages? According to Secure Virtual Network Configuration for Virtual Machine (VM) Protection, 2.5.2 Disadvantages: A given network segment (a particular VXLAN ID) can exist in any virtualized host in the data center. This means that routing packets between any two VMs requires large mapping tables for the MAC addresses of the remote VMs and their corresponding VTEP IP addresses. As previously stated, the preferred way to build the mapping tables is to using a centralized or decentralized controller. However, the introduction of this control plane increases the overhead of network management. Another factor to watch for is the size of the mapping table; this can be controlled by carefully limiting the span of overlay segment by proper definition of Layer 2 Transport Zones (as is the case in typical production networks).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Virtual Network Configuration for Virtual Machine (VM) Protection."}]}
{"id": "nist_00105", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Integrating Forensic Techniques into Incident Response provide? (Section 234) the clientGLYPH&lt;146&gt;s behalf to the desired destination. Remote Access Server: Devices, such as virtual private network gateways and modem servers, that facilitate connections between networks. Reporting: The final phase of the computer and network forensic process, which involves reporting the results of the analysis; this may include describing the actions used, explaining how tools and procedures were selected, determining what other actions need to be performed (e.g., forensic examination of additional data sources, securing identified vulnerabilities, improving existing security controls), and providing recommendations for improvement to policies, guidelines, procedures, tools, and other aspects of the forensic process. The formality of the reporting step varies greatly depending on the situation. Sector: The smallest unit that can be accessed on media. Security Event Management Software: Software that imports security event information from multiple data sources, normalizes the data, and correlates events among the data sources. Slack Space: The unused space in a file allocation block or memory page that may hold residual data. Steganography: Embedding data within other data to conceal it. Subdirectory: A directory contained within another directory. Volatile Data: Data on a live system that is lost after a computer is powered down. Wiping: Overwriting media or portions of media with random or constant values to hinder the collection of data. Write-Blocker: A tool that prevents all computer storage media connected to a computer from being written to or modified. This page has been left blank intentionally. Selected acronyms used in the Guide to Integrating Forensic Techniques into Incident Response are defined below.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Integrating Forensic Techniques into Incident Response."}]}
{"id": "nist_00106", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is References according to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy? References: [SP 800-30]; [SP 800-88]; [IR 8062].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, fips, security control. General security reference material without sensitive content. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_00107", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research provide? (Section 98) Table 6: LOA Mapping to Cryptographic Tokens <!-- image --> | NIST SP 800-63-2 Assurance | PIV Assurance Level | Target Guidance: | Target Guidance: | Cryptographic Token FIPS 140-2 Validation Level | Cryptographic Token Type | PIV Derived Authentication Certificate | Enrollment Method | |------------------------------|-----------------------|--------------------------------------|-----------------------------------------------------|---------------------------------------------------|--------------------------------------------------------------------|------------------------------------------|---------------------| | Level | | M-06-16 /M-07-16 for Separate Tokens | Future Alternate OMB Guidance for Integrated Tokens | | | Policy | | | LOA-3 | Very High | No | \uf0fc | FIPS 140-2 Level 1 | Hybrid hardware/software token \u2022 Windows 8.1 \u2022 TPM \u2022 Microsoft CSP | id-fpki- common- pivAuth- derived | Remote enrollment | | LOA-3 | High | No | \uf0fc | FIPS 140-2 Level 1 | Software token \u2022 Android/iOS \u2022 MyID Identity Agent | id-fpki- common- pivAuth- derived | Remote enrollment | The major controls in the NIST SP 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations 47 control catalog that affect the DPC proof of concept research are: Related controls: AC-2, AC-9, AC-14, IA-5 Related controls: AC-3, AC-7, AC- 18, AC-20, CA-9, CM-2, IA-2, IA-3, MP-2, MP-4, MP-5, PL-4, SC-7, SC-43, SI-3, SI-4 References: OMB M-06-16; NIST SPs 800-114, 800-124, and", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, token. Contains security framework guidance for authentication systems. Source: Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research."}]}
{"id": "nist_00108", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders provide? (Section 111) ph Portner* Mark Russell* Sudhi Umarji The MITRE Corporation McLean, Virginia Dakota Consulting Silver Spring, Maryland *Former employee; all work for this publication was done while at employer. August 2021 FINAL The first and second drafts of this publication are available free of charge from <!-- image --> Certain commercial entities, equipment, products, or materials may be identified by name or company logo or other insignia in order to acknowledge their participation in this collaboration or to describe an experimental procedure or concept adequately. Such identification is not intended to imply special status or relationship with NIST or recommendation or endorsement by NIST or NCCoE; neither is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose. While NIST and the NCCoE address goals of improving management of cybersecurity and privacy risk through outreach and application of standards and best practices, it is the stakeholder's responsibility to fully perform a risk assessment to include the current threat, vulnerabilities, likelihood of a compromise, and the impact should the threat be realized before adopting cybersecurity measures such as this recommendation. National Institute of Standards and Technology Special Publication 1800-13C, Natl. Inst. Stand. Technol. Spec. Publ. 1800-13C, 159 pages (August 2021), CODEN: NSPUE2 As a private-public partnership, we are always seeking feedback on our practice guides. We are particularly interested in seeing how businesses apply NCCoE reference designs in the real world. If you have implemented the reference design, or have questions about applying it in your environment, please email us at psfr-nccoe@nist.gov. All comments are subject to release under the Freedom of Information Act.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, single sign-on. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_00109", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Required Vendor Information according to NIST PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance) According to PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance), Required Vendor Information: VE05.42-R4.01: The vendor shall specify in its documentation that secure messaging is implemented in accordance with AS05.42-R4.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)."}]}
{"id": "nist_00110", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Validity according to NIST Test Personal Identity Verification (PIV) Cards Version 2? Validity: Not Before: Aug 5 08:30:00 2019 GMT, Not After: Dec 31 08:30:00 2040 GMT", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_00111", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2011 Annual Report provide? (Section 123) &amp; Abstract Data Structures. In the coming year, we anticipate conducting a demonstration of the Cloud PM implementation, and bringing parts of the NGAC proposed standard to ballot by INCITS. We expect that this project will: - Offer users capabilities of a variety of services achieved through configuration of PM data alone, such as file management, email, workflow, and forms and records management, rather than managing overlapping user accounts, and potentially different authentication schemes for each data service, through a single authenticated session; - Deliver to select users, through the policy machine, select capabilities (of different services) under combinations of arbitrary, but mission-tailored forms of discretionary, mandatory, and history-based access controls, rather than deploying and managing different access control schemes for different data services; - Provide an inherent property of the PM, the comprehensive nature in which data services interplay. For instance, a user can attach a record, created under a relational database management service, to an email message and send that record to any chosen individual. This property is not achieved through interoperability features, but rather through the underlying framework of the PM that inherently provides a foundational basis for interoperability; and - Provide another inherent property of the PM, the comprehensive nature in which data is protected across data services. For example, regardless of the recipient of the message, any user who opens the attached record would only be able to read and/or write fields for which the user is authorized. Mr. David Ferraiolo (301) 975-3046 Mr.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Computer Security Division 2011 Annual Report."}]}
{"id": "nist_00112", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Extended Key Usage : according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Extended Key Usage :: TLS Web Client Authentication, Microsoft Smartcard Login, PKINIT Client Auth", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_00113", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms say about 2.3.1 American National Standards Institute (ANSI) 20? According to Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms, 2.3.1 American National Standards Institute (ANSI) 20: The American National Standards Institute (ANSI) is the administrator and coordinator of the United States' private-sector voluntary standardization system. ANSI does not develop American National Standards itself; rather, it facilitates the development of standards by establishing consensus among qualified groups. Several ANSI committees have developed standards that use cryptography, but the primary committee that has developed standards for the cryptographic algorithms themselves is Accredited Standards Committee (ASC) X9, which is a financial-industry committee. 21 Many of the standards developed within ASC X9 have been adopted within NIST standards (e.g., the Elliptic Curve Digital Signature Algorithm specified in American National 20 Further information is available at the ANSI web site: www.ansi.org. 21 Further information is available at the ANSI X9 web site: x9.org. Standard X9.62 22 has been adopted in FIPS 186). Likewise, ASC X9 has approved the use of NIST standards via a registry of approved standards from non-ASC X9 sources (e.g., AES, as specified in FIPS 197). A number of ASC X9 standards have also been incorporated into the standards of other standards bodies, such as the International Organization for Standardization (ISO) (see Section 2.3.4) via a Technical Advisory Group (TAG) called the International Committee on Information Technology Standards (INCITS). INCITS has been responsible for assuring that U.S. standards (e.g., both those developed by NIST and those developed within ASC X9) are incorporated within ISO standards.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms."}]}
{"id": "nist_00114", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities provide? (Section 36) ----------------| | High (H) | Remediation measures are available to mitigate the vulnerability in such a way as to collectively decrease the incidence of exploitation by between 76% and 100%. (A decrease of 100% means that the available remediation measures are able to entirely prevent exploitation.) | | Medium (M) | Remediation measures are available to partially mitigate the vulnerability in such a way as to collectively decrease the incidence of exploitation by between 26% and 75%. | | Low (L) | Remediation measures are available to slightly mitigate the vulnerability in such a way as to collectively decrease the incidence of exploitation by between 1% and 25%. | | None (N) | Remediation measures are not available. | | Not Defined (ND) | Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. The default value is None. | Differences between environments can have a large effect on the risk that a vulnerability poses to a particular organization and its stakeholders. The CCSS environmental metrics capture the characteristics of a vulnerability that are associated with a particular IT environment. Each organization computing CCSS metrics can determine an appropriate definition of IT environment, such as the entire enterprise or a logical or physical subset of the enterprise (e.g., a facility, a division, a small group of related systems). Since environmental metrics are optional, each includes a metric value that has no effect on the score. This value is used when the analyst feels the particular metric does not apply and wishes to ignore it. The environmental metrics customize the previously computed base and temporal metrics. The environmental metrics measure three aspects of vulnerability severity: Local Exploit Level, Local Remediation Level, and Local Impact.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities."}]}
{"id": "nist_00115", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Recommendation for Random Number Generation Using Deterministic Random Bit Generators? (Part 23) Control HA-1: tly seedlen bits. 2. seed\\_material = df ( seed\\_material , seedlen ). 3. ( Key , V ) = CTR\\_DRBG\\_Update ( seed\\_material , Key , V ). 4. reseed\\_counter = 1. 5. Return ( V , Key , reseed\\_counter ). ## 10.2.1.5 Generating Pseudorandom Bits Using CTR\\_DRBG Notes for the generate function specified in Section 9.3: The generation of pseudorandom bits using a CTR\\_DRBG instantiation requires a call to the Generate\\_function specified in Section 9.3. Process step 8 of that function calls the generate algorithm specified in this section. The values for max\\_number\\_of\\_bits\\_per\\_request and max\\_additional\\_input\\_length , and blocklen are provided in Table 3 of Section 10.2.1. If the derivation function is not used, then the maximum allowed length of additional\\_input = seedlen . For this DRBG mechanism, there are two cases for the processing. For each case, let CTR\\_DRBG\\_Update be the function specified in Section 10.2.1.2, and let Block\\_Encrypt be the function specified in Section 10.3.3. The seed length ( seedlen ) and the value of reseed\\_interval are provided in Table 3 of Section 10.2.1. The value of ctr\\_len is known by an implementation. ## 10.2.1.5.1 Generating Pseudorandom Bits When a Derivation Function is Not Used This method of generating bits is used when a derivation function is not used by an implementation. The following process or its equivalent shall be used as the generate algorithm for this DRBG mechanism (see step 8 of the generate process in Section 9.3.3): ## CTR\\_DRBG\\_Generate\\_algorithm ( working\\_state, requested\\_number\\_of\\_bits, additional\\_input ): 1. working\\_state : The current values for V , Key , and reseed\\_counter (see Section 10.2.1.1). 2. requested\\_number\\_of\\_bits : The number of pseudorandom bits to be returned to the generate function. 3. additional\\_input : The additional input string received from the consuming application. Note that the length of the additional\\_input string may be zero. ## Output: 1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Number Generation Using Deterministic Random Bit Generators."}]}
{"id": "nist_00116", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control FT-128 in Status Report on the Second Round of the NIST Lightweight Cryptography Standardization Process? (Part 56) Control FT-128: ule that is based on a nonlinear feedback shift register, and the nonlinearity in each round is obtained using a single NAND operation. Variants. The variants of the TinyJAMBU family are listed below. | AEAD variants | Key | Nonce | Tag | State size | |-----------------|-------|---------|-------|--------------| | TinyJAMBU -128 | 128 | 96 | 64 | 128 | | TinyJAMBU -192 | 192 | 96 | 64 | 128 | | TinyJAMBU -256 | 256 | 96 | 64 | 128 | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Security Analysis. In [63], the designers provided a security proof for the mode, analysis of the keyed-permutation, and security against forgery and key recovery attacks (including differential, linear, algebraic, and slide attacks). Saha et al. [228-230] showed that the security margin of TinyJAMBU is around 12 % due to the dependencies between the outputs of multiple AND gates. Tweak plan. In order to provide a larger security margin, the designers considered increasing the number of rounds for the permutation that processes the nonce and the AD [26]. ## 3.2.31 WAGE WAGE , designed by Aagaard et al. [64, 231], is a permutation-based AEAD scheme. WAGE is based on the duplex mode of operation [80], where the rate is 64 bits and the capacity is 195 bits. The mode includes additional key additions during the initialization and finalization phases to prevent a key-recovery attack and a forgery attack even after a state is recovered by an attacker during the encryption. The design of the underlying 259-bit permutation of WAGE , called the WAGE permutation, is inspired by the initialization phase of the Welch-Gong (WG) cipher [232, 233]. The WAGE permutation has 111 rounds, where the state is described by 37 7-bit stages.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Second Round of the NIST Lightweight Cryptography Standardization Process."}]}
{"id": "nist_00117", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for the Secure Deployment of IPv6 say about 3.4 IPv6 Extension Headers? (Part 4) According to Guidelines for the Secure Deployment of IPv6, 3.4 IPv6 Extension Headers: same functions as AH and also, optionally, confidentiality. IPsec as well as AH and ESP is covered in Section 5.3. - \uf03c Destination Options header . NH value of 60 in the immediately preceding header. This header is used to carry optional information that needs to be examined only by a packet's destination node(s). Intermediate nodes (for which the IPv6 base header destination address is not the address of the current node or more Routing Header processing is required) do not examine the Destination Options header. The Destination Options header works similarly to the Hop-by-Hop Option header, as it may carry one or more options, where each option is encoded in type-length-value format. A node receiving a packet that matches the IPv6 destination address examines the NH field, notes the presence of a Destination Options, and processes the Destination Options before forwarding the payload to the upper layer protocol. A Destinations Options header could appear before or after an ESP header; however, it should be placed after an ESP header for increased protection. - \uf03c Mobility header . NH value of 135 in the immediately preceding header. This header is used by a mobile node, correspondent node, and home agent to manage mobile IPv6 bindings. Mobile IPv6 (MIPv6) provides enhanced security, streamlined administrative protocols, and greater efficiency compared with Mobile IPv4. MIPv6 is covered in Section 4.4. Extension headers are established at the source before transmission of the packet. Their order and contents are not altered by intermediary nodes. Extension headers provide important services and functions for the IPv6 protocol. They may direct intermediary nodes about how packet payloads are to be handled prior to reaching their ultimate destination. Defined extension headers for the IPv6 protocol should occur in a recommended order.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_00118", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services say about risk management? According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services, risk management: The program and supporting processes to manage information security risk to organizational operations (including mission, functions, image, 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. [NIST-SP-800-39]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_00119", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control II-6 in A Study of Federal Agency Needs for Information Technology Security? (Part 136) Control II-6: operated as part of the NIST Computer Security Resource and Response Center. It is intended to encourage sharing of information that will help users and managers better protect their data and systems. The BBS contains the following types of Information: - awareness and reference materials - bibliographies of security-relevant publications - lists of security-related seminars and conferences - recent NIST and other publications that deal with security issues - software reviews - archive of computer security incident alert information Issued by ## Appendix I ## various computer security response centers - information about actual incidents and how to protect against or correct known system vulnerabilities ## The bulletin board system contains three subsystems: - The bulletin subsystem consists of eight 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. - The message subsystem permits users and the system operator (sysop) to exchange short messages, primarily for administrative or informational purposes. The BBS is available 24 hours a day, seven days a week. Each BBS user has a maximum of 70 minutes a day, 60 minutes on one call. With a modem, dial (301) 948-5717 for 300, 1200 or 2400 baud rate or dial (301) 948-5140 for 9600 baud rate. To access the BBS via the Internet, use the telnet command, for example: Type 'telnet csrc.nist.gov' or 'telnet 129.6.54.11' The BBS is menu driven and offers an on-line help feature.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of Federal Agency Needs for Information Technology Security."}]}
{"id": "nist_00120", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Assurance Requirements for Linux Application Container Deployments say about Table of Contents? (Part 8) According to Security Assurance Requirements for Linux Application Container Deployments, Table of Contents: | 19 | | 6 Assurance Requirements for Image Integrity Solutions | 6 Assurance Requirements for Image Integrity Solutions | ..................................22 | | 7 | Assurance Requirements for Image Registry Protection.................................23 | | |-------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|--------------------| | 8 | Assurance Requirements for Orchestration Functions....................................24 | | | 9 | Adverse Side Effect of Some Security Solutions..............................................25 | | | 10 | Summary and Conclusions.................................................................................26 | | | List of Appendices | List of Appendices | List of Appendices | | Appendix A-Acronyms..........................................................................................277 | Appendix A-Acronyms..........................................................................................277 | | | Appendix B-References ........................................................................................288 | Appendix B-References ........................................................................................288 | | | List of Figures | List of Figures | List of Figures | | Figure 1 - Container Technology Stack ..........................................................................2 | Figure 1 - Container Technology Stack ..........................................................................2 | | | Figure 2 - vTPM Implemented in a Kernel Module .........................................................8 | Figure 2 - vTPM Implemented in a Kernel Module .........................................................8 | | | Figure 3 - vTPM located in a dedicated Container .........................................................9 | Figure 3 - vTPM located in a dedicated Container .........................................................9 | | | List of Tables | List of Tables | List of Tables | | Table 1- Linux Resource Control using Cgroups..........................................................17 | Table 1- Linux Resource", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Assurance Requirements for Linux Application Container Deployments."}]}
{"id": "nist_00121", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain A.2 Privilege Escalation Attacks according to NIST Guide to Secure Web Services According to Guide to Secure Web Services, A.2 Privilege Escalation Attacks: The objective of privilege escalation attempts is to enable the attacker to change the privilege level of a process, thereby taking control of that now-compromised process to bypass security controls that would otherwise limit the attacker's access to the Web service's functionality, data, resources, and environment. Web services are often configured to run with specific group or user permissions unrelated to those of the end user (human or requester service) responsible for causing the service's execution (e.g., 'anonymous' or 'nobody' permissions). Such Web services, if they also suffer from buffer overflows or race conditions, can be used to increase the permissions grabbed by the attacker, or to escalate the attacker's ability to cause damage to the Web service, its data, resources, or environment. Attackers can perform privilege escalation by taking advantage of defects in the implementation, design, or configuration of Web services. Any standard developed to prevent privilege escalation attempts would remain susceptible to implementation, design, or configuration defects.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Secure Web Services."}]}
{"id": "nist_00122", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EP-67 in Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)? (Part 151) Control EP-67: In a 6LoWPAN stack, sensitive information will normally be protected by transport- or application-layer (or even IP-layer) security, which are all above the adaptation layer, leaving no sensitive information to compress at the GHC level. However, a 6LoWPAN deployment that entirely depends on Media Access Control (MAC) layer security may be vulnerable to attacks that exploit redundancy information disclosed by compression to recover information about secret values. This attack is fully mitigated by not exposing secret values to the adaptation layer or by not using GHC in deployments where this is done. Page 10, Section 5 | Proposed Standard | | RFC 7959 August 2016 | IETF | Block-Wise Transfer in Constrained Application Protocol (CoAP) Security Considerations: Where access to a resource is only granted to clients making use of specific security associations, all blocks of that resource must be subject to the same security | Approved Standard | IT System Security Evaluation: Standards that are used to provide: security assessment of operational systems; security requirements for cryptographic modules; security tests for cryptographic modules; automated security checklists; and security metrics.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_00123", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Digital Identity Guidelines_ Authentication and Authenticator Management provide? (Section 169) gement System of Records Notice (SORN) A notice that federal agencies publish in the Federal Register to describe their system of record. token See authenticator. transaction See digital transaction. Transport Layer Security (TLS) An authentication and security protocol that is widely implemented in browsers and web servers. TLS provides confidentiality, certificate-based authentication of the receiving (server) endpoint, and certificate-based authentication of the originating (client) endpoint. TLS is specified in [RFC8446] and [SP800-52]. usability The extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use. [ISO/IEC9241-11] validation The process or act of checking and confirming that the evidence and attributes supplied by an applicant are authentic, accurate, and associated with a real-life identity. See attribute validation. verification The process or act of confirming that the applicant undergoing identity proofing holds the claimed real-life identity represented by the validated identity attributes and associated evidence. Synonymous with identity verification. verifier An entity that confirms the claimant\u2019s identity by verifying the claimant\u2019s possession and control of one or more authenticators using an authentication protocol. To do this, the verifier needs to confirm the binding of the authenticators with the subscriber account and check that the subscriber account is active. verifier impersonation See phishing. 116 NIST SP 800-63B-4 July 2025 Digital Identity Guidelines Authentication and Authenticator Management Appendix E. Change Log This appendix is informative. This appendix provides an overview of the changes made to SP 800-63B since its initial release. \u2022 Removes Purpose, Definitions, and Abbreviations numbered sections and renumbers sections accordingly. The section numbers referenced below are the new section numbers.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token, sso. Contains security framework guidance for authentication systems. Source: Digital Identity Guidelines_ Authentication and Authenticator Management."}]}
{"id": "nist_00124", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Measurement Guide for Information Security_ Volume 1 \u2014 Identifying and Selecting Measures say about References? (Part 4) According to Measurement Guide for Information Security_ Volume 1 \u2014 Identifying and Selecting Measures, References: burg, MD), NIST Special Publication (SP) NIST SP 800-90B. https://doi.org/10.6028/NIST.SP.800-90B - [21] Stolfo S, Bellovin S, Evans D (2011) Measuring Security. IEEE Security &amp; Privacy 9(3):6065. https://doi.org/10.1109/MSP.2011.56 - [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 - [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", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Measurement Guide for Information Security_ Volume 1 \u2014 Identifying and Selecting Measures."}]}
{"id": "nist_00125", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Blockchain Networks_ Token Design and Management Overview provide? (Section 114) ate the supply. This section discusses different types of stablecoin designs at a high level. A Classification Framework for Stablecoin Designs [130] provides more in-depth details. Projects have been studied or developed for tokens pegged to fiat currencies and cryptocurrencies as well as tokens that directly represent ownership claims for bank deposits, securities, and central bank reserves. Stablecoins may be composable with other blockchain-based protocols and tools to form more advanced financial instruments and exchange platforms. They can make it possible to borrow and lend tokens issued by distinct protocols, earning yields on deposits. Thus, they may be seen as portable and programmable alternatives to traditional bank accounts, savings accounts, and brokerage accounts, with integrated payment systems. As discussed in Section 4.1.3, blockchain-native tokens (i.e., ownerless or non-sovereign cryptocurrencies) can be represented on a separate blockchain through a bridge that collateralizes them and provides proof of that collateral. They are also referred to as wrapped cryptocurrencies . WBTC [131] is meant to represent bitcoins as tokens that follow the ERC-20 standard on the public Ethereum network through a consortium, the members of which act as notaries. WBTC tokens' minting involves two different roles: 1) merchants, who sign mint requests and provide liquidity for the WBTC/BTC pair, and 2) custodians, who process these requests. The consortium members jointly own the token factory contract via multi-signature. tBTC [132] (associated with the CrossChain Group [133]) allows a similar representation using a relay and incentives coupled with an overcollateralized reserve rather than trusted intermediaries. Each bitcoin deposit is represented as a nonfungible token redeemable for fungible tBTC tokens.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: token, sso. Contains security framework guidance for authentication systems. Source: Blockchain Networks_ Token Design and Management Overview."}]}
{"id": "nist_00126", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Section 224) entifier. Thus, these schemes, by themselves, offer no assurance to either party of the accuracy of any identifier that may be used to label the entity with whom they have established a shared secret. The use of C(2e, 0s) schemes may be appropriate in applications where any trusted association desired/required between an identifier and an ephemeral public key is enforced by methods external to the scheme (e.g., in the protocol incorporating the key-agreement scheme). This Recommendation does not specify the incorporation of key confirmation in a C(2e, 0s) scheme. These schemes require each participant to own a static key pair that is used in their keyagreement transaction; in addition, the participant acting as party U is required to generate and use an ephemeral key pair. Different assurances are provided to the participants by the utilization of a C(1e, 2s) scheme, depending upon which one acts as party U and which one acts as party V. The use of static key pairs in the key-agreement transaction can provide the participants with some level of assurance that they have correctly identified the party with whom they will be establishing keying material if the transaction is successfully completed. In the case of a transaction based on the One-Pass Unified model or dhHybridOneflow scheme, each participant has assurance that no unintended entity (i.e., no entity other than the owners of the static key pairs involved in the key-establishment transaction) could employ a Diffie-Hellman primitive (see Section 5.7.1) to compute Zs , the static component of the shared secret Z, without knowledge of one of the static private keys employed during the transaction. Absent the compromise of Zs or one of those static private keys, each participant can be confident of correctly identifying the other participant in the keyestablishment transaction.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}]}
{"id": "nist_00127", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-2 in Computer Security Division 2005 Annual Report? (Part 20) Control HA-2: identity has been authenticated that person needs to be registered with the PIV system and that person's card needs to be issued. The PIV standard provides specifications for this process. - Access Control (determined by resource owner)-this refers to how users are granted access to Federal resources. The government agencies (resource owner) will determine if the person is granted access based on the security level of the card and the sensitivity level of the resource that is being accessed. - Life Cycle Management-the information associated with a user's identity is subject to change. The user may change employers, gain new security clearances, leave an agency, or any one of a host of possibilities. This framework will recommend guidelines for managing these changes through the life cycle of both the card and the associated cardholder. FIPS 201 was divided into two parts. Part 1 addressed the common identification, security, and privacy requirements for issuing organizations. Part 1 is to have been implemented by all Federal departments and agencies by October 27, 2005. Part 2 provided detailed technical specification of components and processes required for interoperability of PIV cards with the personal authentication, access control, and PIV card management systems across the government. The Office of Management and Budget (OMB) has directed that Part 2 be implemented by all Federal departments and agencies by October 27, 2006. In addition to the FIPS 201 standard, we developed a reference implementation, designated an initial set of conformance test laboratories, and published several implementation guidelines.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, sso. Contains security framework guidance for authentication systems. Source: Computer Security Division 2005 Annual Report."}]}
{"id": "nist_00128", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PS-10 in IoT Device Cybersecurity Capability Core Baseline? (Part 11) Control PS-10: ederal 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 - [2] Fagan M, Megas KN, Scarfone K, Smith M (2020) Foundational Cybersecurity Activities for IoT Device Manufacturers. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8259. https://doi.org/10.6028/NIST.IR.8259 - [3] Joint Task Force Transformation Initiative (2012) Guide for Conducting Risk Assessments. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-30, Rev. 4. - [4] Boeckl K, Fagan M, Fisher W, Lefkovitz N, Megas K, Nadeau E, Piccarreta B, Gabel O'Rourke D, Scarfone K (2019) Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8228. https://doi.org/10.6028/NIST.IR.8228 - [5] AgeLight Digital Trust Advisory Group (2019) IoT Safety Architecture &amp; Risk Toolkit (IoTSA) v3.1. (AgeLight Advisory &amp; Research Group, Bellevue, WA). - [6] Broadband Internet Technical Advisory Group (BITAG) (2016) Internet of Things (IoT) Security and Privacy Recommendations. (Broadband Internet Technical Advisory Group [BITAG], Denver, CO). )\\_Security\\_and\\_Privacy\\_Recommendations.pdf - [7] Cloud Security Alliance (CSA) IoT Working Group (2015) Identity and Access Management for the Internet of Things. (Cloud Security Alliance [CSA]). https://cloudsecurityalliance.org/download/identity-and-access-management-for-the-iot/ - [8] Council to Secure the Digital Economy (CSDE) (2019) The C2 Consensus on IoT Device Security Baseline Capabilities.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: IoT Device Cybersecurity Capability Core Baseline."}]}
{"id": "nist_00129", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control GV-2 in Integrating Cybersecurity and Enterprise Risk Management (ERM)? (Part 92) Control GV-2: onsibilities based on its position in the hierarchy and the roles and responsibilities of its officers. | | Enterprise Risk | The effect of uncertainty on enterprise mission and objectives. | | Enterprise Risk Management | 'An effective agency-wide approach to addressing the full spectrum of the organization's significant risks by understanding the combined impact of risks as an interrelated portfolio, rather than addressing risks only within silos.' [1] The 'culture, capabilities, and practices that organizations integrate with strategy-setting and apply when they carry out that strategy, with a purpose | | Enterprise Risk Register | A risk register at the enterprise level that contains normalized and aggregated inputs from subordinate organizations' risk registers and profiles. | | Exposure | The combination of likelihood and impact levels for a risk.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Integrating Cybersecurity and Enterprise Risk Management (ERM)."}]}
{"id": "nist_00130", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to 2016 NIST_ITL Cybersecurity Program Annual Report? http: / /nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST. SP.800-82r2.pdf", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_00131", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) say about 4 Security Policies? According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS), 4 Security Policies: An organization often creates and supports layered security policies, with high-level policies addressing the management of its information and lower-level policies specifying the rules for protecting the information. An organization could have different policies covering different applications or categories of information. For example, a Federal organization could have one set of policies covering its financial information and a different set of policies covering its personnel information. This section describes a layered set of policies, including an Information Management Policy, an Information Security Policy, and an FCKMS Security Policy.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_00132", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Contingency Planning Guide for Federal Information Systems provide? (Section 60) along with outage impacts and estimated downtime. The downtime should reflect the maximum time that an organization can tolerate while still maintaining the mission. 2. Identify resource requirements. Realistic recovery efforts require a thorough evaluation of the resources required to resume mission/business processes and related interdependencies as 14 NIST SP 800-37 further describes the RMF and provides guidance on organization-wide risk management including the development of risk management strategies, risk-related governance issues, defining protection requirements and associated risks for organizational mission/business processes, integration of security and privacy requirements into enterprise architectures, and managing risk within the system development life cycle. - \u0083 COOP functions are subject to a process-focused BIA; federal information systems are subject to a system-focused BIA. - o Information systems that support COOP functions will be identified in the process-based BIA. - o FCD-2 provides a required template for a process-based BIA; NIST 800-34 provides a recommended template for a system-based BIA. quickly as possible. Examples of resources that should be identified include facilities, personnel, equipment, software, data files, system components, and vital records. 3. Identify recovery priorities for system resources. Based upon the results from the previous activities, system resources can be linked more clearly to critical mission/business processes and functions. Priority levels can be established for sequencing recovery activities and resources. The sample BIA process and data collection activities, outlined in this section and illustrated in Figure 3-2, consisting of a representative information system with multiple components (servers), are designed to help the ISCP Coordinator streamline and focus contingency plan development activities to achieve a more effective plan.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, nist 800, rmf. General security reference material without sensitive content. Source: Contingency Planning Guide for Federal Information Systems."}]}
{"id": "nist_00133", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guidelines on Active Content and Mobile Code? (Part 45) Control ES-1: its underlying platform (e.g., system registry). The second is to use its authorized access based on the user's identity in an unexpected and disruptive fashion (e.g., invade privacy or deny service). Because browsers can support multiple associations with different Web servers as separate windowed contexts, the mobile code of one context can also target another context. Unauthorized access may occur simply through a lack of adequate access control mechanisms or weak identification and authentication controls, which allow untrusted code to act or masquerade as a trusted component. Attackers may take advantage of browser vulnerabilities in mobile code execution environments. Once access is gained, information residing at the platform can be disclosed or altered. Attackers may install spyware, connect the platform to a botnet, or modify the platform's configuration. Depending on the level of access, complete control of the platform may be taken over by the mobile code. Even without gaining unauthorized access to resources, malicious code can deny platform services to other processes by exhausting computational resources, if resource constraints are not established or not set tightly. ## 3.3.2 Server-Oriented Attacks Attacks can be launched against Web server components and technologies as the first stage of a larger scheme. For example, a browser or other utility can be used to isolate and capture a response from a server, which may be manipulated and fed back to the server in a subsequent request in an attempt to take advantage of a Web application's failure to sanitize user input. The objective is to induce the server to perform unauthorized commands provided by the browser as user input, which in turn gains an attacker access to sensitive information or control of the server.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, sso. Contains security framework guidance for authentication systems. Source: Guidelines on Active Content and Mobile Code."}]}
{"id": "nist_00134", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Control Item Text according to NIST Automation Support for Security Control Assessments_ Software Asset Management According to Automation Support for Security Control Assessments_ Software Asset Management, Control Item Text: The information system prevents program execution in accordance with [Selection (one or more): [Assignment: organization-defined policies regarding software program usage and restrictions]; rules authorizing the terms and conditions of software program usage].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_00135", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Task 8 - Evaluate ADP Backup Processing Alternatives according to NIST Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out According to Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out, Task 8 - Evaluate ADP Backup Processing Alternatives: The Contractor shall identify and compare ADP processing alternatives against those currently employed. The Contractor shall deliver a ADP Backup Processing Alternatives Report in draft form to the COTR.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out."}]}
{"id": "nist_00136", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Protecting the Confidentiality of Personally Identifiable Information (PII) say about Appendix F-Acronyms and Abbreviations? (Part 2) According to Guide to Protecting the Confidentiality of Personally Identifiable Information (PII), Appendix F-Acronyms and Abbreviations: Department of Health, Education, and Welfare | | HIPAA | Health Insurance Portability and Accountability Act | | ID | Identification | | IIF | Information in Identifiable Form | | IIHI | Individually Identifiable Health Information | | IP | Internet Protocol | | IPA | Initial Privacy Assessment | | IRS | Internal Revenue Service | | ISA | Interconnection Security Agreement | | IT | Information Technology | | ITL | Information Technology Laboratory | | MAC | Media Access Control | | NARA | National Archives and Records Administration | | NIST | National Institute of Standards and Technology | | NPPI | Non-Public Personal Information | | OECD | Organisation for Economic Co-operation and Development | | OMB | Office of Management and Budget | | OPM | Office of Personnel Management | | PDA | Personal Digital Assistant | | PHI | Protected Health Information | | PIA | Privacy Impact Assessment | | PII | Personally Identifiable Information | PRA Paperwork Reduction Act PTA Privacy Threshold Analysis SDLC System Development Life Cycle SOR System of Records SORN System of Records Notice SP Special Publication SSN Social Security Number URL Uniform Resource Locator USB", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)."}]}
{"id": "nist_00137", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain REFERENCES according to NIST Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, REFERENCES: Source Controls: CP-09, CP-09(08) Supporting Publications: SP 800-34 [52], SP 800-130 [53], SP 800-152 [54]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_00138", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 302) tf.org/rfc/rfc3748.txt [accessed 8/11/2014]. 20. B. Aboba, D. Simon, and P. Eronen, Extensible Authentication Protocol (EAP) Key Management Framework, IETF Network Working Group RFC 5247, August 2008. http://www.ietf.org/rfc/rfc5247.txt [accessed 8/11/2014]. 21. J. Salowey, L. Dondeti, V. Narayanan, and M. Nakhjiri, Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK), IETF Network Working Group RFC 5295, August 2008. http://www.ietf.org/rfc/rfc5295.txt [accessed 8/11/2014]. 22. Department of Defense, National Security Agency, Suite B Cryptography [Web page], [accessed 8/11/2014]. 23. D. McGrew, K. Igoe, and M. Salter, \u201cFundamental Elliptic Curve Cryptography Algorithms,\u201d IETF Network Working Group RFC 6090, February 2011. 24. R. Housley, and T. Polk, Planning for PKI: Best Practices Guide for Deploying Public Key Infrastructure, Wiley, NY, NY, March 2001, 352 pp. 249 APPENDIX A CROSSWALK OF CYBERSECURITY DOCUMENTS This Appendix includes a crosswalk of cybersecurity requirements of NISTIR 7628 with key source documents, NIST SP 800-53 Rev. 4 and the DHS Catalog46, and other standards47 relevant to the smart grid. The crosswalk is not an exhaustive mapping of all cybersecurity requirements and best practices applicable to the smart grid.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, key management. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_00139", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols say about 8.2 Security Encapsulation TPDU? According to Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols, 8.2 Security Encapsulation TPDU: The structure of the SE TPDU shall be as follows: <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols."}]}
{"id": "nist_00140", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet say about AN-2013 Annex G: Mapping to the NIEM IEPD? (Part 32) According to Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet, AN-2013 Annex G: Mapping to the NIEM IEPD: action Well- Formed | C.5.2, C.5.3 | All separators are defined by the W3C XMLrecommendations. The characters '<' and '>' are reserved exclusively for enclosing XMLelement names. Every element with a start tag <Name> shall have | 1 | NIEM- Well- Formed XML | Complex ( Test that the XML is well-formed according to W3C XML recommendations. | | M- Transaction | | | | X | | Req. # - ID | Ref.in Base Std. | Requirement Summary | L e v e | Assertion ID | Test Assertion | N o t e | Imp. Required | Imp. Support | Supporte d Range | Test Result | E n c .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet."}]}
{"id": "nist_00141", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Follow the requirements listed in this document, its annex, and the associated component specifications and set of schemas. according to NIST The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3 According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3, Follow the requirements listed in this document, its annex, and the associated component specifications and set of schemas.: Organizations should ensure that their implementation and use of SCAP 1.3 is compliant with the requirements detailed in each component specification, this document and its annex, and the set of schemas. If requirements are in conflict between component specifications, this document will provide clarification. If a component specification is in conflict with this document, the requirements in this document take precedence. If a component specification or this document is in conflict with the annex, the requirements in the annex take precedence. If a specification and a schema are in conflict, the requirements in the specification take precedence.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3."}]}
{"id": "nist_00142", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to NIST_SP_800-53r5_Security_Privacy_Controls? Discussion: Authorized and qualified personnel within the jurisdiction of the organization", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00143", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services provide? (Section 213) ble at Sheet.pdf Federal Aviation Administration, U.S. Department of Transportation (2021) SBAS Worldwide. Available at Federal Trade Commission (2020) Jammer Enforcement. (FCC, Washington, DC). Available at Hopkin P (2018) Fundamentals of risk management: Understanding, evaluating and implementing effective risk management. Kogan Page Publishers. Available at 20Risk%20Management.pdf?sequence=1 International Maritime Organization (2002) IMO Resolution A.915(22) Revised Maritime Policy and Requirements for a Future GNSS. (IMO, London, England). Available at Documents/A.915(22).pdf International Organization for Standardization (2018) ISO 31000:2018 - Risk management Guidelines (ISO, Geneva, Switzerland). Available at https://www.iso.org/standard/65694.html International Organization for Standardization/International Electrotechnical Commission (2018) ISO/IEC 27005:2018 - Information technology - Security techniques - Information security risk management (ISO, Geneva, Switzerland). Available at https://www.iso.org/standard/75281.html 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 Haimes, Y. Y., Kaplan, S., &amp; Lambert, J. H. (2002). Risk filtering, ranking, and management framework using hierarchical holographic modeling. Risk Analysis, 22(2), 383-397. Lambert JH, Keisler JM, Wheeler WE, Collier ZA, Linkov I (2013).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_00144", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.6 Easy Interface into 2Factor/Biometric and Other Authentication Solutions according to NIST 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings According to 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings, 4.6 Easy Interface into 2Factor/Biometric and Other Authentication Solutions: In a typical PKI system, there exists two points of authentication. One is with the CA for issuing an initial certificate which is carried out once in a long time. The other is with the media such as a smartcard that contains the private key. Authentication to the media is usually static PIN-based, as it is the media that enforces the authentication. If the protection of the media requires more complicated or stronger authentication, a lot of more complexity will have to be built into the media, resulting in higher costs. Moreover, not all media can support all forms of strong authentication. In the OTPK system, only one point of authentication (with the CA) is needed. It is carried out when a private key needs to be used. Since the authentication can be centralized to a CA or a collection of CAs, there is economy of scale in implementing a strong authentication (such as 2-factor, biometric etc) to the CA and the cost can be shared across a large pool of entities. There is also no constraint on the media. This makes it easier to integrate a strong authentication mechanism into the OTPK system. However, we do recognize that there are limitations to the implementation of the 2-factor or biometric authentication to the CA. For example, while OTP tokens are suitable for Internet-based transactions, remote authentication over Internet using biometrics is inherently insecure, and subject to replay attacks. On the other hand, using biometrics within a controlled office or a Kiosk environment for paperless eDocument systems is more convenient as compared to the OTP tokens. These considerations will have to be taken into account when designing the OTPK deployment. We envision several scenarios where OTPK can be deployed: - Internet Transactions. A merchant operates an Internet trading portal which requires the user to digitally sign transactions to signify approval. Users will login to the portal using a browser. In such case, the", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, token. Contains security framework guidance for authentication systems. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_00145", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations provide? (Section 91) ied in Key Management Specifications as being required: - Certificate serial number - Authority Key Identifier - Certificate Extensions - Certificate validity period -start and expiration dates 5. In some other applications of public key cryptography (e.g., SSH), the following information shall be specified in Key Management Specifications as being required: - Key subtype -e.g., Host private key, known host key, user private key, authorized key) 82 - Account (to which the key is associated) 79 See Section 5.3.5 of SP 800-57, Part 1. 80 May span the validity periods of successive (i.e., replaced) certificates that include the same public key. 81 If the key type is a private key, the corresponding key is the public key of the key pair; if the key type is a public key, the corresponding key is the private key of the key pair. 82 Certificates and private keys are usually stored together. Because of the explicit trust model of SSH, public keys are stored separately. Consequently, it is important to know which component is where. - Authorized key options (e.g., cert-authority, no-agent-forwarding, no-pty) 83 A Key Management Specification should address any support for the restoration of protected communications in the event of the compromise, corruption, or loss of the keying material used by the cryptographic device or application. The recovery process description should include the methods for replacing keys and/or certificates with new keys. The methods for revocation and compromise notification (e.g., using RKNs) should be provided (e.g., the details for using Certificate Revocation Lists (CRLs) and Compromised Key Lists (CKLs)). When PKI certificates are used, a description of how certificates will be reissued with new public keys and replaced within the cryptographic application should also be included. General compromise-recovery guidance is provided in Section 9.3.4 of Part 1.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations."}]}
{"id": "nist_00146", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Privacy Controls for Information Systems and Organizations provide? (Section 995) ERESTS OF CONSUMERS AND PROVIDERS PROCESSING, STORAGE, AND SERVICE LOCATION ORGANIZATION-CONTROLLED CRYPTOGRAPHIC KEYS ORGANIZATION-CONTROLLED INTEGRITY CHECKING PROCESSING AND STORAGE LOCATION \u2014 U.S. JURISDICTION Developer Configuration Management SOFTWARE AND FIRMWARE INTEGRITY VERIFICATION ALTERNATIVE CONFIGURATION MANAGEMENT PROCESSES HARDWARE INTEGRITY VERIFICATION TRUSTED GENERATION MAPPING INTEGRITY FOR VERSION CONTROL TRUSTED DISTRIBUTION SECURITY AND PRIVACY REPRESENTATIVES Developer Testing and Evaluation STATIC CODE ANALYSIS THREAT MODELING AND VULNERABILITY ANALYSES INDEPENDENT VERIFICATION OF ASSESSMENT PLANS AND EVIDENCE MANUAL CODE REVIEWS PENETRATION TESTING ATTACK SURFACE REVIEWS O/S O/S O/S O/S O/S O/S O/S O/S O/S O/S O/S O/S O/S O/S O/S O/S O/S O/S O/S O O O O O O O O O O O O O O O O O O O O O O O O \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a APPENDIX C PAGE 455 NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, penetration test. Contains technical security guidance that could inform defensive posture. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00147", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RA-3 in NIST_SP_800-53r5_Security_Privacy_Controls? (Part 5) Control RA-3: lytics capabilities to predict and identify risks to [Assignment: organization-defined systems or system components]: [Assignment: organization-defined advanced automation and analytics capabilities]. Discussion: A properly resourced Security Operations Center (SOC) or Computer Incident Response Team (CIRT) may be overwhelmed by the volume of information generated by the proliferation of security tools and appliances unless it employs advanced automation and analytics to analyze the data. Advanced automation and analytics capabilities are typically supported by artificial intelligence concepts, including machine learning. Examples include Automated Threat Discovery and Response (which includes broad-based collection, context- based analysis, and adaptive response capabilities), automated workflow operations, and machine assisted decision tools. Note, however, that sophisticated adversaries may be able CHAPTER THREE PAGE 241 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ to extract information related to analytic parameters and retrain the machine learning to classify malicious activity as benign. Accordingly, machine learning is augmented by human monitoring to ensure that sophisticated adversaries are not able to conceal their activities. Related Controls: None. References: [OMB A-130], [SP 800-30], [SP 800-39], [SP 800-161], [IR 8023], [IR 8062], [IR 8272].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00148", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Security-Focused Configuration Management of Information Systems say about GLOSSARY? (Part 11) According to Guide for Security-Focused Configuration Management of Information Systems, GLOSSARY: cle of the equipment or service), and related resources. Information technology does not include any equipment that is acquired by a contractor incidental to a contract which does not require its use. | |--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | information technology product | See system component . | | malicious code [SP 800-53] | Software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. A virus, worm, Trojan horse, or other code-based entity that infects a host. Spyware and some forms of adware are also examples of malicious code. | | malware | See Malicious malicious Ccode .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_00149", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Risk Assessment Analysis: according to NIST Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE) According to Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE), Risk Assessment Analysis:: Overall Likelihood: Very High Justification: Often applications include hard-coded credentials for the default password of the administrator account. Default passwords are readily available online. These passwords may not be changed to allow for ease of access and to eliminate the pressure of remembering a password. Level of Impact: High Justification: Successful extraction of the credentials allows an attacker to gain unauthorized access to enterprise data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_00150", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Guidelines for Storage Infrastructure say about 4.3.3 Account Management Recommendations? (Part 1) According to Security Guidelines for Storage Infrastructure, 4.3.3 Account Management Recommendations: 4.3.3 Account Management Recommendations AC-SS-R14 - Use of accounts not associated with system users: Accounts not associated with any system user (e.g., not in Active Directory, such as 'guest,' 'anonymous,' 'nobody') should be disabled. In situations where they need to be used, they should not be mapped to any system user, and all of their default configurations (e.g., password, privileges) should be changed to conform to organization-wide policies. AC-SS-R15 - Account lockout: Users should be locked out after a certain number of unsuccessful login attempts. Certain implementations of account locking include automatic reset (account unlock) after a certain period of time or a power cycle. Automatic reset should not be allowed on sensitive storage systems. AC-SS-R16 -A local user account for emergency purposes: A single local user account should be maintained for access to storage resources in order to provide emergency-only access if the centralized authentication system is down. This account should conform to all organizational policies (e.g., password length). In addition, its usage should be allowed from a special physically protected location, and following well documented procedures that include appropriate approval of relevant stakeholders, and notification of use. AC-SS-R17 - Eliminate or disable default user accounts: The default user accounts that come with the storage system installations should be eliminated or disabled immediately, if the feature exists. When the feature to disable or eliminate does not exist or there is a justified reason to keep any of those accounts, the privileges assigned to this account should be kept to the minimum necessary. AC-SS-R18 - Limit local and default user accounts: As much as possible, eliminate the use of local and default accounts. In situations where this is not possible: - (a) Limit the use of such accounts and the privileges they have.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Security Guidelines for Storage Infrastructure."}]}
{"id": "nist_00151", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Comments on this publication may be submitted to: according to NIST Codes for Identification of Federal and Federally-Assisted Organizations According to Codes for Identification of Federal and Federally-Assisted Organizations, Comments on this publication may be submitted to:: National 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 All comments are subject to release under the Freedom of Information Act (FOIA).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Codes for Identification of Federal and Federally-Assisted Organizations."}]}
{"id": "nist_00152", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security provide? (Section 44) e sub-network joins the full network; or 2) place it at the perimeter of the full network and use additional mechanisms to restrict the teleworkers to only be able to access the specified sub-network. The value of placing the remote access server at the network perimeter versus the sub-network perimeter differs for the four types of remote access methods: - \uf03c Tunneling servers usually give administrators sufficient control over the internal resources to which a teleworker has access, such that there is little advantage to setting up a tunneling server at the edge of a sub-network, as opposed to the network perimeter. - \uf03c Portal servers run the application client software on the servers themselves. Placing them at the network perimeter has a similar effect as placing them at the edge of a sub-network because the remote access user is only running applications on the portal server, not on servers inside the network. - \uf03c Remote desktop access does not involve remote access servers, so there is no issue with the placement of the remote access server. - \uf03c Direct application access servers run the application server software on the servers themselves. Placing them at the network perimeter has a similar effect as placing them at the edge of a subnetwork because the remote access user is only running applications on the direct application access server, not on servers inside the network. Thus, the only types of remote access servers that may be appropriate to place at the sub-network perimeter are portal servers and direct application access servers, but even in those two cases, it is often better to run those on the organization's perimeter so that the organization's firewall can control access to these servers for all workers, not just teleworkers. Further, to simplify management of the network and the network's security policy, running all remote access servers at the network perimeter is also advisable.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security."}]}
{"id": "nist_00153", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks provide? (Section 30) oS) attacks against other organizations, and eavesdropping on network traffic or compromising other devices on the same network segment. This goal applies to all IoT devices. 2. Protect data security. Protect the confidentiality, integrity, and/or availability of data (including PII) collected by, stored on, processed by, or transmitted to or from the IoT device. This goal applies to each IoT device except those without any data that needs protection. 3. Protect individuals' privacy. Protect individuals' privacy impacted by PII processing beyond risks managed through device and data security protection. This goal applies to all IoT devices that process PII or that directly or indirectly impact individuals. Figure 4: Risk Mitigation Goals <!-- image --> Each goal builds on the previous goal and does not replace it or negate the need for it. Meeting each of the risk mitigation goals involves addressing a set of risk mitigation areas , which are defined below. Each risk mitigation area defines an aspect of cybersecurity or privacy risk mitigation thought to be most significantly or unexpectedly affected for IoT by the risk considerations defined in Section 3. Risk mitigation areas for Goal 1, Protect Device Security: - Asset Management: Maintain a current, accurate inventory of all IoT devices and their relevant characteristics throughout the devices' lifecycles in order to use that information for cybersecurity and privacy risk management purposes. - Vulnerability Management: Identify and eliminate known vulnerabilities in IoT device software and firmware in order to reduce the likelihood and ease of exploitation and compromise. - Access Management: Prevent unauthorized and improper physical and logical access to, usage of, and administration of IoT devices by people, processes, and other computing devices. - Device Security Incident Detection: Monitor and analyze IoT device activity for signs of incidents involving device security.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks."}]}
{"id": "nist_00154", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.3.9 SECURITY IMPACT ANALYSIS according to NIST Guide for Security-Focused Configuration Management of Information Systems According to Guide for Security-Focused Configuration Management of Information Systems, 2.3.9 SECURITY IMPACT ANALYSIS: Security impact analysis is the analysis conducted by qualified staff within an organization to determine the extent to which changes to the system affect the security posture of the system. Because systems are typically in a constant state of change, it is important to understand the impact of changes on the functionality of existing security controls and in the context of organizational risk tolerance. Security impact analysis is incorporated into the documented configuration change control process. The analysis of the security impact of a change occurs when changes are analyzed and evaluated for adverse impact on security, preferably before they are approved and implemented, but also in the case of emergency/unscheduled changes. Once the changes are implemented and tested, a security impact analysis (and/or assessment) is performed to ensure that the changes have been implemented as approved, and to determine if there are any unanticipated effects of the change on existing security controls. Security impact analysis is performed as a part of the Controlling Configuration Changes phase of SecCM and supports the implementation of NIST [SP 800-53] control CM-4 Security Impact Analysis.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_00155", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PS-201 in Trustworthy Email? (Part 114) Control PS-201: f authenticated mail. A range of different users require access to these disparate private keys: - \ufffde email server must have use of the private key used for TLS and the private key must be protected. - \ufffde end user (and possibly an enterprise security administrator) must have access to private keys for S/MIME or OpenPGP message signing and key decipherment . Special care is needed to ensure that only the relevant parties have access and control over the respective keys . For federal agencies, this means compliance with all relevant policy and best practice for the protection of key material [SP800 -57pt1] and message contents (e.g., FOIA, eDiscovery, etc.). Security Consideration 7-2: Enterprises should establish a cryptographic key management system (CKMS) for keys associated with protecting email sessions with end users. For federal agencies, this means compliance with all relevant policy and best practice for the protection of key material [SP800 -57pt1]. ## 7.4.2 Confidentiality of Data at Rest \ufffdis publication is about securing email and its associated data . \ufffdis is one aspect of securing data in transit. To the extent that email comes to rest in persistent storage in mailboxes and file stores, there is some overlap with NIST SP 800-111 [SP800-111]. \ufffdere is an issue in the tradeoff between accessibility and confidentiality when using mailboxes as persistent storage. End users and their organizations are expected to manage their own private keys, and historical versions of these may remain available to enable the decryption of mail encrypted by communicating partners, and to authenticate cc: mail sent to partners, which have been also stored locally. Partners who sign their mail, and decrypt received mail, make their public keys available through certificates, or through DANE records ( i.e., TLSA, OPENPGPKEY, SMIMEA) in the DNS . \ufffdese certificates generally have a l isted expiry date and are rolled over and replaced with new certificates containing new keys .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Trustworthy Email."}]}
{"id": "nist_00156", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 152) s for which informa\ue000on \ufb02ow control is enforced by privacy \ufb01lters are de\ufb01ned; CHAPTER FOUR PAGE 62 Reference produced from open data h\ue003ps://github.com/usnistgov/oscal-content NIST SP 800-53A, REV. 5 ASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS AC-04(08) INFORMATION FLOW ENFORCEMENT | SECURITY AND PRIVACY POLICY FILTERS AC-04(08)_ODP[05] one or more of the following PARAMETER VALUES is/are selected: {block; strip; modify; quaran\ue000ne}; AC-04(08)_ODP[06] security policy iden\ue000fying ac\ue000ons to be taken a\ue002er a \ufb01lter processing failure are de\ufb01ned; AC-04(08)_ODP[07] privacy policy iden\ue000fying ac\ue000ons to be taken a\ue002er a \ufb01lter processing failure are de\ufb01ned; AC-04(08)(a)[01] AC-04(08)(a)[02] informa\ue000on \ufb02ow control is enforced using <AC-04(08)_ODP[01] security policy \ufb01lter> as a basis for \ufb02ow control decisions for <AC-04(08)_ODP[03] informa\ue000on \ufb02ows>; informa\ue000on \ufb02ow control is enforced using <AC-04(08)_ODP[02] privacy policy \ufb01lter> as a basis for \ufb02ow control decisions for <AC-04(08)_ODP[04] informa\ue000on \ufb02ows>; AC-04(08)(b) <AC-04(08)_ODP[05] SELECTED PARAMETER VALUE(S)> data a\ue002er a \ufb01lter processing failure in accordance with <AC-04(08)_ODP[06] security policy>; <AC-04(08)_ODP[05] SELECTED PARAMETER VALUE(S)> data a\ue002er a \ufb01lter processing failure in accordance with <AC-04(08)_ODP[07] privacy policy>. POTENTIAL ASSESSMENT METHODS AND OBJECTS: AC-04(08)-Examine [SELECT FROM: Access control policy; informa\ue000on \ufb02ow control policies; procedures addressing informa\ue000on \ufb02ow enforcement; system design documenta\ue000on; system con\ufb01gura\ue000on se\ue001ngs and associated documenta\ue000on; list of security policy \ufb01lters regula\ue000ng \ufb02ow control decisions; list of privacy policy \ufb01lters regula\ue000ng \ufb02ow control decisions; system audit records; system security plan; privacy plan; other relevant documents or records].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00157", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-23 in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Control SI-23: Monitoring and Damage Assessment, Behavior Validation Monitoring and Damage Assessment, Behavior Validation Detect", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_00158", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Section 64) | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | POTENTIAL ASSESSMENT METHODS AND OBJECTS Examine : [ SELECT FROM: Identification and authentication policy; password policy; procedures addressing authenticator management; system design documentation; security plan; system configuration settings and associated documentation; list of system authenticator types; change control records associated with managing system authenticators; system audit records; password configurations and associated documentation; other relevant documents or records].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00159", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identity and Access Management for Electric Utilities provide? (Section 346) 1800-2C: Identity and Access Management for Electric Utilities 243 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . attributetypes: ( 2.23.136.1.1.2 NAME 'cscaMasterList' DESC 'CSCA Master List' SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 SINGLE-VALUE X-ORIGIN 'user defined' ) dn: cn=schema changeType: modify add: objectclasses objectclasses: ( 1.3.6.1.4.1.26135.1.1.3 NAME 'ozoneAuthority' DESC '' SUP top STRUCTURAL MAY (authorizationProof $ cscaMasterList) X-ORIGIN 'user defined' ) Modify the directory using the LDIF [root@ozone bin]# ldapmodify -x -D \"cn=Directory Manager\" -W -f /usr/local/authority/bin/389SetupDirectory.ldif Enter LDAP Password: adding new entry \"uid=ozone, ou=Special Users, dc=nccoe, dc=test\" modifying entry \"ou=People, dc=nccoe, dc=test\" adding new entry \"ou=Ozone, dc=nccoe, dc=test\" modifying entry \"cn=schema\" modifying entry \"cn=schema\" 13.4 Ozone Console Server Configuration Before proceeding, ensure that OzoneAuthority has been started by running startauthority.sh on the OzoneAuthority machine. Open Ozone Console. Go to File > Properties (Figure 13-3). Enter the Ozone Authority URL. Click Select Certificate, and then select the Ozone Authority Certificate. Select SHA1withRSA as the Message Signature Algorithm. NIST SP 1800-2C: Identity and Access Management for Electric Utilities 244 Click Save to the connection information. Figure 13-3 Ozone Authority Connection Information T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . Create the publication point for the proofs: Select Publication > Add Publication Point > Add LDAP Publication Point (Figure 13-4). Enter a name for the publication point. Enter the hostname or IP address of the directory server. Enter a base context, if any.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_00160", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain IT Asset Management according to NIST IT Asset Management According to IT Asset Management, IT Asset Management: Includes Executive Summary (A); Approach, Architecture, and Security Characteristics (B); and How-To Guides (C) Michael Stone National Cybersecurity Center of Excellence Information Technology Laboratory Chinedum Irrechukwu Harry Perper Devin Wynne The MITRE Corporation McLean, VA Leah Kauffman, Editor-in-Chief National Cybersecurity Center of Excellence Information Technology Laboratory September 2018 <!-- image --> U.S. Department of Commerce Wilbur Ross, Secretary National Institute of Standards and Technology Walter G. Copan, Undersecretary of Commerce for Standards and Technology and Director", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IT Asset Management."}]}
{"id": "nist_00161", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain TECHNOLOGY PARTNERS/COLLABORATORS according to NIST Mobile Device Security_ Cloud and Hybrid Builds According to Mobile Device Security_ Cloud and Hybrid Builds, TECHNOLOGY PARTNERS/COLLABORATORS: Organizations participating in this project submitted their capabilities in response to an open call in the Federal Register for all sources of relevant security capabilities from academia and industry (vendors and integrators). The following respondents with relevant capabilities or product components (identified as 'Technology Partners/Collaborators' herein) signed a Cooperative Research and Development Agreement (CRADA) to collaborate with NIST in a consortium to build this example implementation. <!-- image --> <!-- image --> <!-- image --> <!-- image --> Certain commercial entities, equipment, products, or materials may be identified by name or company logo or other insignia in order to acknowledge their participation in this collaboration or to describe an experimental procedure or concept adequately. Such identification is not intended to imply special status or relationship with NIST or recommendation or endorsement by NIST or NCCoE; neither is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose. The National Cybersecurity Center of Excellence (NCCoE), a part of the National Institute of Standards and Technology (NIST), is a collaborative hub where industry organizations, government agencies, and academic institutions work together to address businesses' most pressing cybersecurity challenges. Through this collaboration, the NCCoE develops modular, easily adaptable example cybersecurity solutions demonstrating how to apply standards and best practices using commercially available technology.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Cloud and Hybrid Builds."}]}
{"id": "nist_00162", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives say about 6.3 Guardtime Federal and 'Perspectives from a Prime'? According to Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives, 6.3 Guardtime Federal and 'Perspectives from a Prime': As described in the Guardtime Federal questionnaire, each participant submitted a case study for a blockchain pilot they conducted to ensure traceability in the Prime's digital supply chain. The Prime's driver behind implementing a blockchain-based solution is that the company's computer networks, the software supplier's networks, and the Prime's customer, the Department of Defense (DoD), provide critical information even on unclassified networks. Blockchain offers an opportunity to layer on additional data integrity to further enhance existing measures. Guardtime Federal provided the platform for this additional layer and incorporated their own digital integrity and digital provenance solutions like the KSI\u00ae Calendar. The KSI\u00ae Calendar acted as a public, widely witnessed, common anchor that utilized hash functions to verify the provenance and integrity of the digital supply chain data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives."}]}
{"id": "nist_00163", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PM-8200 in Cell Phone Forensic Tools_ an Overview and Analysis? (Part 46) Control PM-8200: access. \u2022 Initiate the tool on a forensic workstation, attempt to connect with the device and acquire its contents, verify that the results are consistent with the known characteristics of the device. \u2022 Expect that the authentication mechanism(s) can be satisfied without affecting the tool, and information residing on the device can be retrieved. | | PIM Applications | Determine whether the tool can find information, including deleted information, associated with Personal Information Management (PIM) applications such as phone book and date book. \u2022 Create various types of PIM files on the device, selectively delete some entries, acquire the contents of the device, locate and display the information. \u2022 Expect that all PIM-related information on the device can be found and reported, if not previously deleted. Expect that remnants of deleted information can be recovered and reported. | | Dialed/Received Phone Calls | Determine whether the tool can find dialed and received phone calls, including unanswered and deleted calls. \u2022 Place and receive various calls to and from different numbers, selectively delete some entries, acquire the contents of the device, locate and display dialed and received calls. \u2022 Expect that all dialed and received phone calls on the device can be recognized and reported, if not previously deleted. Expect that remnants of deleted information can be recovered and reported. | | SMS/MMS Messaging | Determine whether the tool can find placed and received SMS/MMS messages, including deleted messages. \u2022 Place and receive both SMS and MMSmessages, selectively delete some messages, acquire the contents of the device, locate and display all messages. \u2022 Expect that all sent and received SMS/MMS messages on the device can be recognized and reported, if not previously deleted. Expect that remnants of deleted information can be recovered and reported.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_00164", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RA-9 in NIST_SP_800-53r5_Security_Privacy_Controls? (Part 1) Control RA-9: CRITICALITY ANALYSIS Control: Identify critical system components and functions by performing a criticality analysis for [Assignment: organization-defined systems, system components, or system services] at [Assignment: organization-defined decision points in the system development life cycle]. Discussion: Not all system components, functions, or services necessarily require significant protections. For example, criticality analysis is a key tenet of supply chain risk management and informs the prioritization of protection activities. The identification of critical system components and functions considers applicable laws, executive orders, regulations, directives, policies, standards, system functionality requirements, system and component interfaces, and system and component dependencies. Systems engineers conduct a functional decomposition of a system to identify mission-critical functions and components. The functional decomposition includes the identification of organizational missions supported by the system, decomposition into the specific functions to perform those missions, and traceability to the hardware, software, and firmware components that implement those functions, including when the functions are shared by many components within and external to the system. The operational environment of a system or a system component may impact the criticality, including the connections to and dependencies on cyber-physical systems, devices, system-of- systems, and outsourced IT services. System components that allow unmediated access to critical system components or functions are considered critical due to the inherent vulnerabilities that such components create. Component and function criticality are assessed in terms of the impact of a component or function failure on the organizational missions that are supported by the system that contains the components and functions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00165", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2014 Annual Report say about Cryptographic System Validation? (Part 1) According to Computer Security Division 2014 Annual Report, Cryptographic System Validation: Cryptographic System Validation Current validation programs focus on providing a known level of assurance for cryptographic algorithms and modules. These modules are used within the context of a larger system to provide cryptographic services as a method of protecting the data within the system. As information systems continue to become more complex, the methods used to implement cryptographic services have also increased in complexity. Problems with the use of cryptography are often introduced through the interaction of cryptographic components with the operating environment. This program seeks to specify how cryptographic components are used as part of a defined cryptographic system to solve problems with a measureable level of assurance, and to introduce automated methods of quantifying the level of assurance that has been provided. This program will begin the research required to define a reference cryptographic systems architecture and example use cases where cryptographic systems are built from known cryptographic components that cooperate through trust relationships to provide a measureable level of assurance. The architecture should begin at the lowest level with a hardware-based root of trust, and each cryptographic component should be added in successive layers to provide assurance in a systematic way. This should allow the development of tests that would measure the correct implementation of cryptographic components as part of a larger system. This program will perform research and experimentation in applicable technologies and techniques that will enable the efficient testing of the cryptographic capabilities of each layer, and continuous monitoring capabilities of each cryptographic component, providing the necessary interfaces to establish trust relationships with other cryptographic components.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, continuous monitoring. General security reference material without sensitive content. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_00166", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide? (Section 44) Secure Host Operating System | 3.6.1 Secure Host Operating System | | | | 3.6.2 Kernelized Secure Data Management System | 3.6.2 Kernelized Secure Data Management System | | | | 3.6.3 Back-End Data Management System 3.6.4 | Secure Subsystem Approach | 10-11 10-11 | | | 3.6.5 Classification Schemes | Encryption | 10-12 10-12 | | 3.7 | Data | Data | | | | 3.7.1 Global | 3.7.1 Global | 10-12 | | | by Data Base 3.7.2 | by Data Base 3.7.2 | 10-13 | | | Global by Record 3.7.3 Global by Field | Global by Record 3.7.3 Global by Field | 10-13 10-13 | | | 3.7.4 Privileged Program Controls 3.7.5 Formulary | 3.7.4 Privileged Program Controls 3.7.5 Formulary | 10-13 10-14 | | | | | 10-14 | | 4.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls."}]}
{"id": "nist_00167", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Management_ Part 1 \u2013 General provide? (Section 122) ere received messages are stored and decrypted at a later time, the cryptoperiod of a private static key-agreement key may exceed the cryptoperiod of the corresponding public static key-agreement key. | | Cryptoperiod | Cryptoperiod | |------------------------------|-------------------------------|------------------------| | Key Type | Originator-Usage Period (OUP) | Recipient-Usage Period | | 19. Public Authorization Key | < 2 years | < 2 years | Information other than keys does not have well-established cryptoperiods, per se. The following recommendations are offered regarding the disposition of this other information: 1. Domain parameters remain in effect until changed. 2. An IV is associated with the information that it helps to protect and is needed until the information in its cryptographically protected form is no longer needed. 3. A shared secret that is generated during the execution of a key-agreement scheme shall be destroyed as soon as it is no longer needed to derive keying material. 4. An RBG seed shall be destroyed immediately after use. 5. Other public information should not be retained longer than needed for cryptographic processing. 6. Other secret information shall not be retained longer than necessary. 7. An intermediate result shall be destroyed immediately after use. When keying material (e.g., keys, IVs, and domain parameters) is stored or distributed, it may pass through unprotected environments. In such cases, specific assurances are required before the keying material is used to perform normal cryptographic operations. Assurance of integrity shall be obtained prior to using all keying material. At a minimum, assurance of integrity shall be obtained by verifying that the keying material has the appropriate format and came from an authorized source.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_00168", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-2 in Computer Security Division 2005 Annual Report? (Part 75) Control HA-2: SP 800-87 | Codes for the Identification of Federal and Federally-Assisted Organizations | August 2005 | | SP 800-86 | Guide to Computer and Network Data Analysis: Applying Forensic Techniques to Incident Response | August 2005 | | SP 800-85 | PIV Middleware and PIV Card Application Conformance Test Guidelines | August 2005 | | SP 800-84 | Guide to Single-Organization IT Exercises | August 2005 | | SP 800-83 | Guide to Malware Incident Prevention and Handling | August 2005 | | SP 800-81 | Secure Domain Name System (DNS) Deployment Guide | August 2005 | | SP 800-77 | Guide to IPsec VPNs | January 2005 | | SP 800-76 | Biometric Data Specification for Personal Identity Verification | January 2005 | | SP 800-73 | Integrated Circuit Card for Personal Identification Verification | November 2005 | | SP 800-57 | Recommendation on Key Management | April 2005 | | SP 800-56 | Recommendation on Key Establishment Schemes | July 2005 | | SP 800-53A | Guide for Assessing the Security Controls in Federal Information Systems | July 2005 | <!-- image --> ## FEDERAL INFORMATION PROCESSING STANDARDS FIPS 201 Personal Identity Verification for Federal Employees and Contractors", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, incident response. Contains technical security guidance that could inform defensive posture. Source: Computer Security Division 2005 Annual Report."}]}
{"id": "nist_00169", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Roadmap for Successful Regional Alliances and Multistakeholder Partnerships to Build the Cybersecurity Workforce say about 3.2 Identifying Stakeholders? (Part 1) According to A Roadmap for Successful Regional Alliances and Multistakeholder Partnerships to Build the Cybersecurity Workforce, 3.2 Identifying Stakeholders: 3.2 Identifying Stakeholders Including multiple types of stakeholders in your regional alliance will increase opportunities for success. It should be clear that the stakeholders of the alliance can vary across different regions. For instance, in areas near capital cities or military presences, government agencies, in their role as employers, can be strong partners. In other areas, industry could be the primary partner for such an alliance. In addition to providing valuable insight and subject matter expertise, stakeholders may also have existing efforts that would benefit from participation in the alliance. Other groups may have tools, such as existing cyber ranges or established strategies or frameworks that can be utilized by the group. Finding synergies and identifying projects that can show early success to the community can help bring awareness and buy-in from the community. Table 1 provides an idea of the types of groups to consider when building a cybersecurity education and workforce regional alliance.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Roadmap for Successful Regional Alliances and Multistakeholder Partnerships to Build the Cybersecurity Workforce."}]}
{"id": "nist_00170", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Information Security Continuous Monitoring (ISCM) Programs_ Developing an ISCM Program Assessment provide? (Section 23) in Risk Assessment Traceability Chain.................59 | | | Figure 17 - Threat Information Traceability Chain | ........................................................59 | | Figure 18 - External Service Providers Traceability Chain | ...........................................59 | | Figure 19 - Security-focused Configuration Management Traceability Chain...............60 | | | Figure 20 - Impact of Changes to Systems and Environments Traceability Chain.......60 | | | Figure 21 - External Security Service Providers Traceability Chain | .............................60 | | Figure 22 - Security Monitoring Tools Traceability Chain | .............................................60 | | Figure 23 - Sampling Traceability Chain.......................................................................61 | | | Figure 24 - Risk Response Traceability Chain | .............................................................61 | | Figure 25 - Ongoing Authorization Traceability Chain..................................................62 | | | Figure 26 - Acquisition Decisions Traceability Chain....................................................62 | | | Figure 27 - ISCM Resources Traceability Chain | ..........................................................63 | | Figure 28 - ISCM Training Traceability Chain...............................................................63 | | | Figure 29 - Metrics Traceability Chain..........................................................................64 | | | Figure 30 - Security Status Reporting Traceability Chain.............................................65 | | | Figure 31 - Data Traceability Chain..............................................................................66 | | | Figure 32 - ISCM Program Governance Traceability Chain .........................................66 | |----------------------------------------------------------------------------------------------------------------| | Table 1 - Combining Judgments from Two Levels (Unbiased).....................................23 | | Table 2 - Combining Judgments", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Information Security Continuous Monitoring (ISCM) Programs_ Developing an ISCM Program Assessment."}]}
{"id": "nist_00171", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Security for Full Virtualization Technologies? (Part 24) Control ES-1: tal virtualization by replacing a host OS with a hypervisor may improve security, depending on how well-secured the hypervisor is, while adding a hypervisor on top of a host OS tends to increase risk. Organizations should balance security and functionality when deciding whether or not a host OS should be used under a server or desktop virtualization solution. They should also take into account that bare metal hypervisors run on a much more limited range of hardware than hosted hypervisors; for example, bare metal hypervisors often work on only a limited number of Ethernet controllers and graphics cards. Hardware emulation (sometimes called hardware translation ) is a type of hosted virtualization. The primary difference is that in hardware emulation, the hypervisor provides different hardware interfaces from those provided by the physical hardware. Because the hypervisor in hardware emulation can simulate all of the hardware required by the guest OS, it can run unmodified OSs designed for platforms different from the host platform. For example, early versions of VirtualPC allowed users to run the Microsoft Windows OS on the PowerPC processor supported by the Apple MacOS platform. Similarly, Apple supplies the Rosetta software with its Intel Mac OS X platform, allowing programs designed for the PowerPC version of Mac OS X to run on the Intel Mac platform. ## 2.3 Virtualizing Hardware For full virtualization to be effective, the virtualized hardware presented to the guest OS must resemble physical hardware extremely closely. In addition, virtualization systems must offer additional features for the virtualized hardware to help it integrate well with the physical hardware in an organization's network. This section discusses virtualized networking and storage, as well as how a guest OS is encapsulated.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Security for Full Virtualization Technologies."}]}
{"id": "nist_00172", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The Network Security Center_ a System Level Approach to Computer Network Security provide? (Section 70) orithm may be used for purposes other than communications protection and access control. The most obvious use is for protection of data files, using distinct keys to provide separation and protection. The block nature of the algorithm is well suited to random access techniques. The prime difficulty is in finding a secure way of maintaining the keys under a possibly non-secure operating system. One possible approach is for the files and encryption keys to be maintained in a facility remote from the non-secure host. This \"data vault\" would have access controlled by the NSC network mechanisms, and would be trustworthy in the storage of keys and data. This data vault might be a separate, secure device attached to a host, or it might be a self sufficient network site that operates as a host itself. The use of encryption to provide a one-way transformation for personal identification has been mentioned in Section 2.1.4. The same process can be used in other circumstances where a one-way transformation is required. Whenever data values must be verified, yet protected from exposure of their actual value, one-way transformations are valuable. Finally, in circumstances where a non-predictable sequence of values is required, the NBS Data Encryption Algorithm can be used with a simple pseudo-random number generator to generate both data values and keys to produce quite unpredictable (yet repeatable) sequences of output values. The general function of the Network Security Center (NSC) has been described in Section 1. Section 1.3.2 described the role of the NSC in authentication of identity and authorization of access requests. This section describes data structures to be used in the NSC to support these NSC functions. This section will first describe the authentication and authorization modules at an implementation independent level. Then an example implementation of a high-level specification model will be discussed.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: The Network Security Center_ a System Level Approach to Computer Network Security."}]}
{"id": "nist_00173", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AN-2011 in Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record? (Part 54) Control AN-2011: Support | Supported Range | Test Result | Applicable to (T, X, B, B*, or X*) | |---------------|----------------------------------|-----------------------|-------------------------|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------|-------------------|---------------|--------------------------------------| | | 8.18: Record Type-18: DNA record | | | | | | | | | | | | 1 1 1 1 | | - | 18.019- [ELPD, EPS]- CharType | ForEach(SubField in 18.019) { Bytes(InfoItem: 4,5 in SubField) MO[0x30 to 0x39, 0x41 to 0x5A, 0x61 to 0x7A, 0x2B, 0x2F, 0x3D] } | | | | | B* | | | | | | M | 18.021- GLR- CharType ForEach(SubField in 18.021) { Bytes(InfoItem:1 in SubField) MO[0x30 to 0x39] } | | | | | B* | | | | | | M ALP- | 18.021- CharType ForEach(SubField in 18.021) { Bytes(InfoItem:2 in SubField) MO[0x2C, 0x2E, 0x30 to 0x39] } | | | | | B* | | | | | | M GNW- | 18.021- CharType ForEach(SubField in 18.021) { Bytes(InfoItem:3 in SubField) MO[0x2E, 0x30 to 0x39] } | | | | | B* | | | 1 | | | M 18.023- [LIR, LST, LDD]- | CharType TRUE | | | | | B* | | | 1 | | - | [LEPD, | 18.023- LES]- CharType ForEach(SubField in", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record."}]}
{"id": "nist_00174", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Description according to NIST Security Analysis of First Responder Mobile and Wearable Devices According to Security Analysis of First Responder Mobile and Wearable Devices, Description: A law enforcement officer goes to a neighboring jurisdiction and has a need to share sensitive information. The application necessary to share information is not accessible through any commercial app store. The only way to install the application is to side-load the local jurisdiction's application onto the neighboring officer's public safety mobile device. The neighboring officer installs the application and receives the pertinent information.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Analysis of First Responder Mobile and Wearable Devices."}]}
{"id": "nist_00175", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Pro according to 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? Pro: Provides strong authentication without requiring access to biometric information.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_00176", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector say about 5.3.1 PR.AC-1: Identities and Credentials are Issued, Managed, Verified, Revoked, and Audited for Authorized Devices, Users, and Processes? According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector, 5.3.1 PR.AC-1: Identities and Credentials are Issued, Managed, Verified, Revoked, and Audited for Authorized Devices, Users, and Processes: This NIST Cybersecurity Framework Subcategory is supported through user authentication and user authorization capabilities in addition to the native credential management capabilities associated with the tools. In each of the systems, user accounts were issued, managed, verified, revoked, and audited.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, credential management. Contains security framework guidance for authentication systems. Source: Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector."}]}
{"id": "nist_00177", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AN-2011 in Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record? (Part 51) Control AN-2011: Support | Supported Range | Test Result | Applicable to (T, X, B, B*, or X*) | |---------------|----------------------------------|----------------------------------|----------------------------------|---------------------------------------------------|--------------------------------------------------------------------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|--------------------------------------| | | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | | | | 1 - | | CharType 18.015- [PRF, SUP, DPC]- CharType | TRUE | | | | | B* | | | | 1 | M | 18.016- [DST, DLR, ALL, LAI, PCDT, KID]- CharType | ForEach(SubField in 18.016) { Bytes(InfoItem: 1 to 5, 12 in SubField) MO[0x30 to 0x39) } | | | | | B* | | | | 1 | D | 18.016- [AL1, AL2, AL3]- CharType | ForEach(SubField in 18.016) { Bytes(InfoItem: 6 to 8 in SubField) MO[0x30 to 0x39, 0x2E) } | | | | | B* | | | | 1 | - | 18.016- [BID, ECR, LCR, KNM, KMF, KDS]- CharType | TRUE | | | | | B* | |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record."}]}
{"id": "nist_00178", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain A. Agenda according to NIST Enhancing Resilience of the Internet and Communications Ecosystem_ A NIST Workshop Proceedings According to Enhancing Resilience of the Internet and Communications Ecosystem_ A NIST Workshop Proceedings, A. Agenda: The following pages present the public agenda for the workshop as posted before the workshop. There were two 'day-of' agenda changes: Carlos Morales from Arbor Networks participated in the first panel (Communications Infrastructure) on behalf of Arabella Harrington; and Craig Hyps from Cisco participated in the second panel (Products) in Eric Wenger's stead.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Enhancing Resilience of the Internet and Communications Ecosystem_ A NIST Workshop Proceedings."}]}
{"id": "nist_00179", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings provide? (Section 209) e, this is required to access TeraGrid), or will have to prove independently that their site authentication was sufficiently strong. This assurance level can subsequently be managed as a VO attribute. CERN has taken this approach with their internationally approved MICS CA: it issues certificates only to users in the site database with one of fourteen different status, and one type of external contractors. Each of those status flags ensures that the user has shown appropriate photo id to the CERN user office. Finally, for access to, e.g., certain medical images (non-anonymised), or financial data, it may be that medium assurance is not strong enough. High assurance cannot be provided within this PKI, partly because we have no explicit commitment from the institutions. Rather, it would have to be provided by either a separate CA, or with special certificates issued by the e-Science CA with flags (e.g., policy OID) to mark it as high assurance. This work is funded by the National Grid Service in line with its provision of a national Grid CA and Grid support; the closely related work in ShibGrid and SHEBANGS is funded by the UK Joint Information Systems Committee (JISC) under the current (Apr '04-Apr '07) core middleware development programme. This document typeset with L A T E X. In this paper, we have described an architecture for a Grid PKI for the UK National Grid Service, NGS, deployed alongside and interoperating with the national Shibboleth deployment, as well as the existing global Grid PKI. The work aims to provide 'NGS access for the masses' and be scalable to a large number of users, and to improve usability for non-technical users by making-for certain types of client tools-the entire certificate and proxy issuance process hidden from the user. We have described how the deployment is lightweight, requiring no legally binding commitment on behalf of the institutions.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_00180", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity say about C.1 IoT Cybersecurity Capabilities Mapping? (Part 1) According to Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity, C.1 IoT Cybersecurity Capabilities Mapping: C.1 IoT Cybersecurity Capabilities Mapping Table 5-7 below lists the device cybersecurity capabilities and nontechnical supporting capabilities as they map to the NIST Cybersecurity Framework Subcategories of particular importance to this project. It is acknowledged that IoT devices vary in their capabilities, and there may not be a clear delineation between the device cybersecurity capabilities that are provided by the IoT devices and those provided by another system component. It is also understood that the capabilities of cyber-physical components are evolving, so many of the mappings are not necessarily exact. The mapping presents a summary of both technical and nontechnical capabilities that could enhance the security of an IIoT DER ecosystem. It is acknowledged that many of the device cybersecurity capabilities may not be available in modern IoT devices and that other system elements (e.g., proxies, gateways) or other risk mitigation strategies (e.g., network segmentation) may be necessary.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity."}]}
{"id": "nist_00181", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2016 NIST_ITL Cybersecurity Program Annual Report say about P H A S E 4? According to 2016 NIST_ITL Cybersecurity Program Annual Report, P H A S E 4: - Integrate the final version into the operational CMVP program. Currently, the project is focused on completing the documentation of the technical approach for automating the algorithm testing and researching the approaches for automating the software module testing. The team working on this project, in collaboration with the industry, demonstrated successful automated algorithm validations at the International Cryptographic Module Conference in May 2017 for some algorithms (see acvp/home) and continues to develop the automation of the rest of algorithms currently tested by the traditional Cryptographic Algorithm Validation Program ( nist.gov/groups/STM/cavp/index.html) with the goal of replacing it by the second quarter of 2018. The project activities are structured by work areas in order for subject-matter experts to more narrowly focus and make progress. 1. Algorithm and Protocol Testing; 2. Cryptographic Module Testing, - a. Hardware, - b. Software, and - c. Modules in cloud environments; and 3. Positioning and relationships to other Government Validation Programs. The project has several planned deliverables, including the identification of prospective technical approaches that adopt industry best practices and produce artifacts that are machine readable and map to DTR requirements, and a selection of the best technical and feasible approaches.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_00182", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems say about Appendix F. Smart Inverter Vulnerability Survey? (Part 15) According to Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems, Appendix F. Smart Inverter Vulnerability Survey: . | 5-Aug-17 | V3.0: 7.5 HIGH | | 21 | CVE- 2015- 3964 | SMA Solar Sunny WebBox has hardcoded passwords, which makes it easier for remote attackers to obtain access via unspecified vectors. | 11-Sep-15 | V3.x:(not available) | | 22 | CVE- 2018- 7797 | A URL redirection vulnerability exists in Power Monitoring Expert, Energy Expert (formerly Power Manager) - EcoStruxure Power Monitoring Expert (PME) v8.2 (all editions), EcoStruxure Energy Expert 1.3 (formerly Power Manager), EcoStruxure Power SCADA Operation (PSO) 8.2 Advanced Reports and Dashboards Module, EcoStruxure Power Monitoring Expert (PME) v9.0, EcoStruxure Energy Expert v2.0, and EcoStruxure Power SCADA Operation (PSO) 9.0 Advanced Reports and Dashboards Module, which could cause a phishing attack when redirected to a malicious site. | 17-Dec-18 | V3.0: 6.1 MEDIUM | | 23 | CVE- 2012- 5864 | The management web pages on the Sinapsi eSolar Light Photovoltaic System Monitor (aka Schneider Electric Ezylog photovoltaic SCADA management server), Sinapsi eSolar, and Sinapsi eSolar DUO with firmware before 2.0.2870_2.2.12 do not require authentication, which allows remote attackers to obtain administrative access via a direct request, as demonstrated by a request to ping.php. | 23-Nov-12 | V3.x:(not available) | | 24 | CVE- 2012- 5863 | ping.php on the Sinapsi eSolar Light Photovoltaic System Monitor (aka Schneider Electric Ezylog photovoltaic SCADA management server), Sinapsi eSolar, and Sinapsi eSolar DUO with firmware before 2.0.2870_2.2.12 allows remote attackers to execute arbitrary commands via shell metacharacters in the ip_dominio parameter.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, cve-. Contains technical security guidance that could inform defensive posture. Source: Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems."}]}
{"id": "nist_00183", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways say about 7.3.2 Java Removal Policy? (Part 4) According to Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways, 7.3.2 Java Removal Policy: Java\" NOT_COND_UPDATE=\"true\" RECHECK_MAIN_RULE_DEF=\"true\"> <MATCH_TIMING RATE=\"28800\" SKIP_INACTIVE=\"true\"> <ADMISSION ALL=\"true\"/> </MATCH_TIMING> <EXPRESSION EXPR_TYPE=\"SIMPLE\"> <!--Rule expression. Rule name is: Runing Java--> <CONDITION EMPTY_LIST_VALUE=\"false\" FIELD_NAME=\"process_no_ext\" LABEL=\"Windows Processes Running\" LEFT_PARENTHESIS=\"0\" LOGIC=\"AND\" PLUGIN_NAME=\"HPS Inspection Engine\" PLUGIN_UNIQUE_NAME=\"va\" PLUGIN_VESRION=\"11.1.2\" PLUGIN_VESRION_NUMBER=\"111020046\" RET_VALUE_ON_UKNOWN=\"UNMATCH\" RIGHT_PARENTHESIS=\"0\"> <FILTER CASE_SENSITIVE=\"false\" FILTER_ID=\"3138188613733535094\" TYPE=\"contains\"> ``` ``` <VALUE VALUE2=\"Java\"/> </FILTER> </CONDITION> </EXPRESSION> <ACTION DISABLED=\"false\" NAME=\"add-to-group\"> <PARAM NAME=\"temporary\" VALUE=\"true\"/> <PARAM NAME=\"group-name\" VALUE=\"id:3761570262828389651;name:Java Running\"/> <PARAM NAME=\"item_key\" VALUE=\"mac_or_ip\"/> <PARAM NAME=\"comment\" VALUE=\"\"/> <SCHEDULE> <START Class=\"Immediately\"/> <OCCURENCE onStart=\"true\"/> </SCHEDULE> </ACTION> </INNER_RULE> </RULE_CHAIN> <REPORT_TABLES/> </RULE> </RULES> ```", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_00184", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Study of OSI Key Management provide? (Section 220) nition of the Association Control Service Element - [ISO 8649/ADl] ISO 8649, Information Processing Systems -Open Systems Interconnection Service Definition of the Association Control Service element. Addendum1: Peer entity authentication during association establishments. - [ISO 8650] ISO 8650, Information Processing Systems -Open Systems Interconnection -Protocol Specification for the Association Control Service Element. - [ISO 8650/ADl] ISO 8650, Information Processing Systems -Open Systems Interconnection -Protocol Specification for the Association Control Service Element, Addendum 1: Peer entity authentication during association establishments. - [ISO 8732] ISO 8732, Banking - Key management (wholesale). - [ISO 8824] ISO 8824, Information Processing Systems -Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.l). - [ISO 8825] ISO 8825, Information Processing Systems -Open Systems Interconnection -Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.l). - [ISO 9545] ISO/IEC 9545, Information Processing Systems -Open Systems Interconnection - Application Layer Structure. - [ISO 9545/Pl] ISO/IEC 9545/PDAMl, Information Processing Systems - Open Systems Interconnection -Application Layer Structure, Proposed Draft Amendment. - [ISO 9072-1] ISO 9072, Information Processing Systems -Text Communication -Remote Operations Part 1: Model, Notation and Service Definition, International Organization for Standardization and International Electrotechnical Committee. - [ISO 9072-2] ISO 9072, Information Processing Systems -Text Communication -Remote Operations Part 2: Protocol Specification, International Organization for Standardization and International Electrotechnical Committee. - [ISO 9594-1] ISO 9594, Information Technology - Open Systems Interconnection - The Directory - Part 1: Overview of concepts, models and services.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: A Study of OSI Key Management."}]}
{"id": "nist_00185", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Managing Information Security Risk_ Organization, Mission, and Information System View provide? (Section 153) | All components of an information system to be authorized for operation by an authorizing official and excludes separately authorized systems, to which the information system is connected. | | Authorizing Official [CNSSI 4009] | Senior (federal) official or executive with the authority to formally assume responsibility for operating an information system at an acceptable level of risk to organizational operations (including mission, functions, image, or reputation), organizational assets, individuals, other organizations, and the Nation. | | Availability [44 U.S.C., Sec. 3542] | Ensuring timely and reliable access to and use of information. | | Chief Information Officer [PL 104-106, Sec. 5125(b)] | Agency official responsible for: (i) Providing advice and other assistance to the head of the executive agency and other senior management personnel of the agency to ensure that information technology is acquired and information resources are managed in a manner that is consistent with laws, Executive Orders, directives, policies, regulations, and priorities established by the head of the agency; (ii) Developing, maintaining, and facilitating the implementation of a sound and integrated information technology architecture for the agency; and (iii) Promoting the effective and efficient design and operation of all major information resources management processes for the agency, including improvements to work processes of the agency. | | Chief Information Security Officer | See Senior Agency Information Security Officer . | | Classified National Security Information [CNSSI 4009] | Information that has been determined pursuant to Executive Order 13526 or any predecessor order to require protection against unauthorized disclosure and is marked to indicate its classified status when in documentary form.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, national security. Contains guidance on protecting sensitive government information. Source: Managing Information Security Risk_ Organization, Mission, and Information System View."}]}
{"id": "nist_00186", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is https according to Securing Electronic Health Records on Mobile Devices? https: //www.nccoe.nist.gov/sites/default/files/library/sp1800/hit-ehr-nist-sp1800-1-draft.pdf", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Electronic Health Records on Mobile Devices."}]}
{"id": "nist_00187", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security provide? (Section 25) hrough remote access are hardened appropriately against external threats 7 and that access to the resources is limited to the minimum necessary through firewalling and other access control mechanisms. See Section 2.3 for information on security concerns specific to BYOD and third-party-controlled client devices. Section 2.2 describes remote access technologies and discusses security considerations for each, focusing on the elements described above. Organizations have many options for providing remote access to their computing resources. As previously mentioned, remote access methods can also be used to enable access to internal resources for BYOD and third-party-controlled client devices attached to an organization's wireless BYOD networks. For the purposes of this publication, the remote access methods most commonly used for teleworkers have been divided into four categories based on their high-level architectures: tunneling, portals, remote desktop access, and direct application access. The remote access methods in all four categories have some features in common: - \uf03c They are all dependent on the physical security of the client devices. - \uf03c They can use multiple types of server and user authentication mechanisms. This flexibility allows some remote access methods to work with an organization's existing authentication mechanisms, such as passwords or certificates. Some remote access methods have standardized authentication mechanisms, while others use implementation-specific mechanisms. - \uf03c They can use cryptography to protect the data flowing between the telework client device and the organization from being viewed by others. This cryptographic protection is inherent in VPNs and cryptographic tunneling in general, and it is an option in most remote desktop access and direct application access systems.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security."}]}
{"id": "nist_00188", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information 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? (Section 127) it and Variance Detection Software Maintenance Controls Documentation SECURITY AWARENESS AND TRAINING -security awareness and training of users and technical staff concerning the application system. Security Awareness and Training Measures TECHNICAL CONTROLS -hardware and software controls to provide automated protections. User Identification and Authentication Authorization/Access Controls Data Integrity/Validation Controls Audit Trails and Journaling SUPPORT SYSTEM SECURITY MEASURES -adequate security measures are provided by the facility ( ies) , network, etc. where the application system is processed. Security Measures for Support System (s) The following categories of security controls should be addressed for systems which have been identified as General ADP Support Systems. MANAGEMENT CONTROLS -overall management controls of the support system. Assignment of Security Responsibility Risk Analysis/Assessment Personnel Selection/Screening DEVELOPMENT/INSTALLATION -procedures to build protection into the computer system. Acquisition Specifications Certification/Accreditation OPERATIONAL CONTROLS -day-to-day procedures and mechanisms to protect operational systems. Physical and Environmental Protection Production, I/O Controls Emergency, Backup and Contingency Plans Audit and Variance Detection System Software Controls Documentation SECURITY AWARENESS AND TRAINING -security awareness and training of technical staff and users of the system. Security Awareness and Training Measures TECHNICAL CONTROLS -hardware and software controls in the system to provide automated protections. User Identification and Authentication Authorization/Access Controls Audit Trail Mechanisms Confidentiality Controls (e.g., encryption) Integrity Controls (e.g., message authentication) APPLICATION SYSTEM CONTROLS -adequate security measures are in application systems which operate on the subject general purpose system. Security measures for application systems.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)."}]}
{"id": "nist_00189", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Technical Solution Overview according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case, Technical Solution Overview: System use monitoring is accomplished by multiple tools to protect manufacturing system environment from harmful activities using data loss protection, system hardening and syslog server for monitoring, store and auditing. Each tool provides a different level required to protect the manufacturing system. Implementation effort is moderate requiring understanding of Linux systems, along with virtual machine experience.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, rmf, fips. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case."}]}
{"id": "nist_00190", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings say about Foreward? (Part 2) According to 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings, Foreward: t level may be one reason that DNSSEC deployment has been slow. A panel on Domain Keys Identified Mail (DKIM), which leverages the DNS for key distribution, was held on the second day of the workshop. DKIM would seem to provide the incentive for attacking the DNS, so perhaps DNSSEC deployment will become a more urgent requirement. Phillip Hallam-Baker's presentation on the DKIM panel, 'Achieving Email Security Luxury' proposed leveraging DKIM, XKMS, and the PKIX logotype extension to create a comprehensive and compelling solution for securing applications and the infrastructure. Another theme of the workshop was the convergence of PKI and other technologies. Jeffrey Altman's presentation highlighted progress in the convergence of PKI and Kerberos. A decade's efforts have produced PK-INIT, PK-CROSS, and PK-APP, forming a comprehensive suite of standards. PK-INIT and PK-APP allow users to leverage PKI certificates to obtain Kerberos credentials, and vice versa. PK-CROSS supports the establishment of Kerberos cross realm relationships with PKI credentials. The 'Identity Federation and Attribute-based Authorization through the Globus Toolkit, Shibboleth, GridShib, and MyProxy' presentation described the integration of the Grid PKIs, Security Assertion Markup Language (SAML), Kerberos, and one time passwords to support authorization decisions for Grid computing. Identifying and resolving revocation issues continues to be a topic of critical interest. This year's workshop featured two presentations at very different levels of abstraction. Kelvin Yiu's invited talk focused on challenges that had to be faced and compromises required to make revocation usable for consumers in the forthcoming Vista operating system. Santosh Chokhani explored some of the more arcane nuances of the X.509 standard, and their implications for real PKI deployments.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, pki. Contains security framework guidance for authentication systems. Source: 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings."}]}
{"id": "nist_00191", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain AS06.04.09: The digestAlgorithm field specified in the SignerInfo field is in accordance with Table 3-7 of SP 800-78. according to NIST PIV Data Model Test Guidelines According to PIV Data Model Test Guidelines, AS06.04.09: The digestAlgorithm field specified in the SignerInfo field is in accordance with Table 3-7 of SP 800-78.: No requirement for vendor. TE06.04.09.01: The tester shall validate that the digest algorithm in the SignerInfo is based on the expiration date of the PIV card and is in accordance with Table 3-7 of SP80078. ignerInfo field shall be in AS06.04.10: The signatureAlgorithm field specified in the S accordance with Table 3-4 of SP 800-78 and based on the PIV card expiration date in accordance with Table 3-3 of SP 800-78. No requirement for vendor. based on the expiration date of the certificate and is in accordance with Table 3-4 of SP80078. TE06.04.10.01: The tester shall validate that the signature algorithm is", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_00192", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4 Host Protection according to NIST Information System Security Best Practices for UOCAVA-Supporting Systems According to Information System Security Best Practices for UOCAVA-Supporting Systems, 4 Host Protection: The two major parts of an electronic voting system that need to be protected are the computers (hosts) on which processing happens and the network that is between those computers. This section covers how to protect the computers; Section 5 covers how to protect the network. Both parts of an electronic voting system also have ongoing protection such as audits and policy reviews; these are covered in Section 6.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Information System Security Best Practices for UOCAVA-Supporting Systems."}]}
{"id": "nist_00193", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Computer Security Log Management? (Part 22) Control ES-1: nts occurring within an organization's systems and networks. Logs are composed of log entries; each entry contains information related to a specific event that has occurred within a system or network. Originally, logs were used primarily for troubleshooting problems, but logs now serve many functions within most organizations, such as optimizing system and network performance, recording the actions of users, and providing data useful for investigating malicious activity. Logs have evolved to contain information related to many different types of events occurring within networks and systems. Within an organization, many logs contain records related to computer security; common examples of these computer security logs are audit logs that track user authentication attempts and security device logs that record possible attacks. This guide addresses only those logs that typically contain computer security-related information. 1 Because of the widespread deployment of networked servers, workstations, and other computing devices, and the ever-increasing number of threats against networks and systems, the number, volume, and variety of computer security logs has increased greatly. This has created the need for computer security log management , which is the process for generating, transmitting, storing, analyzing, and disposing of computer security log data. This section of the document discusses the needs and challenges in computer security log management. Section 2.1 explains the basics of computer security logs. Section 2.2 discusses the laws, regulations, and operational needs involved with log management. Section 2.3 explains the most common log management challenges, and Section 2.4 offers high-level recommendations for meeting them. ## 2.1 The Basics of Computer Security Logs Logs can contain a wide variety of information on the events occurring within systems and networks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Computer Security Log Management."}]}
{"id": "nist_00194", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Specification for Asset Identification 1.1 provide? (Section 59) res identifying information about a website. | Captures identifying information about a website. | Captures identifying information about a website. | Captures identifying information about a website. | | Properties | Name | Type | Count | Definition | | | document- root | literal - token | 0-1 | The absolute path to the document root location of the website on the host. | | | locale | literal - token | 0-1 | The locale of the website represented as an RFC 5646 language, and optionally, region code. Language and region codes SHOULD be in the Internet Assigned Numbers Authority (IANA) Language Subtag Registry [ILSR]. Regex: [a-zA-Z]{2,3}(-([a-zA-Z]{2}|[0-9]{3}))?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Specification for Asset Identification 1.1."}]}
{"id": "nist_00195", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Test Results and Records according to NIST Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework According to Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework, Test Results and Records: 1. Tester shall record all Required Vendor Information that was used for the test. 2. The test passes if all Test Steps complete successfully and Tester was able to positively confirm step 1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework."}]}
{"id": "nist_00196", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Secure Web Services provide? (Section 46) Specifications and Standards Addressing Security of SOAs | Dimension | Requirement | Specifications | |---------------------|-------------------------------|----------------------------| | Messaging | Confidentiality and Integrity | WS-Security | | Messaging | Confidentiality and Integrity | SSL/TLS | | Messaging | Authentication | WS-Security Tokens | | Messaging | Authentication | SSL/TLS X.509 Certificates | | Resource | Authorization | XACML | | Resource | Authorization | XrML | | Resource | Authorization | RBAC, ABAC | | Resource | Privacy | EPAL | | Resource | Privacy | XACML | | Resource | Accountability | None | | Negotiation | Registries | UDDI | | Negotiation | Registries | ebXML | | Negotiation | Semantic Discovery | SWSA | | Negotiation | Semantic Discovery | OWL-S | | Negotiation | Business Contracts | ebXML | | Trust | Establishment | WS-Trust | | Trust | Establishment | XKMS | | Trust | Establishment | X.509 | | Trust | Trust Proxying | SAML | | Trust | Trust Proxying | WS-Trust | | Trust | Federation | WS-Federation | | Trust | Federation | Liberty IDFF | | Trust | Federation | Shibboleth | | Security Properties | Policy | WS-Policy | | Security", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, token. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services."}]}
{"id": "nist_00197", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PA-5060 in Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation? (Part 128) Control PA-5060: d objectives. - \uf0a7 Operations and maintenance personnel will need to understand these standards to the extent that these personnel will enable the staff to support day-today RPKI -based ROV operations. ## B.3 ISP Versus Enterprise Training Requirements There is not necessarily a strict distinction between the type of RPKI -based ROV training that is needed at enterprises versus that which is needed at ISPs. Rather, the type of training that is required depends more on the roles that each organization assumes with respect to RPKI -based ROV. All ISPs have dual RPKI -based ROV roles, in the sense that they serve as both network operators and address holders. In their capacity as network operators, they are concerned with obtaining and using RPKI information to perform ROV; in their capacity as address holders, they are concerned wit h creating route origin authorizations (ROAs) to help protect their addresses from being hijacked. Hence, the ISP staff need training in both the ROV-related and RPKI -related areas. Unlike ISPs, enterprises do not necessarily need to perform ROV. Instead, an enterprise may rely on its service provider to perform ROV on its behalf. If an enterprise does not perform ROV, then its staff does not need training in ROV-related areas; however, if the enterprise does perform ROV, then its staff will need the same ROV training as the ISP staff. Assuming that an enterprise is an address holder, it will need training in RPKI -related areas. One important difference between the RPKI training neede d at ISPs versus enterprises stems from the fact that an ISP has a choice of deploying either the hosted or delegated model of RPKI, where as an enterprise will always use the hosted model.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, pki. Contains security framework guidance for authentication systems. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_00198", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.2.1 Host and Network Configuration according to NIST Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector, 2.2.1 Host and Network Configuration: Dragos is installed and configured to support the CRS Environment in Build 3. The overall build architecture is shown in Figure B-3, and the Dragos specific components are listed in Table 2-4. Table 2-4 Dragos Deployment | Name | System | OS | CPU | Memory | Storage | Network | |---------------|----------------|-----------------------|-------------------|----------|--------------------------------|----------------------------| | VMware Server | Dell OEMR R740 | VMware 6.7.0 Update 3 | 2x Intel 6130 CPU | 384 GB | 2x 1.5TB Mirror 6x 8TB RAID 10 | Testbed LAN 10.100.0.62/24 | | Dragos Server | VMware | CentOS 7 | 48x vCPU | 192 GB | 215 GB 10 GB 1.5 TB 1.5 TB | Testbed LAN 10.100.0.63/24 | | Dragos Sensor | Dell OEM | CentOS 7 | 64x vCPU | 128 GB | 240 GB 1 TB | Testbed LAN 10.100.0.64/24 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector."}]}
{"id": "nist_00199", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach say about Table of Contents? (Part 23) According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach, Table of Contents: | 4.6.5.1 | Introduction | 154 | | | 4.6.5.2 | Programming and Training Phase Audit Tests | 154 | | | 4.6.6 Audit Results/Reporting | 4.6.6 Audit Results/Reporting | 154 | | | 4.6.6.1 | Potential Deficiencies | 155 | | | 4.6.6.2 | Potential Effects of Deficiencies on Meeting System Mission | 155 | | | 4.6.7 | Reassess Audit Strategy | 156 | | 4.7 | AUDIT PARTICIPATION IN THE EVALUATION AND ACCEPTANCE PHASE -PHASE V | AUDIT PARTICIPATION IN THE EVALUATION AND ACCEPTANCE PHASE -PHASE V | 163 | | | 4.7.1 Primary Audit Objective of the Evaluation and Acceptance Phase | 4.7.1 Primary Audit Objective of the Evaluation and Acceptance Phase | 163 | i | 4.7.2 | Overview of the Evaluation and Acceptance Phase | Overview of the Evaluation and Acceptance Phase | 164 | |-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|---------| | | 4J.2.1 | Participants and Their Tasks | 164 | | | 4.7.2.2 | Evaluation and Acceptance Phase Document | 166 | | 4.7.3 | Audit Survey | Audit Survey | 166 | | | 4.7.3.1 | Review Programming and Training Phase Outputs | 166 | | | 4.7.3.2 | Review Evaluation and Acceptance Phase Plans |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach."}]}
{"id": "nist_00200", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i say about 4.1 Features of RSNs? (Part 1) According to Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i, 4.1 Features of RSNs: 4.1 Features of RSNs With the addition of the IEEE 802.11i amendment in 2004, IEEE 802.11 offers two general classes of security capabilities for IEEE 802.11 WLANs. The first class, pre-RSN security, includes the legacy security capabilities developed in the original IEEE 802.11 specification: open system or shared key authentication for validating the identity of a wireless station, and WEP for the confidentiality protection of traffic. The second class of security capabilities includes a number of security mechanisms to create RSNs. An RSN includes security enhancements to address all the known flaws of WEP and provide robust protection for the wireless link, including data integrity and confidentiality. Figure 4-1 provides a high-level taxonomy of the major pre-RSN and RSN security mechanisms. Figure 4-1. Taxonomy for Pre-RSN and RSN Security <!-- image --> At a high level, RSN includes IEEE 802.1X port-based access control, key management techniques, and the TKIP and CCMP data confidentiality and integrity protocols. Described in Section 4.3, these protocols allow for the creation of several diverse types of security networks because of the numerous configuration options. RSN security is at the link level only, 24 providing protection for traffic between a wireless STA and its associated AP, or between one wireless STA and another wireless STA. It does not provide end-to-end application-level security, such as between a STA and an e-mail or Web server on the DS, because communication between these entities requires more than just one link. To provide end-toend security, organizations can implement network level security mechanisms such as Transport Layer Security (TLS) or IPsec. Also, RSN's security features apply only to the wireless portion of the overall network, not to communications on wired networks. As shown in Figure 4-2, the security provided in an RSN can apply to both IEEE 802.11 modes of operation, BSS (infrastructure mode) and IBSS (ad hoc mode).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, key management. Contains security framework guidance for authentication systems. Source: Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i."}]}
{"id": "nist_00201", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does U.S. Department of Energy Risk Assessment Methodology say about MASTER LIST OF DOE SECURITY REQUIREMENTS? (Part 9) According to U.S. Department of Energy Risk Assessment Methodology, MASTER LIST OF DOE SECURITY REQUIREMENTS: | FIRE PROTECTION | e. | | 5500. 7A | ESSENTIAL AND VITAL RECORDS PROTECTION PROGRAM | ESSENTIAL AND VITAL RECORDS PROTECTION PROGRAM | A | | 5610.2 | CONTROL OF WEAPON DATA | CONTROL OF WEAPON DATA | V. | | 5630.8 | SAFEGUARDING OF NAVAL NUCLEAR PROPULSION INFORMATION | SAFEGUARDING OF NAVAL NUCLEAR PROPULSION INFORMATION | h. | | 5630.13 | MASTER SAFEGUARDS AND SECURITY AGREEMENTS | MASTER SAFEGUARDS AND SECURITY AGREEMENTS | w. | | * 5631. 1A | SECURITY EDUCATION PROGRAM | SECURITY EDUCATION PROGRAM | | | 5631.28 | PERSONNEL SECURITY PROGRAM | PERSONNEL SECURITY PROGRAM | 9' i.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: U.S. Department of Energy Risk Assessment Methodology."}]}
{"id": "nist_00202", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 441) ements, identify areas where policies are not being followed, and so on. An audit should ideally be performed by an objective entity that is independent of the entity being audited. Privacy Use Cases. A Privacy Use Case is a method of looking at data flows that will help entities within the smart grid to rigorously track data flows and the privacy implications of collecting and using data. It is intended to help organizations address and mitigate the associated privacy risks within common technical design and business practices. Use cases can help smart grid architects and engineers build privacy protections into the smart grid. Privacy protection designed into a system is preferable to a privacy patch or \"work around\" in an attempt to remedy a limitation or omission. The Privacy Use Cases presented in Appendix E of this document are focused on data privacy in selected smart grid scenarios109, making them unique amongst the many tools, frameworks, and standards that are noted above. These Privacy Use Cases reflect the electricity value chain and the impacts that smart grid technologies, new policies, new markets, and new consumer interactions will have on the privacy of personal data. The Privacy Use Cases can serve as a valuable tool for all types of smart grid entities to better understand the implications of smart grid changes to existing processes and procedures. These smart grid entities include utilities; energy service companies (ESCOs); vendors of products and services that may include collection, storage, or communication of personal data; and policy-makers. When the general privacy concerns have been identified, the entities within each part of the smart grid can then look at their associated smart grid business processes and technical components to determine which privacy concerns exist within their scope of smart grid use and participation.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_00203", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendations for Federal Vulnerability Disclosure Guidelines say about 2.7.3.1. National Cyber Awareness System? According to Recommendations for Federal Vulnerability Disclosure Guidelines, 2.7.3.1. National Cyber Awareness System: The National Cyber Awareness System (NCAS) contains five products that provide information on vulnerabilities and related threats [CISA] to technical users: 1. Current Activity - provides details on the most frequent, high-impact types of security incidents currently being reported 2. Alerts - provides timely information about current security issues, vulnerabilities, and exploits 3. Bulletins - provides a weekly summary of the newest vulnerabilities 4. Analysis Reports - provides in-depth analysis on new or evolving cyber threats 5. Industrial Control System (ICS) - provides timely information about current security issues, vulnerabilities, and exploits", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Recommendations for Federal Vulnerability Disclosure Guidelines."}]}
{"id": "nist_00204", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is References according to NIST_SP_800-53r5_Security_Privacy_Controls? References: [OMB A-130], [SP 800-37], [SP 800-39], [SP 800-55], [SP 800-137].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00205", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SC-29(1) in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Control SC-29(1): Restriction Preempt", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_00206", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Guide to IPsec VPNs? (Part 208) Control HA-1: n from network layer security controls, such as network-based intrusion detection systems-necessitating the use of additional, host-based security controls that can monitor application layer activity. Having separate controls for each application also complicates or precludes centralized enforcement of security policies across multiple applications, as well as centralized authentication (unless each application supports the use of a third-party authentication server.) The organization considers the network layer and transport layer options to be the most feasible for meeting its remote access needs. The data link layer and application layer solutions are too expensive compared to the network and transport layer solutions. Further investigation of the transport layer solution determines that it is not possible or practical to provide web-based interfaces for several of the desired IT resources. For example, some of the desired applications are off-the-shelf products that offer no web-based client. A terminal server solution could provide access, but this would require users to connect to the terminal server and authenticate before accessing any applications. Each host would also need the terminal server client to be installed and configured. Using an SSL-based VPN would only encrypt communication from the remote endpoint to the SSL VPN gateway and would not encrypt communication between the SSL VPN server and the resources within the internal network. After comparing the three remaining solutions (remote access network layer VPN, gateway-togateway network layer VPN, and terminal server transport layer VPN) and considering how each solution would be deployed in the organization's environment, the organization chooses the gateway-to-gateway network layer VPN. Its primary advantages are that it should be relatively easy for the organization to deploy and maintain, and it will be transparent to users.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to IPsec VPNs."}]}
{"id": "nist_00207", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Specification for Asset Reporting Format 1.1 provide? (Section 43) | 1-n | Contains a relationship between a subject and object(s) assets. | Table 5-9: Element - core:relationship | Element Name: core:relationship | Element Name: core:relationship | Element Name: core:relationship | Element Name: core:relationship | Element Name: core:relationship | |-----------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Definition | Contains a relationship between the subject and object(s) assets.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Specification for Asset Reporting Format 1.1."}]}
{"id": "nist_00208", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain A.10 Man in the Middle Attack (MITM) according to NIST Vetting the Security of Mobile Applications According to Vetting the Security of Mobile Applications, A.10 Man in the Middle Attack (MITM): A Man in the Middle attack (MiTM) is defined simply as any method of intercepting communication between two systems [55]. Mobile applications are specifically vulnerable to these types of attacks because the misuse/misconfiguration of the primary defense against it: Transport Layer Security (TLS). The acceptance of untrusted SSL certificates, permitting the use of weaker TLS modes, and vulnerabilities in the trust model itself can leave a mobile application vulnerable to MiTM attacks leading to potential information leaks and privacy violations.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Vetting the Security of Mobile Applications."}]}
{"id": "nist_00209", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Common Platform Enumeration_ Dictionary Specification Version 2.3 say about Appendix A-References? According to Common Platform Enumeration_ Dictionary Specification Version 2.3, Appendix A-References: The following documents are indispensable references for understanding the application of this specification.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Platform Enumeration_ Dictionary Specification Version 2.3."}]}
{"id": "nist_00210", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessment of Access Control Systems say about Extensible Access Control Markup Language (XACML)? According to Assessment of Access Control Systems, Extensible Access Control Markup Language (XACML): A general purpose language for specifying access control policies.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessment of Access Control Systems."}]}
{"id": "nist_00211", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control II-4 in 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)? (Part 92) Control II-4: ant modifications to existing applications. Management officials who are the primary users of applications should evaluate the sensitivity of new or existing applications being substantially modified. Fcr those applications considered sensitive, the management control process shall, at a minimum, include security specifications and design reviews and systems tests - (a) Security Specifications . Agencies shall define and approve security requirements and specifications prior to acquiring or starting formal development of the applications. The results of risk analyses performed at the information technology installation where the applications will be. processed should be taken into account when defining and approving security specifications for the applications. Othtr vulnerabilities of the appl 1 ca 1 1 ons , such as in telecommunications links, shall als: be considered in defining security requirements. The views and recommendations of the information technology user organization, the information technology installation, and the individual responsible for security at the installation shall be considered prior to the approval of security specifications for the appl i cations (b) Design Reviews and System Tests . Agencies shall conduct and approve design reviews and system tests, prior to placing the application into operation, to assure the propose: design meets the approved security specifications. The objective of the system tests should be to verify that required administrative, technical, and physical safeguards are operationally adequate. The results of the design reviews and system tests shall be fully documented and maintained in the official agency records. (c) Certl f 1 cat ion . Upon completion of the systeo tests, an agency official shall 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)."}]}
{"id": "nist_00212", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings say about Temporal Key Release Infrastructure 4? (Part 2) According to 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings, Temporal Key Release Infrastructure 4: cryptographic key pair for the issuing of TDCs, for safe private key storage, and for event log auditing. This entity is kept isolated, usually in a safe room, without data communication connections. In this way, the off-line TCA is not subjected to threats from public data communication channels. Data insertion and retrieval in the off-line TCA are carried out using removable media. The on-line TCA is responsible for the short-term cryptographic key pair generation, issuing of TDCs, and private key storage. The on-line TCA is also in charge of receiving the TDC requests and its policies and disclosing the private key at the time specified. The private keys that will be necessary in the long-term are sent to the off-line TCA. The on-line TCA can also receive private key publication delays or private key destruction requests. This entity must produce audit logs of its activities and publish them with the audit logs from the off-line TCA. The TSA issues time stamps that are attached to the electronic document and thus can prove its existence at a specific time [11, 19, 6]. The TSA, in this infrastructure, is in charge of producing time-related evidence for the electronic documents received or sent by the on-line and off-line TCA. The TSA clock is synchronized with trusted-time sources [16, 7]. The use of the TSA guarantees that the TCA clock will be synchronized and all the transactions carried out will be associated with the correct date and time, bringing trust to the temporal aspects of the process. As the on-line TCA is in charge of private key disclosure, its clock must be synchronized with a trusted time source. The off-line TCA does not require the same precision. The private keys are released in blocks by the off-line TCA to the on-line TCA. Each block has a group of private keys that must be dis- 2 LabSEC - Computer Security Lab (www.labsec.ufsc.br) closed in the next window of time to release private keys.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, sso. Contains security framework guidance for authentication systems. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_00213", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Web Transactions_ TLS Server Certificate Management provide? (Section 4) the following purposes: - \uf0a7 Recognize the harm that improper management of TLS server certificates can cause to business operations and provide guidance to mitigate risks related to TLS certificates. - \uf0a7 Ensure that the central certificate services team and the local application owners and system administrators understand the risks to the enterprise and are accountable for their roles in managing TLS server certificates. - \uf0a7 Establish an action plan to implement these recommendations and track progress. As the use of web transactions has grown, the number of TLS server certificates has increased to many thousands in some enterprises. Many of these enterprises struggle to effectively manage their certificates and, as a result, face significant risks to their core operations, including: - \uf0a7 application outages caused by expired TLS server certificates - \uf0a7 hidden intrusion, exfiltration, disclosure of sensitive data, or other attacks resulting from encrypted threats or server impersonation - \uf0a7 application outages or attacks resulting from delayed replacement of large numbers of certificates and private keys in response to either certificate authority compromise or discovery of vulnerabilities in cryptographic algorithms or libraries Challenges to TLS server certificate management include the broad distribution of certificates across enterprises, the complexity of certificate management processes, and the multiple roles involved in certificate management and issuance. TLS server certificates are typically issued by a central certificate services team, but the certificates are often installed and managed by the groups (lines of business) and local system administrators responsible for individual web servers, application servers, network devices, and other network components for which certificates are used. Some of these managers and administrators lack awareness of the risks and best practices associated with certificate management.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: certificate authority, sso. Contains security framework guidance for authentication systems. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_00214", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2013 Annual Report say about Cryptography for Constrained Environments? (Part 1) According to Computer Security Division 2013 Annual Report, Cryptography for Constrained Environments: Cryptography for Constrained Environments Pervasive computing is an emerging technical area in which many highly constrained devices (e.g., limited resources, such as program space and RAM) are interconnected, typically communicating wirelessly with one another, and working in concert to accomplish some task. These systems apply to a wide variety of fields. Sample application areas include sensor networks, medical devices, distributed control systems, and the Smart Grid. Security can be very important in each of these areas. For example, an unauthorized party should not be able to take control of an insulin pump or the brakes on a car. There are also privacy concerns, particularly in the area of Health IT. Because the majority of the current cryptographic algorithms were designed for desktop/server environments, many of these algorithms cannot operate under these constraints, or if they can be made to operate in these constrained environments, their performance is typically not acceptable. A particular problem is the use of asymmetric (public key) algorithms. These algorithms tend to be much more computational and resourceintensive and are not easily accommodated in such constrained environments. As a result, CSD is currently focusing on studying the use of the NIST-approved symmetric-key algorithms in constrained environments. Symmetric-key algorithms can perform encryption for confidentiality, and can generate message authentication codes (MAC) for authenticity and integrity. NIST has implemented the Advanced Encryption Standard (AES) to provide both confidentiality and the AES-based message authentication code, CMAC mode, for authentication. Additionally, CTG has implemented the 256-bit version of the Secure Hash Algorithm (SHA-256) to provide a Hash-based Message Authentication Code (HMAC) for authentication.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2013 Annual Report."}]}
{"id": "nist_00215", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2010 Annual Report? (Part 103) Control HA-3: l study of the requirements of a lab that can support a wide variety of virtualization and cloud computing experiments, such as those involving multiple clouds or clouds comprised of diverse software. This resulted in the procurement of needed hardware and software resources as well as the necessary networking sup\u00ad port to allow the lab's unimpeded access to the Internet. In FY2011, CSD plans to deploy and test the hardware and software components of two primary setups to support a variety of virtu\u00ad alization solutions including both commercial and open source software such as VMWare vSphere, Citrix XenServer, and Microsoft Hyper-V hypervisors. CSD also plans to leverage the test environ\u00ad ment to support some of the SAJACC use cases by implementing a proof of concept for supporting the NIST SP 800-53 security con\u00ad trol requirements for low and moderate impact baseline in a cloud computing service model such as infrastructure as a service refer\u00ad ence implementation. Contact: Mr. David Ferraiolo (301) 975-3046 david.ferraiolo@nist.gov ## Access Control and Identity Management in Virtualized Systems The purpose of this project is to conduct research on how to in\u00ad tegrate advanced access control mechanisms into virtualized sys\u00ad tems. Access control has traditionally been integrated into either operating system mechanisms, network components (such as firewalls), or directly in applications. With a virtualized system, the option is available to add access control mechanisms into the hy\u00ad pervisor layer that implements the virtual machine abstractions. Such access control implementations may leverage the isolation feature offered by virtualized systems. This research analyzes the requirements for adding access control at the different layers, and the impact on different access control components such as users, processes, policy enforcements points, policy decision points, and policy database coordinated.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, identity management. Contains security framework guidance for authentication systems. Source: Computer Security Division 2010 Annual Report."}]}
{"id": "nist_00216", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is False Positive according to Guide to Intrusion Detection and Prevention Systems (IDPS)? False Positive: An instance in which an intrusion detection and prevention technology incorrectly identifies benign activity as being malicious.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Intrusion Detection and Prevention Systems (IDPS)."}]}
{"id": "nist_00217", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Section 7) 171A. | | What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements. | | What is the relationship between NIST and CMMC? | The Cybersecurity Maturity Model Certification (CMMC) is a DOD program that references the security requirements in NIST SP 800-171 and SP 800-172. NIST is not involved in the design, development, or implementation of the CMMCmodel, accreditation body, or certification process. It is important to note that CMMCis currently based on SP 800-171, Revision 2. Contractors should check for specific requirements in their contracts to understand which version they are required to use. | <!-- image --> View more FAQs here. If you still have a question after reviewing all our FAQs , send your question to: sec-cert@nist.gov. ht ps:/ csrc.nist.gov/projects/protecting-control ed-unclas ified-information <!-- image --> <!-- image --> <!-- image --> SP 800-171 requirements are focused on protecting confidentiality and are based on a subset of controls found in SP 800-53, which is a catalog of security and privacy controls for systems and organizations. With that in mind, it is important to have a basic understanding of the SP 800-53 series. To assist, NIST has released three self-guided online introductory courses to provide a high-level overview of foundational security and privacy risk management concepts. The online introductory courses are between 45-60 minutes, are available at no cost, and registration is not required. Access the courses. - The National Archives and Records Administration (NARA) , per 32 CFR Part 2002 \"Controlled Unclassified Information,\" determines what CUI is and lists CUI types at archives.gov/cui. - NIST is responsible for developing and publishing the security requirements for the protection of CUI.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer."}]}
{"id": "nist_00218", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PA-5060 in Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation? (Part 193) Control PA-5060: the routing table. 7. AS 65511 removes the ROA published in Step 1 from the RPKI. 8. Verify that the RUT now evaluates the route advertisement for 10.100.0.0/16 that originated from 65511 as invalid . | | Expected Results | Each of the expected results in Steps 4, 5, 6, and 8 above are verified. | Each of the expected results in Steps 4, 5, 6, and 8 above are verified. | Each of the expected results in Steps 4, 5, 6, and 8 above are verified. | | Actual Results | Test completed and functions as intended in Steps 4, 5, 6, and 8. | Test completed and functions as intended in Steps 4, 5, 6, and 8. | Test completed and functions as intended in Steps 4, 5, 6, and 8. | | Additional Comments (If Needed) | Changes in the validation state of selected routes are also observed via iBGP traffic. Step 6 is validated by monitoring the incoming traffic on its iBGP peer. | Changes in the validation state of selected routes are also observed via iBGP traffic. Step 6 is validated by monitoring the incoming traffic on its iBGP peer. | Changes in the validation state of selected routes are also observed via iBGP traffic. Step 6 is validated by monitoring the incoming traffic on its iBGP peer. | Test case SIDR-ROV-1.2.2 is identical to test case SIDR-ROV-1.2.1, except that IPv6 addresses are used instead of IPv4 addresses. ## E.3.1.3 Test Case: SIDR-ROV-1.3.1 and 1.3.2 | Test Objective | Test SIDR Requirement CR-1.3.1. Show that the ROV-capable router correctly evaluates received routes in the following situation: The advertised route is initially evaluated as valid . The single ROA that had made the route valid is removed from the RPKI. There is another ROA that covers the route, but its maximum prefix length is less than the prefix length of the route, so the route is re-evaluated as invalid . \uf0e0 | Test SIDR Requirement CR-1.3.1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_00219", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.4.2.3 Query Handler according to NIST Access Control for SAR Systems According to Access Control for SAR Systems, 3.4.2.3 Query Handler: The primary function of the PEP is to restrict unauthorized access to SAR records. When the PEP receives a user query for SAR records, it creates a series of queries to the PDP to determine whether the user is authorized to access Full, Summary ISE, or Summary SLT SAR records. This involves having the PEP construct an XACML Request for each query that represents an ABAC policy comprising a set of subject attribute values, an action, and a set of resource attribute values. To acquire the attribute values needed for the XACML Request, the PEP queries the subject, environment and resource attribute databases. To achieve this, the PEP must consult the policies used by the PDP in order to acquire the proper attributes. Note that in this version of PET, the PEP is responsible for ensuring that attributes needed by the PDP to render a policy decision are supplied in an XACML Request rather than relying on the PDP to acquire these attributes itself. 4", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Access Control for SAR Systems."}]}
{"id": "nist_00220", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events provide? (Section 106) ngruent with applicable standards and best practices. Section 3.5 of Volume B, Technologies, lists the products we used and maps them to the cybersecurity controls provided by this reference solution. A NIST Cybersecurity Practice Guide does not describe 'the' solution, but a possible solution. This is a draft guide. We seek feedback on its contents and welcome your input. Comments, suggestions, and success stories will improve subsequent versions of this guide. Please contribute your thoughts to dsnccoe@nist.gov. The National Cybersecurity Center of Excellence (NCCoE) built a hybrid virtual-physical laboratory environment to explore methods to effectively identify assets and protect them against a data corruption event in various IT enterprise environments. The NCCoE also explored identifying vulnerabilities in advance of an incident. The servers in the virtual environment were built to the hardware specifications of their specific software components. The NCCoE worked with members of the Data Integrity Community of Interest to develop a diverse but noncomprehensive set of use case scenarios against which to test the reference implementation. These are detailed in Volume B, Section 5.2. For a detailed description of our architecture, see Volume B, Section 4. The following table presents typographic conventions used in this volume. | Typeface/Symbol | Meaning | Example | |-------------------|--------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| | Italics | file names and pathnames; references to documents that are not hyperlinks; new terms; and placeholders | For language use and style guidance, see the NCCoE Style Guide.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_00221", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Conformance Test for FDDI Medium Access Control (MAC) say about FDDI MAC Conformance Test TTCN Machine Processable Form? (Part 35) According to A Conformance Test for FDDI Medium Access Control (MAC), FDDI MAC Conformance Test TTCN Machine Processable Form: TA_Strip $CRef DATA_Strip_R3 $Comment PA, SD, FC, DA, SA, INFO, FCS, ED and FS returned {A=S, E=S, C=R) , $End_Behc $BehaviourLine $Line [5J7TOKEN $CRef T0KEN_R1 $Verdict P $Comment followed by Token. $End_BehaviourLine $BehaviourLine $Line [ 5] 7CTHERWISE $Verdict F $End_BehaviourLine $BehaviourLine $Line [5]7TIMEOUT TRT $Verdict F $End_BehaviourLine $BehaviourLine $Line [ 4 ] 70THERWISE $Verdict F $End_BehaviourLine $BehaviourLine $Line [4]7TIMEOUT TRT $Verdict F $End_BehaviourLine $End_BehaviourDescription $End_TestCase $Begin_TestCase $TestCaseRef FDDI /MAC/FED/DetectFCS ``` ``` $TestCaseId DetectFCS $TestPurpose Testing Frame Error Detection 10: Detecting FCS Errors $BehaviourDescription $TreeHeader DetectFCS $ BehaviourLine $Line [ 1] +FDDI/INITCONNECT $Cornment Intializing Connection $End_BehaviourLine $ BehaviourLine $Line [2] !DATA $CRef DATA_T11_0 $Comment Tester sends the frame (DA=IUT Address; FCS errors), $End_BehaviourLine $BehaviourLine $Line [3] ! TOKEN $CRef TOKEN_Tl $CoiTiment followed by Token. $End_BehaviourLine $BehaviourLine $Line [4]?DATA $CRef DATA_R11_0 $Comment lUT repeats Tester's frame (A=S , E=S , C=R) , $End__BehaviourLine $ BehaviourLine $Line [5]?TOKEN $CRef TOKEN_Rl $Comment Token returned. $End_BehaviourLine $BehaviourLine $Line [6]! DATA $CRef DATA_T11_1 $Comment Tester sends the frame (DAOIUT Address;. FCS error), $End_BehaviourLine $ BehaviourLine $Line [7] ! TOKEN $CRef T0KEN_T1 $Comment followed by Token. $End_BehaviourLine $BehaviourLine $Line [8]?DATA $CRef DATA_R11_1 $Comment lUT repeats Tester's f rame (A-R, E=S, C=R) $End_BehaviourLine $ BehaviourLine $Line [9]?TOKEN $CRef T0KEN_R1 $Verdict P $Coniment lUT returns Token.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, token. Contains security framework guidance for authentication systems. Source: A Conformance Test for FDDI Medium Access Control (MAC)."}]}
{"id": "nist_00222", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Example according to Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Example: The defender uses selectively planted false", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_00223", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Telehealth Remote Patient Monitoring Ecosystem provide? (Section 68) \u00a7\u00a7 164.310(d)(2)(i) 164.310(d)(2)(ii) | A.8.2.3 A.8.3.1 A.8.3.2 A.11.2.7 | | | Information Protection (PR.IP) | PR.IP-9: Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed | CP-1 CP-2 CP-7 CP-10 IR-1 IR-7 IR-8 IR-9 | | DTBK SGUD | 45 C.F.R. \u00a7\u00a7 164.308(a)(6) 164.308(a)(6)(i) 164.308(a)(7) 164.310(a)(2)(i) 164.312(a)(2)(ii) | A.16.1.1 A.17.1.1 A.17.1.2 A.17.1.3 | | | Information Protection (PR.IP) | PR.IP-10: Response and recovery plans are tested | CP-4 IR-3 PM-14 | OM-NET- 001 | DTBK SGUD | 45 C.F.R. \u00a7\u00a7 164.308(a)(7)(ii)(D) | A.17.1.3 | | | Information Protection (PR.IP) | PR.IP-12: A vulnerability management plan is developed and implemented | RA-1 RA-3 RA-5 SI-2 | OV-PMA- 001 | MLDP | 45 C.F.R.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, incident response. Contains technical security guidance that could inform defensive posture. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_00224", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Glossary of Computer Security Terminology provide? (Section 18) IS and for the data and information contained in the AIS. It includes the totality of security safeguards needed to provide an acceptable level of protection for an AIS and for data handled by an AIS. (DODD 5200.28) | analysis | See COST-ANALYSIS, CRYPTOANALYSIS, and RISK ANALYSIS. | |-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | annual loss expectancy (ALE) | The ALE of an ADP system or activity is the expected yearly dollar value loss from the harm to the system or activity by attacks against its assets.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Glossary of Computer Security Terminology."}]}
{"id": "nist_00225", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain FlowStream (from Consilium) according to NIST Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST According to Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST, FlowStream (from Consilium): 1. FlowStream was developed mainly for the pharmaceutical and related chemical industries, thus the compliance to regulations is much emphasized. FlowStream specifically addresses the needs of the chemical research and development facility. The researcher can define and document experiments and procedures, statistically compare results from different experiments, and automatically record notebook changes. FlowStream also maintains a detailed record of laboratory equipment, including its use and servicing history. A Document Vault permanently stores documents and provides a complete audit trail of their life cycle. 2. FlowStream appears to provide some of the basic requirements mentioned in Chapter 2 of this paper. It has not been tested as of the moment, but it might be helpful in the development of a prototype ERN system. One concern about using this product is that its format might be too industry-specific in the area of pharmaceutical, but this will have to be determined at a later time. 3. The Document Vault package is based on a client-server architecture, and requires either Microsoft Windows, XWindows, or a Macintosh platform, as well as network software and hardware. An SQL-compatible relational database could also be used. Tools from the Digital Equipment Corporation should allow the user to connect FlowStream to existing equipment, such as data acquisition devices and laboratory information systems. 4. To obtain all modules of FlowStream for twelve users, the estimated cost ranges between $175,000 and $200,000 (it is not clear if this figure includes the price of hardware).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST."}]}
{"id": "nist_00226", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? http: //www.ittc.ku.edu/resilinets/papers/Sterbenz-Hutchison-Cetinkaya-Jabbar-", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_00227", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does ISCMA_ An Information Security Continuous Monitoring Program Assessment say about Table of Contents? (Part 13) According to ISCMA_ An Information Security Continuous Monitoring Program Assessment, Table of Contents: Inter-Level Consolidation (Alternate Judgments) .......................................................17 | Figure 7 - Inter-Level Consolidation (Alternate Judgments) .......................................................17 | | Figure 9 - ISCMA Report and Follow-on: Formulate Actions .......................................................18 | Figure 9 - ISCMA Report and Follow-on: Formulate Actions .......................................................18 | Figure 9 - ISCMA Report and Follow-on: Formulate Actions .......................................................18 | | Figure 10 - ISCMA Partially Automated Steps.............................................................................21 | Figure 10 - ISCMA Partially Automated Steps.............................................................................21 | Figure 10 - ISCMA Partially Automated Steps.............................................................................21 | | Figure 11 - Required References ................................................................................................22 | Figure 11 - Required References ................................................................................................22 | Figure 11 - Required References ................................................................................................22 | | Figure 12 - TitlePage Worksheet ................................................................................................22 | Figure 12 - TitlePage Worksheet ................................................................................................22 | Figure 12 - TitlePage Worksheet ................................................................................................22 | | Figure 13 - Assessment Worksheet (Recommended Judgments)...............................................23 | Figure 13 - Assessment Worksheet (Recommended Judgments)...............................................23 | Figure 13 - Assessment Worksheet (Recommended Judgments)...............................................23 | | 14 - Assessment Worksheet (Alternate Judgments)........................................................23 | 14 - Assessment Worksheet (Alternate Judgments)........................................................23 | 14 - Assessment Worksheet (Alternate Judgments)........................................................23 | | Figure Figure 15 - Specifying a Detailed Level 1 Assessment of the Full ISCM Program........................24 | Figure Figure 15 - Specifying a Detailed Level 1 Assessment of the Full ISCM Program........................24 | Figure Figure", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: ISCMA_ An Information Security Continuous Monitoring Program Assessment."}]}
{"id": "nist_00228", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Technology Assessment_ Methods for Measuring the Level of Computer Security provide? (Section 135) in transactions effec- tively remaining unrecorded (e.g. when an outdated file is mistaken for a current one), or certain transactions may be recorded twice, or recorded incorrectly, or misclassified. Operator errors may be more frequent (because of inadequate monitoring by operating system) leading to undetected inaccuracies in processed data. oofioo oooofiooooo oo Library is not maintained to control files. Library exists but its operation is inadequate (which may result in authorized requests not being required for file issue, or not being based on the production schedule, or no log of file usage being maintained). Incorrect files may be processed inadvertently resulting in certain transactions effec- tively remaining unrecorded (e.g. when an outdated file is mistaken for a current one) Certain transactions may be recorded twice or recorded incorrectly or misclassified. Unauthorized access to files may lead to deliberate inaccuracies or fictitious trans- actions being inserted in processed data. ooooo ooooofififioo oo Poor programming controls permit logic errors to occur in programming. Undetected logic programming errors may cause inaccuracies in processed data. Control Deficiency Guide Excerpt LCICT5, p. 233 Reprinted with permission from Computer Audit Guidelines, 1975, published by the Canadian Institute of Chartered Accountants, Toronto, Canada. The Arthur Andersen &amp; Co. approach to evaluation of internal accounting controls consists of four tasks: - 0 General risk analysis - 0 Transaction flow reviews - 0 Evaluation of internal control techniques - 0 Compliance testing In the risk analysis, financial planning and control are reviewed to document the processes and obtain an overview of the internal control environment. Most of the document consists of illustrative control objectives and \"risk identifiers\" which presumably assist in the risk analysis process. These will be briefly discussed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technology Assessment_ Methods for Measuring the Level of Computer Security."}]}
{"id": "nist_00229", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2013 Annual Report say about Draft SP 800-101 Revision 1, Guidelines on Mobile Device Forensics? According to Computer Security Division 2013 Annual Report, Draft SP 800-101 Revision 1, Guidelines on Mobile Device Forensics: Mobile device forensics is the science of recovering digital evidence from a mobile device under forensically sound conditions using accepted methods. Mobile device forensics is an evolving specialty in the field of digital forensics. This guide attempts to bridge the gap by providing an in-depth look into mobile devices and explaining technologies involved and their relationship to forensic procedures. This document covers mobile devices with features beyond simple voice communication and text messaging capabilities. This guide also discusses procedures for the validation, preservation, acquisition, examination, analysis, and reporting of digital information.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2013 Annual Report."}]}
{"id": "nist_00230", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TE-1 in Mobile Device Security_ Bring Your Own Device (BYOD)? (Part 45) Control TE-1: 37] (adapted from Government Accountability Office Report 08-536). Predictability Enabling of reliable assumptions by individuals, owners, and operators about PII and its processing by a system [34]. Privacy Event The occurrence or potential occurrence of problematic data actions [2]. Problematic Data Action A data action that could cause an adverse effect for individuals [2]. Threat Any circumstance or event with the potential to adversely impact organizational operations (including mission, functions, image, or reputation), organizational 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 [8]. Vulnerability Weakness in an information system, system security procedures, internal controls, or implementation that could be exploited by a threat source [8]. ## Appendix C References - [1] National Institute of Standards and Technology (NIST). NIST Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1 (Cybersecurity Framework). Apr. 16, 2018. [Online]. Available: - [2] NIST. NIST Privacy Framework: A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0 (Privacy Framework). Jan. 16, 2020. [Online]. Available: - [3] W. Newhouse et al., National Initiative for Cybersecurity Education (NICE) Cybersecurity Workforce Framework, NIST Special Publication (SP) 800-181 rev. 1, NIST, Gaithersburg, Md., Nov. 2020. Available: - [4] NIST. Risk Management Framework (RMF) Overview. [Online]. Available: )-overview. - [5] NIST. Mobile Threat Catalogue. [Online]. Available: - [6] J.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_00231", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Identity and Access Management for Electric Utilities say about Java Application? (Part 40) According to Identity and Access Management for Electric Utilities, Java Application: t t p : / / d o i .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_00232", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Device Security_ Bring Your Own Device (BYOD) say about Appendix D A Note Regarding Great Seneca Accounting? According to Mobile Device Security_ Bring Your Own Device (BYOD), Appendix D A Note Regarding Great Seneca Accounting: A description of a fictional organization, Great Seneca Accounting, was included in the National Institute of Standards and Technology (NIST) Special Publication (SP) 1800-22 Mobile Device Security: Bring Your Own Device (BYOD) Practice Guide. This fictional organization demonstrates how a small-to-medium sized, regional organization implemented the example solution in this practice guide to assess and protect their mobile-devicespecific security and privacy needs. It illustrates how organizations with office-based, remote-working, and travelling personnel can be supported in their use of personally owned devices that enable their employees to work while on the road, in the office, at customer locations, and at home. <!-- image --> <!-- image --> Figure D-1 Great Seneca Accounting's Work Environments <!-- image --> <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_00233", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Section 144) e and inform intrusion detection and threat hunting. Determine if: | 3.14.6e_ODP[1] | External organizations from which to obtain threat indicator information and effective mitigations are defined. | |------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 3.14.6e[a] | Threat indicator information is identified. | | 3.14.6e[b] | Effective mitigations are identified. | | 3.14.6e[c] | Intrusion detection approaches are identified. | | 3.14.6e[d] | Threat hunting activities are identified. | | 3.14.6e[e] | Threat indicator information and effective mitigations obtained from <3.14.6e_ODP[1]: external organizations> are used to guide and inform intrusion detection and threat hunting. | Examine : [ SELECT FROM: System and information integrity policy; information security program plan; procedures addressing security alerts, advisories, and directives; threat awareness program documentation; procedures addressing system monitoring; procedures for the threat awareness program; risk assessment results relevant to threat awareness; records of security alerts and advisories; system design documentation; security plan; system monitoring tools and techniques documentation; system configuration settings and associated documentation; system monitoring logs or records; system audit records; documentation on the cross-organization information-sharing capability; other relevant documents or records].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00234", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Secure Web Services? (Part 104) Control ES-1: element in an XML file to a request for entry through a physical door. When using XACML in a Web service or Web application, it is important to understand that the application itself must be the PEP. All requests for information from the client or requester service must be translated into an access request. In many implementations, XACML is used solely for authentication, in which case only the authentication request needs to be translated while all subsequent requests would be allowed. As mentioned earlier, the PEP needs to send XACML requests to the PDP. The PDP will take the XACML request and determine the appropriate XACML response to send to the PEP, which will then grant or deny the request. Because there is no mechanism for transmitting XACML over a network in the XACML specification, SAML is traditionally used to transmit requests, responses, and attributes over a network. SAML was designed for the secure exchange of authentication and authorization information, but not for performing the actual decisions. This makes it a perfect match for transmitting XACML information over a network. The PEP converts the XACML request into a SAML query and sends it to the PDP. The PDP converts the SAML query into an XACML request and processes the request against the XACML policy. The XACML response is converted into a SAML response and sent back to the PEP, which converts it back into an XACML response. SAML does not provide message confidentiality-only message integrity. If any of the data being transmitted is sensitive, it must be transmitted using SSL/TLS or WS-Security. If the SAML protocol is being used without SSL/TLS, all SAML messages must be signed appropriately. The XACML v2.0 specification only supports a configuration where the PDP and PEP are on the same system. There is no standard specified for transmitting XACML policies, requests, or responses over a network.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services."}]}
{"id": "nist_00235", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is https according to Security and Privacy Controls for Information Systems and Organizations? https: //doi.org/10.6028/NIST.SP.800-34r1", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00236", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Prepared By according to Automated Information System Security Accreditation Guidelines? Prepared By: (Name and Title of AISSO) (Organization)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Automated Information System Security Accreditation Guidelines."}]}
{"id": "nist_00237", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2012 Annual Report say about Leveraging Access Control for Cloud Computing? (Part 2) According to Computer Security Division 2012 Annual Report, Leveraging Access Control for Cloud Computing: ualized environment providing cloud-like features. To appreciate the PM's advantages in computing, it is important to recognize the methoGLYPH(cmap:df00)s in which DSs are delivered today. Each DS runs in an Operating Environment (OE) and an OE can be of many types (e.g., operating systems, web services, miGLYPH(cmap:df00)GLYPH(cmap:df00)leware, and database and database applications), each implementing its own routines to enable the execution of DS-specific operations (e.g., reaGLYPH(cmap:df00), senGLYPH(cmap:df00), anGLYPH(cmap:df00) view) on their respective GLYPH(cmap:df00)ata types (e.g., files, messages, anGLYPH(cmap:df00) fielGLYPH(cmap:df00)s). This heterogeneity among OEs introduces a number of administrative and policy enforcement challenges and user inconveniences. Administrators must contend with a multituGLYPH(cmap:df00)e of security GLYPH(cmap:df00)omains when managing privileges, and ordinary users and administrators alike must authenticate to and establish sessions within GLYPH(cmap:df00)ifferent OEs in orGLYPH(cmap:df00)er to exercise legitimate DS capabilities. Even if properly coordinated across OEs, access control policies are not always globally enforced. An email application may, for example, GLYPH(cmap:df00)istribute files to users regarGLYPH(cmap:df00)less of an operating system's protection settings on those files. Also, while researchers, practitioners, and policy makers have specifieGLYPH(cmap:df00) a large variety of access control policies to aGLYPH(cmap:df00)GLYPH(cmap:df00)ress real-worlGLYPH(cmap:df00) security issues, only a relatively small subset of these policies can be enforced through off-the-shelf technology, and even a smaller subset can be enforced by any one OE.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_00238", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines on Active Content and Mobile Code provide? (Section 55) r malicious code as an embedded file attachment [Fis01]. When the contaminated PDF file is opened for the demonstration, a game is launched that prompts the user to click on a moving image of a peach. The occurrence of that event, in turn, causes the execution of an embedded VBScript file, which attempts to mail out the PDF file to others using Microsoft Outlook. Note that even content readers are not completely immune from problems. From time-to-time, vulnerabilities have occurred in the implementation of Acrobat Reader that could be exploited with carefully constructed content. For example, Adobe released a patch to the Acrobat Reader 8 browser plug-in that eliminates a cross-site scripting vulnerability [Ado07a]. An attacker could exploit the vulnerability by appending Javascript to a PDF URL that would cause any version of the reader to execute arbitrary JavaScript code when the file was rendered. This example illustrates how even relatively benign content can affect document rendering software having implementation errors. PDF does incorporate two distinct security features that can be applied to any conforming document, individually or together. The document can be digitally sealed through a signed document digest, a biometric signature, or other means to certify its authenticity and protect against tampering. The document can also be encrypted so that only authorized users can view or operate on its contents. Java is a full-featured, object-oriented programming language compiled into platform-independent byte code executed by an interpreter called the Java Virtual Machine (JVM). The resulting byte code can be executed where compiled or transferred to another Java-enabled platform. The Java programming language and runtime environment [Gon98, Gos96] enforce security primarily through the Java security manager, which monitors running Java applications and verifies that they are following a specified policy.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Guidelines on Active Content and Mobile Code."}]}
{"id": "nist_00239", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EQ-1 in Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines? (Part 22) Control EQ-1: The integrity of the code in the repository can be trusted such that it can be used for further updates. | | | 5.1.3 Integrity of Evidence Generation During Software Updates (To provide assurance to acquirers that the software they get is legitimate, steps are taken to protect the integrity of evidence generation tasks) | 1. The framework should provide protection against all known attacks on the tasks performed by the software update systems, such as metadata (hash) generation, the signing process, the management of signing keys, the integrity of the authority performing the signing, key validation, and signature verification. 2. The framework should provide a means to minimize the impact of key compromise by supporting roles with multiple keys and threshold or quorum trust (with the exception of minimally trusted roles designed to use a single key). The compromise of roles that use highly- vulnerable keys should have minimal impact. Therefore, online keys (i.e., keys used in an automated fashion) must not be used for any role that clients ultimately trust for files they may install [11]. When keys are online, exceptional care should be taken in caring for them, such as storing them in an HSM and only allowing their use if the artifacts being signed pass the policy defined in Sec. 5.1.1. 3. The framework must be flexible enough to meet the needs of a wide variety of software update systems. 4. The framework must be easy to integrate | Provide a Mechanism for Verifying Software Release Integrity (PS.2): Help software acquirers ensure that the software they acquire is legitimate and has not been tampered with.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines."}]}
{"id": "nist_00240", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance say about 8.1.1 DNS Data Authentication? (Part 1) According to Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance, 8.1.1 DNS Data Authentication: 8.1.1 DNS Data Authentication Cryptographically generated public key-based digital signatures provide authentication for DNS data. Commonly, there will be two or more digital signature public-key pairs (which make up the key set) used to implement DNSSEC in a zone. One key pair is used to sign the zone data (referred to as the Zone Signing Key or ZSK), and a separate key pair is used to sign the zone key set (known as the Key Signing Key or KSK). While some zones may only use one key pair for both ZSK and KSK, it is not recommended for federal agency zones. This KSK is also known as the Secure Entry Point (SEP) key for the zone - using it, a client can authenticate the ZSK (by validating the signature over the ZSK using the KSK public key), and then use the ZSK to authenticate the zone data. The KSK is also used to link the security chain 37 from the zone to its delegating parent. Since the KSK is used to link security from the zone (e.g. 'example.gov') to the delegating parent zone (e.g. '.gov') [RFC 4035], it is often longer lived, and used infrequently (used only to sign the zone key set). Multiple digital signature algorithms can be supported, so there may be multiple keys (one for each algorithm), as there is no algorithm negotiation in DNSSEC, and clients may only understand certain digital signature algorithms. There is one mandatory-to-implement algorithm as defined by the IETF, so there is at least one agreed-upon digital-signature algorithm that all servers and clients will understand. Currently, both RSA using SHA-1 and SHA-256 have been specified and can be used with DNSSEC zones. Most modern implementations either support both or will do so after an upgrade. Zones deploying DNSSEC for the first time can start with RSA using SHA-256. Zones that initially deployed with RSA using SHA-1 should migrate to RSA (2048-bit RSA key) using SHA-256: see [SP 800-131A] for information about guidelines for using RSA with different key sizes and hash algorithms.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance."}]}
{"id": "nist_00241", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TR-124 in Recommended Cybersecurity Requirements for Consumer-Grade Router Products? (Part 7) Control TR-124: than as normative text. - 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. Several of these examples highlight ways consumer-grade router products can use multiple techniques to deliver cybersecurity capabilities. Manufacturers should consider these and other techniques to continually improve router cybersecurity as risks shift and new mitigations become available. ## 3. Conclusion This consumer-grade router profile can help manufacturers determine appropriate cybersecurity to incorporate as they develop their products. These recommendations draw from current effective practices and promote the adoption of accepted and vetted cybersecurity features for router products.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommended Cybersecurity Requirements for Consumer-Grade Router Products."}]}
{"id": "nist_00242", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Framework for Emergency Response Officials (ERO)_ Authentication and Authorization Infrastructure say about 3. Leveraging Standards and Emerging Specifications? (Part 2) According to Framework for Emergency Response Officials (ERO)_ Authentication and Authorization Infrastructure, 3. Leveraging Standards and Emerging Specifications: an identity proofing process before being issued their credentials. This has resulted in the following developments and emerging specifications which will have an impact on the ERO-AA infrastructure. - Personal Identity Verification for Non-Federal Issuers (PIV-NFI) &amp; Revised X.509 Certificate Policy for the Federal Bridge Certification Authority (FBCA) : With the increasing use of PIV tokens, there is a great deal of interest from parties external to the government and who want to do business with the federal government to issue identity cards that are technically operable with federal government PIV systems and are issued in a manner that allows federal relying parties to trust the cards. To facilitate this, a set of minimum requirements for non-federally issued identity cards have been provided in the PIV-NFI document that has been issued by the federal CIO council. The associated trust requirements for these identity cards are specified in the FBCA profile document. - Federal Identity, Credentialing and Access Management (FICAM) - Open ID and Identity Metasystem Interoperability (IMI) Profiles: In order to facilitate exchange of business transactions between federal government agencies and its business partners and constituents, the FICAM subcommittee (that has been established by the Federal CIO council) has already developed profiles for industry developed federation protocols as a means of adopting them for meeting the requirements for various levels of authentication for doing business with the federal government.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, token. Contains security framework guidance for authentication systems. Source: Framework for Emergency Response Officials (ERO)_ Authentication and Authorization Infrastructure."}]}
{"id": "nist_00243", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Threat Analysis on UOCAVA Voting Systems say about Information Types:? According to A Threat Analysis on UOCAVA Voting Systems, Information Types:: Voter name, residency information, mailing address Voter authenticator (e.g. signature, PIN) Voter identifiers (e.g. social security, driver's license and/or passport numbers)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Threat Analysis on UOCAVA Voting Systems."}]}
{"id": "nist_00244", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Situational Awareness for Electric Utilities provide? (Section 253) ing to connect, or of identified host attempting to connect to unidentified host - Use OT network Zones (as defined in SA-1 content). - Use filter for OT network Zones (as defined in SA-1 content). - Filter for events from OT network Zone to/from a different Zone - Filters for authorization, authentication failures - Filter for authorization, authentication failures, or outbound events - Data Monitor and Dashboard to display results of the above Examine the behavior of systems, and configure the SIEM to alert on behavior that is outside the normal baseline. Alerts can be created emanating from OT, IT, and PACS. This test case seeks alerting based on behavioral anomalies rather than recognition of IP addresses, and guards against anomalous or malicious inputs. Anomalous behavior falling outside defined baseline Alert sent to SIEM on any event falling outside of what is considered normal activity based on historical data - Use OT network Zones. - Use Filter for OT network Zones. - Filter for ICS2 OnGuard events or events with a Category of Traffic Anomaly (e.g., as defined in Dragos Security CyberLens ArcSight FlexConnector/Categorizer files). - Data Monitor and Dashboard to display results of the above An alert will be created to notify the SIEM of unauthorized (inadvertent or malicious) uploading of an ICS network device configuration. The detection method will be primarily based on inherent device capability (i.e., log files). Configuration change on Tofino FW, Cisco 2950 Alert will be created to notify SIEM that this has occurred.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Situational Awareness for Electric Utilities."}]}
{"id": "nist_00245", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Technical Guide to Information Security Testing and Assessment say about 5. Target Vulnerability Validation Techniques? According to Technical Guide to Information Security Testing and Assessment, 5. Target Vulnerability Validation Techniques: This section addresses target vulnerability validation techniques, which use information produced from target identification and analysis to further explore the existence of potential vulnerabilities. The objective is to prove that a vulnerability exists, and to demonstrate the security exposures that occur when it is exploited. Target vulnerability validation involves the greatest amount of risk in assessments, since these techniques have more potential to impact the target system or network than other techniques. Target vulnerability validation techniques for application security testing are briefly discussed in Appendix C.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Technical Guide to Information Security Testing and Assessment."}]}
{"id": "nist_00246", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Power Loss according to Cell Phone Forensic Tools_ an Overview and Analysis? Power Loss: The Kyocera 7135 was repopulated with the above scenarios, then completely drained of all battery power and reacquired. No data was found. (Meet)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_00247", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Subject Public Key Info according to NIST Test Personal Identity Verification (PIV) Cards Version 2? Subject Public Key Info: rsaEncryption, 2048-bit modulus, e=65537", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_00248", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Threat Analysis on UOCAVA Voting Systems say about 4 Description of Transmissions Options? According to A Threat Analysis on UOCAVA Voting Systems, 4 Description of Transmissions Options: The purpose of this report is to identify options for distributing election materials to UOCAVA voters. This section will identify several different transmission options and provide brief descriptions for how these technologies and methods could be used to support overseas voting. The descriptions presented in Sections 4.2, 4.3, and 4.4 are merely examples of typical methods for employing the transmission options. This paper will outline threats to the types of systems described in this section, but other types of systems are possible.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Threat Analysis on UOCAVA Voting Systems."}]}
{"id": "nist_00249", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Version 1.1 Manufacturing Profile say about 6.3 Risk Management? According to Cybersecurity Framework Version 1.1 Manufacturing Profile, 6.3 Risk Management: The Profile relies on the manufacturer's risk management processes to inform and prioritize decisions regarding cybersecurity. It supports recurring risk assessments and validation of business drivers to help manufacturers select target states for cybersecurity activities that reflect desired outcomes. To manage cybersecurity risks, a clear understanding of the business drivers and security considerations specific to the Manufacturing system and its environment is required. Each organization's risk is unique, along with its use of ICS and IT, thus the implementation of the profile will vary. The Manufacturing Profile is meant to enhance but not replace current cybersecurity standards and industry guidelines that the manufacturer is currently embracing. Manufacturers can determine activities that are important to critical service delivery and can prioritize investments to maximize the impact of each dollar spent. Ultimately, the Profile is aimed at reducing and better managing cybersecurity risks. The Profile, along with the Cybersecurity Framework, are not one-size-fits-all approaches to managing cybersecurity risk for critical infrastructure. Manufacturers will continue to have unique risks - different threats, different vulnerabilities, different risk tolerances - and how they implement security practices will vary.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Version 1.1 Manufacturing Profile."}]}
{"id": "nist_00250", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways provide? (Section 57) ities and provide mitigation actions, including missing updates for endpoints. See NIST SP 1800-31 Volume C for additional information on each of the technologies we used to demonstrate the scenarios. It explains each technology, summarizes their integration into the laboratory environment, and documents our security decisions and associated configurations. Section 3.4.7 describes Scenario 6, 'Patch management system security (or other system with administrative privileged access).' In support of Scenario 6, this appendix describes recommended security practices for systems like patch management systems which have administrative privileged access over many other systems as defined as 'critical software' in Executive Order (EO) 14028. It then summarizes how the example solution components described in this practice guide could support each of those recommended security practices. The table below defines security measures for software of critical importance. Note that these security measures are not intended to be comprehensive. They are based on those in the NIST publication Security Measures for 'EO-Critical Software' Use Under Executive Order (EO) 14028 . A security measure (SM) is a high-level security outcome statement that is intended to apply to critical software or to all platforms, users, administrators, data, or networks (as specified) that are part of running critical software. The security measures are grouped by five objectives: 1. Protect critical software and critical software platforms (the platforms on which critical software runs, such as endpoints, servers, and cloud resources) from unauthorized access and usage. 2. Protect the confidentiality, integrity, and availability of data used by critical software and critical software platforms. 3. Identify and maintain critical software platforms and the software deployed to those platforms to protect the critical software from exploitation. 4.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: sso, privileged access. Contains security framework guidance for authentication systems. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_00251", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Foundations of a Security Policy for Use of the National Research and Educational Network provide? (Section 12) esearch and educational institutions, libraries, government laboratories, and industry.^ As the NREN continues to evolve, the problem of computer information security is expected to become more acute. The purpose of this report is to explore the foundations of a national network security policy and propose a draft policy for the NREN. Within this context, a network is defined to be a collection of autonomous computers interconnected by some communication media. The term security refers to computer and network information security. References to the NREN are generally intended to include not only the backbone transmission facilities, but also entities connecting to the NREN: local networks, host computers, and end users themselves. To that end, the scope of the proposed ^The NREN is envisioned as the evolution of existing networks, including those of the Federal Agency currently being developed as the Interagency Interim National Research and Education Network (IINREN), to a multigigabyte/second network that is expected to mature by 1996. security policy is broad, addressing the responsibilities of users, managers, system administrators, system developers, vendors, network service providers, and a national coordinating body. The policy presented here is at an abstract 'first-level', somewhat higher than typical policies or directives that establish organization-specific requirements and depend on technology-specific security mechanisms. In order to derive actual security practices from the security policy, further refinements are necessary. Properly addressed, these refinements should culminate in the formulation of formal specifications for security services and supporting mechanisms. Such specifications could be used by service providing organizations or entities, in addition to user organizations, for uniformity and interoperability purposes in providing required protection.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Foundations of a Security Policy for Use of the National Research and Educational Network."}]}
{"id": "nist_00252", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Device Security_ Bring Your Own Device (BYOD) provide? (Section 114) ent Analyst PR-INF-001: Cyber Defense Infrastructure Support Specialist PR-CDA-001: Cyber Defense Analyst | | | | DE.AE-5: Incident alert thresholds are established. | IR-4: Incident Handling IR-5: Incident Monitoring IR-8: Incident Response Plan | A.16.1.4: Assessment of and decision on information security events | CSC 6: Maintenance, Monitoring, and Analysis of Audit Logs CSC 19: Incident Response and Management | PR-CIR-001: Cyber Defense Incident Responder AN-TWA-001: Threat/Warning Analyst | | Specific product used | Function | Applicable NIST Cybersecurity Framework Subcategories | Applicable NIST SP 800-53 Revision 5 Controls | ISO/IEC 27001:2013 | CIS 6 | Applicable NIST SP 800-181 NICE Framework Work Roles (2017) | |-----------------------------------------------------------|---------------------------------------------------------|--------------------------------------------------------------------------------|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| | | | DE.CM-5: Unauthorized mobile code is detected.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_00253", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Control Baselines for Information Systems and Organizations provide? (Section 94) | W: Incorporated into AU-14. | W: Incorporated into AU-14. | W: Incorporated into AU-14. | | AU-14(3) | REMOTE VIEWING AND LISTENING | | | | | | AU-15 | Alternate Audit Logging Capability | W: Moved | to | AU-5(5). | AU-5(5). | | AU-16 | Cross-Organizational Audit Logging | | | | | | AU-16(1) | IDENTITY PRESERVATION | | | | | | AU-16(2) | SHARING OF AUDIT INFORMATION | | | | | | AU-16(3) | DISASSOCIABILITY | | | | | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Table 3-4 provides a summary of the controls and control enhancements assigned to the Assessment, Authorization, and Monitoring Family. The controls are allocated to the low-impact, moderate-impact, and high-impact security control baselines and the privacy control baseline, as appropriate. A control or control enhancement that has been withdrawn from the control catalog is indicated by a 'W' and an explanation of the control or control enhancement disposition in light gray text.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Control Baselines for Information Systems and Organizations."}]}
{"id": "nist_00254", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain FY 2024 event topics included: according to NIST Fiscal Year 2024 Cybersecurity and Privacy Annual Report According to Fiscal Year 2024 Cybersecurity and Privacy Annual Report, FY 2024 event topics included:: | Cryptography | Education and Workforce | Identity and Access Management | Internet of Things | NIST Frameworks | |----------------|---------------------------|----------------------------------|----------------------|-------------------| | Privacy | Risk Management | Securing Emerging Technologies | Small Businesses | Software | Learn more about this priority area", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Fiscal Year 2024 Cybersecurity and Privacy Annual Report."}]}
{"id": "nist_00255", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2011 Annual Report? (Part 133) Control HA-3: es together, and to use NIST's security policies, best practices and tools more effectively. She was cited as one of the most trusted government advisers on cybersecurity. ## Federal CIO 50 Award Dr. Ron Ross The InformationWeek Federal CIO 50 Award recognizes a select number of individuals within federal, state, and local government based on their technology vision, influence among peers in other agencies, and an ability to show tangible, measurable results in the field of information technology. ## INCITS Service Award for 2011 ## Dan Benigni INCITS would like to recognize Dan Benigni's many contributions. As INCITS/CS1 Chairman, his management skills and willingness to accept responsibilities are one of the major contributing factors for the successful and timely development of standards nationally and internationally within ISO/IEC JTC 1/SC 27. Dan's knowledge and dedication on important issues reflect his commitment to standardization efforts. Without question, Dan Benigni has earned this award, and INCITS would like to recognize his contributions to INCITS. <!-- image --> <!-- image --> ## V. Lee Conyers Award Dr. Ron Ross The V. Lee Conyers Award was created by the ISACA\u00ae-National Capital Area Chapter (NCAC-ISACA) to honor and remember V. Lee Conyers, a distinguished member of the chapter. The award recognizes an outstanding chapter member in the field of IT Audit, Security, and Control.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2011 Annual Report."}]}
{"id": "nist_00256", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Training & Awareness Course Compendium provide? (Section 63) what preventive and detective controls are available to mitigate control weaknesses within the LAN or from external connections. LAN Management and the role of the LAN officer is discussed in detail. Special emphasis is placed on management of the hardware and connectivity along with the selection of software. These key items often limit the overall usefulness of the LAN and inhibit the achievement of connectivity and productivity objectives. Each participant will receive detailed audit programs, common control weaknesses and sample recommendations. These are the key tools they need to conduct LAN audits. COURSE TITLE: COURSE LENGTH: 3 DAY Auditing Datacomm Networks VENDOR: Canaudit Inc. P.O. Box 4150 Simi Valley, CA 93093 (805) 583-3723 Wide area networks are the lifeblood of corporate information processing and connectivity, yet many organizations have yet to do a complete audit of network operations and management. This seminar provides the IS auditor with a structured audit approach directed to identifying critical control weaknesses in the network, the carriers, the media and network management Proven solutions to common control weaknesses will be provided to each participant. Focus in this seminar is on a complete audit approach for data and voice communications from a security and cost perspective. Network management tools and problem resolution techniques are the cornerstone of network operations. Special emphasis is placed on using NETVIEW, a popular network management tool to identify network problems. Participants in this session will receive detailed audit programs and checklists which will provide a strong starting point for their first Network Audit. COURSE TITLE: COURSE LENGTH: 3 DAY Computer Security &amp; Contingency Planning VENDOR: Canaudit Inc. P.O. Box 4150 Simi Valley, CA 93093 (805) 583-3723 Security Administration is now a reality in many organizations.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Training & Awareness Course Compendium."}]}
{"id": "nist_00257", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Labels for Open Systems_ an Invitational Workshop say about HOW ESO's ARE PROCESSED? According to Security Labels for Open Systems_ an Invitational Workshop, HOW ESO's ARE PROCESSED: - o CSESO &amp; RMESO -used for MAC, bit encoded Why two ESO' s? - o Default for CSESO if missing: - all 0's - o Default for RMESO if missing: - all 1's - Both what DNSIX calls Network Level ESO's (NLESO) - o SDESO -integer encoded, processing potentially unique per value - o SIESO -integer encoded, all datagrams without known SIESO' s rejected", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Labels for Open Systems_ an Invitational Workshop."}]}
{"id": "nist_00258", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Intrusion Detection and Prevention Systems (IDPS) provide? (Section 79) onnaissance and attacks (e.g., banner grabbing, buffer overflows, format string attacks, password guessing, malware transmission). Most network-based IDPSs analyze several dozen application protocols. Commonly analyzed ones include Dynamic Host Configuration Protocol (DHCP), DNS, Finger, FTP, HTTP, 22 Internet Message Access Protocol (IMAP), Internet Relay Chat (IRC), Network File System (NFS), Post Office Protocol (POP), rlogin/rsh, Remote Procedure Call (RPC), Session Initiation Protocol (SIP), Server Message Block (SMB), SMTP, SNMP, Telnet, and Trivial File Transfer Protocol (TFTP), as well as database protocols, instant messaging applications, and peer-to-peer file sharing software. - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Transport layer reconnaissance and attacks (e.g., port scanning, unusual packet fragmentation, SYN floods). The most frequently analyzed transport layer protocols are TCP and UDP. - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Network layer reconnaissance and attacks (e.g., spoofed IP addresses, illegal IP header values). The most frequently analyzed network layer protocols are IPv4, ICMP, and IGMP. Many products are also adding support for IPv6 analysis. The level of IPv6 analysis that network-based IDPSs can 22 Although network-based IDPSs can analyze HTTP protocol activity, they usually cannot perform analysis on the use of Web services, such as Simple Object Access Protocol (SOAP) and Extensible Markup Language (XML) messages carried over HTTP. Security technologies known as XML gateways or XML firewalls have been created specifically to analyze Web services activity. In addition to providing intrusion prevention functions, these technologies also perform firewalling, authentication and authorization services, access control, and audit logging. More information on XML gateways is available from NIST SP 800-95, Guide to Web Services Security (DRAFT) , which is available at ", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Guide to Intrusion Detection and Prevention Systems (IDPS)."}]}
{"id": "nist_00259", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control WE-1000 in Hardware Security Failure Scenarios_ Potential Hardware Weaknesses? (Part 7) Control WE-1000: scenarios: 1. Description / Extended Description Detailed explanation of the fault type 2. Relationships / Memberships Taxonomic information to organize weaknesses into hierarchies and categories 3. Modes of Introduction Descriptions of the life cycle phase in which the CWE can be introduced 4. Applicable Platforms Involved languages and technologies 5. Common Consequences Affected security attributes and likelihoods (e.g., confidentiality, integrity, availability, access control, authentication, and authorization) 6. Demonstrative Examples Hypothetical examples of the weakness 7. Observed Examples Actual observed examples of the weaknesses, usually with CVE references 8. Potential Mitigations Protection methods ## Weakness Abstractions The CWE weaknesses model is composed of four layers of abstraction: pillar (P), class (C), base (B), and variant (V) 1 . The abstraction reflects the extent to which issues are being described in terms of five dimensions: behavior, property, technology, language, and resource. Variant weaknesses are at the most specific level of abstraction and describe at least three dimensions. Base weaknesses are more abstract than variants and more specific than classes; they describe two to three dimensions. Class weaknesses are very abstract and not typically specific about any language or technology; they describe one to two dimensions. Pillar weaknesses are at the highest level of abstraction. In this work, pillars and classes are used to organize the HW security failure scenarios. ## Weakness Views CWE designators (i.e., CWE-XXXX) are given to weaknesses, views, and categories. A view provides a hierarchical organization of CWEs from a particular perspective (e.g., software development, research, or hardware design). A category is a simpler construct that groups a set of CWEs that have some similarity. Views may contain categories within their hierarchy. As of February 9, 2024, the CWE contains 49 views and 374 categories.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Hardware Security Failure Scenarios_ Potential Hardware Weaknesses."}]}
{"id": "nist_00260", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identity and Access Management for Electric Utilities provide? (Section 337) @ozone local]# mv ~/admin2.cer authority/bin/ [root@ozone local]# cd authority/bin/ [root@ozone bin]# ./startAuthority.sh Configuration file not found, would you like to create a new installation? [Y] Y ***WARNING*** NIST SP 1800-2C: Identity and Access Management for Electric Utilities 233 This product MUST be installed by an Ozone Certified Engineer. Pericore, Inc. cannot be held liable for damages resulting from negligent or fraudulent actions of unauthorized or unqualified administrators. Please review all documentation thoroughly before continuing. Continuation of this configuration process represents an agreement to abide by the Pericore EULA. Do you wish to continue? [N] : y Please select the license file for this Ozone Authority.: 1: /usr/local/authority/conf/AuthorityLicense.xml 2: Other... Choice [1] : 1 Please select the configuration file for this Ozone Authority.: 1: /usr/local/authority/conf/AuthorityConfiguration.xml 2: Other... Choice [1] : 1 Do you wish to set any passphrase complexity requirements? [N] : N Note: If you require passphrase at start, you will not be able to restart this Ozone Authority without user intervention. Do you wish to require a passphrase to start this Ozone Authority? [N] N Using keystore type: RSA T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . Do you have an existing keystore you wish to use for this Ozone Authority? [Y] : Y Please select the keystore file for this Ozone Authority:: 1: /usr/local/authority/keystores/authority.jks NIST SP 1800-2C: Identity and Access Management for Electric Utilities 234 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . 2: Other... Choice [1] : 1 Please enter the passphrase.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_00261", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CP-6 in Security and Privacy Controls for Information Systems and Organizations? (Part 2) Control CP-6: s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ omission or commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate storage sites based on the types of threats that are of concern. For threats such as hostile attacks, the degree of separation between sites is less relevant. Related Controls: RA-3. (2) ALTERNATE STORAGE SITE | RECOVERY TIME AND RECOVERY POINT OBJECTIVES Configure the alternate storage site to facilitate recovery operations in accordance with recovery time and recovery point objectives. Discussion: Organizations establish recovery time and recovery point objectives as part of contingency planning. Configuration of the alternate storage site includes physical facilities and the systems supporting recovery operations that ensure accessibility and correct execution. Related Controls: None. (3) ALTERNATE STORAGE SITE | ACCESSIBILITY Identify potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster and outline explicit mitigation actions. Discussion: Area-wide disruptions refer to those types of disruptions that are broad in geographic scope with such determinations made by organizations based on organizational assessments of risk. Explicit mitigation actions include duplicating backup information at other alternate storage sites if access problems occur at originally designated alternate sites or planning for physical access to retrieve backup information if electronic accessibility to the alternate site is disrupted.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00262", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Tip according to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information? Tip: State agencies commonly manage user accounts and credentials for their state CJIS portal, serving as the IdP for users across the state. The cost of this function, both in upfront costs of procuring and implementing MFA and in ongoing costs in help desk support and authenticator lifecycle management, might be alleviated if local, tribal, and territorial agencies had the option to integrate their local identity services with the state portal using identity federation protocols. Section 3.4.2.3 details an example architecture that supports this functionality.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, mfa. Contains security framework guidance for authentication systems. Source: Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information."}]}
{"id": "nist_00263", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices say about Integrity? According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Integrity: The integrity impact level is based on the specific mission and the data supporting that mission, not on the time required to detect the modification or destruction of information. The consequences of unauthorized modification or destruction of information management information (e.g., configuration settings, passwords, authorization codes, cryptographic keying material) can compromise the effectiveness of the system and impair agency operations. The level of impact depends on the criticality of system functionality to the agency mission Special Factors Affecting Integrity Impact Determination : The loss of integrity for some information management information (e.g., encryption keys) can be very serious for agency operations and can have serious consequences for public confidence in the agency. The integrity impact level recommended for information management information associated with highly critical information is high . Recommended Integrity Impact Level: Potentially serious adverse effects can be expected in most government organizations resulting from the unauthorized modification or deletion of information management information. Therefore, the provisional integrity impact level recommended for information management information is moderate .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_00264", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide say about 5.3.4. Person or Entity Authentication (\u00a7 164.312(d)) 139? (Part 6) According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide, 5.3.4. Person or Entity Authentication (\u00a7 164.312(d)) 139: \u2022 Has the organization researched available MFA options and made a selection based on risk to ePHI? \u2022 Is outside vendor support required to implement the process? \u2022 Are there password-less authentication options (e.g., biometric authentication) available that can sufficiently address the risk to ePHI? | | 3. Select and Implement Authentication Options | \u2022 Consider the results of the analysis conducted under Key Activity 2 and select appropriate authentication methods based on the results of the risk assessment and risk management processes. \u2022 Implement the methods selected in organizational operations and activities. | \u2022 Has the organization's selection of authentication methods been made based on the results of the risk assessment? \u2022 If passwords are being used as an authentication element, are they of sufficient length and strength to protect ePHI? Is this enforced by technical policies? \u2022 Has necessary user and support staff training 141 been completed? \u2022 Have a formal authentication policy and procedures been established and communicated? \u2022 Has necessary testing been completed to ensure that the authentication system is working as prescribed? \u2022 Do the procedures include ongoing system maintenance and updates? \u2022 Is the process implemented in such a way that it does not compromise the authentication information (e.g., password file encryption)? | 141 See Section 5.1.5, HIPAA Standard: Security Awareness and Training.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, mfa. Contains security framework guidance for authentication systems. Source: Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide."}]}
{"id": "nist_00265", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IA-32 in Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases? (Part 61) Control IA-32: ustworthiness. ## D.3.1.1 Arm Realms CCA provides architecture support for dynamically created entities called Realms. A Realm [66] [67] contains both user (EL0) and kernel space (EL1) code and data. The higher-privileged entity that manages Realm resources is the NW hypervisor. Realm tenants do not need to trust either the hypervisor or existing SW code. Realms are protected from each other; a Realm does not need to trust other Realms. The CCA RoT enforces authenticity of the CCA platform by attesting to the boot state and security state of a Realm, the authenticity of the Realm content through verification and measurement, and the confidentiality of the guest data through Physical Address Space (PAS) protection and encryption. Realm world is a world separate from both the NW and the SW which already exist in TrustZone. Realm world is designed for the exclusive use of Realms. A Realm protects the information within it from other system entities. Higher-privileged software retains responsibility for allocating and managing the resources utilized by Realms but cannot access their contents. Higher-privileged software also retains responsibility for scheduling within its Realms, but cannot otherwise control or directly observe their execution flow. Specifically, CCA provides: - Additional memory access control, orthogonal to the existing controls enforced using translation tables - Execution state protection - Trustworthy measurement (attestation) of the initial state - A guarantee that the system configuration (for example, whether external debug is permitted) does not change during the lifetime of the Realm (immutability) Realm data remains confidential even after Realm destruction or system reset. Realms are explicitly designed to be created and destroyed on demand. A Non-secure hypervisor can create a new Realm at any time, much like it can create a new VM at any time.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases."}]}
{"id": "nist_00266", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control MP-128 in Security Guidance for First Responder Mobile and Wearable Devices? (Part 31) Control MP-128: or PIN is recommended on most devices. Even if a biometric authentication method is used, such as fingerprint or facial recognition, a PIN or password is required to unlock a device at power-on/reset. Choosing a sufficiently strong password or PIN is important to ensuring strong device encryption. What is suitably strong also depends on device capabilities. Devices that include hardware-backed key stores for device encryption greatly reduce the risk of brute force attacks on the device encryption keys, particularly when these devices automatically delete locally stored mobile data after too many successive failed password/PIN attempts. Gaps : No observable gaps were found concerning data and device encryption. Vender guidance provided clear configuration instructions, where possible. Since encryption is offered during device setup, it is easily user-configurable. Online resources through the vendor or OS manufacturer offered clear instructions on how to set up encryption or where to check the status of the device's encryption. App-based encryption and configuration varies according to the app developer, this is not considered a notable gap for the device. Guidance: Out-of-the-box most devices are encrypted, however, devices that are not encrypted have setup wizards that provide the option to encrypt the device upon initial setup. It is recommended to enable device encryption whenever possible. Application or app-based specific encryption is only recommended in situations where greater data privacy is required, e.g. evidence data, state secrets, or personally identifiable data. App-based encryption is not typical or available for every app and is usually implemented by the app developer. The level and degree of encryption and authentication complexity is also dependent on the device use, user role, and privacy requirements. Device encryption can be enabled through the setup menu of the device, typically under the security configuration section.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Guidance for First Responder Mobile and Wearable Devices."}]}
{"id": "nist_00267", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2014 Annual Report? (Part 53) Control HA-3: plan. The resulting plan included the following areas of focus: - Coordination with Office of Management and Budget (OMB), and other federal agencies, such as National Security Agency (NSA) and U.S. Department of Homeland Security (DHS), on all matters relating to information security and privacy; - Cybersecurity technical transfer and implementation interests, considering items of particular note to individual industry sectors; - Updates from the Privacy and Civil Liberties Oversight Board (PCLOB); - Updates from NIST's CSD regarding cybersecurity and cryptographic work; - Updates regarding embedded software security, including medical device security; - Considerations surrounding Trusted Internet Connections, DHS Enhanced Cybersecurity Services (ECS) and special needs for critical infrastructures; - Procurement and requirements to reduce supply-chain risk; - Cross-Agency Priority Goals (CAP Goals) for cybersecurity; - Information sharing with a focus on information security and privacy; - Updates regarding FISMA, the related security controls (SP 800-53), and FedRAMP; and - Updates of other critical NIST publications. In addition to the work-plan focus areas, the Board also considered the following topics during FY 2014: - Internet of Things (IOT); - Cryptography and NIST Cryptography processes; - Transportation Sector and Vehicle-to-Vehicle Communication; - GAO reports relating to information security and privacy; - Big Data and Privacy; - Controlled Unclassified Information (CUI) Program; - Federal Cloud Credential Exchange (FCCX) and the NSTIC; and - National Cybersecurity Center of Excellence (NCCoE) Updates. The presenters at each Board meeting were leaders and experts representing private industry; academia; federal agency CIOs, IGs and CISOs. Copies of the current list of members and their biographies, the Board's charter and past Board activities are located at http:/ /csrc.nist.gov/groups/SMA/ispab.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_00268", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-11 in Guidelines for Smart Grid Cybersecurity? (Part 548) Control SI-11: P M G S . ( n o i t c e t o r P a d e M i ) . S P G S ( y t i r u c e S l e n n o s r e P y t i r u c e S l a t n e m n o r i v n E d n a ) . E P G S ( l i a c s y h P ) L P G S . ( l i g n n n a P c g e t a r t i S n o i t a z i r o h t u A d n a t n e m s s e s s A y t i r u c e S ) . A C G S ( ) M P G S . ( t n e m e g a n a M m a r g o r P y t i r u c e S ) L P G S . ( i g n n n a P l d n a m e t s y S n o i t a m r o f n I d i r G t r a m S ) . C S G S ( n o i t c e t o r P n o i t a c n u m m o C i d n a m e t s y S n o i t a m r o f n I d i r G t r a m S ) I . S G S ( y t i r g e t n I n o i t a m r o f n I d n a m e t s y S n o i t a m r o f n I d i r G t r a m S ) . A S G S i ( n o i t i s u q c A s e c v r e S i m e t s y S n o i t a m r o f n I d i r G t r a m S ) A M G S . ( e c n a n e t n a M d n a i t n e m p o e v e D l X X X X X X X X X X X X X X 145 ) . C A G S ( l o r t n o C s s e c c A Security Protocols Synchrophasors Certificates: Time and Date Issues Event Logs and Forensics Security for Radio-Controlled Distribution Devices Weak Protocol Stack Implementations Insecure Protocols Unmanaged Call Home Function Patch Management System Trust Model User Trust Model Security Levels Distributed versus Centralized Model of Management Intrusion Detection for Power Equipment ) T A G S . i i ( g n n a r T d n a s s e n e r a w A ) . U A G S ( y t i l i b a t n u o c c A d n a t i d u A ) M C G S . ( t n e m e g a n a M n o i t a r u g i f n o C ) . P C G S ( s n o i t a r e p O f o y t i u n i t n o C ) A I . G S ( n o i t a c i t n e h t u A d n a n o i t a c i f i t n e d I ) R I . G S ( e s n o p s e R t n e d c n I i t n e m e g a n a M t n e m u c o D d n a n o i t a m r o f n I ) D I . G S ( ) P M G S . ( n o i t c e t o r P a d e M i ) .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_00269", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PM-9 in Guide to Operational Technology (OT) Security? Control PM-9: Risk Management Strategy No OT Discussion for this control.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_00270", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does National Online Informative References (OLIR) Program_ Submission Guidance for OLIR Developers provide? (Section 2) 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. 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 Copyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax Approved by the NIST Editorial Review Board on 2024-02-23 Supersedes NIST IR 8278A (November 2020) https://doi.org/10.6028/NIST.IR.8278A Barrett M, Keller N, Quinn S, Smith MC, Scarfone K, Johnson V (2024) National Online Informative References (OLIR) Program: Submission Guidance for OLIR Developers. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Internal Report (IR) NIST IR 8278Ar1. Matthew Barrett: 0000-0002-7689-427X Nicole Keller: 0000-0003-4761-6817 Stephen Quinn: 0000-0003-1436-684X Matthew C. Smith: 0000-0003-1004-7171 Karen Scarfone: 0000-0001-6334-9486 Vincent Johnson: 0000-0002-7363-996X olir@nist.gov National Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000 Additional information about this publication is available at including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). The National Online Informative References (OLIR) Program is a NIST effort to facilitate standardized definitions of Online Informative References (OLIRs) by subject matter experts.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: National Online Informative References (OLIR) Program_ Submission Guidance for OLIR Developers."}]}
{"id": "nist_00271", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does PDA Forensic Tools_ an Overview and Analysis say about Scripts? According to PDA Forensic Tools_ an Overview and Analysis, Scripts: EnCase has built-in scripts that allow the examiner to perform the following tasks: - Consecutive Sectors: This script searches the disk for sectors that are filled entirely with a specified character. The results of the scan are saved in the bookmarks. - Find Unique E-mail Address List: This script searches through selected files for a \"basic\" e-mail signature, this is further checked out using a built-in EnScript function. Once a good hit is found, it is added to a list, so that if the same address is found, it will not be added again. - Graphics File Finder: This script searches for user specified graphics files of the following types: . emf , . jpg , . gif , and . bmp files. After the script has been compiled and run, all graphics files of the specified type are displayed in the graphics library. In addition examiners can craft a customized graphics file finder for additional graphics files (e.g., . png files). - Valid Credit Card Finder: This script will bookmark valid VISA, MasterCard and AmEx numbers. All valid credit card (CC) hits will be bookmarked in the folder \"All CC Hits\". The first occurrence of each CC hit will be bookmarked in \"Unique CC Hits\". Each of the above scripts are run producing a bookmark of the results, which allow the forensic examiner to evaluate the following: a table view of the data, a gallery for pictures (e.g., . jpg , . bmp , . emf , . gif , etc.), a timeline, and the generated report from the script.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PDA Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_00272", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does CVSS Implementation Guidance say about 2.1.3 Authentication? According to CVSS Implementation Guidance, 2.1.3 Authentication: The Authentication metric measures the access an attacker requires to exploit a vulnerability. As the number of times an attacker must authenticate increases the CVSS base score will decrease. There are three possible values for this metric: Multiple (Au:M), Single (Au:S), and None (Au:N). A value for the Authentication metric is assigned to a vulnerability based upon the number of authentication instances required to exploit the vulnerability. To receive a value of Au:M, the attacker must be required to successfully authenticate more than once in order to exploit a vulnerability. For instance, the requirement of authenticating to exploit a vulnerability within a restricted area of a web application, an attacker may need to first authenticate to gain access to the web application, and authenticate another time to gain privileged access. If an attacker must only prove their identity a single time, the Authentication metric is set to 'Single.' Note that this includes authenticating via the command line, a desktop session, or a web interface. Vulnerability CVE-2012-6530 references remote authenticated users; in this case an attacker is required to authenticate to the server (among other considerations) to exploit the vulnerability. Examples of terms that should trigger a vulnerability analyst to believe the vulnerability is AV:S are authenticated users or authenticated attackers . If authentication is not required to successfully exploit a vulnerability it receives a value of Au:N. Many vulnerabilities, such as CVE-2012-3754 and CVE-2011-4583, within Appendix A do not require authentication.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit, cve-. Contains technical security guidance that could inform defensive posture. Source: CVSS Implementation Guidance."}]}
{"id": "nist_00273", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.2.1.17 BDB Format Owner/Type according to NIST Common Biometric Exchange Formats Framework (CBEFF) According to Common Biometric Exchange Formats Framework (CBEFF), 5.2.1.17 BDB Format Owner/Type: In a CBEFF structure the BDB Format Owner and Format Type, when used in combination, uniquely identify the specific format of the BDB content. The format and content of the BDB is 'owned' by the CBEFF Client (see Clause 6.1 ). This BDB format definition may be published (public) or unpublished (non-public). When transforming a CBEFF record from an initial Format to a target Format, the values of these fields shall identify the target BDB format.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Biometric Exchange Formats Framework (CBEFF)."}]}
{"id": "nist_00274", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Conformance Test for FDDI Medium Access Control (MAC) say about FDDI MAC Conformance Test TTCN Machine Processable Form? (Part 2) According to A Conformance Test for FDDI Medium Access Control (MAC), FDDI MAC Conformance Test TTCN Machine Processable Form: pe INTEGER (4000 TO 167772) $PICS_PIXIT $Comment Tester's Requested TTRT. $End_TS_PARdcl $TS_PARdcl $TS_PARid T_Req_IUT $TS_PARtype INTEGER (4000 TO 167772) $PICS_PIXIT $Comment lUT' s Requested TTRT. $End_TS_PARdcl $TS_PARdcl $TS_PARid T_Bid_Max $TS_PARtype INTEGER (4000 TO 167772) $PICS_PIXIT $Comment Highest Bidding Value of Tester in Claim Token Process. $End_TS_PARdcl $TS_PARdcl $TS_PARid T_Bid_Min $TS_PARtype INTEGER (4000 TO 167772) $PICS_PIXIT $Comment Lowest Bidding Value of Tester in Claim Token process. $End_TS_PARdcl $TS_PARdcl $TS PARid M FCS Rev ``` ``` $TS_PARtype BITSTRING $PICS_PIXIT $End_TS_PARdcl $TS_PARdcl $TS_PARid M_FCS_Tramt $TS_PARtype BITSTRING $PICS_PIXIT $End_TS_PARdcl $End_TS_PARdcls $Begin_CONSTdcls $CONSTdcl $CONSTid T_Max $CONSTtype INTEGER $CONSTvalue 167772 $Cornment The maximum value (default value) of TRT . $End_CONSTdcl $CONSTdcl $CONSTid T_Min $CONSTtype INTEGER $CONSTvalue 4000 $Comment The minimum value (default value) of TRT.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, token. Contains security framework guidance for authentication systems. Source: A Conformance Test for FDDI Medium Access Control (MAC)."}]}
{"id": "nist_00275", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain REFERENCES according to NIST Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, REFERENCES: Source Control: AC-05 Supporting Publications: SP 800-162 [22], SP 800-178 [23]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_00276", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Electronic Health Records on Mobile Devices provide? (Section 131) s OpenSSL to generate a proper certificate and copy it to the SD for installation. In case the above methods do not work, it is possible that the specific device requires a special certificate format. The TLS protocol utility functions provided by the open-source OpenSSL may be used to handle conversion of the certificate from one format to another suitable format so installation of a certificate on this device becomes possible. The process for acquiring the CA signed certificate by using the OpenSSL command line tool is (using CN=nccoe525 as an example): 1. Use a Linux server where the OpenSSL Utility is installed. 2. Generate a new private key and Certificate Signing Request: openssl req \u2013newkey rsa:4096 \u2013days 365 keyout nccoe525.key \u2013out nccoe525.csr \u2013 subj \u201c/CN=nccoe525\u201d 3. Have CA sign the certificate. The certificate request you just created in the file \u201ccertreq.tx\u201d will have a blob of data looking something like this: \u201c-----BEGIN NEW CERTIFICATE REQUEST----- -----END NEW CERTIFICATE REQUEST-----.\u201d Copy the blob to a clipboard. 4. Proceed to the CA main page at >:9443/ca/services, and click on SSL End Users Services. 5. Select the certificate profile \u201cManual Administrator Certificate Enrollment.\u201d 6. Paste the blob to the large edit box while accepting the default format \u2018PKCS#10.\u201d 7. Add the subject name: example, CN=nccoe525. 8. Click Submit. 9. If the process is successful, a request number will be displayed for future retrieval of the approved certificate. NIST SP 1800-1C: Securing Electronic Health Records on Mobile Devices 59 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 1 . . 10. The CA administrator will verify the request and approve the certificate. 11. Retrieve the approved certificate by using the Retrieval tab in the CA main page, and save it as a certificate file.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Electronic Health Records on Mobile Devices."}]}
{"id": "nist_00277", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Secure Web Services say about 3.8.3 Reliable Messaging? According to Guide to Secure Web Services, 3.8.3 Reliable Messaging: The WS-Reliability and WS-ReliableMessaging standards provide guaranteed message delivery using one of the following semantics: - At-Least-Once semantics, which is a guarantee that a message will be delivered. - At-Most-Once semantics, which is a guarantee that a duplicate message will not be delivered. - Exactly-Once semantics, which is a guarantee that a message will be delivered without duplication. In addition to the message guarantee semantics, both standards provide a mechanism for sending messages in order. These features are crucial for critical applications that may rely on Web services. Previously, implementers would have to develop their own reliability mechanisms, which could prove costly or ineffective in practice. With the advent of these standards, robust implementations can be developed and used in the development of reliable Web services. Nevertheless, the existence of two competing standards makes it difficult for organizations to fully adopt either standard.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Secure Web Services."}]}
{"id": "nist_00278", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Smart Card Technology_ New Methods for Computer Access Control say about REFERENCES? (Part 2) According to Smart Card Technology_ New Methods for Computer Access Control, REFERENCES: . \"Taking the Media to Task,\" Personal Identification News, April 1986, page 4. - [MCTl 85] Micro Card Technologies, Incorporated, Micro Card (Mask: M4) Designer's Guide, Version 1.8, October 9, 1985. - [MCT2 85] Micro Card Technologies, Incorporated, Micro Card (Mask: M4) Technical Overview, Version 1.0, November 13, 1985. - [MCIV 85l Mclvor, Robert. \"Smart Cards,\" Scientific American, November 1985, pages 152-159. - [PRRY 88l Perry, John G., Technical Support Manager, Ultron Labs Corporation. Private Communication, April 19, 1988. - [RANT 861 Rant, Jon. \"Intel's EPROMs: Lasting Memories for the Long Haul,\" Solutions, March/April 1986, pages 2-7. - fRSKI 871 Rosinski, John J. \"Smart Card Puts a Database in Your Pocket,\" AT&amp;T Technology Products, Systems and Services, Volume 2, ^2, 1987. - fSVGL 85] Svigals, Jerome. Smart Cards: The Ultimate Personal Compufer, MacMillan Publishing Company, New York, 1985. - fSVGL 871 Svigals, Jerome. \"Wall Street Journal Offers How-To Course in ATM/PIN Fraud,\" Smart Cards and Comments, June 1987, page 4. - [TASK 88l Taskett, John, Customer Support Manager, Micro Card Technologies, Incorporated. Private Communication, June 8, 1988. - fWLSN 85l Wilson, John W. \"Superchips: The New Frontier,\" Business Week, June 10, 1985, pages 82-85. U.S. DEPT. OF COMM. BIBLIOGRAPHIC DATA SHEET (See instructions) - 1, PUBLICATION OR REPORT NO. NIST/SP-Bnn/1.S7 2. Performing Orgzui. Report NoJ 3. Publication Date September 1988 4. TITLE AND SUBTITLE Smart Card Technology: New Methods for Computer Access Control 5. AUTHOR(S) Martha E. Haykin and Robert B.J. Warnar 6. PERFORMING ORGANIZATION (If joint or other than NBS, see instructions) NATIONAL BUREAU OF STANDARDS U.S. DEPARTMENT OF COMMERCE GAITHERSBURG, MD 20899 7. Contract/Grant No. 8. Type of Report &amp; Period Covered Final 9. SPONSORING ORGANIZATION NAME AND COMPLETE ADDRESS (Street. City. Stole. ZIP) Same as item 6 10.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Smart Card Technology_ New Methods for Computer Access Control."}]}
{"id": "nist_00279", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Overview and Considerations of Access Control Based on Attribute Encryption say about 5.1.1. Key Management? (Part 2) According to Overview and Considerations of Access Control Based on Attribute Encryption, 5.1.1. Key Management: s one of the attributes and explicitly defining policies so that user identification is required for access requests, or 2) using schemas that assign IDs to keys as used by multi-authority mechanisms. Key escrow: Because a user's private key is generated through the key management service, ABE has the capability of key escrow. However, such a capability can be a positive or negative feature depending on the usages, such as a private organization using it for security control while sacrificing the privacy of its users. Several variant ABE systems have been proposed that remove the escrow by replacing encryption or key generation processes with certificate-based encryption [CRAI], secure key issuing cryptography [BCEKJS], or certificateless cryptography [AP]. Key revocation: One of the major advantages of any identity encryption scheme is that a third party's secret key can be destroyed after all users have been issued keys and if there is only a finite number of users. This can also take place for ABE systems because it assumes that keys are always valid once issued, and there is no method for key revocation to handle secret keys due to expiry of embedded attributes, faulty access policies, or key compromise. Key revocation for ABE can be handled by including the expiry time and date among the attributes, periodic refreshing, and revocation lists [GOLIC].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, key management. Contains security framework guidance for authentication systems. Source: Overview and Considerations of Access Control Based on Attribute Encryption."}]}
{"id": "nist_00280", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-3 in Guide to Operational Technology (OT) Security? Control SI-3: MALICIOUS CODE PROTECTION CNTL NO. CONTROL NAME Control Enhancement Name CONTROL BASELINES LOW MOD HIGH", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_00281", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services say about 4.3.2. Security Continuous Monitoring Category? (Part 8) According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services, 4.3.2. Security Continuous Monitoring Category: Consider subscribing to or enabling user community and PNT | DOT CMPS 3 GPS IS-200 3 GPS IS-705 3 GPS IS-800 3 | | Detect Security Continuous Monitoring Subcategory | Applicability to PNT | References (PNT-Specific) | |-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | CM-7: Monitoring for unauthorized personnel, connections, devices, and software is performed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_00282", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.6 PKI according to NIST Personal Identity Verification Demonstration Summary According to Personal Identity Verification Demonstration Summary, 3.6 PKI: Six of the companies provided PKI functionality. Most of these companies provided card issuance capabilities and partnered with a Certificate Authority (CA). Eighty percent indicated that their CA was part of the Federal Bridge, and the remaining twenty percent stated that joining their CA to the Federal Bridge was in their future plans. At the time of the demonstration, sixty-seven percent of the companies issued certificates following the Common Policy. Eighty-three percent indicated that the FASC-N was contained in the subject alternative name extension of the PIV Authentication X.509 certificate.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, certificate authority. Contains security framework guidance for authentication systems. Source: Personal Identity Verification Demonstration Summary."}]}
{"id": "nist_00283", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EC-1 in A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments? (Part 14) Control EC-1: authorization during each service request and response. Deploying identity-tier policies requires a standardized infrastructure for creating, issuing, and maintaining tamper-proof service identities. Some of the components of this infrastructure are outlined below and also discussed in [5]: - Creation of application identity: The fundamental requirement to enable this is the assignment of a unique identity to each application or service, just like how each user carries a unique identity (e.g., userid). Prior to the era of cloud-based applications, application requests were validated based on the IP subnet or IP address from which they originated. Since ubiquitous access and multi-clouds have eliminated the concept of network perimeters, authentication and authorization based on those parameters are neither feasible nor scalable. Further, the presence of proxies, network address translations, dynamic infrastructures (e.g., migration of applications between VMs), and load balancers make it impossible for the called application to know the IP address of the calling application in order to make authentication or authorization decisions. A unique application identity is required. - Establishment of trust in application identity: The created application (i.e., workload or service) identity should not be subject to spoofing and should be continuously verifiable. An example of workload identity is a SPIFFE ID [4], which is a string that uniquely and specifically identifies a workload and is encoded as a Uniform Resource Identifier (URI). The SPIFFE ID is carried in a cryptographically verifiable document called a SPIFFE Verifiable Identity Document (SVID). SPIFFE supports multiple SVID formats, but the most commonly used is an X.509 certificate. - Discovery of application resources: There should be a robust and secure method for discovering all of the application dependencies consumed over the network (e.g., services, SaaS endpoints, network appliances).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments."}]}
{"id": "nist_00284", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Intrusion Detection and Prevention Systems (IDPS) say about 8.3 Other Technologies with IDPS Capabilities? According to Guide to Intrusion Detection and Prevention Systems (IDPS), 8.3 Other Technologies with IDPS Capabilities: In addition to dedicated IDPS technologies, organizations typically have several other types of technologies that offer some IDPS capabilities and complement the primary IDPSs. This section discusses common types of complementary technologies: network forensic analysis tools, anti-malware technologies (antivirus software and antispyware software), firewalls and routers, and honeypots. 49 For each, a brief overview of the technology is provided, and its use in intrusion detection and prevention and its relationship to IDPSs are explained. Recommendations are also made as applicable for how the complementary technologies should be used alongside of IDPSs.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Guide to Intrusion Detection and Prevention Systems (IDPS)."}]}
{"id": "nist_00285", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure say about 5.3.1. Anomalies and Events? (Part 9) According to Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure, 5.3.1. Anomalies and Events: siderations. | ISO/SAE 21434 Clause 8 and clause 13.3 | | AE-5 | XFC/EVSE | Applicable, but no additional EVSE-specific considerations. | ISA/IEC 62443-2- 1:D4E1 EVENT 1.1, EVENT 1.7 | | AE-5 | Cloud/Third-Party | Applicable, but no additional Cloud/Third-Party-specific considerations. | [NIST-SP800-53r5] IR-4, IR-5, IR-8 | | AE-5 | Utility/Building Management System | Applicable, but no additional Utility/Building Management System-specific considerations. | ISA/IEC 62443-2- 1:D4E1 EVENT 1.1, EVENT 1.7 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure."}]}
{"id": "nist_00286", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain C.2.e There were Varying Perspectives Regarding Additional External Security Requirements according to NIST A Study of Federal Agency Needs for Information Technology Security According to A Study of Federal Agency Needs for Information Technology Security, C.2.e There were Varying Perspectives Regarding Additional External Security Requirements: The study team observed varying attitudes regarding whether security should br 'required\" (i.e., mandated) or, rather, whether it should be the subject of guidance. The security people interviewed understood the value of protecting sensitive information and resources, and doing so was their direct responsibility. Some of these people wanted to be able to point to some documented authority when they are told by others, \"Show me where it says I have to do it. Otherwise, 1 have more pressing things to do.\" They felt although there are existing laws and directives (e.g., the Computer Security Act and OMB Circular A-130), these did not fully serve the security people In these circumstances. Some of these people felt that in their own environments security was well ingrained in the culture. They therefore were less likely to view external requirements to implement security as a burden. The requirements were more likely to be viewed in a larger IT context. It also appeared that such a view permitted a person requesting additional resources to do so more confidently. Other interviewees, however, felt very strongly that additional requirements were not needed and current requirements were adequate. These people felt what would be helpful was meaningful guidance that would make it easier to do what they already know they needed to do. They felt additional security requirements would be burdensome and would make their jobs harder, not easier.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of Federal Agency Needs for Information Technology Security."}]}
{"id": "nist_00287", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guidelines for Securing Radio Frequency Identification (RFID) Systems? (Part 215) Control ES-1: ed equipment is configured to meet operational and security requirements, RFID data is integrated with legacy enterprise systems, and staff are trained in the proper use and maintenance of the system. - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Phase 4: Operations/Maintenance . This phase includes security-related tasks that an organization should perform on an ongoing basis once the RFID system is operational, including conducting periodic security assessments, applying security-related software patches, and reviewing RFID event logs. - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Phase 5 : Disposition . This phase encompasses tasks that occur when a system or its components have been retired, perhaps as a result of a significant upgrade. These tasks include preserving information to meet legal requirements and disabling or destroying tags and other components when they are taken out of service. The practices presented in this section are provided in tables corresponding to the life cycle phases. Each practice is accompanied by a brief explanation of the rationale for its inclusion and is rated as 'recommended' or 'should consider.' Organizations are strongly encouraged to adopt the 'recommended' practices. Failure to implement them significantly increases the risk of an RFID security failure. Organizations should also examine each of the 'should consider' practices to determine their applicability to the target environment. A 'should consider' practice should be rejected only if it is infeasible or if the reduction in risk from its implementation does not justify its cost. Organizations should develop their RFID security controls based not only on the practices in the tables, but also using other guidelines on security controls.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_00288", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Section 10) ............................................ 5 | | 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 | | 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 | | 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 | | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | | 3.1 ACCESSCONTROL | .................................................................................................................. 12 | | 3.2 AWARENESSANDTRAINING | ...................................................................................................", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_00289", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.4.2 Virtual Machine Configuration according to NIST IT Asset Management According to IT Asset Management, 4.4.2 Virtual Machine Configuration: The Openswan virtual machine is configured with two network interface cards, 8 GB of RAM and one CPU core.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IT Asset Management."}]}
{"id": "nist_00290", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements say about Required Vendor Information:? According to Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements, Required Vendor Information:: SCAP.V.4200.1: The vendor SHALL provide instructions on where the CVE IDs can be located within the product output. The vendor SHALL provide procedures and a test environment (if necessary) so that the product will output vulnerabilities with associated CVE IDs. Instructions SHALL include where the CVE IDs and the associated vendor-supplied and official CVE descriptions can be located within the product output. It is acceptable to have CVEs in the form of a specific link for each CVE to the NVD.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements."}]}
{"id": "nist_00291", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommended Cybersecurity Requirements for Consumer-Grade Router Products say about A.6.17. Software Update 3 \u2020? According to Recommended Cybersecurity Requirements for Consumer-Grade Router Products, A.6.17. Software Update 3 \u2020: The integrity of data, including configuration, is preserved when an update is applied. In the case of a failed update, the product should revert to a usable state.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommended Cybersecurity Requirements for Consumer-Grade Router Products."}]}
{"id": "nist_00292", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Blockchain Networks_ Token Design and Management Overview say about Appendix A-Base Layer Consensus and Compute? (Part 4) According to Blockchain Networks_ Token Design and Management Overview, Appendix A-Base Layer Consensus and Compute: provide such guarantees on their own, and zero-knowledge proofs can add privacy features to them. Frameworks have been developed to assess whether a specific use case is suitable for blockchain [168]. Blockchain platforms can provide highly modular and configurable protocols (e.g., pluggable consensus models) that are intended to allow different types of use cases. Per EEA's Client Specification [84], transaction finality 'occurs when a transaction is definitely part of the blockchain and cannot be removed. A transaction reaches finality after some event defined for the relevant blockchain occurs. For example, an elapsed amount of time or a specific number of blocks added.' In a consortium blockchain, where nodes are partially trusted to behave appropriately, transaction finality can usually be considered deterministic (or absolute ). When deterministic, a transaction is deemed final as soon as it provably satisfies an explicit condition, such as being added to a block. In a permissionless blockchain, transaction finality is often probabilistic . The more blocks are added after a transaction is posted, the more final the transaction. This has fundamental ramifications for participants' expectations of data integrity and risks. Additionally, blockchain protocols enable virtual machines for smart contracts that offer application-specific instruction sets (e.g., Bitcoin Script) or general-purpose programming languages (e.g., Solidity [169], Move [9]), which may be Turing-complete . Note that blockchain protocols' execution environments (e.g., Ethereum Virtual Machine [4], WebAssembly open standard (Wasm) [170]) do not interact with the smart contracts themselves but with the bytecodes that the smart contracts compile into. High expressiveness can enable a variety of use cases, but low expressiveness may be a desirable feature too depending on security models.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain Networks_ Token Design and Management Overview."}]}
{"id": "nist_00293", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does The Common Vulnerability Scoring System (CVSS) and its Applicability to Federal Agency Systems say about 2.1.5 Integrity Impact (I)? According to The Common Vulnerability Scoring System (CVSS) and its Applicability to Federal Agency Systems, 2.1.5 Integrity Impact (I): 2.1.5 Integrity Impact (I) This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and guaranteed veracity of information. The possible values for this metric are listed in Table 5. Increased integrity impact increases the vulnerability score. Table 5. Integrity Impact Scoring Evaluation | Metric Value | Description | |----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | None (N) | There is no impact to the integrity of the system. | | Partial (P) | Modification of some system files or information is possible, but the attacker does not have control over what can be modified, or the scope of what the attacker can affect is limited. For example, system or application files may be overwritten or modified, but either the attacker has no control over which files are affected or the attacker can modify files within only a limited context or scope. | | Complete (C) | There is a total compromise of system integrity. There is a complete loss of system protection, resulting in the entire system being compromised. The attacker is able to modify any files on the target system. |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: The Common Vulnerability Scoring System (CVSS) and its Applicability to Federal Agency Systems."}]}
{"id": "nist_00294", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Validating the Integrity of Computing Devices say about 3.2.1 Scenario 1: Creation of Verifiable Platform Artifacts? According to Validating the Integrity of Computing Devices, 3.2.1 Scenario 1: Creation of Verifiable Platform Artifacts: An OEM, VAR, or other authoritative source creates a verifiable artifact that binds reference platform attributes to unique, trusted, hardware-based components of the computing device. The platform attributes in this artifact (e.g., serial number, embedded components, firmware and software information, platform configuration) are used by the purchasing organization during acceptance and provisioning of the computing device. Customers may also create their own platform artifacts to establish a baseline that could be used to validate devices in the field.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validating the Integrity of Computing Devices."}]}
{"id": "nist_00295", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SA-17(01) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control SA-17(01): DEVELOPER SECURITY AND PRIVACY ARCHITECTURE AND DESIGN | FORMAL POLICY MODEL ASSESSMENT OBJECTIVE: Determine if:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00296", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i say about 4.3.2 Counter Mode with Cipher Block Chaining MAC Protocol (CCMP)? (Part 1) According to Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i, 4.3.2 Counter Mode with Cipher Block Chaining MAC Protocol (CCMP): 4.3.2 Counter Mode with Cipher Block Chaining MAC Protocol (CCMP) CCMP is the second data confidentiality and integrity protocol that may be negotiated as a cipher suite for the protection of user traffic in an RSNA. Like TKIP, CCMP was developed to address all known inadequacies of WEP; however, CCMP was developed without the constraint of requiring the use of existing hardware. CCMP is considered the long-term solution for the creation of RSNs for WLANs. It is mandatory for RSN compliance. CCMP is based on CCM, a generic authenticated encryption block cipher mode of AES. 43 CCM is a mode of operation defined for any block cipher with a 128-bit block size. CCM combines two wellknown and proven cryptographic techniques to achieve robust security. First, CCM uses CTR for confidentiality and Cipher Block Chaining MAC (CBC-MAC) for both authentication and integrity protection. CCMP protects the integrity of both the packet data and portions of the IEEE 802.11 header. CCM for IEEE 802.11 employs a single 128-bit session key (TK) to protect the duplex data channel. The 42 The existence of the countermeasures, which include temporary termination of service, enables an attacker to perform a denial of service attack by generating MIC errors. In this case, TKIP preserves integrity at the expense of availability. 43 CCM is defined by RFC 3610, Counter with CBC-MAC (CCM) (http://www.ietf.org/rfc/rfc3610.txt). AES is defined by FIPS PUB 197 (http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf). CCMP key space has size 2 128 and uses a 48-bit packet number (PN) to construct a nonce to prevent replay attacks. The construction of the nonce allows the key to be used for both integrity and confidentiality without compromising either.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i."}]}
{"id": "nist_00297", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Improving Enterprise Patching for General IT Systems: according to NIST Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways According to Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways, Improving Enterprise Patching for General IT Systems:: Utilizing Existing T ools and Performing Processes in Better Ways", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_00298", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain C.2.2.3 Regulatory Creation Information Type according to NIST Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, C.2.2.3 Regulatory Creation Information Type: Regulatory Creation involves the activities of researching and drafting proposed and final regulations. Subject to exception conditions described below, the recommended security categorization for the regulatory creation information type is as follows: Security Category = {(confidentiality, Low), (integrity, Low), (availability, Low)}", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_00299", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Privacy Controls for Information Systems and Organizations provide? (Section 444) organizations may choose to do so. There may be legal considerations when performing and retaining video surveillance, especially if such surveillance is in a public location. Related Controls: None. (4) MONITORING PHYSICAL ACCESS | MONITORING PHYSICAL ACCESS TO SYSTEMS Monitor physical access to the system in addition to the physical access monitoring of the facility at [Assignment: organization-defined physical spaces containing one or more components of the system]. Discussion: Monitoring physical access to systems provides additional monitoring for those areas within facilities where there is a concentration of system components, including server rooms, media storage areas, and communications centers. Physical access monitoring can be coordinated with intrusion detection systems and system monitoring capabilities to provide comprehensive and integrated threat coverage for the organization. Related Controls: None. References: None. PE-7 VISITOR CONTROL [Withdrawn: Incorporated into PE-2 and PE-3.] PE-8 VISITOR ACCESS RECORDS Control: a. Maintain visitor access records to the facility where the system resides for [Assignment: organization-defined time period]; b. Review visitor access records [Assignment: organization-defined frequency]; and c. Report anomalies in visitor access records to [Assignment: organization-defined personnel]. Discussion: Visitor access records include the names and organizations of individuals visiting, visitor signatures, forms of identification, dates of access, entry and departure times, purpose of visits, and the names and organizations of individuals visited. Access record reviews determine if access authorizations are current and are still required to support organizational mission and business functions. Access records are not required for publicly accessible areas. Related Controls: PE-2, PE-3, PE-6.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00300", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does U.S. Department of Energy Risk Assessment Methodology provide? (Section 114) V Risk management - V Contingency planning - V Security tests and evaluations - Certification - Accreditation - V Open door policy - Establishment of computer security organization - Designation of officials with specific duties and responsibilities - Recovery management - V - V V V - V - V - Security incidents - Facility and system access controls - System operation - Backup - Emergency response - Housekeeping COUNTERMEASURES GUIDANCE: ADMINISTRATIVE PROCEDURAL SECURITY AND SECURITY MANAGEMENT STEP 5 RESOURCE TABLE R5.1g V V V V V V V V V - V V V Uninterrupted power supply Surge protectors Power plant physical security Emergency lighting Grounding (equipment and floor mats) Power off control switch V V V V V V V V V V V V - V V - V V - Fire detectors Fire suppression system Portable fire extinguishers - Fire dampers in duct work - Fire rated walls and partitions - Noncombustible construction materials and furnishings - Smoke exhaust systems - Fire fighting teams V V V V V V V V Water drains Water sensors Humidity recording device and sensors Plastic sheeting for equipment - V V V V V V Good housekeeping Emergency evacuation", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: U.S. Department of Energy Risk Assessment Methodology."}]}
{"id": "nist_00301", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1.4 say about &lt;score&gt;? According to Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1.4, &lt;score&gt;: This element contains the weighted score for a Benchmark test, as a real number. Scoring models are defined in Section 3.3. This element may only appear as a child of a TestResult element. Content: string (non-negative number) Cardinality: 1-n Parent Elements: TestResult Attributes: system, maximum Child Elements: none The system attribute, a URI, identifies the scoring model (see the description of the model element on page 62 for a list of pre-defined models). If the system attribute does not appear, then the model used was the default model. The maximum attribute, a real number, gives the maximum possible value of the score for this Benchmark test. If the maximum attribute does not appear, then it is taken to have a value of 100.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1.4."}]}
{"id": "nist_00302", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3 provide? (Section 112) a way to create and manage infrastructure with reduced manual intervention, Open Control was used by GSA's lean startup-influenced digital services agency 18F to facilitate continuous authorization . Continuous authorization is seen as logically similar to agile's continuous deployment . The 18F team employs YAML to implement a schema which is publicly available on GitHub. Infrastructure management involves security and privacy considerations related to hardware operation and maintenance. Some topics related to infrastructure management are listed below. - Threat and vulnerability management - o DoS-resistant cryptographic protocols - Monitoring and alerting - o As noted in the NIST Critical Infrastructure Cybersecurity Framework, Big Data affords new opportunities for large-scale security intelligence, complex event fusion, analytics, and monitoring. - Mitigation - o Breach mitigation planning for Big Data may be qualitatively or quantitatively different. - Configuration Management - o Configuration management is one aspect of preserving system and data integrity. It can include the following: - o Patch management - o Upgrades - Logging - o Big Data must produce and manage more logs of greater diversity and velocity. For example, profiling and statistical sampling may be required on an ongoing basis. - Malware surveillance and remediation - o This is a well-understood domain, but Big Data can cross traditional system ownership boundaries. Review of NIST's 'Identify, Protect, Detect, Respond, and Recover' framework may uncover planning unique to Big Data. - Network boundary control - o Establishes a data-agnostic connection for a secure channel - \uf0a7 Shared services network architecture, such as those specified as 'secure channel use cases and requirements' in the ETSI TS 102 484 Smart Card specifications [100].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, malware. Contains technical security guidance that could inform defensive posture. Source: NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3."}]}
{"id": "nist_00303", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Product Tested according to Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI? Product Tested: UNIX\u00ae System V/88 Release 4.0 Version: 3", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI."}]}
{"id": "nist_00304", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EC-62443 in 2017 NIST_ITL Cybersecurity Program Annual Report? (Part 20) Control EC-62443: occurred on June 19, 2017 at NIST. The FISSEA audience included managers responsible for information systems security awareness, training, certifications, workforce identification, compliance, etc. in federal agencies; contractors providing awareness and training support; and faculty members of accredited educational institutions who are involved in information security training and education. Clarence Williams, Peggy Himes, Gretchen Morris (DB Consulting Group/NASA), and other members of the FISSEA Working Group, were integral to the effort to support the conference. This year's theme was 'Securing the Future to Infinity and Beyond: Improving Cybersecurity through Awareness, Training, and Education'. Attendees gained new techniques for developing/conducting training, cost-effective practices, considerations for compliance, and free resources and contacts. Over 150 cybersecurity training professionals attended the one-day conference. NIST's ITL Director, Charles Romine, welcomed attendees to the event. FISSEA Lifetime Member, Louis Numkin, provided a historical timeline of FISSEA, recognizing 30 years of providing a platform for security specialists to collaborate, network, and learn. Presenters represented NIST, DHS, DoD, HHS, private industry, and academia. Attendees had an opportunity to share about their specific awareness and training programs throughout the conference. The FISSEA Educator of the Year Award was established to recognize and honor a contemporary who is making special efforts to create, build, manage, or inspire an information systems security awareness, training, or education program. Gretchen Morris, 2015 FISSEA Educator of the Year, presented the 2016 FISSEA Educator of the Year Award to Professor Sushil Jajodia of George Mason University. Mrs. Morris shared Mr.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_00305", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does An Introduction to Information Security say about 3.6 Authorizing Official (AO)? According to An Introduction to Information Security, 3.6 Authorizing Official (AO): The Authorizing Official is a senior official or executive with the authority to formally assume responsibility for operating a system at an acceptable level of risk to organizational operations and assets, individuals, and other organizations. Responsibilities include, but are not limited to: - Approving security plans, memorandums of agreement or understanding, plans of action and milestones, as well as determining whether significant changes in the system or environments of operation require reauthorization; and - Ensuring that authorizing official designated representatives carry out all activities and functions associated with security authorization.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: An Introduction to Information Security."}]}
{"id": "nist_00306", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2009 Annual Report say about Security for Grid and Pervasive Systems? (Part 2) According to Computer Security Division 2009 Annual Report, Security for Grid and Pervasive Systems: tacks, protocols, and application programming interfaces (APIs) for the pervasive systems' security functions that have either been embedded or recommended by commercial or standards organizations. In the future, we will focus on analyzing the capabilities and limitations of authorization management infrastructures that the selected grid or pervasive systems of previous research are capable of providing. We will also develop guide documentations or reference implementations using already-developed tools (such as Globus and Access Control languages) to demonstrate how to configure a grid or pervasive system to satisfy the security requirements. We expect that this project will: - Promote (or accelerate) the adoption of community computing that utilizes the power of shared resources and computing time of grid and pervasive infrastructure; - Provide prototype security standards for the authorization management of community computing environments; - Increase security and safety of static (connected) distributed systems by applying the trust domain concept of grid and pervasive computing; and - Assist system architects, security administrators, and security managers whose expertise is related to community computing in managing their systems, and to learn the limitations and practical approaches for their applications. Contact: Dr. Vincent Hu (301) 975-4975 vhu@nist.gov", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Computer Security Division 2009 Annual Report."}]}
{"id": "nist_00307", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IR-6 in Guide to Operational Technology (OT) Security? Control IR-6: (3) INCIDENT REPORTING | SUPPLY CHAIN COORDINATION Select Select Select Select OT Discussion: The organization should report incidents on a timely basis. CISA collaborates with international and private-sector computer emergency response teams (CERTs) to share control systems-related security incidents and mitigation measures. Control Enhancement: (1) OT Discussion: The automated mechanisms used to support the incident reporting process are not necessarily part of or connected to the OT. Control Enhancement: (3) No OT Discussion for this control. 257 NIST SP 800-82r3 September 2023 Guide to Operational Technology (OT) Security", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_00308", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 596) p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P. 8 0 0 - 5 3 A r 5 CHAPTER FOUR PAGE 320 Reference produced from open data h\ue003ps://github.com/usnistgov/oscal-content NIST SP 800-53A, REV. 5 ASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS MP-05 MEDIA TRANSPORT POTENTIAL ASSESSMENT METHODS AND OBJECTS: MP-05-Examine [SELECT FROM: System media protec\ue000on policy; procedures addressing media storage; physical and environmental protec\ue000on policy and procedures; access control policy and procedures; authorized personnel list; system media; designated controlled areas; system security plan; other relevant documents or records]. MP-05-Interview [SELECT FROM: Organiza\ue000onal personnel with system media protec\ue000on and storage responsibili\ue000es; organiza\ue000onal personnel with informa\ue000on security responsibili\ue000es; system/network administrators]. MP-05-Test [SELECT FROM: Organiza\ue000onal processes for storing informa\ue000on media; mechanisms suppor\ue000ng and/or implemen\ue000ng media storage/media protec\ue000on]. MP-05(01) MEDIA TRANSPORT | PROTECTION OUTSIDE OF CONTROLLED AREAS [WITHDRAWN: Incorporated into MP-05.] MP-05(02) MEDIA TRANSPORT | DOCUMENTATION OF ACTIVITIES [WITHDRAWN: Incorporated into MP-05.] MP-05(03) MEDIA TRANSPORT | CUSTODIANS ASSESSMENT OBJECTIVE: Determine if: MP-05(03)[01] a custodian to transport system media outside of controlled areas is iden\ue000\ufb01ed; MP-05(03)[02] the iden\ue000\ufb01ed custodian is employed during the transport of system media outside of controlled areas. POTENTIAL ASSESSMENT METHODS AND OBJECTS: MP-05(03)-Examine [SELECT FROM: System media protec\ue000on policy; procedures addressing media transport; physical and environmental protec\ue000on policy and procedures; system media transport records; audit records; system security plan; other relevant documents or records].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00309", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Web Transactions_ TLS Server Certificate Management say about Technologies? (Part 6) According to Securing Web Transactions_ TLS Server Certificate Management, Technologies: --------------| | Load balancer | F5 Networks BIG-IP Local Traffic Manager | Acts as a TLS server and distributes re- ceived traffic across a number of other TLS servers. | PR.AC-7, PR.DS-2, PR.PT-5 | | DevOps framework | Kubernetes | Open-source container orchestration system for automating application de- ployment, scaling, and management. | PR.PT-5 | | Automated certificate management frameworks | Jetstack Cert- Manager Certbot | Jetstack Cert-Manager provides auto- mated certificate management for Ku- bernetes. Certbot is an automated client that en- rolls and deploys TLS certificates for web servers by using the ACME proto- col. | PR.AC-1, PR.AC-4 | | TLS servers | Apache Microsoft IIS NGINX | The following TLS server configurations were deployed with a TLS server certifi- cate managed as follows: Microsoft IIS: remote agentless certifi- cate management Microsoft IIS attached to the Thales TCT HSM: remote agentless certificate man- agement Apache: remote agentless certificate management Apache: certificate management via the ACME protocol and certbot client NGINX on Kubernetes: Cert-Manager plug-in for automated certificate man- agement of ingresses. | PR.AC-7, PR.DS-2, PR.PT-5 | | Application servers | Apache | These systems represented a second tier of internal application servers that were also deployed with TLS server cer- tificates. | PR.AC-7, PR.DS-2, PR.PT-5 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_00310", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does An Introduction to Information Security say about 7.4 Interdependencies? According to An Introduction to Information Security, 7.4 Interdependencies: Assurance is an issue for every control and safeguard discussed in this publication. One important point to reemphasize here is that assurance is not only for technical controls, but for operational controls as well. Although this chapter focused on systems assurance, it is also important to have assurance that management controls are working properly. Are user IDs and access privileges kept up to date? Has the contingency plan been tested? Can the audit trail be tampered with? Is the security program effective? Are policies understood and followed? As noted in the introduction to this chapter, the need for assurance is more widespread than individuals often realize. Assurance is closely linked to planning for security in the system life cycle. Systems can be designed to facilitate various kinds of testing against specified security requirements. By planning for such testing early in the process, costs can be reduced. Some kinds of assurance cannot be obtained without proper planning.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: An Introduction to Information Security."}]}
{"id": "nist_00311", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD) provide? (Section 793) Test Case Field Description 2020-06-11T19:45:43.985692867Z 2020-06-11 19:45:43,985 mi- cronets-mud-manager: INFO fromDeviceACL: [{'name': 'cl0- frdev', 'matches': {'ipv4': {'ietf-acldns:dst-dnsname': 'www.osmud.org', 'protocol': 6}, 'tcp': {'ietf-mud:direc- tion-initiated': 'from-device', 'destination-port': {'opera- tor': 'eq', 'port': 443}}}, 'actions': {'forwarding': 'ac- cept'}}, {'name': 'myctl0-frdev', 'matches': {'ietf- mud:mud': {'my-controller': [None]}}, 'actions': {'forward- ing': 'accept'}}] 2020-06-11T19:45:43.985885574Z 2020-06-11 19:45:43,985 mi- cronets-mud-manager: INFO Found ietf-mud:mud: {'my-control- ler': [None]} 2020-06-11T19:45:43.987174428Z 2020-06-11 19:45:43,987 mi- cronets-mud-manager: INFO acls: {'device': {'deviceId': '', 'macAddress': {'eui48': ''}, 'networkAddress': {'ipv4': '10.135.4.2'}, 'allowHosts': ['www.osmud.org', 'my-control- ler'], 'denyHosts': []}} 2020-06-11T19:45:43.989185189Z fromDeviceACL: dip: www.osmud.org 2020-06-11T19:45:43.989232148Z fromDeviceACL: dip: my-con- troller 2020-06-11T19:45:43.989236949Z [2020-06-11 19:45:43,988] 172.17.0.1:36620 POST /getFlowRules 1.0 200 296 5824 2020-06-11T19:45:43.990630231Z 2020-06-11 19:45:43,988 quart.serving: INFO 172.17.0.1:36620 POST /getFlowRules 1.0 200 296 5824 IoT device\u2014second onboarding event: MUD manager\u2014log file showing cached file in use: 2020-06-12T14:39:21.769511212Z 2020-06-12 14:39:21,768 mi- cronets-mud-manager: INFO getMudInfo called with: {'url': 'server2.micronets.net/micronets-mud/nist- model-fe_mycontroller.json'} 2020-06-12T14:39:21.770159883Z 2020-06-12 14:39:21,769 mi- cronets-mud-manager: INFO getMUDFile: url: server2.micronets.net/micronets-mud/nist-model-fe_mycontrol- ler.json 2020-06-12T14:39:21.770708123Z 2020-06-12 14:39:21,770 mi- cronets-mud-manager: INFO getMUDFile: mud filepath for server2.micronets.net/micronets-mud/nist- model-fe_mycontroller.json: /mud-cache-dir/nccoe-server2.mi- cronets.net_micronets-mud_nist-model-fe_mycontroller.json...", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_00312", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TG-005 in Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)? (Part 19) Control TG-005: place outside any feasible integrity perimeter. We also note that circularities are fatal to the inductive verification proposed by Clark and Wilson, in that they lead to indefinite recursive descent. ## 3.4.2 Challenge: A Rigorous Demonstration Our challenge in this regard is to demonstrate that the induction is indeed possible, by taking a representation of even a trivial system in an appropriate formal notation, performing the induction, and submitting the result to the social process. An inductive proof of the overall integrity of an applications subsystem which had been checked by the Boyer-Moore theorem prover would be a convincing demonstration. ## 4. Summary and Conclusion We end our report with a question, two admonitions, and a concluding observation. The question addresses the issue raised often in the plenary sessions, to wit, what the economic value of all this is, and forms a final challenge: If one has a mechanism which enforces the E-rules to some degree of assurance, and one has an applications subsystem whose elements all exhibit Clark and Wilson's properties to varying degrees of assurance, and this system is to protect assets of a known value, then how does one estimate the insurance premium to cover loss? The first admonition is to repeat the theme of the challenges that run through this report: work some examples. The history of computer science is replete with proposals for programming languages, system structuring techniques, notations, and assurance technologies which seemed plausible and even desirable when described at the level of detail used by Clark and Wilson, but which collapsed utterly under the stress of actual use. In particular, we admonish the various organizations which are considering the establishment of standards, criteria, and certification mechanisms not to do so until considerable experience has been gained in the implications of these rules.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)."}]}
{"id": "nist_00313", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report_ Authentication Diary Study say about 6.2.4 Management workload for infrequently used passwords? According to Report_ Authentication Diary Study, 6.2.4 Management workload for infrequently used passwords: Multiple participants described the difficulties of managing a password that needs to be renewed more than it is actually used: '[O]nce or twice a year I have to log into a foreign application we have here, and fill out a form, BizFlow, and I usually have to get my password reset because I don't remember what it was. I try a few times, and before I get to the right one I'm locked out.' (P14) 'I don't travel very often, but when I do I have to log in to something called Travel Management. And that password expires just as fast as any other password. Every single time I go to log in to submit my expense reports, first of all, my account is locked because I haven't changed my password in a few months. So then I have to figure out how to unlock it. Then I've got to go change it.' (P19) 'And e-Approval is something that I use so infrequently that each of the past few times I've had to do something in there, I've had to get my password reset, and it is very embarrassing.' (P11) 'Once again security has gotten in my way and it takes me extra time because now I got to look that one up because I don't use that one often enough.' (P17)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report_ Authentication Diary Study."}]}
{"id": "nist_00314", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Test Personal Identity Verification (PIV) Cards Version 2 say about CRL Distribution Points :? According to NIST Test Personal Identity Verification (PIV) Cards Version 2, CRL Distribution Points :: ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_00315", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Taxonomic Rules for Password Policies_ Translating the Informal to the Formal Language say about 2 IDENTIFYING WITHIN SCOPE STATEMENTS? According to Taxonomic Rules for Password Policies_ Translating the Informal to the Formal Language, 2 IDENTIFYING WITHIN SCOPE STATEMENTS: Upon initial perusal, many password policies make similar types of statements. Policies contain length and character set requirements, restrictions on how passwords are stored and whether they can be communicated, and warnings about consequences for a user who enters a password incorrectly too many times. While individual requirements, restrictions, and consequences may di er slightly, the impression is that all policies cover largely similar territory. However, upon closer examination, di erences emerge in the topics covered by di erent policies. Some policies regulate applications' and system administrators' behavior as well as users'. Some policies discourage passwords entirely, recommending either a security token or long passphrases with dramatically di erent composition requirements. Some policies lay out multiple sub-policies, each pertaining to passwords for di erent kinds of accounts (e.g., shared, normal user, privileged user, or system accounts).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Taxonomic Rules for Password Policies_ Translating the Informal to the Formal Language."}]}
{"id": "nist_00316", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Notional Supply Chain Risk Management Practices for Federal Information Systems say about 4.4.2 Integrators - General Requirements? (Part 3) According to Notional Supply Chain Risk Management Practices for Federal Information Systems, 4.4.2 Integrators - General Requirements: uality processes ISO/IEC 9001, ISO/IEC 27001, ISO 28000, and other certifications, which can be leveraged to help ascertain existence of responsible quality practices as they pertain to SCRM; and - b. Measures such as Common Vulnerability Scoring System (CVSS) scores for vulnerabilities and fixes that they release publicly above a particular severity level, before the product ships. - j) Protect against disclosing the uses of system, elements, or processes by which elements are designed, developed, produced, tested, delivered, or supported, or convey technological or operational advantage. - k) Report supply chain threats and incidents in operational environments to agreed-upon recipient(s) within established time frame parameters.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Notional Supply Chain Risk Management Practices for Federal Information Systems."}]}
{"id": "nist_00317", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-7(12) in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Control SI-7(12): Provenance Tracking Detect, Exert", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_00318", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Electronic Health Records on Mobile Devices provide? (Section 45) c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P . 1 8 0 0 - 1 . Appendix A References [1] M. Souppaya and K. Scarfone, Guidelines for Managing the Security of Mobile Devices in the Enterprise, NIST Special Publication 800-124 Revision 1, National Institute of Standards and Technology, Gaithersburg, Maryland, June 2013, http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-124r1.pdf [accessed 4/24/2018]. [2] [3] [4] [5] [6] [7] Fifth Annual Benchmark Study on Privacy and Security of Healthcare Data, Ponemon Institute, May 2015, [accessed 4/24/2018]. J. Pritts, HHS Mobile Devices Roundtable: Health Care Delivery Experts Discuss Clinicians\u2019 Use of and Privacy & Security Good Practices for mHealth, The Office of the National Coordinator for Health Information Technology, Department of Health and Human Services [Website], [accessed 4/24/2018]. R. Kissel, Glossary of Key Information Security Terms, NISTIR 7298 Revision 2, National Institute of Standards and Technology, Gaithersburg, Maryland, May 2013, [accessed 4/24/2018]. Mobile Devices \u2013 Secure Exchange of Electronic Health Information, Final Draft, National Cybersecurity Center of Excellence, National Institute of Standards and Technology, Gaithersburg, Maryland, November 2014, description-final.pdf [accessed 4/24/2018].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Electronic Health Records on Mobile Devices."}]}
{"id": "nist_00319", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.3 Scenarios and Findings according to NIST Mobile Device Security_ Bring Your Own Device (BYOD) According to Mobile Device Security_ Bring Your Own Device (BYOD), 5.3 Scenarios and Findings: One aspect of the security evaluation involved assessing how well the reference design addresses the security characteristics that it was intended to support. The Cybersecurity Framework and Privacy Framework Subcategories were used to provide structure to the security assessment by consulting the specific sections of each standard that are cited in reference to a subcategory. Using these subcategories as a basis for organizing the analysis allowed systematic consideration of how well the reference design supports the intended security and privacy characteristics. This section of the publication provides findings for the security and privacy characteristics that the example solution was intended to support. These topics are described in the following subsections: - development of the Cybersecurity Framework and NICE Framework mappings - development of the Privacy Framework mappings - TEs related to security and example solution architecture mitigations - problematic data actions related to privacy and potential mitigations that organizations could employ An example scenario that demonstrates how an organization may use NIST SP 1800-22 and other NIST tools to implement a BYOD use case is discussed more in the NIST SP 1800-22 Supplement, Example Scenario: Putting Guidance into Practice of this practice guide.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_00320", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Computer Security Log Management? (Part 14) Control ES-1: | List of Figures | List of Figures | | Figure 2-1. Security Software Log Entry Examples ................................................................ | Figure 2-1. Security Software Log Entry Examples ................................................................ | 2-3 | | Figure 2-2. Operating System Log Entry Example ................................................................. | Figure 2-2. Operating System Log Entry Example ................................................................. | 2-4 | | Figure 2-3. Web Server Log Entry Examples ......................................................................... | Figure 2-3. Web Server Log Entry Examples ......................................................................... | 2-6 | | Figure 3-1. Examples of Syslog Messages ............................................................................ | Figure 3-1. Examples of Syslog Messages ............................................................................ | 3-6 | | List of Tables | List of Tables | List of Tables | | Table 4-1. Examples of Logging Configuration Settings......................................................... | Table 4-1. Examples of Logging Configuration Settings......................................................... | 4-6 | ## This page has been left blank intentionally. ## Executive Summary A log is a record of the events occurring within an organization's systems and networks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Computer Security Log Management."}]}
{"id": "nist_00321", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Engineering Trustworthy Secure Systems say about J.3.1. Security Purpose? According to Engineering Trustworthy Secure Systems, J.3.1. Security Purpose: - -Identify security considerations for projects to meet the strategic objectives of the organization.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_00322", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1.4 say about 7. Appendix B - Sample Benchmark File? (Part 4) According to Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1.4, 7. Appendix B - Sample Benchmark File: stract=\"1\" cluster-id=\"finger\"> <cdf:title>IOS - no IP finger service</cdf:title> <cdf:description> Disable the finger service, it can reveal information about logged in users to unauthorized parties. (For <cdf:sub idref=\"os-name\"/> version 11.3 and later.) </cdf:description> <cdf:question>Prohibit the finger service</cdf:question> <cdf:ident system=\"http:/cce.mitre.org/\">CCE-12345</cdf:ident> <cdf:impact-metric>AV:R/AC:L/Au:N/C:P/I:N/A:N</cdf:impact-metric> <cdf:fixtext fixref=\"no-finger\" xml:lang=\"en\"> Turn off the finger service altogether, it is <htm:i>very</htm:i> rarely used.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1.4."}]}
{"id": "nist_00323", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.3. SSC Security for CI/CD Pipelines - Implementation Strategy according to NIST Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines, 5.3. SSC Security for CI/CD Pipelines - Implementation Strategy: The extensive set of steps needed for SSC security cannot be implemented all at once in the SDLC of all enterprises without a great deal of disruption to underlying business processes and operational costs. Rather, solutions that provide SSC security can be broadly classified into the following types [17]: 1. Solutions that ensure SSC security through features associated with each task in the DevSecOps pipelines: - a. Verifying that the software is built correctly by ensuring tamper-proof build pipelines, such as by providing verified visibility into the dependencies and steps used in the build [18], since compromised dependencies or build tools are the greatest sources for poisoned workflows. - b. Including features for the specification of checklists for each step of the delivery pipeline to provide guidance for implementation and to check and enforce controls for complying with checklists. 2. Solutions that ensure integrity and provenance through digital signatures and attestations 3. Strategy to ensure that running code is up to date, such as instituting a 'build horizon' (i.e., code that is older than a certain time period should not be launched), to keep production as close as possible to the committed code in the repositories. 4. Securing CI/CD clients to prevent malicious code from stealing confidential information (e.g., proprietary source code, signing keys, cloud credentials), reading environment variables that may contain secrets, or exfiltrating data to an adversary-controlled remote endpoint.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, secret. Contains guidance on protecting sensitive government information. Source: Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines."}]}
{"id": "nist_00324", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Scripting Language according to Guidelines on Active Content and Mobile Code? Scripting Language: A definition of the syntax and semantics for writing and interpreting scripts.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Active Content and Mobile Code."}]}
{"id": "nist_00325", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST_SP_800-37r2_Risk_Management_Framework say about SYSTEM LIFE CYCLE CONSIDERATIONS? According to NIST_SP_800-37r2_Risk_Management_Framework, SYSTEM LIFE CYCLE CONSIDERATIONS: OTHER FACTORS EFFECTING THE EXECUTION OF THE RMF ll systems, including operational systems, systems under development, and systems that are undergoing modification or upgrade, are in some phase of the SDLC. 166 Defining requirements is a critical part of an SDLC process and begins in the initiation phase. 167 Security and privacy requirements are part of the functional and nonfunctional 168 requirements allocated to a system. The security and privacy requirements are incorporated into the SDLC simultaneously with the other requirements. Without the early integration of security and privacy requirements, significant expense may be incurred by the organization later in the life cycle to address security and privacy concerns that could have been included in the initial design. When security and privacy requirements are defined early in the SDLC and integrated with other system requirements, the resulting system has fewer deficiencies, and therefore, fewer privacy risks or security vulnerabilities that can be exploited in the future. A Integrating security and privacy requirements into the SDLC is the most effective, efficient, and cost-effective method to ensure that the organization's protection strategy is implemented. It also ensures that security and privacy processes are not isolated from the other processes used by the organization to develop, implement, operate, and maintain the systems supporting ongoing missions and business functions. In addition to incorporating security and privacy requirements into the SDLC, the requirements are integrated into the organization's program, planning, and budgeting activities to help ensure that resources are available when needed and program and project milestones are completed. The enterprise architecture provides a central record of this integration within an organization.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: rmf, fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_00326", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Recovering from Ransomware and Other Destructive Events say about ABSTRACT? According to Data Integrity_ Recovering from Ransomware and Other Destructive Events, ABSTRACT: Businesses face a near-constant threat of destructive malware , ransomware, malicious insider activities, and even honest mistakes that can alter or destroy critical data. These data corruption events could cause a significant loss to a company's reputation, business operations, and bottom line. These types of adverse events, that ultimately impact data integrity, can compromise critical corporate information including emails, employee records, financial records, and customer data. It is imperative for organizations to recover from a data integrity attack and trust the accuracy and precision of the recovered data. The National Cybersecurity Center of Excellence (NCCoE) at NIST built a laboratory environment to explore methods to effectively recover from a data corruption event in various Information Technology (IT) enterprise environments. NCCoE also implemented auditing and reporting IT system use to support incident recovery and investigations. This NIST Cybersecurity Practice Guide demonstrates how organizations can implement technologies to take immediate action following a data corruption event. The example solution outlined in this guide encourages effective monitoring and detection of data corruption in standard, enterprise components as well as custom applications and data composed of open-source and commercially available components.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Recovering from Ransomware and Other Destructive Events."}]}
{"id": "nist_00327", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Maintain Environmental Safety according to NIST Cybersecurity Framework Manufacturing Profile According to Cybersecurity Framework Manufacturing Profile, Maintain Environmental Safety: Manage cybersecurity risks that could adversely affect the environment, including both accidental and deliberate damage. Cybersecurity risk on the manufacturing system could potentially adversely affect environmental safety. Personnel should understand cybersecurity and environmental safety interdependencies.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile."}]}
{"id": "nist_00328", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2 provide? (Section 104) ated with &lt;dt:signature-info&gt; as specified in [TMSAD]. 2. The first &lt;dsig:Reference&gt; element in a &lt;dsig:Signature&gt; element MUST be to the &lt;arf:asset-report-collection&gt; element. The element MUST be referenced in the @URI attribute using the empty string convention ''. 3. Two XPath Filter 2 transforms MUST exist on the first &lt;dsig:Reference&gt; element in a &lt;dsig:Signature&gt; element. Both MUST specify a filter type of 'subtract'. The first transform MUST specify the XPath '/arf:asset-report-collection/arf:extendedinfos[count(arf:extended-info[dsig:Signature]) = count(*)]'. The second transform MUST specify the XPath '/arf:asset-report-collection/arf:extended-infos/arf:extended-info[dsig:Signature]'. In both cases, the namespace prefix 'arf' MUST map to the ARF namespace specified in this document. 4. The second &lt;dsig:Reference&gt; element MUST be to the &lt;dsig:SignatureProperties&gt; element captured in a &lt;dsig:Object&gt; element with the &lt;dsig:Signature&gt; element. The &lt;dsig:SignatureProperties&gt; element MUST be referenced in the @URI attribute using '#' + @Id of the &lt;dsig:SignatureProperties&gt; element. 5. Key information SHOULD be provided on the &lt;dsig:Signature&gt; element. In situations where it is desirable to countersign a result data stream (e.g., when a content consumer automatically signs a result data stream and then a person also wants to sign the results), the following requirements apply. 1. The &lt;arf:extended-info&gt; element containing the original signature SHALL be removed from the resulting document. 2. The original signature SHALL be captured as a &lt;dsig:Object&gt; element on the new &lt;dsig:Signature&gt; element. 3. The first &lt;dsig:Reference&gt; element on the new &lt;dsig:Signature&gt; element SHALL reference the &lt;dsig:Object&gt; element containing the original signature.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2."}]}
{"id": "nist_00329", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings provide? (Section 245) are rather trivial. When A performs a single sign-on, she and her authentication server R first perform mutual authentication using a shared password, and then establish a secure channel (as before). Subsequently, R runs the PARTIAL-PRIVATE-KEY EXTRACT algorithm and issues a partial private key ( S R + s R P \u00af A ) to A , along with other information such as the system parameters and an updated IRL. \u00af When A receives the partial private key, she runs the LOWER-LEVEL SETUP algorithm to randomly pick a seA can then use the proxy cret value s . This secret value, in turn, is used to compute \u00af A her proxy public/private key pair. credential to perform mutual authentication and delegation with a hosting server. Since the value s is unknown to R , A 's new proxy private key is kept secret from R , which is not the case in the protocols described in Section 3.3. \u00af A The cryptographic set-up in CL-PKC allows users to create more than one public key for the same partial private key [3]. For example, A can randomly select two different secret values s and s \u2032 , and compute two sets of dis-\u00af tinct public/private key pairs. However, we believe that this property would not cause any major issues within a grid environment. This is because partial private keys produced by the authentication server are short-lived. In fact, the users can take advantage of this property by extracting different proxy key pairs for different job submissions to increase key freshness, before the expiry of their respective partial private keys. \u00af A A In the context of CL-PKC, we must trust the authentication server not to mount active impersonation attacks against its users. Such attacks are possible because the authentication server can always select a secret value (for some 'victim') and calculate a private key based on the victim's partial private key to which it necessarily has access.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, single sign-on. Contains security framework guidance for authentication systems. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_00330", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Function call according to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography? Function call: RecoverPrimeFactors( n , e , d )", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography."}]}
{"id": "nist_00331", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Telehealth Remote Patient Monitoring Ecosystem provide? (Section 76) \u00a7\u00a7 164.310(a)(2)(ii) 164.310(a)(2)(iii) | A.11.1.1 A.11.1.2 | | NIST Cybersecurity Framework v1.1 | NIST Cybersecurity Framework v1.1 | NIST Cybersecurity Framework v1.1 | NIST Cybersecurity Framework v1.1 | NIST NICE | Sector-Specific Standards and Best Practices | Sector-Specific Standards and Best Practices | Sector-Specific Standards and Best Practices | |-------------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------------|----------------------------------|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------| | Function | Category | Subcategory | NIST SP 800-53 Revision 5 | Framework (NIST SP 800-181) | IEC TR 80001-2-2 | HIPAA Security Rule | ISO/IEC 27001 | | | | potential cybersecurity events | | AN-TWA- 001 | | | | | | | DE.CM-4: Malicious code is detected | SC-44 SI-3 SI-4 SI-8 | | IGAU MLDP | 45 C.F.R.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_00332", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.6 Monitor, Evaluate, and Adjust according to NIST Integrating Cybersecurity and Enterprise Risk Management (ERM) According to Integrating Cybersecurity and Enterprise Risk Management (ERM), 3.6 Monitor, Evaluate, and Adjust: Step 6 in Figure 2 (Monitor, Evaluate, and Adjust) focuses on managing cybersecurity risk to support mission and business objectives. By protecting the value provided by enterprise information and technology; it requires the continual balancing of benefits, resources, and risk considerations. As an input to ERM, CSRM requires a dynamic and collaborative process to maintain that balance by continually monitoring risk parameters, evaluating their relevance to organizational objectives, and responding accordingly when necessary (e.g., by adjusting controls). The risk register provides a formal communication vehicle for sharing and collaborating on cybersecurity risk activities as an input to ERM decision makers. Beginning with the initial agreement and understanding of internal/external context and continuing to discussion and determination and implementation of risk response, ongoing dialogue is needed among all relevant stakeholders. While such discussions often occur within a given business unit or subordinate organization, the enterprise will benefit from broader, frequent, and transparent communication regarding risk options, decisions, changes, and adjustments because it will improve the quality of information used in making enterprise-level decisions. The evolving cybersecurity risk registers and profiles provide a formal method for communicating institutional knowledge and decisions regarding cybersecurity risks and their contributions to ERM.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Integrating Cybersecurity and Enterprise Risk Management (ERM)."}]}
{"id": "nist_00333", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Practical Combinatorial Testing say about Appendix D - REFERENCES? (Part 3) According to Practical Combinatorial Testing, Appendix D - REFERENCES: n Computer Aided Verification CAV , volume 1102 of Lecture Notes in Computer Science , pages 419422, New Brunswick, NJ, USA, July/August 1996. Springer Verlag. 19. M.B. Cohen, J. Snyder, G. Rothermel. Testing Across Configurations: Implications for Combinatorial Testing, Workshop on Advances in Model-based Software Testing , Raleigh, Nov. 2006, pp. 1-9 20. D. M. Cohen, S. R. Dalal, J. Parelius, G. C. Patton The Combinatorial Design Approach to Automatic Test Generation, IEEE Software , Vol. 13, No. 5, pp. 83-87, September 1996 21. L. Copeland, A Practitioner's Guide to Software Test Design , Artech House Publishers, Boston, 2004. 22. Apilli, B. S., L. Richardson, C. Alexander, Fault-based combinatorial testing of web services. In Proc. 24th ACM SIGPLAN Conference Companion on Object Oriented Programming Systems Languages and Applications (Orlando, October 25 29, 2009) 23. Dalal, S.R., C.L. Mallows, Factor-covering Designs for Testing Software, Technometrics , v. 40, 1998, pp. 234-243. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ 24. S. Dunietz, W. K. Ehrlich, B. D. Szablak, C. L. Mallows, A. Iannino. Applying design of experiments to software testing, Proceedings of the Intl. Conf. on Software Engineering, (ICSE '97) , 1997, pp. 205-215, New York 25. L. du Bousquet, Y. Ledru, O. Maury, C. Oriat, J.-L. Lanet, A case study in JMLbased software validation. Proceedings of 19th Int. IEEE Conf. on Automated Sofware Engineering , pp. 294-297, Linz, Sep. 2004 26. M. Grindal, J. Offutt, S.F. Andler, Combination Testing Strategies: a Survey, Software Testing, Verification, and Reliability , v. 15, 2005, pp. 167-199. 27. C.A.R. Hoare, 'Assertions, a Personal Perspective', IEEE Annals of the History of Computing, vol. 25, no. 2, pp. 14-25, 2003. 28. R. Kramer, 'iContract - The Java Design by Contract Tool'.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Practical Combinatorial Testing."}]}
{"id": "nist_00334", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Labels for Open Systems_ an Invitational Workshop provide? (Section 57) il 1977. - [2] ISO 7498, Information Processing Systems - Open Systems Interconnection Basic Reference Model. - [3] ISO 7498/2, Addendum to ISO 7498 on Security Architecture. - [4] Branstad, Dennis K. \"Categories of Information Requiring Protection,\" Proceedings from INTEROP 89, Advanced Computing Environments, October 1989. 5. Estrin, Deborah. \"Requirements for a Commercial-Use IP Security Option\" Proceedings from INTEROP 89, Advanced Computing Environments, October 1989. [5] \"Security Labels in Open Systems\" (Presentation Slides) , Russell Housley (Xerox Corporation) . r Russell Housley Xerox Special Information Systems McLean, Virginia 31 May 1990 \\ ) r V - The measures taken to protect data from accidental, unauthorized, intentional, or malicious modification, destruction, or disclosure. - A condition that results from the establishment and maintenance of protective measures. Xerox Special Information Systems J r - Security labels tell the protocol processing how to handle data communicated between open systems. That is, the security label indicates what measures need to be taken to preserve the condition of security. - \"Handle\" denotes the activities performed on data such as collecting, processing, transferring, storing, retrieving, sorting, transmitting, disseminating, and controlling. Xerox Special Information Systems r V - Data integrity service - Biba integrity - Data confidentiality service - Bell &amp; LaPadula secrecy Xerox Special Information Systems A J r V.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Labels for Open Systems_ an Invitational Workshop."}]}
{"id": "nist_00335", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Considerations for Remote Electronic UOCAVA Voting say about 7.3.4 Social Engineering? According to Security Considerations for Remote Electronic UOCAVA Voting, 7.3.4 Social Engineering: Social engineering is a class of attack where malicious (or curious) individuals manipulate legitimate users of a system into divulging sensitive information, such as login credentials for a system. Phishing and pharming can be considered a type of large-scale, automated social engineering attack, but social engineering attacks could be highly targeted and interactive. For instance, an attacker conducting a social engineering attack could call an election official or system administrator claiming to be from the service provider hosting the voting system and convince the victim to divulge his or her password. Social engineering is a class of attacks, and the objective of the attacker may not be solely to steal login credentials. The objectives of social engineers can be to obtain any type of sensitive information that may help them conduct an attack.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Remote Electronic UOCAVA Voting."}]}
{"id": "nist_00336", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Domain Name System-Based Electronic Mail Security say about Test Sequence 2: MUA/MTA/DNS Service Combinations Exchanged Signed and Encrypted Email with an NLnet Labs Site and a Secure64 Site? According to Domain Name System-Based Electronic Mail Security, Test Sequence 2: MUA/MTA/DNS Service Combinations Exchanged Signed and Encrypted Email with an NLnet Labs Site and a Secure64 Site: Outlook and Thunderbird MUAs, configured to use a Postfix MTA with Dovecot IMAP support, were configured in turn to use BIND and Secure64's DNS Authority, DNS Cache, and DNS Signer implementations. Each of the six configurations exchanged email with a Secure64 site that included a ThunderBird MUA, DNS Cache/DNS Signer/DNS Authority DNS services, and Postfix/ Dovecot MTA and an NLnet Labs MUA/MTA/ DNS service stack that included a ThunderBird MUA, NSD4, Unbound, and OpenDNSSEC DNS services and a Postfix/Dovecot MTA. The test events include using Well-Known CA issued (TLSA/SMIMEA CU=1), Enterprise CA issued (CU=2), and Self-Signed Certificates (CU=3). Email messages between MTAs were encrypted and successfully decrypted. (Scenario 1). Signature and encryption were logged. All messages were S/MIME signed. Outlook attempted to verify received messages (Scenario 2). Signature verification results were noted. DNS name verification results were noted. Figure 2.1 on Page 8 depicts the set-up for laboratory support for this test sequence, with connections selected for Event 7 below.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_00337", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-37r2_Risk_Management_Framework provide? (Section 295) The risk executive (function) coordinates with senior leaders and executives to: - Establish risk management roles and responsibilities; - Develop and implement an organization-wide risk management strategy that provides a strategic view of security risks for the organization 120 and that guides and informs organizational risk decisions (including how risk is framed, assessed, responded to, and monitored over time); - Provide a comprehensive, organization-wide, holistic approach for addressing risk-an approach that provides a greater understanding of the integrated operations of the organization; - Manage threat, vulnerability, and security and privacy risk (including supply chain risk) information for organizational systems and the environments in which the systems operate; - Establish organization-wide forums to consider all types and sources of risk (including aggregated risk); - Identify the organizational risk posture based on the aggregated risk from the operation and use of systems and the respective environments of operation for which the organization is responsible; - Provide oversight for the risk management activities carried out by organizations to help ensure consistent and effective risk-based decisions; - Develop a broad-based understanding of risk regarding the strategic view of organizations and their integrated operations; - Establish effective vehicles and serve as a focal point for", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_00338", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Measuring the Common Vulnerability Scoring System Base Score Equation say about Measuring the Common Vulnerability Scoring System Base Score Equation? According to Measuring the Common Vulnerability Scoring System Base Score Equation, Measuring the Common Vulnerability Scoring System Base Score Equation: Peter Mell Jonathan Spring Domain Expert Co-authors: Dave Dugal Srividya Ananthakrishna Francesco Casotto Troy Fridley Christopher Ganas Arkadeep Kundu Phillip Nordwall Vijayamurugan Pushpanathan Daniel Sommerfeld Matt Tesauro Chris Turner This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8409 <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Measuring the Common Vulnerability Scoring System Base Score Equation."}]}
{"id": "nist_00339", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain NISTIR 7756 (DRAFT): CAESARS Framework Extension: An Enterprise Continuous Monitoring Technical Reference Architecture Group: Systems and Emerging Technologies Security Research according to NIST Computer Security Division 2011 Annual Report According to Computer Security Division 2011 Annual Report, NISTIR 7756 (DRAFT): CAESARS Framework Extension: An Enterprise Continuous Monitoring Technical Reference Architecture Group: Systems and Emerging Technologies Security Research: This publication and its supporting documents present an enterprise continuous monitoring technical reference model that extends the framework provided by the DHS Federal Network Security CAESARS architecture. This extension enables added functionality, defines each subsystem in more detail, and further leverages security automation standards. It also extends CAESARS to allow for large implementations that need a multitier architecture and focuses on the necessary intertier communications. The goal of this document is to facilitate enterprise continuous monitoring by presenting a reference model that enables organizations to aggregate collected data from across a diverse set of security tools, analyze that data, perform scoring, enable user queries, and provide overall situational awareness. The model design is focused on enabling organizations to realize this capability by leveraging their existing security tools and thus avoiding complicated and resource-intensive custom tool integration efforts.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, continuous monitoring. General security reference material without sensitive content. Source: Computer Security Division 2011 Annual Report."}]}
{"id": "nist_00340", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1.4 say about Profile? (Part 4) According to Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1.4, Profile: Multiple platform URIs may be listed if the Profile applies to several platforms | | reference | string + URL | 0-n | A reference to a document or resource where the user can learn more about the subject of this Profile: a string and optional URL | | selectors | special | 0-n | References to Groups, Rules, and Values, see below (references may be the unique id of an Item, or a cluster id) | | signature | special | 0-1 | Digital signature over this Profile, optional | A Profile object is a named tailoring of a Benchmark. While a Benchmark can be tailored in place, by setting properties of various objects, only Profiles allow one Benchmark document to hold several independent tailorings. A Profile can extend another Profile in the same Benchmark. The set of platform, reference, and selector properties of the extended Profile are prepended to the list of properties of the extending Profile. Inheritance of title, description, and reference properties are handled in the same way as for Rule objects. The note-tag property is a simple identifier. It specifies which profile-note properties on Rules should be associated with this Profile. Benchmark authors can use the Profile's 'status' property to record the maturity or consensus level of a Profile. If the status is not given explicitly in a Profile definition, then the Profile is taken to have the same status as its parent Benchmark. Note that status properties are not inherited. Each Profile contains a list of selectors which express a particular customization or tailoring of the Benchmark. There are four kinds of selectors: - select - a Rule/Group selector. This selector designates a Rule, Group, or cluster of Rules and Groups.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1.4."}]}
{"id": "nist_00341", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Contacts according to Computer Security Division 2007 Annual Report? Contacts: Mr. Kevin Stine (301) 975-4483 kevin.stine@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2007 Annual Report."}]}
{"id": "nist_00342", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3. The 4-Chip DES according to NIST Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard According to Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard, 3. The 4-Chip DES: In summary, we are going to use four of these devices, where each device consists of two 8-bit shift registers for the data, four 8-bit shift registers for the key and two 64 X 4 ROM's for the S tables. Each device will have a parity check facility for the key and other required control logic. The four devices will work in parallel from a single clock. Our estimate of the speed is that it could be clocked at 5 megahertz. The two control lines that I mentioned would implement four control functions. The first is load key, the second is load data, the third instruction is to encrypt and the fourth is to decrypt data. The device will check parity of the key as it is entered and set a flag for the microprocessor control if the parity is incorrect. It will not, however, prevent operating with a \"bad\" key. It takes eight clock pulses to load the key and eight more clock pulses to load the data. Then the devices require sixteen more clock pulses to either encrypt or decrypt the data, and eight additional clock cycles to unload the devices. However, the next eight bytes can be loaded at the same time that the unloading is taking place. Therefore, only twenty- four cycles are used for a complete operation of the DES unit. With a clock operating at 5 megahertz, this gives an effective throughput of 13 million bits per second, or in other words, each 64-bit block requires 5 micro-seconds to encrypt or decrypt. Our company is planning to build these LSI devices and market them in various forms to our customers. <!-- image --> Howard Crumb Federal Reserve Bank 33 Liberty Street New York, N. Y. 10045 The following paper has been extracted from the verbal presentation of Mr. Crumb at the February 15th Conference. A written paper had not been submitted at the time of publication of these proceedings.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard."}]}
{"id": "nist_00343", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to NIST_SP_800-53r5_Security_Privacy_Controls? Discussion: Environmental controls include fire suppression and detection devices or", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00344", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Web Transactions_ TLS Server Certificate Management say about Microsoft Active Directory and Domain Services Installation and Configuration? According to Securing Web Transactions_ TLS Server Certificate Management, Microsoft Active Directory and Domain Services Installation and Configuration: Active Directory Services (ADS) and DNS work together to store directory data and make those resources available to administrators and users. For example, ADS stores information about user accounts such as names and passwords. Security is integrated with ADS through log-on authentication and enforced access control for user, file, directory, and other system objects in the directory of services. Administrators are able to manage directory data and organization roles across the enterprise. They can assign permissions to users, which allows users to access resources anywhere on the network. ADS authenticates and authorizes all users and computers in a Windows domain network. ADS works in conjunction with Group Policies Objects (GPOs) in assigning and enforcing security policies for all computers. A DNS is a protocol for how computers translate domain names. It manages a database used to resolve domain names to IP addresses, allowing computers to identify each other on the network. DNS is the primary locator service for AD. ADS is highly dependent on the DNS in most cases, and as a result, most implementations-including the TLS lab-opt to install the DNS service on the same server as the ADS.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_00345", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-08(09) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control CM-08(09): SYSTEM COMPONENT INVENTORY | ASSIGNMENT OF COMPONENTS TO SYSTEMS ASSESSMENT OBJECTIVE: Determine if:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00346", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Section 175) ng as intended. Also used to refer to units of related data fields (i.e., groups of data fields that can be accessed by a program and that contain the complete set of information on particular items). | | risk [OMB A-130] | A measure of the extent to which an entity is threatened by a potential circumstance or event, and typically is a function of: (i) the adverse impact, or magnitude of harm, that would arise if the circumstance or event occurs; and (ii) the likelihood of occurrence. | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | risk assessment [SP 800-30] | The process of identifying risks to organizational operations (including mission, functions, image, reputation), organizational assets, individuals, other organizations, and the Nation, resulting from the operation of a system. | |-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | sanitization | Actions taken to render data written on media unrecoverable by both ordinary and, for some forms of sanitization, extraordinary means. Process to remove information from media such that data recovery is not possible. | | security | A condition that results from the establishment and maintenance of protective measures that enable an organization to perform its mission or critical functions despite risks posed by threats to its use of systems.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00347", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Design Alternatives for Computer Network Security say about 5.4.2 Spoofability? According to Design Alternatives for Computer Network Security, 5.4.2 Spoofability: Depending on the encryption method, different spoofing methods can cause confusion, or at least errors, in communications. If a self-synchronizing method is utilized, then play-back of recorded messages is possible and must be countered by the usage of sequence numbers or time stamps. If these mechanisms are not provided, one might still be able to recognize a duplicate message, unless it had been modified. However, modification of the cipher text would result in the error propagation effect and thereby introduce a large number of erroneous bits, helping to ensure that the forgery was detected. (Check sums could also be utilized to detect changes in other encipherment schemes) Spoofing threats can be countered by: (1) detecting modified messages by use of error checks on the clear text, (2) detecting the \"replaying\" of legitimate messages by the use of encrypted sequence numbers or time stamps, and (3) discar&lt; ing any messages that do not meet these checks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Design Alternatives for Computer Network Security."}]}
{"id": "nist_00348", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Trustworthy Email say about 5.2.2.3 Certificate Revocation? According to Trustworthy Email, 5.2.2.3 Certificate Revocation: Every certificate has a period of validity typically ranging from 30 days up to a numbe r of years. \ufffdere may , however, be reasons to revoke a certificate prior to its expiration, such as the compromise or loss of the private key [RFC5280]. \ufffde act of revocation is associated with the CA publishing a certificate revocation list . Part of authenticating a certificate chain is perusing the certificate revocation list (CRL) to determine if any certificate in the chain is no longer valid . \ufffde presence of a revoked certificate in the chain should result in failure of authentication. Among the problems of CRL management, the lack of real-time revocation checks leads to nondeterminism in the authentication mechanism. Problems with revocation led the IETF to develop a realtime revocation management protocol, the Online Certificate Status Protocol (OCSP) [RFC6960]. Mozilla has now taken the step to deprecate CRLs in favor of OCSP.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Trustworthy Email."}]}
{"id": "nist_00349", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.5.2 Preinstallation Steps according to NIST Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers According to Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers, 2.5.2 Preinstallation Steps: Before beginning installation, ensure that the following steps are completed: - \uf0a7 Download and install the TokenOne mobile application from either the Apple App Store or the Google Play Store. - \uf0a7 Speak with your TokenOne representative to receive the TokenOne10.zip file. - \uf0a7 Download the TokenOne10.zip file to the /home/magento/Downloads directory.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_00350", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-11 in Assessing Security and Privacy Controls in Information Systems and Organizations? Control SI-11: ERROR HANDLING ASSESSMENT OBJECTIVE: Determine if:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00351", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Wireless Infusion Pumps in Healthcare Delivery Organizations provide? (Section 378) rfaces Attached.......................... 0 No. Interface Groups Attached.................... 0 No. Wlans........................................ 0 No. Local Policies Attached...................... 0 mDNS AP Summary NIST SP 1800-8C: Securing Wireless Infusion Pumps 239 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P 1 8 0 0 - 8 . . Number of mDNS APs............................. 0 PMIPv6 Global Configuration PMIPv6 Profile Summary No Profile Created. PMIPv6 MAG Statistics PMIPv6 domain has to be configured first EoGRE Global Configuration Heartbeat Interval...............60 Max Heartbeat Skip Count.........3 Interface........................management EoGRE Gateway Configuration EoGRE Domain Configuration Domain Name Gateways Active Gateway -------------- ----------------- -------------------- NIST SP 1800-8C: Securing Wireless Infusion Pumps 240 EoGRE Profile Configuration WLAN Express Setup Information. WLAN Express Setup - ............................ False T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o Flex Avc Profile summary. Profile-Name Number of Rules status ============ =============== ======== i . . o r g / 1 0 6 0 2 8 / N I S T . S P 1 8 0 0 - 8 . . Flex Avc Profile Detailed Configuration. Certificate Summary. Web Administration Certificate................... 3rd Party Web Authentication Certificate................... Locally Generated Certificate compatibility mode:.................. off Lifetime Check Ignore for MIC ................... Disable NIST SP 1800-8C: Securing Wireless Infusion Pumps 241 Lifetime Check Ignore for SSC ................... Disable Smart-licensing status Summary. T h i s p u b l i c a t i o n Call-home Summary.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Wireless Infusion Pumps in Healthcare Delivery Organizations."}]}
{"id": "nist_00352", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Annual Report 2018_ NIST_ITL Cybersecurity Program provide? (Section 17) and academia in the United States and around the globe to confront a variety of urgent technical and implementation challenges to cryptographic security. These included: - Post-Quantum Cryptography . In recent years, there has been a substantial amount of research on quantum computers-machines that exploit quantum mechanical phenomena to solve mathematical problems that are difficult or intractable for conventional computers. If large-scale quantum computers are ever built, they will be able to break many of the public key cryptosystems currently in use, seriously compromising the confidentiality and integrity of digital data. During FY18, NIST continued to prioritize work on post-quantum cryptography (also called quantumresistant cryptography) with the ambitious goal of developing cryptographic systems that are secure against both quantum and classical computers and can interoperate with existing communications protocols and networks. After an earlier call to the public to submit post-quantum algorithms 11 that could resist a quantum computer's onslaught, from FY18 to FY19 NIST worked with the larger cryptography community to narrow the field from 69 submitted algorithms to 26. The remaining algorithms are those which NIST mathematicians and computer scientists consider to be the strongest candidates. Next, NIST is asking the cryptography community to focus on analyzing how these algorithms will perform in the real world (e.g., how they will fit into the internet protocols currently in use). This second round of analysis focuses more heavily on evaluating the submissions' performance across a wide variety of systems, not just in big computers and smartphones. 11/emspace NIST Asks Public to Help Future-Proof Electronic Information, https:/ /www.nist.gov/news-events/news/2016/12/ nist-asks-public-help-future-proof-electronic-information - Lightweight Cryptography .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Annual Report 2018_ NIST_ITL Cybersecurity Program."}]}
{"id": "nist_00353", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DS-3 in Cryptographic Key Management Workshop Summary -- June 8-9, 2009? (Part 62) Control DS-3: We have to support this interoperability among future systems. - Standards must not only be technically correct and precise, but they must be understandable to, and easily used by, the general public. We need to be able to communicate what we're doing and why we're doing it to the people who make policies, procurement regulations, and user instructions. - We need to create standards that are testable. Ideally, they should be tested automatically so we can minimize the effort of conducting manual product assurance. - Executive and legislative oversight and resource allocation must be in the proper context. Expectations must be consistent with technical reality. We must work with industry, not just from the standpoint of innovation and technical expertise, but making sure that the standards that result will be implemented, not just can be implemented. - We need to work with academia because we get many creative inputs from its members, who are not constrained by short-term corporate goals. We also rely on obtaining innovative ideas from our colleagues overseas. - IETF protocol efforts include: IKEv1 and IKEv2, TLS, Secure Shell, EAP, CMS, and Kerberos. - The Extensible Authentication Protocol (EAP) provides authentication for people and devices. - The IETF enrollment efforts include: KeyProv and a dynamic symmetric key provisioning protocol. - There is a clear need for standards in certificate enrollment, but previous attempts have failed. - There are few standards for: key generation, ordering, distribution, accounting, destruction, commercial implementation, and formats for keys. - NSA is helping to define standards packages and key formats in the IETF and PKIX for the Suite B cryptographic algorithms (i.e., those used to protect classified data up to SECRET).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, secret. Contains guidance on protecting sensitive government information. Source: Cryptographic Key Management Workshop Summary -- June 8-9, 2009."}]}
{"id": "nist_00354", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification say about 4.4 Personal Authentication Certificate Object? According to A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification, 4.4 Personal Authentication Certificate Object: Another common credential object found on a smart token is the Personal Authentication Certificate. This certificate contains the Person Identifier of the Cardholder/Credential Holder (in the Subject or the Subject Alternate Name field) and a Public Cryptographic key counterpart of a token-held secret (i.e., a private cryptographic key). Naturally, the digital signature of the CA that issued this certificate provides the binding between the two values. Therefore the Personal Authentication Certificate establishes the Person Identifier Token secret binding . Just as in the case of verifying the Card Issuer - Token Secret binding, the primary authentication mechanism for verifying the above binding consists of validating the Digital Authentication Certificate. Again as in the case of Card Issuer- Token Secret binding, the follow-on activity for verifying the Token Secret - Physical Token binding (which thus verifies the secret associated with Person Identifier) involves testing the presence of the private key counterpart (described in Sec. 4.6) of the public key of the certificate, which in this instance is the Personal Authentication Certificate.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token, sso. Contains security framework guidance for authentication systems. Source: A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification."}]}
{"id": "nist_00355", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain D.3 Win/win and the production possibility frontier candidates according to NIST Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives According to Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives, D.3 Win/win and the production possibility frontier candidates: Traceability technologies can be said to move the PPF such that the Win/Win situation of having more of both can be realized. For some, this is counter-intuitive because protecting data has been a traditional method of securing it. As suggested in cases, efforts to share data to protect the objectives of an ecosystem can encounter a myriad of existing assessments, controls, and procedures, all enforced at the data owner's level. The responsibility for data and associated information can be burdensome as it can reflect IP (such as a bill of materials) or national security concerns as in export-controlled technology data. While we see our respondents' recognition of the value in cooperating to share data across supply lines, there is still the hard work of determining what information is crucial to the success of traceability efforts. Several avenues of research surface as a result: - What is the minimum set of data elements and associated message or process context to support a successful traceability project? Can strategies from previous efforts at design criteria, such as an hour-glass model (reference ACM on Hour-Glass Model) [36], or existing business exchange standards be leveraged to tackle this challenge. In one case an existing standards review did result in usable message types. - What cryptographical or other means allow data to both be shared and obscured at the same time? Blockchain and other traceability technology could be improved in ways unimagined today. - What other trade-offs between concerns exist that are today analyzed as zero-sum, but have technologies in the pipeline that would shift the PPF?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives."}]}
{"id": "nist_00356", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.16.1 Siemens RUGGEDCOM RX1501 (O1) Installation Guide according to NIST Situational Awareness for Electric Utilities According to Situational Awareness for Electric Utilities, 2.16.1 Siemens RUGGEDCOM RX1501 (O1) Installation Guide: The instructions for installation of the RUGGEDCOM RX1501 are very similar to those in Section 2.15, with the following additional information: - Ensure that the shared key used in this installation is the same as the one used in the previous installation. - The remote IPs and local IPs will be different for this installation as they are relative to the device. - NAT Traversal Negotiation Method will be on the left menu option (as opposed to the right listed earlier) and must be the same value (e.g., rfc-3947).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Situational Awareness for Electric Utilities."}]}
{"id": "nist_00357", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RC-32 in Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series? (Part 10) Control RC-32: phant diffuser A (now deprecated) component in BitLocker Drive Encryption to increase resistance against ciphertext modification. ## encryption The process of transforming plaintext into ciphertext. ## exclusive-or The bitwise addition, modulo 2, of two bit strings of equal length. ## GiB (gibibyte) 2 30 bytes. [78, Sec. 4.3] ## integrity Guarding against improper information modification or destruction; includes ensuring information nonrepudiation and authenticity. [82] ## KiB (kibibyte) 2 10 bytes. [78, Sec. 4.3] ## MAC algorithm An algorithm that computes an authentication tag from a message and a key. The term 'MAC' is sometimes also used to refer to the authentication tag itself. ## MiB (mebibyte) 2 20 bytes. [78, Sec. 4.3] ## mode of operation (mode) An algorithm for the cryptographic transformation of data that is based on a block cipher. ## nonce A value that is only used once. ## password A string of characters (letters, numbers, and other symbols) that is used to authenticate an identity, to verify access authorization, or to derive cryptographic keys. ## PiB (pebibyte) 2 50 bytes. [78, Sec. 4.3] ## plaintext Intelligible data that has meaning and can be understood without the application of decryption. ## segment In the CFB mode, a sequence of bits whose length is a parameter that does not exceed the block size. ## semantic security What can be efficiently computed about some plaintexts from their ciphertexts can be computed, just as easily, in the absence of those ciphertexts. [14] ## TiB (tebibyte) 2 40 bytes. [78, Sec. 4.3]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series."}]}
{"id": "nist_00358", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain &lt;Signature&gt;: according to NIST Representation of PIV Chain-of-Trust for Import and Export According to Representation of PIV Chain-of-Trust for Import and Export, &lt;Signature&gt;:: This element is optional and if used occurs only once. The element contains a JPEG image of the cardholder's signature. The &lt;Signature&gt; element is the value for Zone 3F on the front of the PIV Card. The data is provided in an xs:base64Binary format.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Representation of PIV Chain-of-Trust for Import and Export."}]}
{"id": "nist_00359", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control GV-2 in Integrating Cybersecurity and Enterprise Risk Management (ERM)? (Part 8) Control GV-2: r management has taken action to alter its severity. Actual residual risk should be equal to or less than the target residual risk.' Cybersecurity risk identification is comprised of four inputs: 1. Identification of the organization's mission-supporting assets and their valuation 2. Determination of potential threats that might jeopardize the confidentiality, integrity, and availability of those assets and potential information and technology opportunities that might benefit the organization 3. Consideration of the vulnerabilities of those assets 4. Evaluation of the potential consequences of risk scenarios Risk practitioners often perform risk identification as both a top-down and bottom-up exercise. For example, after the organization has considered critical or mission-essential functions, it may consider various types of issues that could jeopardize those functions as an input to risk scenario development. Subsequently, as a detailed threat and vulnerability assessment occurs, assessors consider how those threats might affect various assets, conducting a bottom-up assessment. This bi-directional approach helps support holistic and comprehensive risk identification. Risk identification and analysis will be discussed in greater detail in a subsequent NIST publication. ## 3.2.1 Inventory and Valuation of Assets Since cybersecurity risk reflects, in part, the effect of uncertainty on digital components that support enterprise objectives, practitioners identify the assets that are necessary to achieve those objectives. SP 800-37 Revision 2 points out that risk could impact 'organizational operations (including mission, functions, image, or reputation), organizational assets, or individuals.' Similarly, the Cybersecurity Framework describes assets as 'the data, personnel, devices, systems, and facilities that enable the organization to achieve business purposes' [15]. The value of an asset extends beyond its replacement cost.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Integrating Cybersecurity and Enterprise Risk Management (ERM)."}]}
{"id": "nist_00360", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Digital Identity Guidelines_ Federation and Assertions provide? (Section 66) d a notice to the subscriber, as discussed in Sec. 5.4 of [SP800-63A]. For additional considerations on providing a notice to a subscriber about account management events, see Sec. 4.6 of [SP800-63B]. A single RP subscriber account MAY be associated with more than one federated identifier. This practice is sometimes known as account linking . If the RP allows a subscriber to link multiple subscriber accounts in this way, the RP SHALL require an authenticated session with the subscriber account for all linking functions. This authenticated session SHOULD require authentication using one existing federated identifier before linking the new federated identifier to the RP subscriber account. When a federated identifier is removed from an RP subscriber account, the RP SHALL disallow access to the RP subscriber account from the removed federated identifier. The RP MAY associate different access rights with the same account, depending on which federated account is used to access the RP. The means by which an RP determines authorization and access is out of scope for these guidelines. If the RP has access to existing information about a set of subscribers, and this information is not associated with a federated identifier, the RP performs a process known as account resolution to determine which set of subscriber information to associate with a new RP subscriber account. An RP that performs account resolution SHALL ensure that the attributes requested from the IdP are sufficient to uniquely resolve the subscriber within the RP's system before linking the federated identifier with the RP subscriber account and granting access. The intended use of each attribute by the RP is detailed in the trust agreement, including whether the attribute is used for account resolution in this manner.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, sso. Contains security framework guidance for authentication systems. Source: Digital Identity Guidelines_ Federation and Assertions."}]}
{"id": "nist_00361", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does An Introduction to Privacy Engineering and Risk Management in Federal Systems say about 2.3.2 The Utility of Risk Management? (Part 4) According to An Introduction to Privacy Engineering and Risk Management in Federal Systems, 2.3.2 The Utility of Risk Management: a Protection Regulation,' Regulation (EU) 2016/679 of the European Parliament and of the Council (2016) available at 50 Stuart S. Shapiro, et al., 'Privacy Engineering Framework,' The MITRE Corporation (AUG 2014), available at http://www.mitre.org/publications/technical-papers/privacy-engineering-framework; Centre for Information Policy 2016), available at Leadership, 'Protecting Privacy in a World of Big Data: The Role of Risk Management,' Hunton &amp; Williams LLP (FEB the\\_role\\_of\\_risk\\_management\\_16\\_february\\_2016.pdf; Centre for Information Policy Leadership, 'Risk, High Risk, Risk Assessments and Data Protection Impact Assessments under the GDPR,' Hunton &amp; Wiliams LLP (DEC 2016), available at 16.pdf; and 'LINDDUN: A Privacy Threat Assessment Framework,' available at In addition, the 'NIST Roadmap for Improving Critical Infrastructure Cybersecurity' (FEB 2014) highlights the need for a risk management model, available at 51 'Situating Anonymization Within a Privacy Risk Model,' supra note 36. 52 Notably, the World Economic Forum has highlighted how security risk models are inappropriate for understanding the full nature of privacy risk. See 'Rethinking Personal Data,' supra note 31, at p. 18.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: An Introduction to Privacy Engineering and Risk Management in Federal Systems."}]}
{"id": "nist_00362", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-2 in Status Report on the Final Round of the NIST Lightweight Cryptography Standardization Process? (Part 63) Control HA-2: -bit 32-bit 32-bit 32-bit | 16 MHz 16 MHz 48 MHz 64 MHz 80 MHz 80 MHz 80 MHz 84 MHz | 32 KB 48 KB 256 KB 1MB 128 KB 512 KB 4MB 512 KB | 2 KB 6 KB 32 KB 256 KB 16 KB 32 KB 80 KB 96 KB | | Renner et al. [254] | ATmega328P STM32F103C8T6 STM32F746ZG ESP32WROOM Kendryte K210 | AVR ARMCortex-M3 ARMCortex-M7 Tensilica Xtensa LX6 RISC-V (Dual Core) | 8-bit 32-bit 32-bit 32-bit 64-bit | 16 MHz 72 MHz 216 MHz 240 MHz 400 MHz | 32 KB 64 KB 1MB 4MB 16MB | 2 KB 20 KB 320 KB 520 KB 8MB | | Weatherley [255] | ATmega2560 AT91SAM3X8E ESP32 | AVR ARMCortex-M3 Tensilica Xtensa LX6 | 8-bit 32-bit 32-bit | 16 MHz 84 MHz 240 MHz | 256 KB 512 KB 4MB | 8 KB 96 KB 520 KB | \u2217 PIC32MX340F512H microcontroller used with PlatformIO's PIC32MX320F128H board profile ## 4.1.1. Microcontroller Benchmarking by NIST The NIST team evaluated the performance of the finalists on microcontrollers and compared them against the NIST standards AES-GCM and SHA-256. The implementations were collected from the submission packages, GitHub repositories of the finalists, and the repositories of other benchmarking initiatives. In total, 275 AEAD, 153 hash and 103 com- bined implementations were used on two 8-bit MCUs and six 32-bit MCUs [253] (See Table 9). This benchmarking effort focused on two metrics: code size and execution time. Results were analyzed under each metric independently, as well as jointly. Code size is measured in the amount of flash used, in bytes, upon successful compilation of each implementation under test. Execution time is measured in either microseconds or cycles depending on the platforms. Table 9.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Final Round of the NIST Lightweight Cryptography Standardization Process."}]}
{"id": "nist_00363", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Usability and Security Considerations for Public Safety Mobile Authentication provide? (Section 13) | 3.2 EMS................................................................................................................ | 7 | | | 3.2.1 Current Authentication Practice............................................................8 | | | | 3.3 Law Enforcement............................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Usability and Security Considerations for Public Safety Mobile Authentication."}]}
{"id": "nist_00364", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does The Use of Passwords for Controlled Access to Computer Resources say about \u00b7 Mathematical Sciences (Section B)? According to The Use of Passwords for Controlled Access to Computer Resources, \u00b7 Mathematical Sciences (Section B): Studies and compilations designed mainly for the mathematician and theoretical physicist. Topics in mathematical statistics, theory of experiment design, numerical analysis, theoretical physics and chemistry, logical design and programming of computers and computer systems. Short numerical tables. Issued quarterly. Annual subscription: Domestic, $9.00; Foreign, $11.25. DIMENSIONS/NBS (formerly Technical News Bulletin) -This monthly magazine is published to inform scientists, engineers, businessmen, industry, teachers, students, and consumers of the latest advances in science and technology, with primary emphasis on the work at NBS. The magazine highlights and reviews such issues as energy research, fire protection, building technology, metric conversion, pollution abatement, health and safety, and consumer product performance. In addition, it reports the results of Bureau programs in measurement standards and techniques, properties of matter and materials, engineering standards and services, instrumentation, and automatic data processing. Annual subscription: Domestic, .$12.50; Foreign, $15.65.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Use of Passwords for Controlled Access to Computer Resources."}]}
{"id": "nist_00365", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about ASSESSMENT OBJECTIVE? According to Assessing Security Requirements for Controlled Unclassified Information, ASSESSMENT OBJECTIVE: Determine if: A.03.05.11: feedback of authentication information during the authentication process is obscured.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00366", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The Network Security Center_ a System Level Approach to Computer Network Security provide? (Section 73) uthentication consists of comparing a pre-stored pair &lt;subject identifier, authenticator&gt;, with a similar pair offered by the subject. The NSC data structure used is a set called AUTHENTICATION. AUTHENTICATION contains 2-tuples of the form &lt;subject identifier, authenticator&gt;. There will be at least one such tuple in AUTHENTICATION for each valid subject known to the NSC. The authentication module in the NSC acts as a predicate. The input is a tuple &lt;subject identifier, password&gt; offered by the subject. The output is either TRUE or FALSE, depending on whether the password is a proper authenticator for that subject identifier. The authentication module will perform range checking on the form of the input parameters. To authenticate the tuple &lt;subject identifier, password&gt;: IF subject identifier is valid AND password is valid AND &lt;subject identifier, password&gt; is a member of AUTHENTICATION THEN TRUE ELSE FALSE; - 3.1.2 Authorization. The conceptual model of the access authorization structure is a three-dimensional matrix. The axes are Subject Identifier, Object Identifier, Access Right. The entries in the matrix are Boolean flags that indicate whether the corresponding triple (&lt;subject identifier, object identifier, access right&gt;) defines an authorized access. This can be represented in a set model of NSC data structures as a set AUTHORIZATION. AUTHORIZATION contains 4-tuples of the form &lt;subject identifier, object identifier, access right, Boolean flag&gt;. The set will contain one such tuple for each possible combination of subject identifier, object identifier, and access right. The Boolean flag will be TRUE if the specified triple defines a permitted access and FALSE if it defines a prohibited access. The object identifier element has some additional structure to it. Object identifier is itself a 2-tuple of the form &lt;host name, resource name&gt;.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: The Network Security Center_ a System Level Approach to Computer Network Security."}]}
{"id": "nist_00367", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.20.5.4 Hardening Network Devices according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case, 4.20.5.4 Hardening Network Devices: 1. Disable unsecure services such as Telnet, SNMP (v1 and v2). If SNMP is required, change the default community string or use SNMP v3. 2. Following vendor recommended hardening guidelines", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case."}]}
{"id": "nist_00368", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-6 in Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy? (Part 48) Control AM-6: tion, and those objectives are assigned a relative priority among them. For example, human and environmental safety objectives may be the two most important objectives relevant to a Profile's context. In this example, when performing Task P-6, a system that relates to a human safety objective may be prioritized higher than a system that has the same impact levels but does not relate to the human safety objective. References: [FIPS 199]; [FIPS 200]; [SP 800-30]; [SP 800-39] (Organization and System Levels); [SP 80059]; [SP 800-60 v1]; [SP 800-60 v2]; [SP 800-160 v1] (System Requirements Definition Process); [IR 8179] (Criticality Analysis Process B); [CNSSI 1253]; [NIST CSF] (Core [Identify Function]; Profiles). ## CONTINUOUS MONITORING STRATEGY-ORGANIZATION TASK P-7 Develop and implement an organization-wide strategy for continuously monitoring control effectiveness. Potential Inputs: Risk management strategy; organization- and system-level risk assessment results; organizational security and privacy policies. Expected Outputs: An implemented organizational continuous monitoring strategy. Primary Responsibility: Senior Accountable Official for Risk Management or Risk Executive (Function). 62 Organizations operating National Security Systems follow the categorization guidance in [CNSSI 1253] which does not apply the high-water mark concept. 63 Organizations can also elect to use an alternative, organization-defined categorization approach to add additional granularity to the impact levels defined in [FIPS 199]. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Supporting Roles: Chief Information Officer; Senior Agency Information Security Officer; Senior Agency Official for Privacy; Mission or Business Owner; System Owner; Authorizing Official or Authorizing Official Designated Representative.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: csf, risk management framework, fips. General security reference material without sensitive content. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_00369", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) say about 2.1 Profile Topics and Requirements, Augmentations, and Features? (Part 2) According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS), 2.1 Profile Topics and Requirements, Augmentations, and Features: vice-using organizations could selectively require that their FCKMSs support some of the recommended augmentations or suggested features, but such requirements are beyond the scope of this document. In order to easily recognize Profile requirements, augmentations and features from the surrounding text, each type is presented in separate tables. For each table: - \uf0b7 Column one provides the PR, PA or PF number; - \uf0b7 Column two identifies any related security controls in [SP 800-53]; when column two is blank, no related security control has been identified; and - \uf0b7 Column three provides the text of the requirement, augmentation or feature. The first Framework requirement and the first Profile requirement, recommended augmentation and suggested feature are concerned with the overall conformance to the Framework and Profile. FR:1.1 A conformant CKMS design shall meet all 'shall' requirements of the Framework [SP 800-130] . | PR:2.1 | A Federal CKMS shall satisfy all Framework requirements ( FRs ) and Profile requirements ( PR s). | |----------|-----------------------------------------------------------------------------------------------------| | PA:2.1 | A Federal CKMS should support Profile augmentations ( PA s). | |----------|----------------------------------------------------------------| | PF:2.1 | A Federal CKMS could support Profile features ( PF s). |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_00370", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Comments on this publication may be submitted to: according to NIST Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies According to Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies, Comments on this publication may be submitted to:: National Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930 Email: SP800-175@nist.gov All comments are subject to release under the Freedom of Information Act (FOIA).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies."}]}
{"id": "nist_00371", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-1 in Domain Name System-Based Electronic Mail Security? (Part 34) Control AC-1: r each option. The orange arrows between the mail clients and the Postfix MTA reflect the fact that clients submitted email directly to the SMTP server for relay, while using Dovecot only to get mail. (The depiction in Figure 4.2 reflects that IMAP is not used to submit mail, only retrieve it, so the MUA sent mail directly to the Postfix server, but received the reply through the Dovecot server.) The project team demonstrated 30 different events using various combinations of MUA, MTA, and DNS Server components divided among five test sequences. In each sequence, signed and encrypted messages were sent from a sender to a recipient. Both Exchange and Postfix encrypted mail by default. Most of the exchanges employed either self-signed certificates or local CAs (see Appendix C). The BIND configuration was set up to obtain and validate certificates from the NIST Advanced Network Technologies Division's (ANTD's) DNS source (acting as a root CA). (See section 6 below for test sequence sets.) In one test sequence, fraudulently signed S/MIME email was sent from a malicious sender to recipients using Outlook and Thunderbird MUAs configured to use Exchange and Postfix as MTAs. The Outlook/Exchange configuration used Active Directory as its DNS server. The configurations employing Postfix/Dovecot MTAs were demonstrated with each of the other three contributed DNS services. In one event, the Thunderbird MUA employed an Apple Key Chain Utility tool that allows a host to obtain X.509 certificates via of DANE RRs. All events were conducted using well-known CA and Enterprise CAissued certificates for the impersonated sender. The fraudulent site attempted to spoof a valid sending domain belonging to a Secure64 site that was configured with DNS Authority/Cache/Signer DNS services, a Postfix/Dovecot MTA, and Thunderbird equipped with the Apple Key Chain utility. An Outlook/Exchange/ Active Directory set-up acted as the fraudulent site.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_00372", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to NIST Test Personal Identity Verification (PIV) Cards Version 2? http: //smime2.nist.gov/PIVTest2/RSA2048IssuingCA.crl", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_00373", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to Computer Security Division 2011 Annual Report? http: //csrc.nist.gov/groups/SNS/security-risk-analysis- enterprise-networks/", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2011 Annual Report."}]}
{"id": "nist_00374", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Privacy Controls for Information Systems and Organizations provide? (Section 63) rational, environmental, and technical scenarios. The controls can be used to demonstrate compliance with a variety of governmental, organizational, or institutional security and privacy requirements. Organizations have the responsibility to select the appropriate security and privacy controls, to implement the controls correctly, and to demonstrate the effectiveness of the controls in satisfying security and privacy requirements.19 Security and privacy controls can also be used in developing specialized baselines or overlays for unique or specialized missions or business applications, information systems, threat concerns, operational environments, technologies, or communities of interest.20 15 [SP 800-30] provides guidance on the risk assessment process. 16 [IR 8062] introduces privacy risk concepts. 17 [SP 800-39] provides guidance on risk management processes and strategies. 18 [SP 800-37] provides a comprehensive risk management process. 19 [SP 800-53A] provides guidance on assessing the effectiveness of controls. 20 [SP 800-53B] provides guidance for tailoring security and privacy control baselines and for developing overlays to support the specific protection needs and requirements of stakeholders and their organizations. CHAPTER ONE PAGE 4 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ Organizational risk assessments are used, in part, to inform the security and privacy control selection process.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00375", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Special Factors Affecting Confidentiality Impact Determination according to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices? Special Factors Affecting Confidentiality Impact Determination: In cases where the consequences of unauthorized disclosure of labor relations information could seriously affect the agencies mission capability, protection of agency assets, and safety of individuals, the confidentiality impact level might be moderate", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_00376", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Property Management Systems provide? (Section 86) | | CM-8, PM-5 | Technical Sup- port Specialist | | NIST Cybersecurity Framework | NIST Cybersecurity Framework | NIST Cybersecurity Framework | Standards and Best Practices | Standards and Best Practices | Standards and Best Practices | |--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|-----------------------------------------------------| | Func- tion | Category | Subcategory | PCI DSS v3.2.1 | NIST SP 800- 53r5 Security and Privacy Con- trols [9] | NICE Framework 2017 Work Roles [11] | | PROTECT (PR) | objectives and the organiza- tion's risk strat- egy.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Securing Property Management Systems."}]}
{"id": "nist_00377", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Privacy Controls for Information Systems and Organizations provide? (Section 902) The set of hardware, software, and/or firmware that implements Approved security functions (including cryptographic algorithms and key generation) and is contained within the cryptographic boundary. Prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation. The interdependent network of information technology infrastructures that includes the Internet, telecommunications networks, computer systems, and embedded processors and controllers in critical industries. A system operation that processes personally identifiable information. An analytical process that attempts to find correlations or patterns in large data sets for the purpose of data or knowledge discovery. General term for any process of removing the association between a set of identifying data and the data subject. A planned, systematic set of multidisciplinary activities that seek to identify, manage, and reduce risk of exploitable vulnerabilities at every stage of the system, network, or subcomponent life cycle, including system, network, or product design and development; manufacturing; packaging; assembly; system integration; distribution; operations; maintenance; and retirement. An information security strategy that integrates people, technology, and operations capabilities to establish variable barriers across multiple layers and missions of the organization. An attribute associated with an assessment method that addresses the rigor and level of detail associated with the application of the method. A general term that includes developers or manufacturers of systems, system components, or system services; systems integrators; vendors; and product resellers.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00378", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Workforce Framework for Cybersecurity (NICE Framework) say about 3.1 Using Existing Task, Knowledge, and Skill (TKS) Statements? According to Workforce Framework for Cybersecurity (NICE Framework), 3.1 Using Existing Task, Knowledge, and Skill (TKS) Statements: Users of the NICE Framework reference one or more Task, Knowledge, and Skill statements (TKS statements), as described in Section 2, to describe both work and learners. Task statements are used to describe the work. Task statements have associated K&amp;S statements. Although a Task statement may have a recommended set of associated K&amp;S statements, users may include other existing K&amp;S statements to tailor Tasks for their unique context. K&amp;S statements are used to describe learners. K&amp;S statements can be used in many ways to manage the cybersecurity workforce. They can be used in part, all together, or not at all, depending on the implementing organization's unique context. The notional examples of use below demonstrate areas where TKS statements might be implemented: - Employee Skill tracking program to determine promotion qualifications - Required Knowledge for completion of a course - Weekly Task list for completion at an organization TKS statements and examples can be found in the NICE Framework Resource Center and will be updated, as needed, to keep pace with changes resulting from evolving business missions, risks, or emerging technologies. [1]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Workforce Framework for Cybersecurity (NICE Framework)."}]}
{"id": "nist_00379", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TF-8 in Common Platform Enumeration_ Naming Specification Version 2.3? (Part 45) Control TF-8: sions are roundtrip safe , meaning that taking one of the two bound forms, converting it to the other form, then converting that back to the original binding form, will result in the original binding. ## 7.1 Converting a URI to a Formatted String Given a URI u which conforms to the CPE v2.2 specification, the procedure for converting it to a formatted string fs has two steps: ``` function convert_uri_to_fs(u) w := unbind_uri(u). fs := bind_to_fs(w). return fs. end. ``` ## 7.2 Converting a Formatted String to a URI Given a formatted string fs which conforms to the description in Section 6.2.2, the procedure for converting it to a URI has two steps: ``` function convert_fs_to_uri(fs) w := unbind_fs(fs). uri := bind_to_uri(w). return uri. end. ``` ## Appendix A-References The following documents are indispensable references for understanding the application of this specification. ## A.1 Normative References [CPE22] Buttner, A. and N. Ziring, Common Platform Enumeration (CPE)-Specification, Version 2.2, March 11, 2009. See [RFC2119] Bradner, S. (1997). Key words for use in RFCs to Indicate Requirement Levels . March 1997. See [RFC2234] Crocker, D. and P. Overell. (1997). Augmented BNF for Syntax Specifications: ABNF . Internet RFC 2234, November 1997. See [RFC3629] Yergeau, F. (2003). UTF-8, a transformation format of ISO 10646. Internet RFC 3629, November 2003. See [RFC3986] Berners-Lee, T., Fielding, R. and L. Masinger. (2005). Uniform Resource Identifier (URI): Generic Syntax. Internet RFC 3986, January 2005. See [RFC5646] Phillips, A. and M. Davis. (2009). Tags for Identifying Languages. RFC 5646, September 2009. See ## A.2 Informative References [ISO19770-2] ISO/IEC 19770-2. (2009).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Platform Enumeration_ Naming Specification Version 2.3."}]}
{"id": "nist_00380", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for the Creation of Interoperable Software Identification (SWID) Tags provide? (Section 4) rpreted as RFC 2119 key words. Some of the requirements and conventions used in this report reference Extensible Markup Language (XML) content. These references come in two forms, inline and indented. An example of an inline reference is: A patch tag is differentiated by the fact that the value of the @patch attribute within the &lt; SoftwareIdentity &gt; element is ' true '. In this example, the notation &lt; SoftwareIdentity &gt; can be replaced by the more verbose equivalent 'the XML element whose qualified name is SoftwareIdentity '. The general convention used when describing XML attributes within this report is to reference the attribute as well as its associated element, employing the general form ' @attributeName for the &lt; prefix:localName &gt;'. Attribute values are indicated in quotations, such as the example ' true ' above. In cases where any valid value may be provided for an XML attribute, this report specifies ' &lt;any&gt; ' as the attribute value. This report defines a number of new XML attributes that are extensions to the SWID specification. These extension attributes are defined in a new XML namespace, These new attributes will be assigned the prefix 'n8060' mapped to this namespace. In guidelines and examples, extension attributes will be provided in the form ' @n8060:attributeName '. The schema for these extensions can be downloaded at Indented references are intended to represent the form of actual XML content. Indented references represent literal content by the use of a fixed-length font, and parametric (freely replaceable) content by the use of an italic font. Square brackets '[]' are used to designate optional content. Both inline and indented forms use qualified names to refer to specific XML elements. A qualified name associates a named element with a namespace.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Creation of Interoperable Software Identification (SWID) Tags."}]}
{"id": "nist_00381", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders provide? (Section 141) ct the list. Your screen should look like Figure 2-10. Figure 2-10 PSX Cockpit User Interface <!-- image --> - On the Cockpit screen, you can trigger an emergency (triangle icon in the upper right). Set your status (drop-down menu under your name); or reselect roles and groups, see configuration, and sign off (hamburger menu to the left of your name, and then tap username ). - If you pull down your notifications, you should see icons and text indicating Reporting interval: 120 seconds, Signed In: &lt;date&gt; &lt;time&gt;, Connected, and Registered. - Open the Mapping application. You should see the screen shown in Figure 2-11. - Select the Layers icon in the lower-right corner. Group names should appear under Layers. - Select a group. Your screen should look like Figure 2-12. Figure 2-11 PSX Mapping User Interface <!-- image --> Figure 2-12 PSX Mapping Group Member Information <!-- image --> - The locations of the devices that are members of that group should appear as dots on the map. - Select a device. A pop-up will show the user of the device and icons for phoning and messaging that user. - Selecting the Messenger icon for the selected user will take you to the Messenger application, where you can send a message to the user. - Open the Messenger application. Your screen should look like Figure 2-13. - Your screen should show People and Groups. Select one of them. - A list of people or groups to which you can send a message should appear. Select one of them. Your screen should look like Figure 2-14. Figure 2-13 PSX Messenger User Interface <!-- image --> Figure 2-14 PSX Messenger Messages <!-- image --> - You are now viewing the messaging window. You can type text for a message and attach a picture, video, voice recording, or map. - Tap the Send icon. The message should appear on your screen. - Tap the Pivot icon in the upper-right corner of the message window.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, single sign-on. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_00382", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-14 in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? (Part 47) Control SI-14: conditions listed above. \u2022 Compliance controls (e.g., those checking to ensure that all patches are up to date) Cyber resiliency focuses primarily on evolving and adapting rather than on compliance. Thus, unless a control is explicitly focused on ensuring that some specific (already established) cyber resiliency capability is implemented correctly and operating as intended, compliance controls are generally not considered part of cyber resiliency. \u2022 Vulnerability assessment controls While adversaries take advantage of vulnerabilities, identifying such vulnerabilities is not the focus of cyber resiliency. Some control families are more likely to support cyber resiliency than others. The Contingency Planning (CP), Incident Response (IR), System and Communications Protection (SC), and System and Information Integrity (SI) families have a high percentage of controls that are cyber resiliency oriented. However, controls that support cyber resiliency are not confined to these families nor are all controls in these families automatically controls supporting cyber resiliency. After the above criteria are applied, there may still be some ambiguity for some controls as to whether or not they are cyber resiliency in their focus. This is due in part to the overlap between aspects of cybersecurity and cyber resiliency. Delineation between the two is not easy to discern. To illustrate the distinction, it is useful to reference first principles. Cyber resiliency is essentially about ensuring continued mission operations despite the fact that an adversary has established a foothold in the organization\u2019s systems and cyber infrastructure. \u2022 Controls that are largely focused on keeping the adversary out of systems and infrastructure are generally not resiliency controls. For example, identification and authentication controls such as IA-4 (Identifier Management) are generally not focused on combating an adversary after they have achieved a foothold in an organizational system.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, adversary, incident response. Contains technical security guidance that could inform defensive posture. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_00383", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 886) Segmented Integer Counter (SIC) mode. Common Vulnerabilities and Exposures Common Weakness Enumeration Distribution Automation Defense Advanced Research Projects Agency Distributed Control System. A computer-based control system where several sections within the plants have their own processors, linked together to provide both information dissemination and manufacturing coordination. Distributed Denial of Service A form of anonymization that does not attempt to control the data once it has had PII identifiers removed, so it is at risk of re-identification. Distributed Energy Resources Data Encryption Standard Domain Expert Working Group Digital Fault Recorder Distribution Grid Management Department of Homeland Security Diffie-Hellman A cryptographic key exchange protocol first published by Whitfield Diffie and Martin Hellman in 1976. It allows two parties that have no prior knowledge of each other to jointly establish a shared secret key over an insecure communications channel. Distinguished names String representations that uniquely identify users, systems, and organizations. DMS DN DNP DNS DoD DOE DoS DR Distribution Management System Distinguished Name Distributed Network Protocol Domain Name Service Department of Defense Department of Energy Denial of Service Demand Response DRBG Deterministic Random Bit Generators 156 DRM DRMS DSL DSPF DSS EAP EAX mode EAX\u2019 ECC ECDH ECDSA ECPA EEO Digital Rights Management. A generic term for access control technologies used by standards providers, publishers, copyright holders, manufacturers, etc. to impose limitations on the usage of digital content and devices. The term is used to describe any technology that inhibits the use of digital content in a manner not desired or intended by the content provider.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_00384", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-256 in Fiscal Year 2021 Cybersecurity and Privacy Annual Report? (Part 14) Control HA-256: publishes access control characteristics and general access control guidelines for various cloud service models. NIST also performs research and development regarding access control rules and methods. ## Personal Identity Verification (PIV) As required by Homeland Security Presidential Directive 12, NIST developed and maintains FIPS 201 for the personal identity verification (PIV) of federal employees and contractors. In FY 2019, NIST initiated a revision of FIPS 201 to incorporate the changing business requirements of federal departments and agencies and to adapt to an evolving technology environment. Revision activities began in FY 2019 with a business requirement meeting to engage with federal stakeholders about the revision goals. In FY 2020, the PIV team updated the draft standard based on the revision goals and published a public draft of FIPS 201. Comments received were adjudicated in FY 2021 and subsequently reflected in the final FIPS 201. The standard expands the set of PIV authenticators beyond the current practices (including the current smart card form factor) while addressing the interagency use of new types of PIV authenticators (i.e., derived PIV credentials) via federation. The revision also aims to facilitate the issuance of PIV cards by enabling remote identity proofing. These changes closely align with Office of Management and Budget (OMB) Policy Memorandum M-19-17, Enabling Mission Delivery through Improved Identity, Credential, and Access . For FY 2022, the PIV team will actively work on Special Publications associated with FIPS 201 to further specify the standard's technical details while continuing outreach to federal stakeholders. ## Digital Identity Guidelines The four-volume set of Digital Identity Guidelines (NIST SP 800-63-3) was published in June 2017.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Fiscal Year 2021 Cybersecurity and Privacy Annual Report."}]}
{"id": "nist_00385", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Information Security Handbook_ A Guide for Managers say about 6.3.1 Emergency Disconnection? According to Information Security Handbook_ A Guide for Managers, 6.3.1 Emergency Disconnection: If one or both organizations detect an attack, intrusion attempt, or other contingency that exploits or jeopardizes the connected systems or their data, it might be necessary to abruptly terminate the interconnection without providing written notice to the other party. This extraordinary measure should be taken only in extreme circumstances and only after consultation with appropriate technical staff and senior management. The decision to make the emergency disconnection should be made by the system owner (or a designated staff member) and implemented by technical staff. The system owner or designee should immediately notify the other party verbally and receive confirmation of the notification. Both parties should work together to isolate and investigate the incident, in accordance with incident response procedures. If necessary, law enforcement authorities should be notified, and evidence should be preserved. The initiating party should provide a written notification to the other party in a timely manner (e.g., within five days). The notification should describe the nature of the incident, explain why and how the interconnection was terminated, and identify actions taken to isolate and investigate the incident. The notification should also specify when and under what conditions the interconnection may be restored, if appropriate.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, incident response. Contains technical security guidance that could inform defensive posture. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_00386", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guidelines for Securing Radio Frequency Identification (RFID) Systems? (Part 89) Control ES-1: dditional step takes time. When considering security controls, organizations need to balance the business impact of each security control's effect on transaction speed with the protection it provides. ## 3.3.3 Network Connectivity and Data Storage Whether or not an RFID system's readers are networked with database applications has major implications for the architecture of the RFID system and its security. When an application needs to link data with tags, the data needs to be stored somewhere. If the readers are networked with databases, then the data can be stored in the databases. Otherwise, the data must be stored on the tags. When data is stored centrally on database servers, the tag only needs to contain an identifier, which links the tag to its associated information. In this architecture, the vast majority of the data processing occurs on the supporting systems to which the reader is connected. On the other hand, when data is stored on tags, the tags must have some form of memory and support both write and read transactions. Regardless of where data is stored, the data's integrity must be protected. If the data is sensitive, its confidentiality must also be protected. The methods for achieving this include authentication, access control, encryption, and physical security. However, database servers and tags implement these methods in different ways. Nearly all commercial database servers support a wide variety of configurable security controls, but most tags do not. In general, RFID systems that use networked readers to access database servers are preferable to those that store data on tags, both in terms of cost and security. However, a system may require local storage of data on tags for several reasons, including: - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Extending the network to a remote RFID reader is not feasible or is more expensive than using tags that support the required functionality.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, sso. Contains security framework guidance for authentication systems. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_00387", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Note according to Usability and Security Considerations for Public Safety Mobile Authentication? Note: Embedded cryptographic tokens are commonly used in MFA situations alongside a PIN, password, or biometric, and in this situation, would inherit the usability considerations and technical considerations from using the PIN or password, or any other second factor that is implemented. The use of a PIN, password, or biometric to unlock a mobile device could be considered the first factor in an MFA scenario.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, mfa, token. Contains security framework guidance for authentication systems. Source: Usability and Security Considerations for Public Safety Mobile Authentication."}]}
{"id": "nist_00388", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings say about 6th Annual PKI R&amp;D Workshop - Proceedings? According to 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings, 6th Annual PKI R&amp;D Workshop - Proceedings: Directory browsers, to automatically trust Argonne's administrative web servers. The key to a seamless portal experience is single sign-on (SSO). Although not required, s ingle sign-on allows users to jump from resource to resource and application to application within the portal without having to log in to each component individually. If a user had to provid e credentials to each application he accessed, even if those credentials were identical, the experience would be severely diminished.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, single sign-on, sso. Contains security framework guidance for authentication systems. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_00389", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-17(06) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control AC-17(06): informa\ue000on about remote access mechanisms is protected from unauthorized use and disclosure. POTENTIAL ASSESSMENT METHODS AND OBJECTS:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00390", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CP-9(8) in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Control CP-9(8): SYSTEM BACKUP | CRYPTOGRAPHIC PROTECTION", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_00391", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Considerations for Remote Electronic UOCAVA Voting say about Notes:? According to Security Considerations for Remote Electronic UOCAVA Voting, Notes:: Individuals with privileged access to the voting system should be uniquely identified by the voting system. That is, system administrators, election officials, and other with access to voting system should not share accounts or login credentials. This allows for greater accountability of administrative actions performed on the voting system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Remote Electronic UOCAVA Voting."}]}
{"id": "nist_00392", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PM-8200 in Cell Phone Forensic Tools_ an Overview and Analysis? (Part 101) Control PM-8200: MIS provides examiners with a user interface containing a set of tabs providing examiners with the ability to create report notes, import archived reports, search acquired data and PIN administration. SIMIS allows the following data types to be acquired from SIM cards: Abbreviated Dial Numbers (ADN), Fixed Dial Numbers (FDN), International Mobile Subscriber Identity (IMSI), Last Numbers Dialed (LND), Mobile Subscriber Integrated Services Digital Network Number (MSISDN), Short Message Server Parameters (SMSP), SMS Short Messages, Deleted Messages, Public Land Mobile Networks (PLMNS), Forbidden Public Land Mobile Networks (FPLMNS), Location Information, Broadcast Control Channel (BCCH), Cell Broadcast Message Identifier for Data Download (CBMID), Voicemail Number, Integrated Circuit Card Identification (ICCID), Phase ID, Service Provider, Administration Data, Service Dialing Number (SDN) and Capability Configuration Parameters. The tool can also perform a full dump of the card contents for analysis. ## Acquisition Stage The acquisition stage begins by prompting the examiner to select the interface to be used as illustrated below. Figure 66: Interface Selection <!-- image --> If the SIM is password protected, the screen below appears. If the examiner does not have the PIN for the SIM, only unprotected data can be acquired from the SIM. Figure 67: SIM PIN Wizard <!-- image --> If the correct PIN is known, it can be entered into the input window shown in Figure 68 below. 19 Additional information about SIMIS can be found at: Figure 68: SIM PIN Input <!-- image --> After the correct PIN number has been entered, the examiner can Change, Unlock, Activate, or Deactivate the PIN from the user interface, as illustrated in Figure 69 below.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_00393", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2012 Annual Report? (Part 199) Control HA-3: knows how to engage successfully with the White House; civilian, defense and intelligence agencies; and industry on cybersecurity, keeping these constituencies focused on the issues. She is heavily invested in initiatives to secure cloud and mobile computing, the Smart Grid, and supply chain. Kevin Stine 2012 WEDI Award of Merit <!-- image --> Kevin Stine was GLYPH(cmap:df00)esignateGLYPH(cmap:df00) by the Workgroup for Electronic Data Interchange (WEDI) BoarGLYPH(cmap:df00) of Directors as a recipient of the 2012 WEDI AwarGLYPH(cmap:df00) of Merit. WEDI, established in 1991 in response to a challenge from then Secretary of Health anGLYPH(cmap:df00) Human Services, Louis Sullivan, MD, brings together a consortium of leaGLYPH(cmap:df00)ers within the healthcare industry to identify practical strategies for reducing administrative costs in healthcare through the implementation of electronic data interchange. This awarGLYPH(cmap:df00) recognizes inGLYPH(cmap:df00)iviGLYPH(cmap:df00)uals who have contributeGLYPH(cmap:df00) in a meaningful way to the success of WEDI and/or WEDI Strategic National Implementation Process (SNIP) programs and activities through their volunteer commitment and talents. Dr. Ron Ross Distinguished Practitioner Award 28th Annual Computer Security Applications Conference Dr. Ross received the Distinguished Practitioner AwarGLYPH(cmap:df00) at the 28 th Annual Computer Security Applications Conference. <!-- image --> This awarGLYPH(cmap:df00) is presenteGLYPH(cmap:df00) to an inGLYPH(cmap:df00)iviGLYPH(cmap:df00)ual who has GLYPH(cmap:df00)emonstrateGLYPH(cmap:df00) a continuing, vital, anGLYPH(cmap:df00) influential contribution to the fielGLYPH(cmap:df00) of information security . SC Magazine's Influential IT Security MinGLYPH(cmap:df00)s in 2012 Dr. Ross was also recognizeGLYPH(cmap:df00) by SC Magazine as one of the Influential IT Security MinGLYPH(cmap:df00)s in 2012.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_00394", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms say about 2.3.4 International Organization for Standardization (ISO) 37? (Part 1) According to Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms, 2.3.4 International Organization for Standardization (ISO) 37: 2.3.4 International Organization for Standardization (ISO) 37 ISO is a non-governmental, worldwide federation of national standards bodies. Its mission is to develop international standards that help make industry more efficient and effective. ISO standards cover almost all aspects of technology and business, from food safety to computers, and from agriculture to healthcare. Experts from all over the world develop the standards that are required by the nation or liaison organization they represent using a consensus process. ISO/IEC JTC 1 is a joint technical committee of the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC). ISO/IEC JTC 1 SC 27 is the subcommittee for IT security. Working group 2 (WG2) is the group developing standards for cryptography and security mechanisms. It usually has more than 20 active projects to develop either a revision of an existing standard or a new standard. Each standard consists of multiple parts, and each part includes multiple algorithms and/or mechanisms. The cryptographic algorithms and schemes in FIPS and SPs are usually included in ISO/IEC standards, along with many other algorithms submitted by other countries. The following is a list of ISO/IEC standards that include cryptographic algorithms and schemes specified in NIST standards. 1. ISO/IEC 9797-1, Information technology -Security techniques -Message Authentication Codes (MACs) - Part 1: Mechanisms using a block cipher . 2. ISO/IEC 9797-2, Information technology -Security techniques -Message Authentication Codes (MACs) - Part 2: Mechanisms using a dedicated hashfunction . 3. ISO/IEC 10116, Information technology -Security techniques -Modes of operation for an n-bit block cipher . 4. ISO/IEC 10118-3, Information technology -Security techniques -Hash-functions - Part 3: Dedicated hash-functions . 5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms."}]}
{"id": "nist_00395", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 256) of the systems that are the targets of the penetration testing. CA-2(1) provides additional information on independent assessments that can be applied to penetration testing. Related Controls: CA-2. (2) PENETRATION TESTING | RED TEAM EXERCISES Employ the following red-team exercises to simulate attempts by adversaries to compromise organizational systems in accordance with applicable rules of engagement: [Assignment: organization-defined red team exercises]. Discussion: Red team exercises extend the objectives of penetration testing by examining the security and privacy posture of organizations and the capability to implement effective cyber defenses. Red team exercises simulate attempts by adversaries to compromise mission and business functions and provide a comprehensive assessment of the security and CHAPTER THREE PAGE 93 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ privacy posture of systems and organizations. Such attempts may include technology-based attacks and social engineering-based attacks. Technology-based attacks include interactions with hardware, software, or firmware components and/or mission and business processes. Social engineering-based attacks include interactions via email, telephone, shoulder surfing, or personal conversations. Red team exercises are most effective when conducted by penetration testing agents and teams with knowledge of and experience with current adversarial tactics, techniques, procedures, and tools.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: penetration test, red team. Contains technical security guidance that could inform defensive posture. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00396", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives provide? (Section 49) manufacturing supply chains requires: 1. An information sharing approach that transcends the typical business-to-business (B2B) bilateral exchanges of information that is exchanged in supply chains. The existing bi-lateral exchanges are well-supported by existing IT, legal, contractual, and liability methods and means. In contrast, blockchain and related technologies have potential to share information in a wider yet trusted scope, but are not yet widely supported in IT, legal, contractual, and liability methods and means. 2. Agreement and cooperation to share traceability information across relevant stakeholders, sufficient to correlate traceability with each relevant stakeholders' internal enterprise systems. The tradeoff is between minimal information shared with potentially redundant information in enterprise systems, or more information shared but with increased requirement for fine grained and rules-based access control. The analysis of tradeoff alternatives must include time, effort, and resilience to future changes. 3. Linking physical objects to cyber records. Validation of authenticity of a physical part, requires that the part is inspected (independent of its packaging and labeling) to detect a unique characteristic or signature which can be linked to electronic records. This can occur at 2 layers. The first is an actual physical marking (see Section 4.2, Cyber-Physical Anchors) and the second is a trusted data layer or hardware root of trust. For example, the operator of a nuclear power plant can verify the authenticity of an ICT/OT microelectronic component by comparing the traceability signature on the component with the matching traceability data record in the trusted data layer, before using that component during routine maintenance. 4. Cooperation across the supply chain to write and read traceability records, and adoption of technology, methods, and means to mark and inspect goods and services for linkage with electronic records. 5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives."}]}
{"id": "nist_00397", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-06(05) in Assessing Security Requirements for Controlled Unclassified Information? (Part 8) Control AC-06(05): n accordance with applicable access control policies. A.03.01.02[02]: approved authorizations for logical access to system resources are enforced in accordance with applicable access control policies. ## ASSESSMENT METHODS AND OBJECTS ## Examine [SELECT FROM: access control policy and procedures; procedures for access enforcement; system design documentation; system configuration settings; list of approved authorizations (i.e., user privileges); system audit records; system security plan; other relevant documents or records] ## Interview [SELECT FROM: personnel with access enforcement responsibilities; system administrators; personnel with information security responsibilities; system developers] ## Test [SELECT FROM: mechanisms for implementing the access control policy] ## REFERENCES Source Assessment Procedure: AC-03 ## 03.01.03 Information Flow Enforcement ## ASSESSMENT OBJECTIVE Determine if: A.03.01.03[01]: approved authorizations are enforced for controlling the flow of CUI within the system. A.03.01.03[02]: approved authorizations are enforced for controlling the flow of CUI between connected systems.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00398", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Protocol Control and Liability : according to NIST Blockchain Networks_ Token Design and Management Overview According to Blockchain Networks_ Token Design and Management Overview, Protocol Control and Liability :: The distributed and cryptographic nature of blockchain technology provides resilience and verifiability but does not eliminate the notions of control and liability. Permissions, roles, and backstops may be placed at the base layer and the smart contract layer, potentially giving some degree of protocol control to privileged entities that could be held accountable for their actions. This entails making policy decisions that can have wide-ranging implications, especially if nodes span across jurisdictions. Isolated legal actions from a small subset of those jurisdictions may, by design, not be able to affect a blockchain's global state. Note that data may also be isolated and kept within certain region(s) via the use of separate blockchain networks, states for subsets of participants, or off-chain schemes. International regulation, survey, and standardization efforts have been developed to help address adverse outcomes and rethink oversight approaches in such distributed and digital environments [122][123].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain Networks_ Token Design and Management Overview."}]}
{"id": "nist_00399", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control VE-20131763 in CVSS Implementation Guidance? (Part 49) Control VE-20131763: [Web page] [accessed 3/26/14]. | | [2] | D. Waltemire, S. Quinn, K. Scarfone, and A. Halbardier, The Technical Specification for the Security Content Automation Protocol (SCAP): SCAP Version 1.2 , NIST SP 800-126 Revision 2, National Institute of Standards and Technology, U.S. Department of Commerce, Gaithersburg, MD, September 2011. [Web page] [accessed 3/26/14]. | | [3] | D. Kaminsky, It's The End Of The Cache As We Know It , Presented at Black Ops 2008, Japan, 2008. [Web page] Kaminsky/BlackHat-Japan-08-Kaminsky-DNS08-BlackOps.pdf [accessed 3/26/14]. | | [4] | Gallagher, Sean, 'New JavaScript hacking tool can intercept PayPal, other secure sessions,' ArsTechnica , September 21, 2011. [Web page] http://arstechnica.com/business/2011/09/new-javascript-hacking-tool-can-intercept- paypal-other-secure-sessions/ [accessed 3/26/14]. | | [5] | IBM, Security Bulletin: Multiple security vulnerabilities in the IBM InfoSphere Information Server Suite . [Web page] 01.ibm.com/support/docview.wss?uid=swg21623501 [accessed 3/26/14]. | | [6] | IBM Internet Security Systems, Apple QuickTime Clear() code execution . [Web page] [accessed 3/26/14]. | | [7] | IBM Internet Security Systems, OpenStack Dashboard session hijacking . [Web page] [accessed 3/26/14]. | | [8] | Industrial Control Systems Cyber Emergency Response Team, Post Oak Bluetooth Traffic Systems Insufficient Entropy Vulnerability , Advisory (ICSA-12-335-01), November 30, 2012. [Web page] [accessed 3/26/14].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: CVSS Implementation Guidance."}]}
{"id": "nist_00400", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE) say about 3.4.2.8 Threat Event 8-Compromise of Device Integrity via Observed, Inferred, or Brute-Forced Device Unlock Code? According to Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE), 3.4.2.8 Threat Event 8-Compromise of Device Integrity via Observed, Inferred, or Brute-Forced Device Unlock Code: Summary: A malicious actor may be able to obtain a user's device unlock code by direct observation, side-channel attacks, or brute-force attacks. Both the first and second can be attempted with at least proximity to the device; only the third technique requires physical access. However, side-channel attacks that infer the unlock code by detecting taps and swipes to the screen can be attempted by applications with access to any peripherals that detect sound or motion (microphone, gyroscope, or accelerometer). Once the device unlock code has been obtained, a malicious actor with physical access to the device will gain immediate access to any data or functionality not already protected by additional access control mechanisms. Additionally, if the user employs the device unlock code as a credential to any other systems, the attacker may further gain unauthorized access to those systems.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_00401", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach provide? (Section 529) 1 DEVELOPING CYBER-RESILIENT SYSTEMS _________________________________________________________________________________________________ ATT&CK Technique Mitigation or Candidate Mitigation Cyber Resiliency Implementation Approaches Potential Effects Cyber Resiliency Controls Scheduled Transfer (T1029) Network Intrusion Prevention (M1031) Monitoring and Damage Assessment Detect SI-4(4) Covert Signaling (CM1112) Tainting Detect, Reveal SI-20 Present Decoy Data (CM1113) Disinformation, Misdirection Tainting Deceive, Degrade Detect, Scrutinize SC-30(4), SC-26 SI-20 Fragment Information (CM1114) Fragmentation Delay, Exert SI-23 Modulate Information Flows (CM1153) Design Diversity, Replication Negate, Exert Process Monitoring (CM2015) Monitoring and Orchestration Analyze Outgoing Traffic Patterns (CM2042) Damage Assessment, Behavior Validation Monitoring and Damage Assessment, Behavior Validation Exert Detect Detect AC-4(27), AC- 4(30) AC-4(29) AU-6, IR-4(13) SI-4(18), IR- 4(13) Transfer Data to Cloud Account (T1537) Covert Signaling (CM1112) Tainting Detect, Reveal SI-20 Present Decoy Data (CM1113) Disinformation, Misdirection Tainting Deceive, Degrade Detect, Scrutinize SC-30(4), SC-26 SI-20 Fragment Information (CM1114) Cloud Account Monitoring (CM2016) Fragmentation Delay, Exert SI-23 Monitoring and Damage Assessment, Behavior Validation Detect AC-2(12) TABLE F-16: POTENTIAL EFFECTS OF CYBER RESILIENCY ON IMPACT ATT&CK Technique Mitigation or Candidate Mitigation Account Access Removal (T1531) Use Alternate Communications (CM1140) Dynamic Account Management (CM1117) Cyber Resiliency Implementation Approaches Potential Effects Cyber Resiliency Controls Path Diversity Shorten, Reduce AC-7(4), SC-47 Dynamic Privilege, Dynamic Reconfiguration Dynamic Reconfiguration Shorten, Reduce AC-2(6)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_00402", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Device Security_ Cloud and Hybrid Builds provide? (Section 1) Includes Executive Summary (A); Approach, Architecture, and Security Characteristics (B); and How-To Guides (C) Joshua Franklin Kevin Bowler Christopher Brown Spike E. Dog Sallie Edwards Neil McNab Matthew Steele This publication is available free of charge from: The original draft of this publication is available free of charge from: <!-- image --> Includes Executive Summary (A); Approach, Architecture, and Security Characteristics (B); and How-To Guides (C) Joshua Franklin National Institute of Standards and Technology Information Technology Laboratory Kevin Bowler Christopher Brown Spike E. Dog Sallie Edwards Neil McNab Matthew Steele The MITRE Corporation McLean, VA February 2019 <!-- image --> U.S. Department of Commerce Wilbur Ross, Secretary National Institute of Standards and Technology Walter G. Copan, Undersecretary of Commerce for Standards and Technology and Director Executive Summary National Institute of Standards and Technology Information Technology Laboratory Kevin Bowler Christopher Brown Spike E. Dog Sallie Edwards Neil McNab Matthew Steele The MITRE Corporation McLean, VA This publication is available free of charge from: The original draft of this publication is available free of charge from: <!-- image --> - \u25fc Adopting mobile devices without the necessary policies and management infrastructure in place increases the opportunities for attackers to breach sensitive enterprise data. - \u25fc The National Cybersecurity Center of Excellence (NCCoE) at the National Institute of Standards and Technology (NIST) developed example mobile device and enterprise mobility management solutions that organizations can use to reduce the likelihood of a data breach.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Cloud and Hybrid Builds."}]}
{"id": "nist_00403", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AN-2013 in Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet? (Part 92) Control AN-2013: It also specifies the order in which the remaining records shall appear in the file. | | REC-IDC- Matches Records | ForEach (Record in Recs) ( Present(Subfield in 1.003 ST AND ( EQ({InfoI(1.003.REC) in Subfield}, RecType(Record)), EQ({InfoI(1.003.IDC) in Subfield}, {Record.002}) ) ) Note: The record types must appear in the same order that they are listed in Fld(1.003) ) | | | | | | | | | | | 2 | NIEM- Transaction REC-CNT- IDC- Matches Records | Complex ( ForEach (Record in Recs) ( Present(XElm(1.003.biom:ContentRecordSummar y) ST AND ( EQ({XElm(1.003.biomRecordCategoryCode) in XElm(1.003.biom:ContentRecordSummary)}, RecType(Record)), EQ({XElm(1.003.ImageReferenceIdentification) in XElm(1.003.biom:ContentRecordSummary)}, {Record.002}) ) ) Note: The record types must appear in the same order that they are listed in Fld(1.003) ) | | M- Transaction | | | | B | | TX.14 - Tra nsaction: SRN Sequential | 7.3.2.1 | The value of the SRN shall be a sequentially assigned positive integer starting from one and incremented by one, not to exceed 255.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet."}]}
{"id": "nist_00404", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.1.3 Globally Unique Identifiers according to NIST The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2 According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2, 3.1.3 Globally Unique Identifiers: The elements listed in Table 13 have special conventions around the format of their identifiers ( @id attribute). Authors MUST follow these conventions because they preserve the global uniqueness of the resulting identifiers. In Table 13, namespace contains a valid reverse-DNS style string (limited to letters, numbers, periods, and the hyphen character) that is associated with the content author. Examples include \"com.acme.finance\" and \"gov.tla\". These namespace strings MAY have any number of parts, and SCAP content consumers processing them SHALL treat them as case-insensitive (e.g., com.ABC is considered identical to com.abc). The name in the format conventions MUST be an NCName-compliant string [XMLS]. Table 13 - Element Identifier Format Convention | Element | Identifier Format Convention | |-----------------------------|-----------------------------------| | <ds:data-stream-collection> | scap_ namespace _collection_ name | | <ds:data-stream> | scap_ namespace _datastream_ name | | <ds:component-ref> | scap_ namespace _cref_ name | | <ds:component> | scap_ namespace _comp_ name | | <ds:extended-component> | scap_ namespace _ecomp_ name |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2."}]}
{"id": "nist_00405", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Considerations for Voice Over IP Systems say about 8.1 IPsec? (Part 2) According to Security Considerations for Voice Over IP Systems, 8.1 IPsec: d. The IPsec header and the new IP Header for this encapsulating packet are the only information left in the clear. Usually each 'tunnel' is between two network elements such as a router or a gateway. In some cases, such as for mobile users, the tunnel could be between a router/gateway on one end and a client on the other end. The IP addresses of these nodes are used as the unencrypted IP address at each hop. Hence, at no point is a plain IP header sent out containing both the source and destination IP. Thus if an attacker were to intercept such packets, they would be unable to discern the packet contents or the origin and destination. Note that some traffic analysis is possible even in tunnel mode, because gateway addresses are readable. If a gateway is used exclusively by a particular organization, an attacker can determine the identity of one or both communicating organizations from the gateway addresses. IPsec allows nodes in the network to negotiate not only a security policy, which defines the security protocol and transport mode as described previously, but also a security association defining the encryption algorithm and algorithm key to be used Figure 11. IPsec Tunnel and Transport Modes <!-- image --> \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_00406", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 7.3. LEV Recall of KEV Lists according to NIST Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability According to Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability, 7.3. LEV Recall of KEV Lists: The statistical measurement of 'recall', applied to LEV, measures the coverage of KEV lists by LEV lists of differing threshold values. As discussed previously in Sec. 3.3, an LEV list can be created by choosing a threshold probability and then including all vulnerabilities with an LEV probability greater than the threshold. Fig. 4 provides the recall measurements for an LEV list relative to its coverage of a KEV list. Fig. 4. Recall measurements for LEV and CISA KEV <!-- image --> Even at a threshold of 0.1, the LEV list does not provide more than 60 % coverage. This indicates that LEV lists should not be used as a replacement for KEV lists. It does not necessarily show a deficiency in LEV. It demonstrates that there are a large number of low probability vulnerabilities, and given the large number, many of them will actually be exploited despite their low probability.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability."}]}
{"id": "nist_00407", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-06(05) in Assessing Security Requirements for Controlled Unclassified Information? (Part 23) Control AC-06(05): ned. A.03.02.01.ODP[03]: the frequency at which to update security literacy training content is defined. A.03.02.01.ODP[04]: events that require security literacy training content updates are defined. A.03.02.01.a.01[01]: security literacy training is provided to system users as part of initial training for new users. security literacy training is provided to system users A.03.02.01.a.01[02]: &lt;A.03.02.01.ODP[01]: frequency&gt; after initial training. A.03.02.01.a.02: security literacy training is provided to system users when required by system changes or following &lt;A.03.02.01.ODP[02]: events&gt; . A.03.02.01.a.03[01]: security literacy training is provided to system users on recognizing indicators of insider threat. A.03.02.01.a.03[02]: security literacy training is provided to system users on reporting indicators of insider threat. A.03.02.01.a.03[03]: security literacy training is provided to system users on recognizing indicators of social engineering. A.03.02.01.a.03[04]: security literacy training is provided to system users on reporting indicators of social engineering. A.03.02.01.a.03[05]: security literacy training is provided to system users on recognizing indicators of social mining. A.03.02.01.a.03[06]: security literacy training is provided to system users on reporting indicators of social mining. ## A.03.02.01.b[01]: security literacy training content is updated &lt;A.03.02.01.ODP[03]: frequency&gt; . A.03.02.01.b[02]: security literacy training content is updated following &lt;A.03.02.01.ODP[04]: events&gt; .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00408", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Secure Web Services say about A.7.3 Logic Bombs, Trapdoors, and Backdoors? According to Guide to Secure Web Services, A.7.3 Logic Bombs, Trapdoors, and Backdoors: A logic bomb is malicious code that is left dormant until the Web service reaches a certain state, at which point the malicious code is executed. A trapdoor or backdoor is malicious code that has the specific objective of enabling the attacker (or the Web service that acts as a proxy service on the attacker's behalf) to bypass the targeted Web service's (or its host's) authentication mechanisms to gain access to sensitive data or resources, without being detected. Logic bombs, trapdoors, and backdoors are usually delivered as Trojan horses via another attack vector such as a virus or worm payload or planted by an attacker who has gained the necessary level of write-access to the Web service host. Note that many logic bombs, backdoors, and trapdoors are planted by the developer of the Web service that contains them. Unlike external attackers, developers can exploit their deep knowledge of how a particular Web service's host will be configured in deployment, and how its system-, middleware-, and application-level components will interact.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, attack vector. Contains technical security guidance that could inform defensive posture. Source: Guide to Secure Web Services."}]}
{"id": "nist_00409", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Bluetooth Security say about 3.2.1 Low Energy Security Modes and Levels? (Part 1) According to Guide to Bluetooth Security, 3.2.1 Low Energy Security Modes and Levels: 3.2.1 Low Energy Security Modes and Levels Low energy security modes are similar to BR/EDR service-level security modes (i.e., Security Modes 2 and 4) in that each service can have its own security requirements. However, Bluetooth low energy also specifies that each service request can have its own security requirements as well. A device enforces the service-related security requirements by following the appropriate security mode and level. - Low energy Security Mode 1 has multiple levels associated with encryption. Level 1 specifies no security, meaning no authentication and no encryption will be initiated. Level 2 requires unauthenticated pairing with encryption. Level 3 requires authenticated pairing with encryption. 4.2 added Level 4 which requires authenticated low energy Secure Connections pairing with encryption. - Low energy Security Mode 2 has multiple levels associated with data signing. Data signing provides strong data integrity but not confidentiality. Level 1 requires unauthenticated pairing with data signing. Level 2 requires authenticated pairing with data signing. If a particular service request and the associated service have different security modes and/or levels, the stronger security requirements prevail. For example, if either requires Security Mode 1 Level 3, then the requirements for Security Mode 1 Level 3 are enforced. Because Security Mode 1 Level 4 requires low energy Secure Connections authenticated pairing and Encryption, using AES-CMAC and P-256 elliptic curve for pairing and AES-CCM for encryption, NIST considers this the most secure of these modes/levels and strongly recommends its use for all low energy connections in 4.2. For 4.0 and 4.1 low energy connections, NIST strongly recommends using Security Mode 1 Level 3 as it requires authenticated pairing and encryption although not as strong (not using P-256 elliptical curve) encryption as Level 4. Security Mode 1 Level 1 is the least secure and should never be used.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Guide to Bluetooth Security."}]}
{"id": "nist_00410", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) provide? (Section 219) g an architectural review, the assessment team for a Federal CKMS shall have access to all CKMS design information, third-party-validation information, and the available results of FCKMS/CKMS testing. | |-----------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | PA:11.4 | | When penetration testing is to be performed on a Federal CKMS, the penetration-testing scenarios should be determined by the architectural review team. | | PA:11.5 | SA-4 | A Federal CKMS using-organization should analyze the results of the architectural review before procuring an FCKMS. | Functional and security testing of an FCKMS should be performed prior to initial deployment, during subsequent periodic security reviews, and during incremental security assessments. Functional and security tests could be performed by the CKMS developer, CKMS implementer, the FCKMS service provider, or a trusted third-party. These tests could also be performed, or the results reviewed, by an FCKMS-using organization. Functional testing should include usability tests for users whose knowledge and experience with an FCKMS range from novice to expert. An FCKMS is considered to be 'user-friendly' when it can be easily used by novice users, or when the services are automatically provided and controlled by an FCKMS that is 'transparent' to the user. FR:11.7 The CKMS design shall specify all required functional and security testing of the CKMS. FR:11.8 The CKMS design shall report the results of all functional and security tests performed to date. | PR:11.6 | SA-11 | AFederal CKMS shall undergo functional and security testing, including ease-of-use tests before initial operation.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_00411", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Abstract according to NIST Building Secure Microservices-based Applications Using Service-Mesh Architecture According to Building Secure Microservices-based Applications Using Service-Mesh Architecture, Abstract: The 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. The 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, key management. Contains security framework guidance for authentication systems. Source: Building Secure Microservices-based Applications Using Service-Mesh Architecture."}]}
{"id": "nist_00412", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Labels for Open Systems_ an Invitational Workshop say about End System Label Requirements? According to Security Labels for Open Systems_ an Invitational Workshop, End System Label Requirements: - Between two ESs, confidentiality and integrity requirements must be exchanged with data - Multilevel ESs on multilevel networks require security labels in order to perform trusted demultiplexing - ESs usually translate network security labels to a local format Xerox Special Information Systems A V", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Labels for Open Systems_ an Invitational Workshop."}]}
{"id": "nist_00413", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Recommendation for Key Management_ Part 1 \u2013 General? (Part 178) Control HA-3: ld be maintained in a central repository or network of mutually trusted repositories and operated in accordance with a Key-Inventory Policy. See SP 800-57, Part 2 for additional information. If a key is compromised, the owners or sponsors associated with the compromised key need to be notified so that remedial actions can be taken, including revoking the key, performing an analysis of the effects of the compromise, and replacing the key when appropriate. The information in the inventory can be used to identify who is to be notified and how to contact them. If an owner is no longer authorized to use a key (e.g., the owner is a human who left the organization or a device that is removed from the system), other entities need to be notified so that further interaction using that key is terminated. If the key is a symmetric key, the information in the inventory can be used to identify other entities that need to be notified and how to contact them. If the key is an asymmetric key and PKI certificates are used, notification is usually accomplished using CRLs. If the cryptoperiod for a key expires or is about to expire, the key needs to be replaced if interactions between the entities using that key are to continue (i.e., using a replacement key). A key-inventory management system can be used to monitor cryptoperiods and alert the key owners or sponsors that keys are about to expire. The inventory management system can also be used to find keys for algorithms and key lengths that are no longer considered to be secure in order to arrange for algorithm and/or key replacement.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_00414", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information say about B.2. Challenges in Using Federation Technologies for Message Switch Use Cases? (Part 3) According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information, B.2. Challenges in Using Federation Technologies for Message Switch Use Cases: e CAD/RMS system. This can limit the damage an attacker could do by intercepting and using that assertion. They would be unable to forward it on to gain access to other agency systems or applications. Applying federation technologies to the message switch scenario is challenging because it is not a traditional identity federation scenario, but rather delegated authorization. The CAD/RMS system initiates a transaction with the message switch on the user's behalf. The user is not directly involved in this transaction; they are one step removed from it. Authorization protocols like Kerberos and the OAuth 2.0 Authorization Framework are designed for these types of transactions. However, Kerberos is not typically deployed across organizational boundaries, and OAuth 2.0 is not yet widely deployed in the public safety environment. Therefore, this document presents two options for implementing this scenario with the widely used SAML 2.0 standards: - Proxy IdP -A Proxy IdP accepts an assertion from an IdP and uses it to create its own assertion to provide to another RP, effectively acting as an IdP to that other RP. In the above example, the CAD/RMS system could use the identity information received in the assertion from the IdP to craft its own assertion, sign it with its own private key, and pass it on to the message switch, adjusting the audience parameter and other fields to reflect the intended use of this new assertion. Refer to Appendix A.3.1 of [8] for more details on the Proxy IdP concept. - WS-Trust -WS-Trust is another federation standard that the CAD/RMS system can use to request a new assertion from the IdP that is intended to be presented to the message switch.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, multi-factor. Contains security framework guidance for authentication systems. Source: Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information."}]}
{"id": "nist_00415", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.3.8.3 Vulnerability Scan Targets according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case, 3.3.8.3 Vulnerability Scan Targets: All devices connected to the Plant and Supervisory network segments are scanned. The IT Staff will configure a scan for all network segments of Westman. A new scan can be established, or a modification can be made to an existing scan, by submitting a request to the IT Manager. Note: If an individual identifies that a scan is impacting the manufacturing process, they must report the situation immediately to the IT Manager to request stopping the scan and report the situation to the Director of Operations.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case."}]}
{"id": "nist_00416", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Random Bit Generator (RBG) Constructions say about 2.8.1.2. DRBG Generation Request? (Part 1) According to Recommendation for Random Bit Generator (RBG) Constructions, 2.8.1.2. DRBG Generation Request: 2.8.1.2. DRBG Generation Request Pseudorandom bits are generated after DRBG instantiation using the following function: ( status, returned\\_bits ) = DRBG\\_Generate ( state\\_handle, requested\\_number\\_of\\_bits, requested\\_security\\_strength, additional\\_input ) . Fig. 6. DRBG\\_Generate function <!-- image --> The DRBG\\_Generate function (shown in Fig. 6) is used to generate a specified number of bits. If a suitable state\\_handle is provided during instantiation, it is included as input to indicate the DRBG instance to be used. The number of bits to be returned and the security strength that the DRBG needs to support for generating the bitstring are provided with (optional) additional input. As stated in Sec. 2.4.1, the ability to accept additional input is recommended. The DRBG\\_Generate function returns status information - either an indication of success or an error. If the returned status code indicates a success, the generated bits are returned. - If requested\\_number\\_of\\_bits is equal to or greater than the instantiated security strength, the security strength that the returned\\_bits can support (if used as a key) is: ss\\_key = the instantiated security strength, where ss\\_key is the security strength of the key. - If the requested\\_number of bits is less than the instantiated security strength, and the returned\\_bits are to be used as a key, the key is capable of supporting a security strength of: <!-- formula-not-decoded --> - If the output is used to form multiple keys, the security strength that can be supported by each key is: ss\\_of\\_each\\_key = min ( key\\_length , instantiated\\_security\\_strength ) . If the status code indicates an error, the returned\\_bits consists of a Null bitstring. An example of a condition in which an error indication may be returned is a request for a security strength that exceeds the instantiated security strength for the DRBG. Details about the DRBG\\_Generate function are provided in [SP\\_800-90A].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Bit Generator (RBG) Constructions."}]}
{"id": "nist_00417", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Government Smart Card Interoperability Specification, Version 2.1 provide? (Section 226) d. A transaction must be completed by a call to gscBsiUtilEndTransaction(). For single-threaded BSI implementations, it can be assumed that each application will be associated with a separate process. The same process that starts a transaction must also complete the transaction. For multi-threaded BSI implements, it can be assumed that each application will be associated with a separate thread and/or process. The same thread that starts a transaction must also complete the transaction. If this function is called by a thread that has already called gscBsiUtilBeginTransaction() but has not yet called gscBsiUtilEndTransaction() it will return the error BSI\\_NOT\\_TRANSACTED . If the SPS (Service Provider Software) does not support transaction locking, it should return the error code BSI\\_NO\\_SPSSERVICE in response to a call to gscBsiUtilBeginTransaction() . ``` Prototype: ``` ``` public abstract void gscBsiUtilBeginTransaction ( int hCard boolean blType ) throws gov.gsc.classes.BSIException; ``` Parameters: hCard: Card communication handle returned from gscBsiUtilConnect() blType: Boolean specifying the type of transaction call ( blType set to 'true' in blocking mode. blType set to 'false' in non blocking mode). Return Code: BSI\\_OK BSI\\_BAD\\_HANDLE BSI\\_UNKNOWN\\_ERROR BSI\\_SC\\_LOCKED BSI\\_NOT\\_TRANSACTED BSI\\_NO\\_SPSSERVICE Purpose: Completes a previously started transaction, allowing other applications to resume interactions with the card. If this function is called by a thread that has not yet called gscBsiUtilBeginTransaction() it will return the error BSI\\_NOT\\_TRANSACTED . If the SPS (Service Provider Software) does not support transaction locking, it should return the error code BSI\\_NO\\_SPSSERVICE in response to a call to gscBsiUtilEndTransaction() . Prototype: public abstract void gscBsiUtilEndTransaction ( int hCard ) throws gov.gsc.classes.BSIException; Parameters: hCard: Card communication handle returned from gscBsiUtilConnect().", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_00418", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Head Start on Assurance_ Proceedings of an Invitational Workshop on Information Technology (IT) Assurance and Trustworthiness, March 21-23, 1994 say about TABLE OF CONTENTS? (Part 3) According to A Head Start on Assurance_ Proceedings of an Invitational Workshop on Information Technology (IT) Assurance and Trustworthiness, March 21-23, 1994, TABLE OF CONTENTS: WHY | 11 | | 3.4 IS SECURITY OF THE OPERATING SYSTEM TCB DIFFERENT FROM SECURITY OF AN APPLICATION? | 12 | | 3.5 IS IT POSSIBLE TO QUANTIFY ASSURANCE VERSUS VULNERABILITY TRADEOFFS? | 13 | | 3.6 WHO SHOULD MAKE TRADEOFF DECISIONS? | 15 | | 3.7 CONCLUSIONS | 15 | | PEDIGREE | 17 | |-----------------------------------------------------------------------------------------------|------| | 4.1 INTRODUCTION | 17 | | 4.2 ISSUES ASSOCIATED WITH PEDIGREE | 18 | | 4.2.1 WHAT Is A Pedigree?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Head Start on Assurance_ Proceedings of an Invitational Workshop on Information Technology (IT) Assurance and Trustworthiness, March 21-23, 1994."}]}
{"id": "nist_00419", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain C.3.3 Human Resource Management according to NIST Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, C.3.3 Human Resource Management: Human resource management activities involve all activities associated with the recruitment and management of personnel.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_00420", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Zero Trust Architecture say about 3.3 Algoritmos de confianza? (Part 2) According to Zero Trust Architecture, 3.3 Algoritmos de confianza: factores y de la postura de seguridad de los activos, se podr\u00eda restringir o denegar el acceso a estos - Base de datos de los sujetos : corresponde a qui\u00e9n solicita el acceso al recurso ( SP 80063 ). Es decir, es el conjunto de sujetos (humanos y procesos) de la empresa o colaboradores, as\u00ed como los atributos y privilegios que se les asignan. Estos sujetos y atributos forman la base de las pol\u00edticas de acceso a los recursos ( SP 800-162 ) ( NISTIR 7987 ) 7 . Las identidades de los usuarios pueden incluir una mezcla de identidades l\u00f3gicas, por ejemplo, la identificaci\u00f3n (ID, por su nombre en ingl\u00e9s identity document ) de la cuenta y los resultados de las comprobaciones de autenticaci\u00f3n realizadas por los PEP. Los par\u00e1metros de la identidad que se consideran para derivar el nivel de confianza incluyen la hora y la geolocalizaci\u00f3n. Se podr\u00eda considerar una serie de privilegios otorgados a varios sujetos con un mismo rol; sin embargo, los permisos deben asignarse al sujeto de forma individual y no simplemente porque detiene un papel determinado en la organizaci\u00f3n. Esta selecci\u00f3n de privilegios deber\u00eda codificarse y almacenarse en un sistema de gesti\u00f3n de ID y en una base de datos de pol\u00edticas. Tambi\u00e9n podr\u00e1 incluir informaci\u00f3n sobre el comportamiento anterior del sujeto observados en algunas variantes del TA (v\u00e9ase la secci\u00f3n 3.3.1). - Base de datos de los activos (y observaci\u00f3n del estatus): se trata de la base de datos que contiene el estado registrado de cada uno de los activos (f\u00edsicos y virtuales, hasta cierto punto) que son propiedad de la empresa (y posiblemente de los que no lo son, es decir, los BYOD). Este estado se compara con el estatus del activo que realiza la solicitud y puede incluir la versi\u00f3n del SO, el software presente y su integridad, la ubicaci\u00f3n (de la red y la geolocalizaci\u00f3n) y el nivel de parches. En funci\u00f3n de la comparaci\u00f3n entre el estado del activo y esta base de datos, se restringir\u00e1 o denegar\u00e1 el acceso.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Zero Trust Architecture."}]}
{"id": "nist_00421", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Best Practices for Privileged User PIV Authentication provide? (Section 23) tion architecture, the user authenticates to a Verifier that is not the Relying Party, after which the Verifier provides the Relying Party with an assertion that the user's identity has been verified. As described in Section 9 of NIST SP 800-63 [2], which provides detailed requirements for use of assertions, some assertion mechanisms can provide e-authentication level 4 assurance to the Relying Party (e.g., Kerberos), and such mechanisms are preferred and should be employed whenever possible, if the indirect verification architecture is used. 15 The Kerberos Network Authentication Protocol [16] is commonly used to implement indirect verification, and it can be implemented in such a way that it provides e-authentication level 4 assurance to the Relying Party. The assertions created by the Verifier in Kerberos are called Kerberos tickets, and they include symmetric session keys that allow the Relying Party to perform a strong cryptographic authentication of the Claimant. The overall authentication process must ensure that the Claimant uses a PIV credential to authenticate to the Verifier before access is granted by the Relying Party. This requirement is satisfied if the Verifier is configured to only accept PIV authentication. Security Assertion Markup Language (SAML) bearer assertions [17] are also commonly used to implement indirect verification. Unlike Kerberos, with bearer assertions the Claimant authenticates to the Relying Party by simply providing a copy of the assertion that it got from the Verifier. So, unlike Kerberos, an attacker could defeat the authentication mechanism by 14 See Section 6.2.3.1 of FIPS 201-2 [5] for an example of PKI-based authentication using the PIV Authentication certificate.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Best Practices for Privileged User PIV Authentication."}]}
{"id": "nist_00422", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Note according to Platform Firmware Resiliency Guidelines? Note: This guideline that RoTs and CoTs be implemented as part of platform firmware applies only to elements that implement the platform resiliency functions described in this paper. Platform vendors are encouraged to maintain a chain of trust from boot firmware through the Operating System to provide resiliency against various forms of attacks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Platform Firmware Resiliency Guidelines."}]}
{"id": "nist_00423", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2011 Annual Report provide? (Section 93) ine whether any changes need to be made to the final specification for the sets of test cards. Sets of test cards based on the final specification will then be created and made available for purchase. <!-- image --> Contacts: Dr. David Cooper (301) 975-3194 david.cooper@nist.gov Mr. William Polk (301) 975-3348 william.polk@nist.gov Modern computers rely on fundamental system firmware, commonly known as the Basic Input/Output System (BIOS), to facilitate the hardware initialization process and transition control to the operating system. The BIOS is a security-critical component because of its unique and privileged position within modern computers. A malicious BIOS modification could be part of a sophisticated, targeted attack on an organization-either a permanent denial of service (if the BIOS is corrupted) or a persistent malware presence (if the BIOS is implanted with malware). As security in operating systems and applications has improved, a race to 'bare metal' has begun between those wishing to attack systems and those responsible for protecting them. Attacks on the BIOS are an evolving threat area that could become a future battlefront. To combat this threat, in FY2011, NIST began a new project to secure the BIOS. As the computer industry is currently transitioning to BIOS based on the Unified Extensible Firmware Interface (UEFI), a recent industry specification for system firmware, NIST had the opportunity to influence the next generation of systems. For the past year, NIST has been working with key members of the computer industry on mechanisms to improve the security of the BIOS. In April 2011, NIST issued SP 800-147, BIOS Protection Guidelines, which provides guidance on protecting the BIOS in laptop and desktop computers. This document provides platform vendors with recommendations and guidelines for a secure BIOS update process.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2011 Annual Report."}]}
{"id": "nist_00424", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices say about Confidentiality? According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Confidentiality: The confidentiality impact level is the effect of unauthorized disclosure of public comment tracking information on the ability of responsible agencies to solicit, maintain, and respond to public comments regarding proposed regulations. The effects of loss of confidentiality of information associated with the public comment process are unlikely to pose the threat of serious harm to agency assets, personnel or operations. In a few cases, the rationale for public comments can include information that is sensitive in terms of proprietary information sensitive Federal government information, or even national security information. However, such cases are exceptional and the information in question would be expected to be representative of information types covered elsewhere in this guideline. Recommended Confidentiality Impact Level : The provisional confidentiality impact level recommended for public comment tracking information is low .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_00425", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control NT-7 in Dramatically Reducing Software Vulnerabilities_ Report to the White House Office of Science and Technology Policy? (Part 16) Control NT-7: a significant part of the national information infrastructure. Given the clear manageability, cost and performance advantages of using them, it is reasonable to expect their use to continue to expand. Security-enhanced versions of these technologies, if adopted, can therefore have a widespread effect on the exploitation of software vulnerabilities throughout the National Information Infrastructure. Additive Software Analysis. There are many types of software analysis - some are general and some target very specific vulnerabilities. The goal of additive software analysis is to be able to use multiple tools as part of an ecosystem. This will allow for increased growth and use of specialized software analysis tools and ability to gain a synergy between tools and techniques. More Mature Domain-Specific Software Development Frameworks. The goal of this approach is to promote the use (and reuse) of well-tested, well-analyzed code, and thus to reduce the incidence of exploitable vulnerabilities. Moving Target Defenses (MTD) and Automatic Software Diversity. This approach is a collection of techniques to vary the software's detailed structures and properties such that an attacker has much greater difficulty exploiting any vulnerability. The goal of automatic software diversity and MTD is to reduce an attacker's ability to exploit any vulnerabilities in the software, not to reduce the number of weaknesses in software. A critical need for improving security is to have software with fewer and less exploitable vulnerabilities. The measures, techniques and approaches we have described will be able to do this. Higher quality software, however, does not get created in a vacuum. There must be a robust research infrastructure, education and training and customer demand. Higher quality software is a necessary step, but it is insufficient. A robust operation and maintenance agenda that spans a system's lifecycle is still needed.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Dramatically Reducing Software Vulnerabilities_ Report to the White House Office of Science and Technology Policy."}]}
{"id": "nist_00426", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Study of OSI Key Management provide? (Section 170) ncryption and notarization are employed. [ANSI X9.17] defines notarization as: A method of applying additional security to a key utilizing the identities of the originator and the ultimate recipient. Thus, when notarization or just offset encryption is done, the KEK is transformed. Before notarization is explained, a double DES encryption must be described . The following figure is taken from Security For Computer Networks [DAVI89]. Two single DES keys are concatenated to form a double DES key. The double DES key consists of two halves, KKl and KKr respectively. Figure Al:l Double DES encryption/decryption <!-- image --> Encryption is performed by encrypting the plaintext X with KKl, thereafter the result of the encryption is decrypted with KKr. The decryption is followed by a new encryption with KKl, Double DES decryption is the inverse operation, see the figure above. The motive to employ a double DES key is that the KEK becomes cryptographically stronger than a single DES key. More about double DES encryption can be found in [MEYE82a]. Now notarization can be explained. The following figure is also taken from [DAVI89] and explains notarization when using a double DES key as a KEK. As explained above the double DES key consists of two parts, KKl and KKr. The identity of the initiating entity is given by FO and the identity of the responding entity is given by TO. The identities are split into two halves. The identity of the initiating entity, FM, is split into FMl and FM2 respectively. The identity of the responding entity, TO, is split into TOl and T02 respectively. CT is a counter which is associated with the *KK. Figure Al:2 Key notarization <!-- image --> A notarization key, *KN, is produced, a data key is encrypted with *KN. The data key then becomes notarized. By including the identities of the originator and recipient the situation is avoided where a legitimate party can perform a masquerade.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: A Study of OSI Key Management."}]}
{"id": "nist_00427", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does De-Identifying Government Datasets_ Techniques and Governance provide? (Section 129) very, analysts should be able to validate their discoveries against the original data to ensure that the things they discover are in the original data and not artifacts of the data generation process. Both high-fidelity models and synthetic data generated from models may leak personal information that is potentially re-identifiable. The amount of leakage can be controlled using formal privacy models (e.g., differential privacy) that typically involve the introduction of noise. Section 4.4.7 describes the construction of fully synthetic data with differential privacy. There are several advantages for agencies that choose to release de-identified data as a fully synthetic dataset: - It can be very difficult to map records to actual people if the synthetic dataset is sufficiently large. - The privacy guarantees can potentially be mathematically established and proven ( Sec. 4.4.7). - The privacy guarantees can remain in force even if there are future data releases. Fully synthetic data also have these disadvantages and limitations: - It is not possible to create pseudonyms that map back to actual people because the records are fully fabricated. - The data release may be less useful for accountability or transparency. For example, investigators equipped with a synthetic data release would be unable to find the actual 'people' who make up the release because they would not actually exist. - For traditional models (such as Gaussian mixture models), it may be difficult to find meaningful correlations or abnormalities in synthetic data that are not represented in the model. For example, if a model contains only main effects and first-order interactions, then all second-order interactions can only be estimated from the synthetic data to the extent that their design is correlated with the main or first-order interactions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: De-Identifying Government Datasets_ Techniques and Governance."}]}
{"id": "nist_00428", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Section 182) Officer; System Privacy Officer; Senior Agency Information Security Officer; Control Assessor. System Development Life Cycle Phase: New - Implementation/Assessment. Existing - Operations/Maintenance. Discussion: Authorization packages 96 include security and privacy plans, security and privacy assessment reports, plans of action and milestones, and an executive summary. Additional information can be included in the authorization package at the request of the authorizing official. Organizations maintain version and change control as the information in the authorization package is updated. Providing timely updates to the plans, assessment reports, and plans of action and milestones on an ongoing basis supports the concept of near real-time risk management and ongoing authorization, and can be used for reauthorization actions, if required. The senior agency official for privacy reviews the authorization package for systems that process PII to ensure compliance with applicable privacy requirements and to manage privacy risks, prior to authorizing officials making risk determination and acceptance decisions. The information in the authorization package is used by authorizing officials to make informed, risk-based decisions. When controls are implemented by an external provider through contracts, interagency agreements, lines of business arrangements, licensing agreements, or supply chain arrangements, the organization ensures that the information needed to make risk-based decisions is made available by the provider. The authorization package may be provided to the authorizing official in hard copy or electronically or may be generated using an automated security/privacy management and reporting tool. Organizations can use automated support tools in preparing and managing the content of the authorization package.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_00429", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach say about 3.4.5 Two Level Work Priority Dimensions/Characteristics? According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach, 3.4.5 Two Level Work Priority Dimensions/Characteristics: The two level work priority scheme permits a high amount of flexibility since it can be applied in any degree of detail required. For example, the results of Level I ranking may be adequate to prioritize all audit work, based on available time and resources. If additional ranking characteristics are necessary, the more detailed Level II can be used to further prioritize audit work. A two level review, additionally, enables the auditor to purge from consideration those systems which will definitely not be reviewed for any number of reasons. Environment and resource issues enter in here. The two level work priority scheme follows in outline form, identifying the five dimensions and their related characteristics. [Note: The same characteristic may be used in more than one dimension. The question asked in each will, however, be different.]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach."}]}
{"id": "nist_00430", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The NIST Cybersecurity Framework (CSF) 2.0 provide? (Section 43) d. Organizational cybersecurity practices are regularly updated based on the application of risk management processes to changes in business/mission requirements, threats, and technological landscape. | There is an organization-wide approach to managing cybersecurity risks. Cybersecurity information is routinely shared throughout the organization. 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 the cybersecurity risks of assets. Senior cybersecurity and non-cybersecurity executives communicate regularly regarding cybersecurity risks. Executives ensure that cybersecurity is considered through all lines of operation in the organization.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, csf, fips. General security reference material without sensitive content. Source: The NIST Cybersecurity Framework (CSF) 2.0."}]}
{"id": "nist_00431", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 7.3.5 Location tracking of public safety wearables according to NIST Security Analysis of First Responder Mobile and Wearable Devices According to Security Analysis of First Responder Mobile and Wearable Devices, 7.3.5 Location tracking of public safety wearables: Threat Description: Wearables may beacon out identifying information about the device, such as WiFi or LTE identifiers. From another perspective, installed applications could programmatically access a device's location information. Vulnerability: A lack of temporary identities means that many wireless protocols and devices regularly transmit unencrypted permanent identities that can be stored and tracked. Threat Source: Adversarial Moderate Likelihood: Justification : COTS WiFi, Bluetooth, and LTE devices regularly expose this information. Severity - Emergency Medical Service: Low Confidentiality Impact Justification: Being able to track an EMT would not lead to loss of life or severely impact dayto-day operations. Low Confidentiality Impact Severity - Fire Service: Justification: Being able to track a firefighter would not lead to loss of life or severely impact day-to-day operations. Severity - Law Enforcement: High Confidentiality Impact Justification: If a malicious user could track an officer's device entering an area, they could evade their presence or place the officer in danger. If an undercover agent's device is targeted, it could reveal their identity and result in loss of life. Source: N/A", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Analysis of First Responder Mobile and Wearable Devices."}]}
{"id": "nist_00432", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Workshop on Enhancing Security of Devices and Components Across the Supply Chain provide? (Section 20) ltiple vulnerabilities to fully exploit a system. In the past, it has been difficult to organize data for higher-level contextual information using datasets and standards from NIST, MITRE, and others. However, Jeremy's team has recently utilized generative AI tooling to obtain this higher-level context without the additional resources needed for conventional methods. For him, the emergence of AI tools has moved the industry from the 'age of context' to, as he terms it, the 'age of interface.' With this perspective and tools at hand, Jeremy presented his success with advanced generative AI to augment the development of attack chains with vulnerability information. This approach shows promise, yet it is not devoid of risks. Jeremy presented examples of using generative AI systems with prompts defining strict policies that tools violated, despite being given the needed context. Nonetheless, he is confident that they will improve in this age of interface and enable new capabilities for attackers and defenders alike. Finally, Peter Mell presented his research on the software, hardware, and trends for vulnerability management in the past, present, and future. Historically, claims of unbreakable secure software were met with skepticism, while hardware was perceived to be the immutable root of trust. This perception persisted, even though hardware is designed and programmable with software. As Peter put it, in some sense, 'hardware is software.' To effectively compare and contrast hardware and software, more data are needed for hardware vulnerability research. Peter compared the public infrastructure for software to the current hardware vulnerability landscape. For the categorization of vulnerability types, less than half have been observed with confirmed hardware bugs, with little overlap in categories between hardware and software bugs. Additionally, Peter pointed out that he found little public evidence of hardware bugs, as opposed to thousands a year for software.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Workshop on Enhancing Security of Devices and Components Across the Supply Chain."}]}
{"id": "nist_00433", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Integrating Forensic Techniques into Incident Response say about N? (Part 8) According to Guide to Integrating Forensic Techniques into Incident Response, N: See Incident response | O | O | O | O | O | O | O | O | O | O | O | O | O | O | | Incident Incident response, 2-1, 2-3, 2-4, 3-5, 3-7 | Office of Inspector General, 2-3, 2-5 | Office of Inspector General, 2-3, 2-5 | Office of Inspector General, 2-3, 2-5 | Office of Inspector General, 2-3, 2-5 | Office of Inspector General, 2-3, 2-5 | Office of Inspector General, 2-3, 2-5 | Office of Inspector General, 2-3, 2-5 | Office of Inspector General, 2-3, 2-5 | Office of Inspector General, 2-3, 2-5 | Office of Inspector General, 2-3, 2-5 | Office of Inspector General, 2-3, 2-5 | Office of Inspector General, 2-3, 2-5 | Office of Inspector General, 2-3, 2-5 | Office of Inspector General, 2-3, 2-5 | | Containment, 3-5 Exercises, B-1 | Operating system, 5-1, C-2 | Operating system, 5-1, C-2 | Operating system, 5-1, C-2 | Operating system, 5-1, C-2 | Operating system, 5-1, C-2 | Operating system, 5-1, C-2 | Operating system, 5-1, C-2 | Operating system, 5-1, C-2 | Operating system, 5-1, C-2 | Operating system, 5-1, C-2 | Operating system, 5-1, C-2", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Integrating Forensic Techniques into Incident Response."}]}
{"id": "nist_00434", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide for Conducting Risk Assessments provide? (Section 72) _\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ The first step in the risk assessment process is to prepare for the assessment. The objective of this step is to establish a context for the risk assessment. This context is established and informed by the results from the risk framing step of the risk management process. Risk framing identifies, for example, organizational information regarding policies and requirements for conducting risk assessments, specific assessment methodologies to be employed, procedures for selecting risk factors to be considered, scope of the assessments, rigor of analyses, degree of formality, and requirements that facilitate consistent and repeatable risk determinations across the organization. Organizations use the risk management strategy to the extent practicable to obtain information to prepare for the risk assessment. Preparing for a risk assessment includes the following tasks: - Identify the purpose of the assessment; - Identify the scope of the assessment; - Identify the assumptions and constraints associated with the assessment; - Identify the sources of information to be used as inputs to the assessment; and - Identify the risk model and analytic approaches (i.e., assessment and analysis approaches) to be employed during the assessment. TASK 1-1: Identify the purpose of the risk assessment in terms of the information that the assessment is intended to produce and the decisions the assessment is intended to support. Supplemental Guidance: The purpose of the risk assessment is explicitly stated in sufficient detail to ensure that the assessment produces the appropriate information and supports the intended decisions. Organizations can provide guidance on how to capture and present information produced during the risk assessment (e.g., using a defined organizational template). Appendix K provides an exemplary template for a risk assessment report or the preferred vehicle for risk communication.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guide for Conducting Risk Assessments."}]}
{"id": "nist_00435", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Printed Information : according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Printed Information :: Name: Test Cardholder IV Employee Affiliation: Employee Expiration Date: 2040DEC31 Agency Card Serial Number: 0000212348 Issuer Identification: TSTISR320161719 Organization Affiliation (Line 1): Not present Organization Affiliation (Line 2): Not present", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_00436", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio provide? (Section 70) (the product of likelihood and impact). Public officials and board members also provide guidance to their corporate officers at the enterprise level and highlevel executives at the organization level. This includes guidance on ceilings for capital expenditures (CapEx) and operating expenses (OpEx) and objectives for free cash flow. For the Federal Government, similar requirements are expressed through OMB guidance and strategic direction from senior agency officials, chief executives, and other designees (e.g., an ERM Council). For both private- and public-sector entities, leaders issue guidance to continue, accelerate, reduce, delay, or cancel significant enterprise initiatives while considering their risk appetite and tolerance levels. They also do this while making decisions about what constitutes prudent risk disclosures, balancing the competing objectives of a) properly informing stakeholders and overseers (including regulators) through required filings and statements at hearings and b) protecting sensitive information from competitors and adversaries. The second step in the risk management life cycle involves identifying a comprehensive set of risks and recording them in the risk register. This involves identifying events that could enhance or impede objectives, including the risks involved in failing to pursue opportunities. ICT risk identification is composed of four inputs: 1. Identification of the organization's mission-supporting assets and their valuation, 2. Determination of potential threats that might jeopardize the security or performance of those assets and potential ICT opportunities that might benefit the organization, 3. Consideration of the vulnerabilities of those assets, and 4. Evaluation of the potential consequences of risk scenarios. Sections 3.2.1 through 3.2.4 discuss each of these four inputs in more detail. Risk practitioners often perform risk identification as both top-down and bottom-up exercises.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio."}]}
{"id": "nist_00437", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog say about 1.4 Publication Organization? (Part 2) According to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog, 1.4 Publication Organization: further define support needed related to the higher-level capability. The need for a sub-capability or its elements is guided by the cybersecurity needs of the organization as described in SP 800-213. Figure 1 shows the structure of a sub-capability, which like capabilities are named and defined with a short description and further discussion about the sub-capability and why it may be needed. A mapping to related SP 800-53 Rev. 5 controls is also provided for each sub-capability that can help organizations identify the controls and/or enhancements 6 that may be supported by each 5 Capability names follow from NISTIRs 8259A [IR8259A] and 8259B [IR8259B], which were used as inputs along with SP 800-53 Rev. 5 [800-53] to generate this catalog. 6 Organizations should note that applicable control enhancements are sometimes included in the mapping for a sub-capability without the corresponding control that would be assumed in place if the enhancement is in place. Mappings in this catalog reflect the controls and/or enhancements from SP 800-53 Rev. 5 [800-53] that may be supported by the functionality or actions described in the sub-capability. In some cases, control enhancements are supported by the sub-capability while the base control sub-capability. This support for controls may come from a fulfilment of all or part of a control by the presence of the functionality or actions described in the sub-capability. For example, the control may state that the element should function in a specific way and the sub-capability describes how the IoT device should function based on the control. In other cases, support for controls is in the form of enabling the system and/or organization to perform some system/organization-wide function or action including the IoT device.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog."}]}
{"id": "nist_00438", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Guidelines for Storage Infrastructure provide? (Section 114) astructure and should be used: EN-SS-R1 - TLS, hashing, and encryption: To support encrypted communication between storage clients and servers, Transport Layer Security (TLS) protocol should be used. To prevent the use of insecure or outdated configuration, the selection and configuration of TLS protocol implementations, including the selection of TLS version, and the choice of hashing and encryption algorithms, should be based on the following guidelines (or more current versions when published): - Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations (NIST SP800-52 Rev2) [37] - SNIA TLS Specification for Storage Systems Version 1.1 [38] EN-SS-R2 - Cleartext protocols (e.g., HyperText Transfer Protocol (HTTP), Telnet, File Transfer Protocol (FTP), or Remote Shell (RSH)) should not be used: Cleartext protocols are vulnerable to sniffing, interception, and other attacks as they do not encrypt traffic or logon details, making it easy for an eavesdropper to intercept this information. In some implementations, HTTP is supported only for the purpose of redirection to HTTPS to deal with the case of mistyped URL. This should not be allowed in sensitive storage environments. EN-SS-R3 - Encryption for storage management API sessions: Storage management APIs and CLIs are used for administrative access to storage systems. All API and CLI client sessions should be encrypted leveraging features such as vendor configuration options within the management software or the API/CLI software component. EN-SS-R4 - Encryption for administrative access sessions: Administrative sessions over HTTP should use TLS (HTTPS). CLI access should be encrypted using SSH rather than Telnet. The authentication during API access should not use cleartext, and the session itself should be encrypted.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security Guidelines for Storage Infrastructure."}]}
{"id": "nist_00439", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Cryptographic Standards and Guidelines Development Process say about 6. Consider Contributing Standards and Guidelines for Adoption by SDOs? (Part 2) According to NIST Cryptographic Standards and Guidelines Development Process, 6. Consider Contributing Standards and Guidelines for Adoption by SDOs: nvolve seeking public comment on the applicability and currency of the standard or guideline. Comments on proposed updates to or the withdrawal of a FIPS will be solicited using the Federal Register . - \uf0b7 Make the review results public, including any public comments received. - \uf0b7 Renew, update or withdraw the standard or guideline. Renewal involves keeping the document unchanged. Update involves making revisions to the document (technical and otherwise). Withdrawal may be immediate, or it may be a phased withdrawal ('sunsetting'). Some technical content of a withdrawn standard or guideline can potentially be moved to another new or existing standard or guideline. An analysis of the comments received on existing FIPS will be published in the Federal Register and the comments posted on the CSRC website; comments received on existing SPs will be posted on the CSRC website. NIST also will announce its decision on any maintenance effort (e.g., document update or withdrawal) that will take place. NIST will use the processes and procedures described in this publication to develop future cryptographic standards and guidelines. They are designed to provide broad opportunity to offer input on its cryptographic standards and guidelines, and to maximize openness and transparency. NIST will review this publication and its processes and procedures every five years -and more frequently if a need arises. Please address any comments regarding these principles, processes and procedures -and NIST's use of them in developing cryptographic standards and guidelines -to Chief, NIST Computer Security Division at crypto@nist.gov. All comments and NIST's responses will be posted on the CSRC website.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Cryptographic Standards and Guidelines Development Process."}]}
{"id": "nist_00440", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PE-6 in Identity and Access Management for Electric Utilities? (Part 154) Control PE-6: igure 9-3 Guardian ActiveMQ T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . 9.2.3.4 You must install hardware and OS versions specific to Apache Tomcat: Installing Apache Tomcat Double-click the setup launcher to start the setup. It will start the installation process. Click Next to start the installation process. NIST SP 1800-2C: Identity and Access Management for Electric Utilities 155 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . Click I Agree to accept the license terms. It displays the Choose Components screen. Select Custom as the install type, and uncheck the Examples option. Click Next to specify the destination folder for installation. We strongly recommend using the D:\\AlertEnterprise\\Tomcat location. Click Next to specify the configuration parameters. Enter the desired port in the Connector Port text area. The default port is 8080. Specify the User Name and Password in the respective fields. Click Next to select the path of the JRE installed on the system. Select the path of the JDK/JRE that you just installed (e.g., C:\\Program Files\\Java\\jre1.6). Click Install to start the file copying process. Uncheck the Run Apache Tomcat and Show Readme options in the final dialog box. Click Finish to finish the installation. 9.2.3.5 Apache Tomcat Configuration You need to specify the Tomcat configuration, as described in the following steps: Click Start > Programs > Apache Tomcat > Configure Tomcat. Click the Java tab in the Apache Tomcat Properties dialog box. Enter the following settings: a. Initial memory pool: 1024 b. Maximum memory pool: 1024 c. Thread stack size: 300 Note: These settings may vary with the volume of random access memory (RAM) in the server. Click Apply > OK to close the dialog box.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_00441", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD) say about DO NOT EDIT THESE LINES. OSMUD WILL REPLACE WITH ITS CON-? (Part 4) According to Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD), DO NOT EDIT THESE LINES. OSMUD WILL REPLACE WITH ITS CON-: ip 192.168.20.197 NIST SP 1800-15D: Securing Small-Business and Home Internet of Things Devices 181 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Test Case Field Description config rule option enabled '1' option name 'mud_192.168.20.197_same-manufac- ture-pi_REJECT-ALL-LOCAL-TO' option target REJECT option src lan option dest lan option proto all option family ipv4 option src_ip any option dest_ip 192.168.20.197 config rule option enabled '1' option name 'mud_192.168.20.197_same-manufac- ture-pi_REJECT-ALL' option target REJECT option src lan option dest wan option proto all option family ipv4 option src_ip 192.168.20.197", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_00442", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2010 Annual Report? (Part 78) Control HA-3: er's license. We continue to work with the U.S. national standards committees to ensure compatibility with federal credentials and to address the needs of non-federal com\u00ad munities. Contact: Mr. Sal Francomacaro (301) 975-6414 salfra@nist.gov ## Biometric Standards and Conformity Assessment Activities Biometric technologies are currently required in many public and private sector applications worldwide to authenticate an individ\u00ad ual's identity, secure national borders and restrict access to secure sites including buildings and computer networks. Biometrics pro\u00ad vide for secure transactions, positive identification, and augmenta\u00ad tion to human judgment. Use of biometrics is being considered by financial institutions, the healthcare industry, and in educational ap\u00ad plications. Consumer uses are also expected to significantly increase for personal security and convenience in home automation and se\u00ad curity systems, and in the retail, gaming and hospitality industries. These many varied uses require the development of open standards to maintain interoperability and encourage continued adoption. The NIST Biometrics program supports the development of volun\u00ad tary standards for biometrics, and responds to government, indus\u00ad try and market demands for open systems standards by: - Accelerating development oGLYPH(cmap:df00) GLYPH(cmap:df00)ormal national and international biometric standards and associated conformity assessment; - Educating users on the capability oGLYPH(cmap:df00) standards-based open systems solutions; - Promoting standards adoption; - Developing conGLYPH(cmap:df00)ormance test architectures and test tools to test implementations of these standards; - Supporting harmonization oGLYPH(cmap:df00) biometric, tokens and security standards; and - Addressing the use oGLYPH(cmap:df00) biometric-based solutions GLYPH(cmap:df00)or ID Management applications.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: token, sso. Contains security framework guidance for authentication systems. Source: Computer Security Division 2010 Annual Report."}]}
{"id": "nist_00443", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Codes for Identification of Federal and Federally-Assisted Organizations say about Code Organization? (Part 2) According to Codes for Identification of Federal and Federally-Assisted Organizations, Code Organization: | 1900 | STATE , Department of - continued | |--------|-----------------------------------------------------------------------------------| | 1914 | Office of the Under Secretary for Economic and Agricultural Affairs | | 1933 | Bureau of Economic and Business Affair | | 1934 | Bureau of Overseas Buildings Operations | | 1915 | Office of the Under Secretary for Arms Control and International Security Affairs | | 1950 | Bureau of Political-Military Affairs | | 1951 | Assistant Secretary for Arms Control | | 1955 | Assistant Secretary for Non-Proliferation | | 1956 | Assistant Secretary for Verification and Compliance | | 19TB | Office of the Under Secretary for Public Diplomacy and Public Affairs | | 1952 | Bureau of Public Affairs | | 1953 | Bureau of Educational and Cultural Affairs | | 1957 | International Public Information Core Group Secretariat | | 1959 | Office of International Information Programs | | 1941 | Office of the Under Secretary for Global Affairs | | 1936 | Bureau of Democracy, Human Rights and Labor | | 1942 | Bureau of International Narcotics and Law Enforcement Affairs | | 1948 | Bureau of Oceans and International Environmental and Scientific Affairs | | 1954 | Bureau of", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: Codes for Identification of Federal and Federally-Assisted Organizations."}]}
{"id": "nist_00444", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Key Management Documents say about 7.3.4 Per KPDU Security Label and Format? According to Secure Data Network Systems (SDNS) Key Management Documents, 7.3.4 Per KPDU Security Label and Format: This option is used to negotiate the existence and format of an explicit security label on every PDU exchanged while using the TEK identified. The choices for this option and the mnemonics are: ppl abs Per PDU security label absent ppl DoD DoD security label per PDU ppl XXX XXX security label per PDU NOTE: XXX is yet to be defined. 7.3.5", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_00445", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 7.2.2 Delegated RPKI-Model Functional Requirements according to NIST Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, 7.2.2 Delegated RPKI-Model Functional Requirements: The SIDR example implementation included the capability for a resource holder to set up its own delegated CA, create its own repository, and offer a hosted service to its customers, including the ability to publish customer ROAs to its repository, delete customer ROAs from its repository, and have customer ROAs expire from its repository. The ROAs in this delegated CA repository were included in the RPKI data that RPs downloaded to their VCs, and VRPs derived from these ROAs were provided to RP routers via the RPKI -to-router protocol.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_00446", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Framework for Designing Cryptographic Key Management Systems provide? (Section 23) | Destroy Key and Metadata............................................................................. Associate a Key with its Metadata............................................................... | 44 45 | | Modify | | Metadata.......................................................................................... 45 | | 6.4.11 | Delete Metadata............................................................................................ | 45 | | 6.4.12 | List Key Metadata........................................................................................", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_00447", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security of Interactive and Automated Access Management Using Secure Shell (SSH) say about Source Restriction? (Part 1) According to Security of Interactive and Automated Access Management Using Secure Shell (SSH), Source Restriction: Source Restriction A person who uses an SSH client to access one or more SSH servers, typically to perform administrative operations, transfer data, or access applications. A cryptographic key. In this document, keys generally refer to public key cryptography key pairs used for authentication of users and/or machines (using digital signatures). Examples include identity key and authorized keys. The SSH protocol also uses host keys that are used for authenticating SSH servers to SSH clients connecting them. Changing the key, i.e., replacing it by a new key. The places that use the key or keys derived from it (e.g., authorized keys derived from an identity key, legitimate copies of the identity key, or certificates granted for a key) typically need to be correspondingly updated. With SSH user keys, it means replacing an identity key by a newly generated key and updating authorized keys correspondingly. A file associated with a specific account that contains one or more host keys. Each host key is associated with an SSH server address (IP or hostname) so that the server can be authenticated when a connection is initiated. The user or administrator who makes the first connection to an SSH server is responsible for verifying that the host key presented by that server is the actual key (not a rogue key) before it gets placed in the known hosts file. A password used to protect an identity key. After entered by a user or administrator, a passphrase is mathematically converted into large number which serves as a key that is used to encrypt the identity key. In order to decrypt the identity, the passphrase must be entered again so that the same key can be regenerated for decryption. The act of an attacker moving from one compromised system to one or more other systems within the same or other organizations. Pivoting is fundamental to the success of advanced persistent threat (APT) attacks. SSH trust relationships may more readily allow an attacker to pivot.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Security of Interactive and Automated Access Management Using Secure Shell (SSH)."}]}
{"id": "nist_00448", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Telehealth Remote Patient Monitoring Ecosystem say about 10. Click OK.? According to Securing Telehealth Remote Patient Monitoring Ecosystem, 10. Click OK.: <!-- image --> 11. Add additional servers by following the same pattern described above, populating the respective Interface and Address Pool, and check the Enable DHCP Server that corresponds to the appropriate server. Values for each server are described below: 2. e. - a. Interface: Enterprise-Services - i. - Address Pool: 192.168.40.100-192.168.40.254 - ii. Enable DHCP Server: - checked - b. - Interface: HIS-Services - i. - Address Pool: 192.168.41.100-192.168.41.254 - ii. Enable DHCP Server: checked - c. - Interface: Remote-Services - i. - Address Pool: 192.168.42.100-192.168.42.254 - ii. Enable DHCP Server: - checked - d. Interface: Databases - i. - Address Pool: 192.168.43.100-192.168.43.254 - ii. Enable DHCP Server: checked Clinical-Workstations - Interface: - i. - Address Pool: 192.168.44.100-192.168.44.254 - ii. Enable DHCP Server: - checked", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_00449", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Derivation Using Pseudorandom Functions say about key hierarchy? According to Recommendation for Key Derivation Using Pseudorandom Functions, key hierarchy: A multiple-level tree structure such that each node represents a key and each branch - pointing from one node to another - indicates a key derivation from one key to another key.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key Derivation Using Pseudorandom Functions."}]}
{"id": "nist_00450", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations? (Part 68) Control HA-1: | CertiPath Key Recovery Policy , CertiPath, December 2013. 0v.1.5.pdf | | CP X509 CP | CertiPath X.509 Certificate Policy , CertiPath, Version 3.26, November 2014. | | DoD Policy | X.509 Certificate Policy for the United States Department of Defense , Department of Defense, Version 10.5, January 2013.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations."}]}
{"id": "nist_00451", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does An Analysis of Computer Security Safeguards for Detecting and Preventing Intentional Computer Misuse provide? (Section 16) iagram that reflects the model we suggest. Insurance, personnel, and contracts are defined as staff activities, but could be placed at the same level as operations, data processing, security or audit. Following is a brief description of each element of the model: &lt; z g Io Ico &lt; 111 Z -J D &gt; QC UJ O w Li. ^ Vi &gt; ^ O X &lt; ILU IQ. o o LU <!-- image --> CO St &lt; z \\_1 u. &lt; CO O &lt; N QC LU hD Q. o o (J z N OQ \u00a72 &lt; ec O &lt; QC O UJ O Q QC O O O &lt; CM LU QC D <!-- image --> - General Management -This element includes those persons or functions whose primary responsibility is the management and administration of the agency. This element is responsible for establishing policy and ensuring that adequate financial and line management support is provided to carry out the agency charter. - Personnel-This subelement is responsible for maintaining personal information on employees required by the agency as well as providing the official guidelines describing the policy of the agency regarding hiring and firing criteria. - Contracts -This subelement is responsible for ensuring that all contracts, including those involving software and hardware, are well specified to minimize the potential for loss resulting from improper performance. - Insurance-This subelement is responsible for ensuring that the facilities, including software and hardware, are adequately insured. - Operations Division-Most Government agencies will have more than one operations division, but conceptually they are all similar from a data processing point of view. Consequently the model provides for only one operations division. An operations division is an organizational unit responsible for one general agency function such as logistics. Each operations division has many departments, but only two, application program development and data handling, are germane to the model.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: An Analysis of Computer Security Safeguards for Detecting and Preventing Intentional Computer Misuse."}]}
{"id": "nist_00452", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Evaluator action elements: according to NIST COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0 According to COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0, Evaluator action elements:: ADO\\_IGS.1.1E The evaluator shall confirm that the information provided meets all requirements for content and presentation of evidence. ADO\\_IGS.1.2E The evaluator shall confirm that the installation procedures result in a secure configuration.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0."}]}
{"id": "nist_00453", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Framework for Designing Cryptographic Key Management Systems say about Contents? (Part 35) According to A Framework for Designing Cryptographic Key Management Systems, Contents: ................................................................................ | 9.3 Interoperability Testing ........................................................................................ | 9.3 Interoperability Testing ........................................................................................ | 77 | | 9.4 Self-Testing .......................................................................................................... | 9.4 Self-Testing .......................................................................................................... | 9.4 Self-Testing .......................................................................................................... | 78 | | 9.5 Scalability Testing ................................................................................................ | 9.5 Scalability Testing ................................................................................................ | 9.5 Scalability Testing ................................................................................................ | 78 | | 9.6 Functional Testing and Security Testing.............................................................. | 9.6 Functional Testing and Security Testing.............................................................. | 9.6 Functional Testing and Security Testing.............................................................. | 78 | | 9.7 Environmental Testing .........................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_00454", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2016 NIST_ITL Cybersecurity Program Annual Report say about F E B R U A R Y 2 0 1 6 :? According to 2016 NIST_ITL Cybersecurity Program Annual Report, F E B R U A R Y 2 0 1 6 :: Trustworthy Suppliers Framework Forum ( Postponed due to inclement weather - rescheduled in May 2016 ) February 16", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_00455", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Minimum Security Requirements for Multi-User Operating Systems provide? (Section 48) , date, location of terminal, or method of access (e.g., dial-up port or local area network port). These requirements provide finer-grained and organizationspecific system access control capabilities. Requirements are specified to display an advisory warning message to all users prior to system logon to discourage a would-be system penetrator from attempting an unauthorized system access. Such a message can also provide a legal basis for subsequent prosecution of system penetrators. Although not a direct countermeasure, auditing requirements are specified to provide the capability to perform an after-the-fact analysis of unauthorized system access attempts. The MSR specify auditing requirements to monitor failed login attempts. In addition, the MSR specify requirements to display to an authorized user, upon successful system access, the date and time, method of access or port of entry, and the number of failed logon attempts since the last successful system access by his or her userlD. These requirements provide an organization with the capability to detect attempted or successful system penetrations. This provides the opportunity for the organization to take corrective action, such as strengthening existing user authentication methods or changing a password. Authorized users can gain access to resources for which they are not allowed by assuming the userlD of another user and gaining the associate access rights. This can be accomplished by exploiting vulnerabilities associated with passwords, or by spoofing legitimate userlD authorization prompts and stealing passwords associated with other users. To address the vulnerability associated with passwords, the MSR specify password requirements that promote a strong organizational password management program.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Minimum Security Requirements for Multi-User Operating Systems."}]}
{"id": "nist_00456", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Securing Web Transactions_ TLS Server Certificate Management? (Part 322) Control HA-1: he following checkbox: - Include in all CRLs. Specifies where to publish in the Active Directory when publishing manually. - In Specify locations, users can obtain a certificate revocation list (CRL). Select the entry C:\\\\Windows\\system32\\CertSrv\\CertEnroll\\&lt;CaName&gt;&lt;CRLNameSuffix&gt;&lt;DeltaCRLAll owed&gt;.crl. 10. On the Extensions tab, select the following checkboxes: - Publish CRLs to this location. - Publish Delta CRLs to this location. 11. Change Select extension to Authority Information Access (AIA). 12. In the Specify locations, users can obtain a certificate revocation list (CRL) do the following: - a. Select the entry &gt;.crt and then click Remove. In Confirm removal, click Yes. This publication is available free of charge from: http://doi.org/10.6028/NIST.SP.1800-16. - b. Select the entry file://&lt;ServerDNSName&gt;/CertEnroll/&lt;ServerDNSName&gt;\\_&lt;CaName&gt;&lt;CertificateName&gt; .crt and then click Remove. In Confirm removal, click Yes. 13. In Specify locations, users can obtain a CRL, click Add. 14. In Add Location, in Location , type click OK. This returns to the CA properties dialogue box. 15. On the Extensions tab, select the following checkbox: - Include in the AIA of issued certificates. 16. In Specify locations from which users can obtain a certificate revocation list (CRL), select the entry that starts with ldap://CN=CATruncatedName&gt;,CN=AIA,CN=PublicKeyServices. 17. On the Extensions tab, select the following checkbox: - Include in the AIA extension of issued certificates. 18. In Specify locations, users can obtain a certificate revocation list CRL. Select the entry C:\\\\Windows\\system32\\CertSrv\\CertEnroll\\&lt;ServerDNSName&gt;\\_&lt;CaName&gt;&lt;CertificateName&gt; .crt. 19.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_00457", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to NIST_SP_800-53r5_Security_Privacy_Controls? Discussion: Communications paths can be logically separated using encryption.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00458", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations say about 1.5.1 Glossary? (Part 9) According to Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations, 1.5.1 Glossary: module. | | Cryptographic product | Software, hardware or firmware that includes one or more cryptographic functions. Acryptographic product is or contains a cryptographic module. | | Cryptographic service | A service that provides confidentiality, integrity, source authentication, entity authentication, non-repudiation support, access control and availability (e.g., encryption and decryption, and digital signature generation and verification). | | Cryptoperiod | The time span during which a specific key is authorized for use or in which the keys for a given system or application may remain in effect. | | Data integrity | A property whereby data has not been altered in an unauthorized manner since it was created, transmitted, or stored. | | Decryption | The process of changing ciphertext into plaintext using a cryptographic algorithm and key. | | De-registration (of a key) | The inactivation of the records of a key that was registered by a registration authority. | | Destruction | The process of overwriting, erasing, or physically destroying information (e.g., a cryptographic key) so that it cannot be recovered. See SP 800-88. 4 | 4 SP 800-88 Revision 1, Guidelines for Media Sanitization.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations."}]}
{"id": "nist_00459", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings? (Part 17) Control PD-12: it can be supported in a more complex way by adding a second permitted subtree containing the name of the North American Bridge CA and an excluded subtree of all names subordinate to this). This tight trust model is further shown by the Certificate Path Processing Procedure in Section 12.4.3 of the 97 standard, which states: The following checks are applied to a certificate: \u2026.. e) Check that the subject name is within the name-space given by the value of permitted-subtrees and is not within the name-space given by the value of excluded-subtrees. If any of the above checks fails, the procedure terminates, returning a failure indication and an appropriate reason code. Unfortunately, when the GeneralName syntax replaced the X.500 DN syntax in the name constraints extension, it was not as straightforward as simply replacing one syntax with another. The text describing the name constraints extension should have been significantly enhanced, because new possibilities now existed that did not before. Enhancements were needed in a number of ways. Firstly, how was the name constraints extension to ## 5th Annual PKI R&amp;D Workshop - Proceedings handle general names that were not hierarchically structured, such as IP addresses. How could one specify permitted and excluded subtrees for nonhierarchical names? The answer was to exclude these name forms from being applicable to this extension, as is indicated by the text ' only those name forms that have a well-defined hierarchical structure may be used in these fields '. Secondly, what was a relying party to do if there was a mismatch between the various subject alternative name forms in a certificate, and those in the name constraints extension in the issuing CA's certificate? Furthermore what is the default constraint on a name form that is not included in the name constraints extension?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings."}]}
{"id": "nist_00460", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 844) Interface between control systems and equipment with high availability, without compute nor bandwidth constraints Table H-2 Analysis Matrix of Security-Related Logical Interface Categories, Defined by Attributes s t n e m e r i u q e r y t i l i b a l i a v A : 3 - R T A s t n e m e r i u q e r y t i r g e t n I : 2 - R T A f o i h t d w d n a b w o L : 4 - R T A l s e n n a h c i s n o i t a c n u m m o c i s t n a r t s n o c r o s s e c o r p o r c M i : 5 - R T A e t u p m o c d n a y r o m e m n o s e i t i l i b a p a c y t i l a i t n e d i f n o", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_00461", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Section 192) documentation costs, provide increased speed and efficiency in generating important information for decision makers, and provide more effective means for updating critical risk management information. It is recognized that certain controls are not conducive to the use of automated tools and therefore, manual methods are acceptable in those situations. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ be provided. The terms and conditions for the common control authorization provide a description of any specific limitations or restrictions placed on the operation of the system or the controls that must be followed by the system owner or common control provider. The authorization termination date is established by the authorizing official and indicates when the authorization expires. Organizations may eliminate the authorization termination date if the system is operating under an ongoing authorization-that is, the continuous monitoring program is sufficiently robust and mature to provide the authorizing official with the needed information to conduct ongoing risk determination and risk acceptance activities regarding the security and privacy posture of the system and the ongoing effectiveness of the controls employed within and inherited by the system. The authorization decision is included with the authorization package and is transmitted to the system owner or common control provider. Upon receipt of the authorization decision and the authorization package, the system owner or common control provider acknowledges and implements the terms and conditions of the authorization.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, fips, security control. General security reference material without sensitive content. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_00462", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Random Number Generation Using Deterministic Random Bit Generators say about Table of Contents? (Part 30) According to Recommendation for Random Number Generation Using Deterministic Random Bit Generators, Table of Contents: | Instantiation of CTR_DRBG Without a Derivation Function.......................... 86 | | | B.4.3 | Reseeding a CTR_DRBG Instantiation Without a Derivation Function........ 86 | | | B.4.4 | Generating Pseudorandom Bits Using CTR_DRBG.......................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Number Generation Using Deterministic Random Bit Generators."}]}
{"id": "nist_00463", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management say about 2.2.2.4 Use of Gap Analysis to Identify Threats? (Part 3) According to Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management, 2.2.2.4 Use of Gap Analysis to Identify Threats: , but inventory is not always accurate. \u2022 Network flows are not mapped. \u2022 Asset classification is performed and effective. \u2022 Internal security roles are defined but not those of supply chain partners. | \u2022 Internal user (adds a non-compliant device; because a device is not in inventory, scans may miss it as a host so vulnerabilities may go undetected) \u2022 External adversary (could gain network access, and activities might not be distinguished from unmapped, typical traffic patterns) \u2022 External partner (may not fulfill responsibilities for protecting, detecting, or responding to incidents) | | ID.BE | Business Environment | \u2022 Priorities and responsibilities based on the Commercial Facilities Sector. \u2022 Dependencies and resilience requirements are anecdotally understood but not more formally recorded. | \u2022 Power failure (causes customers [e.g., emergency services, hospitals] with critical dependencies to experience an extended loss of internet service due to a lack of service level agreements and documented resilience requirements) | | PR.AT | Awareness and Training | \u2022 All staff have been trained in physical and information security practices during onboarding. | \u2022 Internal user (may fall victim to an email phishing attack due to a lack of sufficient training) | | PR.DS | Data Security | \u2022 Inbound and outbound remote connections are encrypted. \u2022 Laptops with proprietary facility information do not have full-disk encryption. \u2022 Email systems are configured to provide limited data loss prevention.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management."}]}
{"id": "nist_00464", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Digital Identity Guidelines_ Federation and Assertions say about 4.6.1. IdP-Controlled Decisions? According to Digital Identity Guidelines_ Federation and Assertions, 4.6.1. IdP-Controlled Decisions: - 4.6.1.1. IdP Allowlists of RPs In a pre-established trust agreement, IdPs MAY establish allowlists of RPs that are authorized to receive authentication and attributes from the IdP without a runtime decision from the subscriber. When placing an RP on its allowlist, the IdP SHALL confirm that the RP abides by the terms of the trust agreement. The IdP SHALL determine which identity attributes are passed to the allowlisted RP upon authentication. IdPs SHALL make allowlists available to subscribers, as described in Sec. 7.2. IdP allowlists SHALL uniquely identify RPs through fully qualified domain names, cryptographic keys, or other identifiers that are applicable to the federation protocol in use. Any entities that share an identifier SHALL be considered equivalent for the purposes of the allowlist. Allowlists SHOULD be as specific as possible to avoid unintentional impersonation of an RP. An allowlist entry for an RP SHALL NOT use a wildcard domain identifier. IdP allowlist entries for an RP SHALL indicate which attributes are included as part of an allowlisted decision. If additional attributes are requested by the RP, the request SHALL be: - Subject to a runtime decision of the authorized party to approve the additional attributes requested, - Redacted to only the attributes in the allowlist entry, or - Denied outright by the IdP. IdP allowlist entries MAY be applied based on aspects of the federation transaction, such as the xALs required for the transaction. For example, an IdP could use an allowlist entry to bypass a consent screen for an FAL1 transaction but require confirmation of consent from the subscriber during an FAL3 transaction.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Digital Identity Guidelines_ Federation and Assertions."}]}
{"id": "nist_00465", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Architecture Design Process for Health Information Exchanges (HIEs) provide? (Section 45) ital Two are part of an HIE. When exchanging information, the communication channel is protected through various security and privacy controls to ensure that security and privacy requirements are met. For example, Transport Layer Security (TLS) is used to encrypt the channel, and patient consent information will be verified and exchanged before sending health information. HITSP: T17, Secured Communication Channel; TN907, Common Data Transport Technical Note. NHIN Core Service : Messaging Platform. HIPAA Security Rule: 45 CFR 164.312(e)(1), Standard: Transmission Security; Implementation Specification: Encryption. - SP 800-45, Version 2, Guidelines on Electronic Mail Security. - SP 800-52, Guidelines for the Selection and Use of Transport Layer Security (TLS) Implementations. - SP 800-53 Rev. 3, Recommended Security Controls for Federal Information Systems and Organizations, security control family: System and Communications Protection (SC). - SP 800-58, Security Considerations for Voice Over IP Systems. - SP 800-77, Guide to IPsec VPNs. - SP 800-113, Guide to SSL VPNs. Definition: To ensure that sensitive health information is not sent intentionally or unintentionally to a party that is not authorized to view it. Illustration: 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. HITSP: TP13, Manage Sharing of Documents. HIPAA Security Rule: 45 CFR 164.312(e)(1), Standard: Transmission Security; Implementation Specification: Encryption. - Draft FIPS 140-3, Security Requirements for Cryptographic Modules . - SP 800-45, Version 2, Guidelines on Electronic Mail Security. - SP 800-52, Guidelines for the Selection and Use of Transport Layer Security (TLS) Implementations. - SP 800-53 Rev.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, control family, security control. General security reference material without sensitive content. Source: Security Architecture Design Process for Health Information Exchanges (HIEs)."}]}
{"id": "nist_00466", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Considerations for Voice Over IP Systems say about 1. Develop appropriate network architecture.? (Part 2) According to Security Considerations for Voice Over IP Systems, 1. Develop appropriate network architecture.: 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. An especially challenging security environment is created when new technologies are deployed. Risks often are not fully understood, administrators are not yet experienced with the new technology, and security controls and policies must be updated. Therefore, agencies should carefully consider such issues as their level of knowledge and training in the technology, the maturity and quality of their security practices, controls, policies, and architectures, and their understanding of the associated security risks. These issues should be considered for all systems but are especially important with VOIP deployment for essential operations, such as systems designated \"high\" under FIPS 199, Standards for Security Categorization of Federal Information and Information Systems [2].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_00467", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Recommendation for Key Management_ Part 1 \u2013 General? (Part 30) Control HA-3: private key may be used to generate signatures) is often shorter than the recipient-usage period (i.e., the period during which the signature may be verified by the public signatureverification key). In this case, the private key is intended for use for a fixed period of time, after which the key owner shall destroy 56 the private key. The public key may be available for a longer period for verifying signatures. The cryptoperiod of a private source-authentication key that is used to sign challenge information is basically the same as the cryptoperiod of the associated public key (i.e., the public source-authentication key). That is, when the private key is no longer to be used to sign challenges, the public key is no longer needed. In this case, the originator and recipient-usage periods are the same. - For key transport keys, the public key-transport key is used to apply protection (i.e., encrypt data), so its cryptoperiod would be considered to be an originator-usage period; the private key-transport key is used to decrypt the encrypted data, so its cryptoperiod to be the recipient-usage period. The originator-usage period (i.e., the period during which the public key may be used for encryption) is often shorter than the recipient-usage period (i.e., the period during which the encrypted information may be decrypted). - For key-agreement algorithms, the cryptoperiods of the two keys of the key pair are usually the same. Where public keys are distributed in public-key certificates, each certificate has a validity period indicated by the notBefore and notAfter dates in the certificate. Certificates may be renewed (i.e., a new certificate containing the same public key may be issued with a new validity period).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_00468", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is The CIA triad represents the three pillars of information security according to Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events? The CIA triad represents the three pillars of information security: confidentiality, integrity, and availability, as follows:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_00469", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case provide? (Section 190) his would be a new domain controller in a new forest. Mention a Root Domain name as applicable to your environment. <!-- image --> 11. Set a Directory Services Restore Mode password in the next step. Click Next. 12. Under ' DNS Options ' leave the default options selected. Click Next. <!-- image --> <!-- image --> 13. Confirm the NETBIOS domain name under Additional Options . Click Next . 14. Leave the default folder paths as it is Under Paths . Click Next. <!-- image --> <!-- image --> 15. Confirm all the settings On the Review Options page. Click Next . 16. Click Install on the Prerequisites Check to launch the installation process. The server will auto reboot upon completion. 17. Login with domain administrator credentials upon reboot. Open Server Manager and click on Active Directory Users and Computers under Tools to manage your AD. <!-- image --> <!-- image --> All the Linux systems from the work-cell were joined to the AD domain lan.lab using Centrify Express . The initial domain join process is a onetime task and involves a system restart. The procedure to join Ubuntu Linux Systems to Active Directory domain using Centrify is mentioned below. In addition, DNS records for each Linux host were manually created on the Active Directory server. Connectivity between your Linux clients and AD server: Ensure the Linux clients can reach the AD Domain Controller. Configure the appropriate DNS settings on the Linux client. Set the search domain to domain name of Active Directory. Verify the DNS-settings in the /etc/resolv.conf file of your Linux server. The following instructions are for a Debian/Ubuntu system: 1. Download the Centrify Express (CentrifyDC) free package from https://launchpad.net or https://www.centrify.com/express/linux/download/ as per CPU architecture of the Linux client. 2. Install the package: dpkg -i &lt;package\\_name&gt; 3. Install any dependencies if prompted. Re-run when done. 4.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case."}]}
{"id": "nist_00470", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RA-1 in Guide to Operational Technology (OT) Security? (Part 176) Control RA-1: t of Japan and sent a massive tsunami inland toward the nuclear plant. The tsunami compromised the plant\u2019s seawall, flooding much of the plant, including the location housing the emergency generators. This emergency power was critical for operating the control rooms and providing coolant water for the reactors. The loss of coolant caused the reactor cores to overheat to the point where the fuel\u2019s zirconium cladding reacted with water, releasing hydrogen gas and fueling large explosions in three of the four reactor buildings. This resulted in large-scale radiation leakage that has impacted plant employees, nearby citizens, and the local environment. Post-event analysis found that the plant\u2019s emergency response center had insufficient secure communication lines to provide other areas of the plant with information on key safety-related instrumentation. C.3.4. Accidental Events \u2022 \u2022 \u2022 \u2022 29 While a ping sweep was being performed on [N][D] Vulnerability scanner incidents. an active SCADA network that controlled 9-foot robotic arms, one arm became active and swung around 180 degrees. The controller for the arm was in standby mode before the ping sweep was initiated. In a separate incident, a ping sweep was being performed on an ICS network to identify the hosts that were attached to the network for inventory purposes, and it caused a system that controlled the creation of integrated circuits in the fabrication plant to hang. This test resulted in the destruction of $50,000 worth of wafers. 30 [N][D] Penetration testing incident. consulting organization to conduct penetration testing on its corporate IT network. The consulting organization carelessly ventured into a part of the network that was directly connected to the SCADA system. The penetration test locked up the SCADA system, and the utility was not able to send gas through its pipelines for four hours. A natural gas utility hired an IT security In 2019, a U.S.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, penetration test. Contains technical security guidance that could inform defensive posture. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_00471", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Conducting Risk Assessments say about REPRESENTATIVE THREAT EVENTS INITIATED BY THREAT SOURCES? (Part 15) According to Guide for Conducting Risk Assessments, REPRESENTATIVE THREAT EVENTS INITIATED BY THREAT SOURCES: s to which information is supplied, from carrying out operations. | | Compromise design, manufacture, and/or distribution of information system components (including hardware, software, and firmware). | Adversary compromises the design, manufacture, and/or distribution of critical information system components at selected suppliers. | | Conduct an attack (i.e., direct/coordinate attack tools or activities). | Conduct an attack (i.e., direct/coordinate attack tools or activities). | | Conduct communications interception attacks. | Adversary takes advantage of communications that are either unencrypted or use weak encryption (e.g., encryption containing publically known flaws), targets those communications, and gains access to transmitted information and channels. | | Conduct wireless jamming attacks. | Adversary takes measures to interfere with wireless communications so as to impede or prevent communications from reaching intended recipients. | | Conduct attacks using unauthorized ports, protocols and services. | Adversary conducts attacks using ports, protocols, and services for ingress and egress that are not authorized for use by organizations. | | Conduct attacks leveraging traffic/data movement allowed across perimeter. | Adversary makes use of permitted information flows (e.g., email communication, removable storage) to compromise internal information systems, which allows adversary to obtain and exfiltrate sensitive information through perimeters. | | Conduct simple Denial of Service (DoS) attack. | Adversary attempts to make an Internet-accessible resource unavailable to intended users, or prevent the resource from functioning efficiently or at all, temporarily or indefinitely. | | Conduct Distributed Denial of Service (DDoS) attacks. | Adversary uses multiple compromised information systems to attack a single target, thereby causing denial of service for users of the targeted information systems. | | Conduct targeted Denial of Service (DoS) attacks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guide for Conducting Risk Assessments."}]}
{"id": "nist_00472", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to NIST_SP_800-53r5_Security_Privacy_Controls? Discussion: Organizations identify software that may be of concern regarding its origin or", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00473", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for Derived Personal Identity Verification (PIV) Credentials say about B.1.2 Derived PIV Application Data Model Elements? (Part 2) According to Guidelines for Derived Personal Identity Verification (PIV) Credentials, B.1.2 Derived PIV Application Data Model Elements: sent in the Derived PIV Application if the Derived PIV Application contains any retired key management private keys, but may be present even if no such keys are present in the Derived PIV Application. The requirements for the Key History object are as described in Section 3.3.3 of [SP800-73Part1] except for the following: - o References to ' keysWithOnCardCerts ' should be interpreted as keys for which the corresponding certificate is populated within the Derived PIV Application. - o References to ' keysWithOffCardCerts ' should be interpreted as keys for which the corresponding certificate is not populated within the Derived PIV Application. - o References to ' offCardCertURL ' should be interpreted as a URL that points to a file containing the certificates corresponding to all of the retired key management private keys within the Derived PIV Application including those for which the corresponding certificate is stored within the Derived PIV Application. - \uf0b7 Retired X.509 Certificates for Key Management -The read access control rules for the Retired X.509 Certificates for Key Management and PKI cryptographic function access rules for corresponding private keys are as described in Section 3.3.4 of [SP800-73Part1] . - \uf0b7 Security ObjectThe Security Object shall be present in the Derived PIV Application if either the Discovery Object or the Key History object is present, and shall be absent otherwise. The requirements for the Security Object are as described in Section 3.1.7 of [SP800-73Part1] , except for the following: - o The Security Object for a Derived PIV Application is signed using a private key whose corresponding public key is contained in a PIV content signing certificate that satisfies the requirements for certificates used to verify signatures on Cardholder Unique Identifiers (CHUID), as specified in Section 4.2.1 of [FIPS201]. - o The signature field of the Security Object, tag 0xBB, shall include the Derived PIV Credential Issuer's certificate.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, pki, key management. Contains security framework guidance for authentication systems. Source: Guidelines for Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_00474", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2014 Annual Report? (Part 56) Control HA-3: and then developed a SHA-3 standardization plan, which was presented at numerous cryptography conferences in 2013, and posted at the NIST hash website, indicated below, for public feedback. On May 28, 2014, NIST CSD announced Draft FIPS 202, SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions, in the Federal Register (79 FR 30549) and requested comments. The announcement also proposed a revision of the Applicability Clause (#6) of the Announcement Section of FIPS 180-4, Secure Hash Standard, to allow the use of hash algorithms specified in either FIPS 180-4 or FIPS 202 for federal applications that require a cryptographic hash algorithm. The revision was necessary because the original text in FIPS 180-4 mandates the use of hash algorithms specified in FIPS 180-4 only. The other sections of FIPS 180-4 remain unchanged. The ninetyday public comment period for Draft FIPS 202 and the revision in FIPS 180-4 ended on August 26, 2014. The CSD also hosted a SHA-3 workshop at the University of California, Santa Barbara, on August 22, 2014 to obtain feedback on the proposed SHA-3 Standard, and on additional modes of operation based on SHA-3 that are being considered for standardization. Approximately 75 participants from around the world attended the workshop. The CSD received much feedback throughout the year, especially during the week of the workshop. Official comments received on Draft FIPS 202 and on the revision of the Applicability Clause of FIPS 180-4 are posted at http:/ /csrc.nist.gov/groups/ST/hash/sha-3/fips-202-publiccomments-aug2014.html. CSD is in the process of addressing these comments, and incorporating them, as appropriate, in the final versions of FIPS 202 and FIPS 180-4, to be approved by the Secretary of Commerce. NIST will announce the final approval by the Secretary in the Federal Register.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_00475", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does General Access Control Guidance for Cloud Systems provide? (Section 2) 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. 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-210 Natl. Inst. Stand. Technol. Spec. Publ. 800-210, 34 pages (July 2020) CODEN: NSPUE2 This publication is available free of charge from: 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. 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 ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: General Access Control Guidance for Cloud Systems."}]}
{"id": "nist_00476", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3. Introduction to CSF Profiles and Tiers according to NIST The NIST Cybersecurity Framework (CSF) 2.0 According to The NIST Cybersecurity Framework (CSF) 2.0, 3. Introduction to CSF Profiles and Tiers: This section defines the concepts of CSF Profiles and Tiers.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, csf, fips. General security reference material without sensitive content. Source: The NIST Cybersecurity Framework (CSF) 2.0."}]}
{"id": "nist_00477", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Primitive authentication mechanisms that perform the task of either according to A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification? Primitive authentication mechanisms that perform the task of either: (a) verifying the binding of the person identifier with a personal trait sample (e.g., biometric) and perform a comparison of a live sample of a biometric from a cardholder with the validated trait stored on the card (PUM-6, PUM-7 and PUM-8), or (b) verifying cardholder knowledge of a secret shared between the himself/herself (PUM-4) address the threat of an imposter presenting somebody else's token to the authentication system (FF-T1).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification."}]}
{"id": "nist_00478", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Third-Round Report of the SHA-3 Cryptographic Hash Algorithm Competition say about 1.2 Background? (Part 4) According to Third-Round Report of the SHA-3 Cryptographic Hash Algorithm Competition, 1.2 Background: announcement on October 2, 2012 [29], and officially ended the SHA-3 competition. Table 2 shows the competition timeline, including major events leading to the start of the SHA-3 competition. Table 2. SHA-3 Competition Timeline | Date | Event | |-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 10/31-11/1/2005 | Cryptographic Hash Workshop [30], NIST, Gaithersburg, Maryland. | | 8/24-8/25/2006 | Second Cryptographic Hash Workshop [31], UCSB, California. | | 1/23/2007 | Algorithm(s) for the Revision of Federal Information Processing Standard | | 11/2/2007 | Issued the Federal Register Notice Announcing a Request for Candidate Algorithm Nominations for a New Cryptographic Hash Algorithm (SHA-3) Family [6]. SHA-3 competition began. | | 10/31/2008 | SHA-3 Submission Deadline. | | 12/10/2008 | First-round candidates announced. The first round began. | | 2/25-2/28/2009 | First SHA-3 Candidate Conference [32],KU Leuven, Belgium. | | 7/24/2009 | Second-round candidates announced. The first round ended. | | 9/28/2009 | Second-round candidates posted for public review. The second round began. | | 8/23-8/24/2010 | Second SHA-3 Candidate Conference [33], UCSB, California. | | 12/9/2010 | SHA-3 finalists announced. The second round ended. | | 1/31/2011 | Third-round candidates posted for public review. The third round began. | | 3/22-3/23/2012 | Third SHA-3 Candidate Conference [15], Washington, D.C. | | 10/2/2012 | Keccak announced as the SHA-3 winner. SHA-3 competition ended. |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Third-Round Report of the SHA-3 Cryptographic Hash Algorithm Competition."}]}
{"id": "nist_00479", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cloud Computing Synopsis and Recommendations provide? (Section 87) , access to the application is over a network connecting the SaaS provider with the consumer. For public or outsourced SaaS, most application program logic is executed on the cloud provider's servers. The consumer's browser 11 provides: (1) the consumer interface that captures consumer keystrokes and other inputs, and produces output in the form of graphics/sound, and (2) the data export that outputs data to local storage devices such as USB devices or printers. To protect application data exchanged between the consumer's browser and the cloud provider over the network, cryptography is required. Typically, the consumer's browser and the cloud provider's server begin a session by first negotiating a shared key using one of several standard key exchange protocols (e.g., TLS[Die08] or SSL[Net96]). The consumer's browser and the cloud provider can then use the key to encrypt communications. 12 The consumer and provider can then exchange credentials to prove their 11 The consumer may use a browser or other thin-client application to communicate with a SaaS cloud; in practice, browsers are often used as they require no additional installation. For simplicity, this document describes the consumer-side software simply as a \"browser.\" 12 This protection is not without risk however because past implementation errors or protocol flaws have enabled man-in-themiddle attacks that could allow an attacker to hijack a consumer's cloud resources [Mar09]. identities to one another. Generally, a consumer provides an account name and password or other authentication credential such as a time-based hardware token value. The SaaS provider's main responsibility to the consumer is to ensure that the software that it supplies is solidly supported and tested. Another key requirement is that SaaS applications be scalable to increasingly larger consumer workloads.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Cloud Computing Synopsis and Recommendations."}]}
{"id": "nist_00480", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Secure Web Services? (Part 33) Control ES-1: and then initiate a choreography among the services. The rate service may be implemented as an orchestration, as all of the involved Web services would be internal to the rate service's organization. To fully calculate the interest rates that the loan service will use, the rate service consists of a chain of SOAP requests and responses passed from one internal Web service to another to gather the necessary information to respond with accurate rates. Each transaction within the orchestration is controlled by the rate service, so that requests and responses occur in the proper order and failures do not propagate throughout the transaction. Once complete, the rate service returns the result of the orchestration to the loan service, as shown in Figure 2-8. Figure 2-8. The Rate Service as an Orchestration <!-- image --> ## 2.2 Elements of Security Because a Web service relies on some of the same underlying HTTP and Web-based architecture as common Web applications, it is susceptible to similar threats and vulnerabilities. Web services security is based on several important concepts, including 11 : - Identification and Authentication: Verifying the identity of a user, process, or device, often as a prerequisite to allowing access to resources in an information system. - Authorization. The permission to use a computer resource, granted, directly or indirectly, by an application or system owner. - Integrity. The property that data has not been altered in an unauthorized manner while in storage, during processing, or in transit. - Non-repudiation. Assurance that the sender of information is provided with proof of delivery and the recipient is provided with proof of the sender's identity, so neither can later deny having processed the information. 11 The definitions are taken from NIST IR 7298, Glossary of Key Information Security Terms and NIST SP 800-100, Information Security Handbook: A Guide for Managers, available at http://csrc.nist.gov/publications/nistpubs/.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services."}]}
{"id": "nist_00481", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2013 Annual Report? (Part 48) Control HA-3: o holds bimonthly meetings and an annual 2-day conference to discuss current issues and developments of interest to those responsible for protecting sensitive (unclassified) federal systems. Participation in Forum meetings is open to Federal Government employees, and their designated support contractors, who participate in the management of their organization's information security program. Topics of discussion at Forum meetings in FY 2013 included briefings from various federal agencies on Preparing for and Responding to Certification Authority Compromise and Fraudulent Certificate Issuance; Software Assurance: Enabling Security throughout the Software Development Lifecycle; Use of Cybersecurity Function Code; Census Risk Management Program Implementation; National Cybersecurity Center of Excellence (NCCoE); demonstration of Trusted Geolocation in the Cloud; and Policy Machine: Enabling an Enterprise-wide, Data Centric Computing Environment. This year's annual 2-day offsite meeting featured updates on the computer security activities of the Government Accountability Office (GAO), General Services Administration (GSA), Bureau of the Fiscal Service, and NIST. Recent administration guidance directing federal agencies to reduce travel and conference budgets significantly reduced attendance. Technical 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. On August 8, 2013, a Cybersecurity and Risk Management Training Workshop was held at the Department of Commerce with over 500 registrants. Attendees gained a greater understanding of the Risk Management Framework (RMF) and its practical application. Dr.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, rmf, fips. General security reference material without sensitive content. Source: Computer Security Division 2013 Annual Report."}]}
{"id": "nist_00482", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Personal Identity Verification Card Management Report provide? (Section 38) so be accomplished by passing a custom attribute to C\\_CreateObject with the OID to be passed to pivPutData. These complexities are attributed to the nature of the fixed data model that PIV uses. - a. The PIV Client API provides some mechanisms for doing card personalization, specifically to write existing data objects and to generate keys and change default PINs on the card. Currently, no CMSs use this API for abstract card management and personalization. - a. Personal Computer Smart Card (PC/SC) is commonly used to communicate directly to the card from the back-end CMS. It has the most control of the card but also the least amount of card abstraction depending on how it is used. PC/SC does contain a card abstraction layer, which may find more use in upcoming versions of Microsoft operating systems. Each of these lacks an abstract means to perform card application management with ISO 7816-13 or Global Platform. Consequently, card application management is often performed with PC/SC communicating directly with the card over a Secure Sockets Layer (SSL) connection from a CMS server issuing commands to the card. Often, the CMS will use a hybrid combination of PC/SC and PKCS#11 to meet all the requirements to issue and manage cards securely. Standard APIs and operating systems provide reasonable support for the usage of already managed and personalized identity tokens. It is expected that the abstract management and personalization of identity tokens will be addressed in future revisions of standard APIs and operating systems. The PIV suite of standards and specifications define a foundation for interoperability of smart card identity tokens across federal agencies. Many organizations are investigating the need to augment the card management and personalization capabilities of the PIV suite.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Personal Identity Verification Card Management Report."}]}
{"id": "nist_00483", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to Security and Privacy Controls for Information Systems and Organizations? Discussion: The principle of performance security states that security mechanisms are", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00484", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Government Smart Card Interoperability Specification, Version 2.1 provide? (Section 175) ssociated with a Data Model. However, if the smart card uses any of the data elements defined in Data Model then it must use the container and TLV format specified by that Data Model for that element. The SEIWG [SEIW] string is defined as the minimum interoperability mechanism for card holder authentication. The SEIWG strings and files are therefore mandatory for both contact and contactless GSC cards. This specification defines two Data Models. The GSC Data Model was developed for version 1.0 of the GSC-IS (see Appendix C). The GSC Data Model is sometimes referred to as the 'J.8' Data Model, since it was first defined in Section J.8 of the Smart Access Common ID Card contract. The second Data Model was developed for the DoD Common Access Card (CAC) and is referred to as the CAC Data Model (see Appendix D). Applications can discover which Data Model a given card supports by examining the Registered Data Model field of the card's Card Capabilities Container (see Chapter 6). The Registered Data Model field shall contain a 0x01 if the card is using the GSC-IS Data Model defined in Appendix C, or a 0x02 if the card conforms to the CAC Data Model in Appendix D. Error Detection Codes (EDC) are only mandated for the GSC-IS Data Model. All container data elements are stored in SIMPLE-TLV format. Each SIMPLE-TLV data object shall consist of a tag field, a length field and an optional value field. For VM cards implementing the VM card edge interface, the SIMPLE-TLV format is split into a T-Buffer and V-Buffer. (See description in Section 8.4) The tag field T shall consist of a single byte encoding only a number from 1 to 254. No class or construction types are coded. The values '0x00' and '0xFF' are invalid for tag fields. The tag value 0xFE is reserved for the mandatory EDC data object in each container. The scope of tag values is at the container level, so the same tag value could appear in different containers and have different meanings.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_00485", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007 provide? (Section 157) | 18.1 | It is required that the first two fields of the record are ordered, and the field containing the image data shall be the last physical field in the record. | 2 | M | 13.001::LEN_First | First(Field in Record) ST Type(Record) EQ 13 AND Field EQ 13.001 | | | | | | 13::FixedPosition- Fields | 18.1 | It is required that the first two fields of the record are ordered, and the field containing the image data shall be the last physical field in the record. | 2 | M | 13.002::IDC_Second | Second(Field in Record) ST Type(Record) EQ 13 AND Field EQ 13.002 | | | | | | 13::FixedPosition- Fields | 18.1 | It is required that the first two fields of the record are ordered, and the field containing the image data shall be the last physical field in the record. | 2 | M | 13.999::DATA_Last | Last(Field in Record) ST Type(Record) EQ 13 AND Field EQ 13.999 | | | | | | 13::Len=Bytes | 18.1.1 | Field 13.001: Logical record length (LEN) This mandatory ASCII field shall contain the total count of the number of bytes in the Type-13 logical record.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007."}]}
{"id": "nist_00486", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Data Protection Approach for Cloud-Native Applications provide? (Section 7) ical step in data protection. Unlike the former, which only secures stored information, in-transit categorization actively monitors and secures data as they move across services and network protocols. This shift to real-time data analysis within the network brings new observability capabilities, eliminating the need for traffic mirroring and data duplication. To address the need for data categorization during travel across services, a relatively new class of in-proxy applications called the WebAssembly [1] program (also called a WASM module) has been increasingly deployed. A WASM module is a lightweight executable compiled to low-level bytecode. This bytecode can be: - (a) Generated from code written in any language using their associated WebAssembly compilers, including C, C++, and Rust - (b) Run using a WASM runtime in an isolated virtual machine (VM) within the proxy, which allows developers to enhance applications with necessary functionality and run them as efficiently as native code in the proxies. Over the last few years, the Envoy WASM VM as enabled new types of compute and traffic processing capabilities and allowed for custom WASM modules to be built and deployed in a sandboxed and fault-tolerant manner. [3] h Additionally, the following features of WebAssembly modules make them particularly effective for data protection: - Data Discovery and Categorization: WASM modules can dynamically identify and categorize data as they traverse the network, ensuring that sensitive information is recognized and handled appropriately. - Dynamic Data Masking (DDM): WASM modules can apply DDM techniques to redact or mask sensitive information in transit, enhancing privacy and security. - User and Entity Behavior Analytics (UEBA): WASM modules can analyze user and entity behaviors in real time, detecting anomalies and potential security threats.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Data Protection Approach for Cloud-Native Applications."}]}
{"id": "nist_00487", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Secure Web Services say about 2.8 Web Services' Interfaces with Network/Infrastructure Security Architectures? (Part 2) According to Guide to Secure Web Services, 2.8 Web Services' Interfaces with Network/Infrastructure Security Architectures: ely than others to have bugs. An additional security feature provided by Java and .NET frameworks is sandboxing, which is designed to separate all actions of the Web service from the operating system. Sandboxing affords added benefits to developers and administrators: stricter permissions and capabilities than those provided by the operating system can be applied to a Web service, and the sandbox helps to prevent the Web service from inadvertently or maliciously harming the underlying operating system, providing the sandbox itself is robust against attack. Web services frameworks provide a number of benefits to developers in addition to well-tested tools and libraries: automatic creation of WSDL descriptors, client and server stubs, and potentially some implementation code. While this support can greatly improve the productivity of the development team, some developers may begin to rely on these tools when developing Web services and may not fully understand the code that is automatically generated. Should such developers be required to use a different development environment for Web services, they may not be adaptable and may inadvertently introduce security vulnerabilities. Additionally, the use of non-vetted, automatically generated code can itself lead to security vulnerabilities; most automatically generated code is intended merely to guide and aid developers, not for production use. Developers need to be fully versed in the libraries supported by the framework when dealing with libraries that perform authentication, authorization, and other security functions that are not supported by the base framework. For example, XACML and SAML provide a flexible and platform-independent framework for distributed authorization. To properly implement XACML and SAML support may require overriding the framework's authentication mechanism at various points, which could lead to potential vulnerabilities in the Web service application.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services."}]}
{"id": "nist_00488", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 8.1.2 Network Architecture according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance, 8.1.2 Network Architecture: The PCS network is segmented from the main Laboratory LAN by a boundary router. The router uses a dynamic routing protocol, Open Shortest Path First (OSPF), to communicate with the main top-level router. The network architecture is shown in Figure 8-3. All network traffic needs to go through the boundary router to access the main Laboratory LAN. There are two virtual network segments in the system. Each network is managed by an Ethernet switch. The HMI and the Controller are in virtual network VLAN-1, while the Plant Simulator, Data Historian, OPC DA Server, and PLC are in virtual network VLAN-2. VLAN-1 simulates a central control room environment where the HMI and the controllers are virtually located in the same network segment. VLAN-2 simulates the process operation environment which typically consists of the operating plant, PLCs, OPC server, and the Data Historian. Figure 8-3 PCS Network Architecture <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance."}]}
{"id": "nist_00489", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Module-Lattice-Based Key-Encapsulation Mechanism Standard say about 1.1 Purpose and Scope? According to Module-Lattice-Based Key-Encapsulation Mechanism Standard, 1.1 Purpose and Scope: This standard specifies the Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM). A key-encapsulation mechanism (KEM) is a set of algorithms that can be used to establish a shared secret key between two parties communicating over a public channel. A KEM is a particular type of key establishment scheme. Other NISTapproved key establishment schemes are specified in NIST Special Publication (SP) 800-56A, Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm-Based Cryptography [2], and SP 800-56B, Recommendation for Pair-Wise Key Establishment Schemes Using Integer Factorization Cryptography [3]. The key establishment schemes specified in SP 800-56A and SP 800-56B are vulnerable to attacks that use sufficiently-capable quantum computers. ML-KEM is an approved alternative that is presently believed to be secure, even against adversaries in possession of a large-scale fault-tolerant quantum computer. ML-KEM is derived from the round-three version of the CRYSTALS-KYBER KEM [4], a submission in the NIST Post-Quantum Cryptography Standardization project. For the differences between ML-KEM and CRYSTALS-KYBER, see Appendix C. This standard specifies the algorithms and parameter sets of the ML-KEM scheme. It aims to provide sufficient information to implement ML-KEM in a manner that can pass validation (see https://csrc.nist.gov/projects/cryptographic-module-validation-program). For general definitions and properties of KEMs, including requirements for the secure use of KEMs in applications, see SP 800-227 [1]. This standard specifies three parameter sets for ML-KEM that offer different trade-offs in security strength versus performance. All three parameter sets of ML-KEM are approved to protect sensitive, non-classified communication systems of the U.S. Federal Government.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, secret. Contains guidance on protecting sensitive government information. Source: Module-Lattice-Based Key-Encapsulation Mechanism Standard."}]}
{"id": "nist_00490", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Information Security Handbook_ A Guide for Managers provide? (Section 33) | Step 4 - Risk Analysis................................................................... | 88 | | | | 10.1.4.1 Control Analysis................................................................ | 88 | | | | 10.1.4.2 Likelihood Determination.................................................... | 89 | | | | 10.1.4.3 Impact Analysis ................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_00491", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-256 in Trust Model for Security Automation Data 1.0 (TMSAD)? (Part 28) Control HA-256: N. Borenstein, (1996). Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies . November 1996. See [RFC2119] Bradner, S. (1997). Key words for use in RFCs to Indicate Requirement Levels . March 1997. See [RFC4051] Eastlake, D. (2005). Additional XML Security Uniform Resource Identifiers (URIs) . April 2005. See [XML-C14N] Boyer, John (2001). Canonical XML Version 1.0, W3C Recommendation, March 2001. See http://www.w3.org/TR/2001/REC-xml-c14n-20010315 or [XML-C14N11] Boyer, John and Glenn Marcy (2008). Canonical XML Version 1.1 , W3C Recommendation, May 2008. See http://www.w3.org/TR/2008/REC-xml-c14n11-20080502. [XMLDSIG] Eastlake, Donald, et al. (2008). XML Signature Syntax and Processing, 2 nd Edition , W3C Recommendation, June 2008. See http://www.w3.org/TR/xmldsig-core/. [XML-exc-C14N] Boyer, John, Donald Eastlake, and Joseph Reagle (2002). Exclusive XML Canonicalization Version 1.0 , W3C Recommendation, July 2002. See [XPath] Clark, James and Steve DeRose (1999). XML Path Language (XPath) Version 1.0 , W3C Recommendation. October 1999. See http://www.w3.org/TR/1999/REC-xpath-19991116. [XPath Filter-2] Boyer, John, Merlin Hughes, and Joseph Reagle (2002). XML-Signature XPath Filter 2.0 , W3C Recommendation, November 2002. See ## B.2 Informative References [RFC4050] Blake-Wilson, S., et al. (2005). Using the Elliptic Curve Signature Algorithm (ECDSA) for XML Digital Signatures . April 2005. See [SP800-57] United States. National Institute of Standards and Technology. Special Publication 800-57, Recommendation for Key Management - Part 1: General . March 2007.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Trust Model for Security Automation Data 1.0 (TMSAD)."}]}
{"id": "nist_00492", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments say about 3 Approach? (Part 2) According to Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments, 3 Approach: data encryption and key management servers; and cloud services. Cooperative Research and Development Agreements (CRADAs) were established with qualified respondents, and 'build teams' were assembled. The following actions were performed by the build teams: - \uf0a7 fleshing out the initial architecture and composing the collaborators' components into demonstration prototypes - \uf0a7 documenting the architecture and design implementation, including the steps taken to install and configure each component of the demonstration environment - \uf0a7 conducting security and functional testing of the demonstration environment, and then conducting and documenting the results of a risk assessment and a security characteristics analysis - \uf0a7 working with industry collaborators to suggest future considerations", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments."}]}
{"id": "nist_00493", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide say about 5.2.4. Device and Media Controls (\u00a7 164.310(d))? (Part 6) According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide, 5.2.4. Device and Media Controls (\u00a7 164.310(d)): | \u2022 Ensure that an individual is responsible for and records the receipt and removal of hardware and software with ePHI. | \u2022 Has a process been implemented to maintain a record of the movements of and persons responsible for hardware and electronic media that contain ePHI? \u2022 Where is data stored (i.e., what type of media)? \u2022 What procedures already exist to track hardware and software within the organization (e.g., an enterprise inventory management system)? \u2022 If workforce members are allowed to remove electronic media that contain or may be used to access ePHI, do procedures exist to track the media externally? \u2022 Who is responsible for maintaining records of hardware and software? | | 4. Develop Data Backup and Storage Procedures Implementation Specification (Addressable) | \u2022 Create a retrievable exact copy of ePHI, when needed, before movement of equipment. \u2022 Ensure that an exact retrievable copy of the data is retained and protected to maintain the integrity of ePHI during equipment relocation. | \u2022 Has a process been implemented to create a retrievable, exact copy of ePHI when needed and before the movement of equipment? \u2022 Are backup files maintained off-site to ensure data availability in the event that data is lost while transporting or moving electronic media that contain ePHI? \u2022 If data were to be unavailable while media are transported or moved for a period of time, what would the business impact be? |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide."}]}
{"id": "nist_00494", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case say about Sample Risk Management Log? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case, Sample Risk Management Log: The Risk Management Log will be maintained by the Director of Operations and reviewed in the monthly senior management meeting. This log captures the results of the latest risk analysis and the status of planned corrective actions. | Risk | Category (Technical, Management, Contractual, External) | Probability | Impact | Risk Score | Risk Mitigation Strategy (e.g. Avoid, Transfer, Mitigate or Accept the risk) | Actions required | Status (Open, closed, In Progress) | Due Date | |--------|-----------------------------------------------------------|---------------|----------|--------------|--------------------------------------------------------------------------------|--------------------|--------------------------------------|------------|", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case."}]}
{"id": "nist_00495", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD) provide? (Section 196) es Micronets components, the Micronets Microservices layer, the Intelligent Services and Business Logic layer, and the Micronets API framework are each described in their respective subsections below. Figure 8-1 Logical Architecture\u2014Build 3 8.3.1.1 MUD Capability As shown in Figure 8-1, Build 3 includes integrated support for MUD in the form of a MUD registry, a MUD manager, a MUD-capable Micronets Manager, and a MUD-capable Micronets Gateway. Support NIST SP 1800-15B: Securing Small-Business and Home Internet of Things Devices 133 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 This publication is available freeof charge from:https://doi.org/10.6028/NIST.SP.1800-15 for MUD also requires access to a MUD file server that hosts MUD files for the MUD-capable IoT devices being onboarded. Build 3 is based on Release 1 of Wi-Fi Easy Connect, which does not include a mechanism for explicitly conveying the device\u2019s MUD file URL as part of the device bootstrapping information. To work around this deficiency, Build 3 uses both the information element field and the public key field in the device bootstrapping information to determine the device\u2019s MUD file URL. These two fields are used in the following manner: \uf0a7 The information element field indicates the device\u2019s MUD file server. The value in the information element field identifies the device\u2019s manufacturer, and it is assumed that each manufacturer has a well-known location for serving MUD files. \uf0a7 The public key field both conveys the device\u2019s public key and identifies the specific file on the manufacturer\u2019s MUD file server that is the device\u2019s MUD file. \uf0a7 The Micronets Manager extracts these two values from the bootstrapping information and provides them to the MUD registry lookup service, which in turn responds with the URL of the MUD file associated with an onboarded device.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_00496", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to IPsec VPNs provide? (Section 272) data, contains a topological drawing of the interconnection, and provides a signature line. The MOU/A documents the terms and conditions for sharing data and information resources in a secure manner. The MOU/A also defines the purpose of the interconnection, identifies relevant authorities, specifies the responsibilities of both organizations, and defines the terms of agreement, including the apportionment of costs and the timeline for terminating or reauthorizing the interconnection. The MOU/A should not include technical details on how the interconnection is established or maintained; that is the function of the ISA. Items that are typically part of the ISA include the following: - The information and data that will be made available, exchanged, or passed in only one direction between the systems through the IPsec gateways and the sensitivity of that information - The services offered over the VPN by each organization, if any - The user community that will be served by the VPN - A description of all system security technical services pertinent to the secure exchange of data between the systems; examples include the use of NIST-approved encryption 87 NIST SP 800-47, Security Guide for Interconnecting Information Technology Systems , contains information on interconnection agreements, as well as extensive guidance on planning, establishing, maintaining, and disconnecting system interconnections and developing an interconnection agreement [93]. 88 Appendices A and B of NIST SP 800-47 [93] contain detailed guidance on developing an ISA and an MOU/A, as well as a sample of each. Rather than develop an ISA and MOU/A, organizations may choose to incorporate this information into a formal contract, especially if the interconnection is to be established between a Federal agency and a commercial organization. In some cases, organizations may also decide to use established organizational procedures for documenting the agreement in lieu of an ISA and MOU/A.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Guide to IPsec VPNs."}]}
{"id": "nist_00497", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Overview and Considerations of Access Control Based on Attribute Encryption say about Table of Contents? (Part 2) According to Overview and Considerations of Access Control Based on Attribute Encryption, Table of Contents: ...................................................... | 5 | | 2.3. | Bilinear Pair Mapping.................................................................................................. | 7 | | 2.4. | Bilinear Pairing for Cryptography................................................................................ | 9 | | 3. | Identity-Based Encryption ..............................................................................................11 | | | 4. | Attribute-Based Encryption............................................................................................13 | | | 4.1. | Ciphertext-Policy Attribute-Based Encryption | ............................................................13 | | 4.2. | Key-Policy Attribute-Based Encryption ......................................................................18 | | | 5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Overview and Considerations of Access Control Based on Attribute Encryption."}]}
{"id": "nist_00498", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does An Analysis of Computer Security Safeguards for Detecting and Preventing Intentional Computer Misuse say about Safeguard Rankings? (Part 12) According to An Analysis of Computer Security Safeguards for Detecting and Preventing Intentional Computer Misuse, Safeguard Rankings: | | H | | CD | CO | | | | | | woo: | | CO QCcn4-)CQPj4-lCOt-( | | | | | | | | Vj | | | OXJ 03.-iV43a33 | | | | | | | | | | | c^ | | | | | | | | | | | | | | | | ^ | | | | | | | | | in | | | M-l \u2022r4 TJ J-l 4J CO .-I CJ Cfl 44 M-l 0) CO -H 3 o CU -H x: di g O Q H O S Q O H Q \u2022H a!", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: An Analysis of Computer Security Safeguards for Detecting and Preventing Intentional Computer Misuse."}]}
{"id": "nist_00499", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Considerations for Voice Over IP Systems provide? (Section 68) \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ SIP is the IETF specified protocol for initiating a two-way communication session. It is considered by some to be simpler than H.323 [18][16], though it is now the largest RFC in IETF history. SIP is text based; thereby avoiding the ASN.1 associated parsing issues that exist with the H.323 protocol suite, if S/MIME is not used as part of SIP inherent security measures.. Also, SIP is an application level protocol, that is, it is decoupled from the protocol layer it is transported across. It can be carried by TCP, UDP, or SCTP. UDP may be used to decrease overhead and increase speed and efficiency, or TCP may be used if SSL/TLS is incorporated for security services. Newer implementations may use stream control transmission protocol (SCTP), developed in the IETF SIGTRAN working group (RFC 2960) specifically to transport signaling protocols. SCTP offers increased resistance to DoS attacks through a four-way handshake method, the ability to multi-home, and optional bundling of multiple user messages into a single SCTP packet. Additional security services can be used with SCTP via RFC 3436 (TLS over SCTP) or 3554 (SCTP over IP Sec). Unlike H.323, only one port is used in SIP (note that H.323 may also be used in a way that uses only one port - direct routed calls). The default value for this port is 5060. The architecture of a SIP network is different from the H.323 structure. A SIP network is made up of end points, a proxy and/or redirect server, location server, and registrar. A diagram is provided in Figure 5. In the SIP model, a user is not bound to a specific host (neither is this the case in H.323, gatekeeper provides address resolution). The user initially reports their location to a registrar, which may be integrated into a proxy or redirect server. This information is in turn stored in the external location server.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_00500", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings provide? (Section 66) ompliant manner and as electronic evidence in a court of law. Previously the lab employees had to print, hand sign, fax, mail and archive hard copy documents associated with the paper-based processes. The labs increased their competitive advantage by decreasing the time it takes to submit reports to clients (from 1-3 business days with a paper process to immediately available using an electronic process). The lab is using dual appliances in high availability configuration. In addition, SAPI was used to directly integrate report file signing into their LIMS system. Since signed documents need to be validated outside the organization, the lab had set up their system so that the CRL is published to an externally accessible web address (instead to the default location on their internal directory). The lab's root CA certificate was also published to an externally accessible web address along with instructions to clients on how to install this certificate in their local trusted root certificates store. It should be noted that since reports in this system are securely delivered to clients using a web portal, the lab's clients themselves are not necessarily concerned with validating the signatures. However the lab needs to protect itself from a scenario in which external parties may want to change a report to suit their needs. In this case the ability for stand-alone verification of a signed document outside of the lab's system is important for dispute resolution.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, sso. Contains security framework guidance for authentication systems. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_00501", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-06(05) in Assessing Security Requirements for Controlled Unclassified Information? (Part 110) Control AC-06(05): orrectly, operating as intended, and producing the desired outcome with respect to meeting the security requirements for an information system or organization. [2] ## system See information system . ## system security plan A document that describes how an organization meets or plans to meet the security requirements for a system. In particular, the system security plan describes the system boundary, the environment in which the system operates, how the security requirements are satisfied, and the relationships with or connections to other systems. ## Appendix C. Security Requirement Assessment This appendix provides an overview of the process for assessing the security requirements in SP 800-171 [3]. The four-phase process is based on the methodology in SP 800-53A [5] 6 and includes: - Preparing for assessments - Developing assessment plans - Conducting assessments - Analyzing, documenting, and reporting assessment results ## C.1. Preparing for Assessments Thorough preparation by the organization and assessors is an important aspect of conducting an effective assessment. Preparatory activities address a range of issues relating to the cost, schedule, and conduct of the assessment.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00502", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations say about PL-2 SYSTEM SECURITY AND PRIVACY PLANS? According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, PL-2 SYSTEM SECURITY AND PRIVACY PLANS: Supplemental C-SCRM Guidance: The system security plan (SSP) should integrate CSCRM. The enterprise may choose to develop a stand-alone C-SCRM plan for an individual system or integrate SCRM controls into their SSP. The system security plan and/or system-level C-SCRM plan provide inputs into and take guidance from the CSCRM Strategy and Implementation Plan at Level 1 and the C-SCRM policy at Level 1 and Level 2. In addition to internal coordination, the enterprise should coordinate with suppliers, developers, system integrators, external system service providers, and other ICT/OT-related service providers to develop and maintain their SSPs. For example, building and operating a system requires a significant coordination and collaboration between the enterprise and system integrator personnel. Such coordination and collaboration should be addressed in the system security plan or stand-alone C-SCRM plan. These plans should also consider that suppliers or external service providers may not be able to customize to the acquirer's requirements. It is recommended that suppliers, developers, system integrators, external system service providers, and other ICT/OT-related service providers also develop C-SCRM plans for non-federal (i.e., contractor) systems that are processing federal agency information and flow down this requirement to relevant sub-level contractors. Section 2, Appendix C, and Appendix D provide guidance on C-SCRM strategies, policies, and plans. Controls in this publication (NIST SP 800-161, Rev. 1) should be used for the C-SCRM portion of the SSP.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_00503", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to Security and Privacy Controls for Information Systems and Organizations? Discussion: If a federal agency asks individuals to supply information that will become part", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00504", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1.1 Authority according to NIST BIOS Protection Guidelines According to BIOS Protection Guidelines, 1.1 Authority: The National Institute of Standards and Technology (NIST) developed this document in furtherance of its statutory responsibilities under the Federal Information Security Management Act (FISMA) of 2002, Public Law 107-347. NIST is responsible for developing standards and guidelines, including minimum requirements, for providing adequate information security for all agency operations and assets; but such standards and guidelines shall not apply to national security systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), 'Securing Agency Information Systems,' as analyzed in A-130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in A-130, Appendix III. 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: BIOS Protection Guidelines."}]}
{"id": "nist_00505", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST say about Current Notekeeping Practice? According to Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST, Current Notekeeping Practice: - Primary purpose of notekeeping - Notebook issuance - Types of notebook entries - Notebook maintenance", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST."}]}
{"id": "nist_00506", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to SSL VPNs provide? (Section 18) active content, which allows them to provide functionality that is not accessible to SSL portal VPNs. Examples of active content include Java, JavaScript, Active X, or Flash applications or plug-ins. This publication discusses the fundamental technologies and features of SSL VPNs. It describes SSL and how it fits within the context of layered network security. It presents a phased approach to SSL VPN planning and implementation that can help in achieving successful SSL VPN deployments. It also compares the SSL VPN technology with IPsec VPNs and other VPN solutions. This information is particularly valuable for helping organizations to determine how best to deploy SSL VPNs within their specific network environments. Implementing the following recommendations should assist in facilitating more efficient and effective SSL VPN use for Federal departments and agencies. Some organizations, such as Federal agencies, have strict requirements for encryption and integrity protection. SSL VPNs should support the required algorithms for symmetric encryption, key exchange, and hash functions. For government agencies, traffic that requires protection must employ Federal 1 Detailed information on the IPsec components may be found in NIST Special Publication (SP) 800-77, Guide to IPsec VPNs , available from http://csrc.nist.gov/publications/nistpubs/. Information Processing Standard (FIPS)-compliant cryptographic algorithms and modules. Many of the cryptographic algorithms used in some SSL cipher suites are not FIPS-approved, and therefore are not allowed for use in SSL VPNs that are to be used in applications that must conform to FIPS 140-2. This means that to be run in FIPS-compliant mode, an SSL VPN gateway must only allow cipher suites that are allowed by FIPS 140-2. Some of the cryptographic requirements, including allowable hash functions and certificate key lengths, will change at the end of 2010.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Guide to SSL VPNs."}]}
{"id": "nist_00507", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Storage Encryption Technologies for End User Devices? (Part 31) Control ES-1: m and permitting access to the encrypted data only after proper authentication is provided. Folder encryption is very similar to file encryption, only it addresses individual folders instead of files. Some OSs offer built-in file and/or folder encryption capabilities, 24 and many third-party programs are also available. Although folder encryption and virtual disk encryption sound similar-both a folder and a container are intended to contain and protect multiple files-there is a difference. A container is a single opaque file, meaning that no one can see what files or folders are inside the container until the container is decrypted. File/folder encryption is transparent, meaning that anyone with access to the filesystem can view the names and possibly other metadata for the encrypted files and folders, including files and folders within encrypted folders, if they are not protected through OS access control features. File/folder encryption is used on all types of storage for end user devices. File/folder encryption can be implemented in many ways, including through drivers, services, and applications. When a user attempts to open an encrypted file (either encrypted by itself or located in an encrypted folder), the software requires the user to first authenticate successfully. Once that has been done, the software will automatically decrypt the chosen file. Because it decrypts a single file at a time, the performance impact of file/folder encryption should be minimal. File/folder encryption is most commonly used on user data files, such as word processing documents and spreadsheets. File/folder encryption solutions can sometimes encrypt swap files, but typically not OS executables and hibernation files.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Guide to Storage Encryption Technologies for End User Devices."}]}
{"id": "nist_00508", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Hardware-Enabled Security_ Container Platform Security Prototype say about 3 Prototyping Stage 0? According to Hardware-Enabled Security_ Container Platform Security Prototype, 3 Prototyping Stage 0: This section describes stage 0 of the prototype implementation (platform attestation and measured worker node launch).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Hardware-Enabled Security_ Container Platform Security Prototype."}]}
{"id": "nist_00509", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1.2.2.1 Client Systems and Mail User Agents (MUAs) according to NIST Domain Name System-Based Electronic Mail Security According to Domain Name System-Based Electronic Mail Security, 1.2.2.1 Client Systems and Mail User Agents (MUAs): Client systems environments demonstrated were Microsoft Office, an open-source Linux-based Thunderbird application, and Thunderbird with a Secure64-provided Apple Key Chain utility. This set includes both commercial products and open-source software. MUA capabilities associated with the client systems are used to invoke S/MIME digital signature and signature verification for email, but userto-user encryption is not demonstrated. Collaborators assisted in installation, integration tailoring as necessary, and testing of laboratory configurations.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_00510", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Disclaimer according to NIST Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products According to Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products, Disclaimer: Any 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products."}]}
{"id": "nist_00511", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0? (Part 19) Control AM-1: | \u2022 CCS CSC 17 \u2022 COBIT 5 APO01.06, DSS06.06 \u2022 ISA 62443-3-3:2013 SR 3.1, SR 3.8, SR 4.1, SR 4.2 \u2022 ISO/IEC 27001:2013 A.8.2.3, A.13.1.1, A.13.2.1, A.13.2.3, A.14.1.2, A.14.1.3 \u2022 NIST SP 800-53 Rev. 4 SC-8 | | | Data Security (PR.DS): Information and records (data) are managed consistent with the organization's risk strategy to protect the confidentiality, integrity, and availability of information. | PR.DS-3: Assets are formally managed throughout removal, transfers, and disposition | \u2022 COBIT 5 BAI09.03 \u2022 ISA 62443-2-1:2009 4. 4.3.3.3.9, 4.3.4.4.1 \u2022 ISA 62443-3-3:2013 SR 4.2 \u2022 ISO/IEC 27001:2013 A.8.2.3, A.8.3.1, A.8.3.2, A.8.3.3, A.11.2.7 \u2022 NIST SP 800-53 Rev. 4 CM-8, MP-6, PE-16 | | | Data Security (PR.DS): Information and records (data) are managed consistent with the organization's risk strategy to protect the confidentiality, integrity, and availability of information.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0."}]}
{"id": "nist_00512", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control UI-64 in Guidelines for the Secure Deployment of IPv6? (Part 315) Control UI-64: uthentication in IKEv2 , P. Eronen, H. Tschofenig, Y. Sheffer, September 2010. RFC 6027, IPsec Cluster Problem Statement , Y. Nir, October 2010. RFC 6052, IPv6 Addressing of IPv4/IPv6 Translators , C. Bao, C. Huitema, M. Bagnulo, M. Boucadair, X. Li, October 2010. RFC 6071, IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap , S. Frankel, S. Krishnan, December 2010. ## IETF Internet Drafts IETF Internet Draft (expired), Distributed NAT for Broadband Deployments Post IPv4 Exhaustion . IETF Internet Draft, DNS64: DNS extensions for Network Address Translation from IPv6 Clients to IPv4 Servers , Work in Progress . IETF Internet Draft , Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion , Work in Progress. IETF Internet Draft, Framework for IPv4/IPv6 Translation , Work in Progress . IETF Internet Draft, Home Agent Reliability Protocol (HARP) , Work in Progress. IETF Internet Draft, IP/ICMP Translation Algorithm , Work in Progress . IETF Internet Draft, IPv6 Router Advertisement Guard , Work in Progress . IETF Internet Draft (expired), Mobile IPv6 Residual Threats. IETF Internet Draft, Mobility Support in IPv6 , Work in Progress. IETF Internet Draft, Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers , Work in Progress . IETF Internet Draft (expired), NAT-PT Security Considerations . IETF Internet Draft, Protocol Support for High Availability of IKEv2/IPsec , Work in Progress. IETF Internet Draft, A Quick Crash Detection Method for IKE , Work in Progress . IETF Internet Draft, Security Concerns with IP Tunneling , Work in Progress IETF Internet Draft, Transport Layer Security-based Mobile IPv6 Security Framework for Mobile Node to Home Agent Communication , Work in Progress . ## Other Sources of IPv6 Information Handbook of IPv4 to IPv6 Transition: Methodologies for Institutional and Corporate Networks , J. Amos and D. Mimili, Auer Bach, 2007. IP Addressing &amp; Subnetting including IPv6 , J.D.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_00513", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) say about 10.4 FCKMS Hardware Failure? (Part 2) According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS), 10.4 FCKMS Hardware Failure: ns should attempt to find an optimum trade-off between redundancy and cost. FR:10.4 The CKMS design shall specify the strategy for backup and recovery from failures of hardware components and devices. | PR:10.15 | CP-9 (+2) | AFederal CKMS shall perform initial and periodic tests of backup and recovery capabilities of its critical FCKMS modules and devices. | |------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | PR:10.16 | | AFederal CKMS shall test the backup and recovery of services requiring high availability at least annually or in accordance with a Service Level Agreement. | | PR:10.17 | | AFederal CKMS shall perform tests of security-critical hardware monthly or in accordance with a Service Level Agreement. | | PR:10.18 | | AFederal CKMS shall repair or replace failed critical hardware and be returned to operational status within 24 hours of a failure or in accordance with a Service Level Agreement. | | PF:10.4 | | AFederal CKMS could repair or replace failed hardware and be returned to operational status within one hour of a failure when high availability is required. | | PF:10.5 | | AFederal CKMS could automatically verify the operational readiness of its backup services. |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_00514", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Electronic Health Records on Mobile Devices say about puppet will install here? (Part 18) According to Securing Electronic Health Records on Mobile Devices, puppet will install here: es 29 Figure 7-3 Certificate Viewer \u2013 General T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 1 . . d. Select the Details tab to view the detailed certificate information. From there you should have an Export button to export the certificate. Figure 7-4 Certificate Viewer \u2013 Details NIST SP 1800-1C: Securing Electronic Health Records on Mobile Devices 30 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 1 . . e. Save the certificate to a file. 4. Import the certificate into the local certificate store in ISE. a. From the ISE Administration Portal, use the navigation path Administration > System > Certificates > Certificate Store to perform the import action. b. Grant ISE Access to the Fiberlink MaaS360 Application Programming Interface (API). 5. Create a Fiberlink MaaS360 administrator account with an API role. a. Log on to the MaaS360 with an Administrator Account. b. Navigate to Setup > Administrators and click Add Administrator. c. Enter the new username and a corporate email address and click Next. d. Enter Roles for the newly created administrator and click Next. e. Verify the setting and press Save. 6. Add MDM server to ISE. a. Use the MaaS360 MDM admin account created above. b. Configure Cisco ISE to integrate with the MaaS360: Administration > MDM > External MDM Server, then click Add. c. Fill out the required information using the account created in Step 5 and the host name or IP address provided by Fiberlink. A sample result is given below: Figure 7-5 Identity Services Engine d. You can use the Test Connection button to test the connection between the Cisco ISE and the cloud MaaS360. A successful message will be displayed if the connection succeeds.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Electronic Health Records on Mobile Devices."}]}
{"id": "nist_00515", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems say about Guideline #2: Use Role-Based Access Control (RBAC)? (Part 2) According to Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems, Guideline #2: Use Role-Based Access Control (RBAC): smart-inverter capabilities that require updates to role definitions. The assignment of people and organizations to roles should be reviewed periodically to ensure they are up to date and appropriate. 3 MFA is authentication using two or more of the following factors: (i) something you know (e.g., password/personal identification number [PIN]), (ii) something you have (e.g., cryptographic identification device, token), or (iii) something you are (e.g., biometric). 4 Reference [4] describes current best practices in a variety of authentication techniques, including MFA and passwords. Additional password best-practice guidance is provided by Cybersecurity and Infrastructure Security Agency (CISA) [5] and the Federal Bureau of Investigation (FBI) [6]. Fig. 4. Guideline #2 life cycle phase <!-- image --> A basic collection of roles for a smart inverter might include: - An Installer role with the access permissions needed to perform initial setup and configuration of the smart inverter. A smart-inverter manufacturer might include this as a default role along with a default user account, as described in Guideline #1 (Sec. 2.1). - A Maintainer role with the access permissions needed to install software updates, perform diagnostics, and make repairs. - A Homeowner role with the access permissions needed to monitor the operation of the smart inverter and respond to alerts.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, mfa. Contains security framework guidance for authentication systems. Source: Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems."}]}
{"id": "nist_00516", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PE-6 in Identity and Access Management for Electric Utilities? (Part 126) Control PE-6: o f Click on Create Rule, and configure as shown in Figure 7-63 and Figure 7-64 for new users. c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . NIST SP 1800-2C: Identity and Access Management for Electric Utilities 103 Figure 7-63 IMG New User T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . NIST SP 1800-2C: Identity and Access Management for Electric Utilities 104 Figure 7-64 IMG New User T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f Click on Create Rule, and configure as shown in Figure 7-65 and Figure 7-66 for user terminations. c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . NIST SP 1800-2C: Identity and Access Management for Electric Utilities 105 Figure 7-65 IMG User Termination T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . NIST SP 1800-2C: Identity and Access Management for Electric Utilities 106 Figure 7-66 IMG User Termination (Continued) Click OK. 7.3.13 Create Provisioning Template The next step is to create a template that IMG uses when provisioning accounts in Adaptive Directory. Click on Requests > Configuration > Account Template > Create Account Template, as shown in Figure 7-67. Figure 7-67 IMG Request Configuration Enter a name, and click OK, as shown in Figure 7-68. T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_00517", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does U.S. Department of Energy Risk Assessment Methodology say about STEP 2 WORKSHEETS? (Part 5) According to U.S. Department of Energy Risk Assessment Methodology, STEP 2 WORKSHEETS: | | | | 2. Ref. No. | (a) Data 1) Unclaasifiad? | Senaitivity or 2) Sensitive Unclassified? (Note Type) | Claaalfication 3) Classified?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: U.S. Department of Energy Risk Assessment Methodology."}]}
{"id": "nist_00518", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 say about ADVERSARY EFFECTS? According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171, ADVERSARY EFFECTS: See [SP 800-160-2]: [ Preclude (Expunge, Preempt); Impede (Contain); Expose (Detect)]. - 3.4.3e Employ automated discovery and management tools to maintain an up-to-date, complete, accurate, and readily available inventory of system components.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_00519", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Web Transactions_ TLS Server Certificate Management provide? (Section 439) . Click Continue. 8. Review the License page. Click Next. 9. On the Resource Provisioning page, verify that the only default value, Local Traffic (LTM), is selected and set to Nominal. Click Next. 10. On the Device Certificates page, leave the default as self-sign device Certificate. Click Next. 11. On the Platform page, fill these values. Then click Next. | Field | Value | Comments | |-------------------------------|---------------------|------------| | Management Port Configuration | 443 | | | IP Address | 192.168.3.85 | | | Network Mask | 255.255.255.0 | | | Management Route | 192.168.3.1 | | | Host Name | f5lb1.ext-nccoe.org | | | Time Zone | EST | | |---------------|-----------------|-------------------------------------------------| | Root Account | <your password> | Refer to NIST SP 800-63B for password guidance. | | Admin Account | <your password> | Refer to NIST SP 800-63B for password guidance. | <!-- image --> 12. System logs off the user with password change. Log back in with the new admin password. 13. In the Standard Network Configuration page, click Next. 14. In the Redundant Device Wizard Options page, Un-Select Display configuration synchronization options. 15. In the Internal Network Configuration page, fill in these values. 16. Click Add , then click Next .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_00520", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders say about 4.3.2 Configuring the OIDC Client Connection? According to Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders, 4.3.2 Configuring the OIDC Client Connection: Registering a client at an OIDC IdP is analogous to creating an SP connection at a SAML IdP. Some coordination is required between the administrators of the two systems. The client ID and client secret must be provided to the RP, and the RP must provide the redirect URI to the IdP. - To add a client, click the OAuth Settings section tab, and then click Create New under Clients . - Create a CLIENT ID and CLIENT SECRET (Figure 4-36). If mutual TLS authentication is being used instead, the RP must provide its certificate, which can be uploaded to the client creation page. Only the Authorization Code grant type is needed for this integration. In the example shown in Figure 4-36, user prompts to authorize the sharing of the user's attributes with the RP have been disabled in favor of streamlining access to applications. Figure 4-36 OIDC Client Configuration <!-- image --> This completes configuration of the OIDC IdP. .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, single sign-on. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_00521", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines on Electronic Mail Security provide? (Section 276) | United States | | VBScript | Visual Basic Script | | VLAN | Virtual Local Area Network | | VPN | Virtual Private Network | | WSH | Windows Scripting Host | | WWW | World Wide Web | Base64 encoding, 2-3 Access control, 5-6, 6-2, 8-2, 9-2 Access control list (ACL), 7-2 Active content, 6-4, 6-10, 8-1 Address Resolution Protocol (ARP), 7-11 Advanced Encryption Standard (AES), 3-2, 3-4 Anti-spyware software, 5-6, 6-5 Anti-virus software, 5-6, 6-4, 6-5 Application proxy, 6-5 Attachment, 6-3, 6-10, 6-12, 8-4 Authentication, 2-9, 5-4, 6-14, 8-2, 8-5 Availability, 4-4 C Certificate authority (CA), 3-5 Certification and accreditation, 4-5 Challenge-Response Authentication Mechanism (CRAM), 2-8 Chief Information Officer (CIO), 4-3 Compromise, 9-6 Confidentiality, 3-1, 4-4, 5-6 Configuration control, 4-5 Content filtering, 3-6, 6-9, 6-11, 7-8 Contingency planning, 4-5 Continuity of operations planning, 4-3, 4-5 Cryptographic hash, 2-7, 3-2 Cryptographic Module Validation Program (CMVP), 3-2 Cryptography Public key, 3-1, 3-3 Symmetric key, 3-3 Defense in depth, 4-8 Demilitarized zone (DMZ), 7-1 Denial of service (DoS), 7-8 Digital signature, 3-1, 3-3 Digital Signature Standard (DSS), 3-2 Directory services, 5-3 Disaster recover planning, 4-5 DNS blacklist (DNSBL), 6-13 Domain name system (DNS), 2-2 Encryption, 2-9, 3-1, 3-6 Encryption key", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, certificate authority. Contains security framework guidance for authentication systems. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_00522", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does CVSS Implementation Guidance say about CVE Description:? According to CVSS Implementation Guidance, CVE Description:: The http\\_request\\_split\\_value function in request.c in lighttpd before 1.4.32 allows remote attackers to cause a denial of service (infinite loop) via a request with a header containing an empty token, as demonstrated using the \"Connection: TE,,Keep-Alive\" header. Analysis: Vector: AV:N/AC:L/Au:N/C:N/I:N/A:P Base Score: 5.0 CWE: CWE-399 - Resource Management Errors | Metric | Value | Explanation | |-------------------|---------|----------------------------------------------------------------------------| | Access Vector | Network | From keyword 'remote attackers' | | Access Complexity | Low | No special conditions exist | | Authentication | None | Not required | | Confidentiality | None | Not impacted | | Integrity | None | Not impacted | | Availability | Partial | From Table 2 Resource Management Template and affects only the application |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: CVSS Implementation Guidance."}]}
{"id": "nist_00523", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Security-Focused Configuration Management of Information Systems say about 2.2.2 IDENTIFYING AND IMPLEMENTING CONFIGURATIONS? According to Guide for Security-Focused Configuration Management of Information Systems, 2.2.2 IDENTIFYING AND IMPLEMENTING CONFIGURATIONS: After the planning and preparation activities are completed, a secure baseline configuration for the system is developed, reviewed, approved, and implemented. The approved baseline configuration for a system and associated components represents the most secure state consistent with operational requirements and constraints. For a typical system, the secure baseline may address configuration settings, software loads, patch levels, how the information system is physically or logically arranged, how various security controls are implemented, and documentation. Where possible, automation is used to enable interoperability of tools and uniformity of baseline configurations across the system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_00524", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is OrgSize according to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs? OrgSize: VL=Very Large, M=Medium,S=Small, VS=Very Small/Micro", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs."}]}
{"id": "nist_00525", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Purpose according to Interfaces for Personal Identity Verification_ Part 3 \u2013 PIV Client Application Programming Interface? Purpose: Returns the PIV Middleware version string Prototype: status_word pivMiddlewareVersion ( OUT version versionString );", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interfaces for Personal Identity Verification_ Part 3 \u2013 PIV Client Application Programming Interface."}]}
{"id": "nist_00526", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST say about 3.4.1 Multimedia Hardware? According to Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST, 3.4.1 Multimedia Hardware: Multimedia, as the term implies, requires a group of hardware integrated under the control of a computer. Although multimedia may pose great demands on computing power, today's PCs are adequate for general multimedia usage. Because of the wide range of equipment available on the market, building a multimedia station takes some planning and careful selection. Some of the factors that should be considered are discussed in the following paragraphs.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST."}]}
{"id": "nist_00527", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Validity according to NIST Test Personal Identity Verification (PIV) Cards Version 2? Validity: Not Before: Mar 6 08:30:00 2013 GMT, Not After: Mar 6 08:30:00 2016 GMT", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_00528", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-3 in Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders? (Part 18) Control AC-3: ASWebAuthenticationSession did not seem to support opening a different application like Passport and then returning to the same ASWebAuthenticationSession instance once the other application closes. This issue was resolved by configuring AppAuth to use Safari instead of ASWebAuthenticationSession. ## 4.4 Single Sign-On with the OAuth Authorization Flow When multiple applications invoke a common user-agent to perform the OAuth authorization flow, the user-agent maintains the session state with the AS and IdP. In the build architecture, this can enable SSO in two scenarios. In the first case, assume that a user has launched a mobile application, been redirected to an IdP to authenticate, and completed the OAuth flow to obtain an access token. Later, the user launches a second application that connects to the same AS used by the first application. The application will initiate an authorization request using the same user-agent as the first application. Provided that the user has not logged out at the AS, this request will be sent with the session cookie that was established when the user authenticated in the previous authorization flow. The AS will recognize the user's active session and issue an access token to the second application without requiring the user to authenticate again. In the second case, again assume that the user has completed an OAuth flow, including authentication to an IdP, while launching the first application. Later, the user launches a second application that connects to an AS that is different from the first application. Again, the second application initiates an authorization request using the same user-agent as the first application. The user has no active session with the second AS, so the user-agent is redirected to the IdP to obtain an authentication assertion.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, token. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_00529", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ID-19 in Securing Telehealth Remote Patient Monitoring Ecosystem? (Part 436) Control ID-19: wing information: 7. Click Save. <!-- image --> - a. Name: HDO-Upstream-Gateway - b. Network (Host): - 192.168.4.1 <!-- image --> ## 8. Click OK. <!-- image --> 9. Click Save. 10. Click Deploy. Verify that the static route has been set correctly. From Devices, when selecting the Routing tab, the Static Route will indicate the network routing settings. The screen displays the static route settings in a table format that includes values for Network, Interface, Gateway, Tunneled, and Metric. The static route applies to the IP addressing that has been specified, where network traffic traverses the interface. Note the Gateway value. The Tunneled and Metric values display the default value. <!-- image --> ## Configure Cisco FTD Network Address Translation (NAT) 1. Click Devices &gt; NAT. 2. Click New Policy &gt; Threat Defense NAT. 3. The New Policy pop-up window appears. Fill out the following information: 4. Click Save. <!-- image --> - a. Name: TRPM NAT - b. Selected Devices: - FTD-TRPM <!-- image --> 5. Click the edit symbol for TRPM NAT. 6. Click Add Rule. <!-- image --> <!-- image --> 7. The Edit NAT Rule pop-up window appears. Under Interface Objects, fill out the following information: - d. Destination Interface Objects: WAN 8. Click Translation. 9. Under Translation, fill out the following information: 10. Click OK. - a. - NAT Rule: Auto NAT Rule - b. - Type: Dynamic - c. Source Interface Objects: Enterprise-Services <!-- image --> - a. Original Source: Enterprise-Services - b. Translated Source: - Destination Interface IP <!-- image --> 11. Create additional rules following the same pattern described above, populating the respective information for each rule. Values for each rule are described below: - a. HIS-Services - b. Remote-Services - i. - NAT Rule: Auto NAT Rule - ii. - Type: Dynamic - iii. Source Interface Objects: - HIS-Services - iv. Destination Interface Objects: WAN - v. - Original Source: HIS-Services - vi.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_00530", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PS-15413 in Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations? (Part 262) Control PS-15413: formation or a system. | | Risk | Likelihood | Enter the likelihood that a specific event or events may occur. Likelihood: Chance of something happening | | Risk | Risk Exposure (Impact x Likelihood) | Enter the risk score by multiplying impact x likelihood. A measure of the extent to which an entity is threatened by a potential circumstance or event and typically a function of: (i) the adverse impacts that would arise if the circumstance or event occurs and (ii) the likelihood of occurrence. | | Risk | Acceptable Level of Risk | Define an acceptable level of risk (risk threshold) per the enterprise's assessment of Tactics, Techniques, and Procedures (TTPs); system criticality; risk appetite and tolerance; and a risk owner's set strategic goals and objectives. Acceptable Risk: A level of residual risk to the enterprise's operations, assets, or individuals that falls within the risk appetite and risk tolerance statements set by the enterprise. | | Potential Mitigating Strategies and C-SCRM Controls | List the potential mitigating risk strategies and any relevant C-SCRM controls.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_00531", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-200901022 in Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171? (Part 93) Control PD-200901022: er capabilities or TTPs. | Reduce likelihood of occurrence and/or reduce likelihood of impact. | \u2022 The adversary's efforts are wasted as the assumptions on which the adversary bases attacks are false. \u2022 The adversary takes actions based on false information, thus revealing that they have obtained that information. Example: The defender strategically places false information (disinformation) about the cybersecurity investments that it plans to make. As a result, the adversary's malware development is wasted by being focused on countering non-existent cybersecurity protections. Example: The defender uses selectively planted false information (disinformation) and honeynets (misdirection) to cause an adversary to focus its malware at virtual sandboxes while at the same time employing obfuscation to hide the actual resources. | | Preclude (includes expunge, preempt, and negate) Ensure that the threat event does not have an impact. | Reduce likelihood of occurrence and/or reduce likelihood of impact. | \u2022 The adversary's efforts or resources cannot be applied or are wasted.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_00532", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-5 in Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control? (Part 134) Control PD-5: ay have automated processes in place to enable SOAR capabilities to reduce response time. Organizations should evaluate and revise these processes as a result of the lessons learned from the incident. | [NIST-SP800-53r5] CP-2, IR-4, IR-8 | ## Recover Function The Recover Function develops and implements the appropriate activities to maintain resilience and restore any capabilities or services that were impaired due to a cybersecurity event. The activities in the Recover Function support timely recovery to normal operations and return the organization back to its proper working state after an incident has occurred. The effectiveness of the Recover Function is dependent upon the implementation of the previous FunctionsIdentify, Protect, Detect, and Respond. The objectives of the Recover Function are as follows: - restore the ground segment's services to a proper working state using a verified recovery procedure so that systems dependent on those services can function properly; - communicate the recovery activities and status of the ground segment services to stakeholders; and - evolve recovery strategies and plans based on lessons learned. The Recover Function within the Cybersecurity Framework defines three Categories, which are summarized in Table 5. Table 5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control."}]}
{"id": "nist_00533", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide provide? (Section 95) ct an access control method (e.g., identity-based, role- based, or other reasonable and appropriate means of access.) \u2022 Decide and document how access to ePHI will be granted for privileged functions. | \u2022 Have appropriate authorization and clearance procedures, as specified in Workforce Security (\u00a7 164.308(a)(3)), been performed prior to granting access? \u2022 Do the organization's systems have the capacity to set access controls? 55 \u2022 Are there documented job descriptions that accurately reflect assigned duties and responsibilities and enforce segregation of duties? 56 \u2022 Has the organization documented procedures that specify how authorized personnel will be granted access to ePHI? \u2022 Does the organization grant remote access to ePHI? | 53 See Sec. 5.2.1, HIPAA Standard: Facility Access Controls , and Sec. 5.3.1, HIPAA Standard: Access Control. 54 Where the healthcare clearinghouse is a separate legal entity, it is subject to the Security Rule whether or not the larger organization is a covered entity. 55 See Sec. 5.3.1, HIPAA Standard: Access Control. 56 See Sec. 5.1.3, HIPAA Standard: Workforce Security.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide."}]}
{"id": "nist_00534", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Engineering Trustworthy Secure Systems provide? (Section 170) ered secure. The [need to be tamperproof] is obvious, since if the reference validation mechanism can be tampered with, its validity is destroyed, as is any hope of achieving security through it. The [third] requirement of always invoking the reference validation mechanism simply states that if the reference validation is (or must be) suspended for some group of programs, then those programs must be considered part of the security apparatus and be [tamper-proof and evaluatable]. The [evaluatable] requirement is equally important. It states that because the reference validation mechanism is the security mechanism in the system, it must be possible to ascertain that it works correctly in all cases and is always invoked. If this cannot be achieved, then there is no way to know that the reference validation correctly takes place in all cases, and therefore there is no basis for certifying a system as secure.' -- James P. Anderson The Anderson Report [37] Situational awareness is a foundational security means objective. That is, to achieve other security objectives, situational awareness is necessary and must be accounted for in design. For example: - Mediating access requires situational awareness in cases where rules for granting access involve timing, sequence, state, and other conditions about the system and prior access. - Preventing and limiting loss are informed by comprehensive data and information about system states and conditions ( Anomaly Detection ). Situational awareness requires the ability to accurately detect, capture, record, and analyze the needed characteristics and details of the system's behaviors and actions at a frequency and with the granularity necessary to act and/or inform external entities for subsequent action to be taken. 74 False positives and false negatives are to be avoided to the extent practicable.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_00535", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard say about 2. Uses of Cryptography? According to Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard, 2. Uses of Cryptography: Cryptography can be used to provide three aspects of data security: - (1) Data secrecy. - (2) Data authentication. j - (3) Originator authentication. The first use of cryptography, data secrecy, is relatively well understood, and will be an important use in an EDP environment. Data authentication and originator authentication are less understood, but will be very important uses of cryptography in the future. To understand data authentication, assume that \"A\" is transmitting data to \"B.\" \"B\" wants assurance that the data it is receiving is precisely the data which \"A\" transmitted. Though conventional error control techniques can protect against communications errors, \"B\" is concerned that someone with a sophisticated \"active wiretapping\" capability may have deliberately modified the data from \"A,\" and made the appropriate modifications in any associated error control fields. Cryptographicallyimplemented data authentication provides assurance that the data was received as originated. Originator authentication is similar to data authentication. This time \"B\" requires assurance that it is receiving data from the \"real 'A'\" and not from an impostor who may have assumed \"A's\" identity. Again, cryptography can provide the solution. There are an almost unlimited number of ways in which cryptography can be applied. Some applications meet only one or two of the above objectives, and some meet them all.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard."}]}
{"id": "nist_00536", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Intrusion Detection and Prevention Systems (IDPS) provide? (Section 35) . Stateful protocol analysis can identify unexpected sequences of commands, such as issuing the same command repeatedly or issuing a command without first issuing a command upon which it is dependent. Another state tracking feature of stateful protocol analysis is that for protocols that perform authentication, the IDPS can keep track of the authenticator used for each session, and record the authenticator used for suspicious activity. This is helpful when investigating an incident. Some IDPSs can also use the authenticator information to define acceptable activity differently for multiple classes of users or specific users. The 'protocol analysis' performed by stateful protocol analysis methods usually includes reasonableness checks for individual commands, such as minimum and maximum lengths for arguments. If a command typically has a username argument, and usernames have a maximum length of 20 characters, then an argument with a length of 1000 characters is suspicious. If the large argument contains binary data, then it is even more suspicious. Stateful protocol analysis methods use protocol models, which are typically based primarily on protocol standards from software vendors and standards bodies (e.g., Internet Engineering Task Force [IETF] Request for Comments [RFC]). The protocol models also typically take into account variances in each protocol's implementation. Many standards are not exhaustively complete in explaining the details of the protocol, which causes variations among implementations. Also, many vendors either violate standards or add proprietary features, some of which may replace features from the standards. For proprietary protocols, complete details about the protocols are often not available, making it difficult for IDPS technologies to perform comprehensive, accurate analysis. As protocols are revised and vendors alter their protocol implementations, IDPS protocol models need to be updated to reflect those changes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Intrusion Detection and Prevention Systems (IDPS)."}]}
{"id": "nist_00537", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2 Reference Platform for Microservices-based Application and Service Mesh according to NIST Attribute-based Access Control for Microservices-based Applications using a Service Mesh According to Attribute-based Access Control for Microservices-based Applications using a Service Mesh, 2 Reference Platform for Microservices-based Application and Service Mesh: The objective of this document is to offer recommendations for the deployment of an authentication and authorization framework for microservices-based applications within a service mesh that provides the infrastructure for various services, including critical security services. A reference platform for hosting microservices-based applications and the service mesh is included to provide clarity and context for concepts and recommendations in real-world application environments. A brief description of these reference platforms is also provided in terms of their overall architecture and salient building blocks.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Attribute-based Access Control for Microservices-based Applications using a Service Mesh."}]}
{"id": "nist_00538", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about Interview? According to Assessing Security Requirements for Controlled Unclassified Information, Interview: [SELECT FROM: personnel with acquisition responsibilities; personnel with information security responsibilities; personnel with SCRM responsibilities]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00539", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Policy Machine_ Features, Architecture, and Specification provide? (Section 25) he access matrix. Each access entry in the ACL contains the pair (Si, Ai,j), which specifies the subjects that can access the object, along with each subject's rights or modes of access to the object. ACLs are widely used in present-day operating systems. Similarly, a capability list is associated with each subject and corresponds to a row of the matrix. Each entry in a capability list is the pair (Ai,j, Oj), which specifies the objects the subject can access, along with its access rights to each object. A capability list can thus be thought of as the inverse of an access control list. Capability lists, when bound with the identity of the subject, have use in distributed systems. Figure 1: Access Matrix <!-- image --> A key difference between the capability list and access control list is the subject's ability to identify objects in the latter. With an access control list, a subject can identify any object in the system and attempt access; the access control mechanism can then mediate the access attempt using the object's access list to verify whether the subject is authorized the request mode of access. In a capability system, a subject can identify only those objects for which it holds a capability. Possessing a capability for the object is a requisite for the subject to attempt access to an object, which is then mediated by the reference mediation function. Both the contents of access control and capability lists, as well as the access control mechanism itself, must be protected from compromise to prevent unauthorized subjects from gaining access to an object. Discretionary models form a broad class of access control models. Discretionary in this context means that subjects, which represent users as opposed to administrators, are allowed some freedom to manipulate the authorizations of other subjects to access objects [Hu06].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization, sso. Contains security framework guidance for authentication systems. Source: Policy Machine_ Features, Architecture, and Specification."}]}
{"id": "nist_00540", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Public Safety Mobile Application Security Requirements Workshop Summary say about Table of Contents? (Part 5) According to Public Safety Mobile Application Security Requirements Workshop Summary, Table of Contents: | APCOKEY ATTRIBUTE REFINEMENT AND ADDITIONS ..............................................................................7 | | 4. | MOBILE APPLICATION VETTING...................................................................................................8 | | 4.1 | EXISTING KEY ATTRIBUTES ...................................................................................................................8 | | 4.2 | BREAKOUT SESSION DISCUSSION SUMMARY ..........................................................................................8 | | 4.3 | NEXT STEPS ......................................................................................................................................9 | | 5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Public Safety Mobile Application Security Requirements Workshop Summary."}]}
{"id": "nist_00541", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SA-09(06) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control SA-09(06): exclusive control of cryptographic keys is maintained for encrypted material stored or transmi\ue003ed through an external system. POTENTIAL ASSESSMENT METHODS AND OBJECTS:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00542", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for the Use of PIV Credentials in Facility Access say about 3.4 Skimming? According to Guidelines for the Use of PIV Credentials in Facility Access, 3.4 Skimming: A contactless PIV Card reader with a sensitive antenna can be concealed in a briefcase, and is capable of reading [ISO/IEC 14443] contactless smart cards like the PIV Card at a distance of at least 25 cm, as demonstrated in [SKIMMER]. The range of a skimmer is limited primarily by the requirement for the skimmer to supply power to the PIV Card by inductive coupling. A concealed skimmer could immediately obtain the free-read data from the PIV Card through the contactless interface. [FIPS201] introduced the concept of an optional virtual contact interface (VCI), which allows all data on the PIV Card that is not protected by a PIN to be read once this interface is established. [SP 800-73], Interfaces for Personal Identity Verification , specifies an optional pairing code that can be used to authenticate the card reader to a PIV Card before the card establishes a VCI session. If agencies deploy PIV Cards that support establishing a VCI without requiring the submission of a pairing code, all data on these cards that is not protected by a PIN is vulnerable to skimming. The PIV Card mitigates the risk of skimming by implementing access rules that prevent the release of biometric and other data over the contactless interface when a VCI has not been established, by requiring the use of a pairing code in order to establish a VCI. The risk of skimming can also be mitigated by employing shielding techniques that positively deactivate the PIV Card when not in use. The electromagnetically opaque holder mentioned in Section 2.11 of [FIPS201] is one such technique.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Use of PIV Credentials in Facility Access."}]}
{"id": "nist_00543", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN) provide? (Section 111) .SP.800-150 | | [NIST-SP 800-154] | Scarfone K, Souppaya M(2016) Guide to Data-Centric System Threat Modeling. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-154, df | | [NIST-SP-800-160v1r1] | McEvilley M, Oren J, Ross R (2018) Systems Security Engineering: Considerations for a Multidisciplinary Approach in the Engineering of Trustworthy Secure Systems. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800- 160 Ver. 1 Rev. 1, https://doi.org/10.6028/NIST.SP.800-160v1r1 | | [NIST-SP-800-161] | Bartol N, Boyens J, Fallon M, Holbrook A, Smith A, Winkler K (2022) Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations. (National Institute of Standards and | Technology, Gaithersburg, MD), NIST Special Publication (SP) 800161 Rev. 1, | [NIST-SP-800-175Br1] | Barker E (2020) Guideline for Using Cryptographic Standards in the Federal Government: Cryptographic Mechanisms.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)."}]}
{"id": "nist_00544", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2003 Annual Report say about IT SECURITY CHECKLISTS FOR COMMERCIAL IT PRODUCTS? (Part 2) According to Computer Security Division 2003 Annual Report, IT SECURITY CHECKLISTS FOR COMMERCIAL IT PRODUCTS: Federal Government, consortia, and commercial IT product vendors currently developing, or planning to develop, security configuration checklists for IT products were encouraged to attend. Workshop topics addressed included: government and commercial requirements, the NIST checklist template framework, the NIST checklist development process, defining checklist target environments, a vendor session to discuss business case advantages/disadvantages for checklist development, methods and incentives to gain commercial vendor support, ideas and proven methods for producing high quality checklists, and deploying and verifying checklists. One of the next steps for this project is to produce a step-by-step document that would assist regular users and novice system administrators in utilizing the various checklists and guidance for commonly used IT products. We are also undertaking the development of a Windows XP Professional System draft document and accompanying template, similar to the Windows 2000 Professional guidance previously developed by the CSD. We will continue to solicit checklists from vendors, government agencies, academia, and consortia. Contacts: Mr. John Wack (301) 975-3411 john.wack@nist.gov Mr. Murugiah Souppaya (301) 975-4758 murugiah.souppaya@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2003 Annual Report."}]}
{"id": "nist_00545", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Family: Incident Response according to NIST Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer, Family: Incident Response: Description: Establishing an incident handling capability for systems that includes adequate preparation, detection, analysis, containment, recovery, and user response activities; and tracking, documenting, and reporting incidents to appropriate organizational officials and/or authorities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer."}]}
{"id": "nist_00546", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity say about Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity? According to Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity, Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity: Prepared by the International Cybersecurity Standardization Working Group of the National Security Council's Cyber Interagency Policy Committee This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.IR.8074v1 <!-- image --> This page left intentionally blank", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity."}]}
{"id": "nist_00547", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches say about 2.9.1 Configure Fireye Helix to Collect Logs from Symantec SWG? According to Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches, 2.9.1 Configure Fireye Helix to Collect Logs from Symantec SWG: 1. Navigate to the Symantec dashboard, and login. 2. Navigate to Account Configuration by clicking the gear icon on the left sidebar. 3. Click API Credentials . 4. Click Add . 5. Check the boxes next to Reporting Access Logs , Location Management , Audit Logs , Agent Config Management , and Egress IP . 6. Set an Expiration Date for the credential (1 year recommended). 7. Copy the Username and Password provided, as you will not be able to retrieve these once you create the credential. <!-- image --> <!-- image --> 8. Click Save . 9. On the Helix Dashboard, click Configure &gt; Cloud Connect . <!-- image --> <!-- image --> 10. Click Add Cloud Connection. 11. Click the arrow next to Symantec Web Security Service. 12. Click Install . <!-- image --> <!-- image --> 13. Enter the username and password from the credential created earlier. 14. Click Submit and Verify. 15. Click Back to Home . You will now be able to see events from Symantec SWG in Helix. <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches."}]}
{"id": "nist_00548", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE) say about 3.6.1.4 Mobile Application Vetting Service? (Part 1) According to Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE), 3.6.1.4 Mobile Application Vetting Service: 3.6.1.4 Mobile Application Vetting Service Mobile application vetting services use a variety of static, dynamic, and behavioral techniques to determine if an application demonstrates any behaviors that pose a security or privacy risk. The risk may be to a device owner or user, to parties that own data on the device, or to external systems to which the application connects. The set of detected behaviors is often aggregated to generate a singular score that estimates the level of risk (or conversely, trustworthiness) attributed to an application. Clients can often adjust the values associated with given behaviors (e.g., hard-coded cryptographic keys) to tailor the score for their unique risk posture. Those scores may be further aggregated to present a score that represents the overall risk or trustworthiness posed by the set of applications currently installed on a given device. Mobile applications, malicious or benign, have high potential to negatively impact both security and user privacy. A malicious application can contain code intended to exploit vulnerabilities present in potentially any targeted hardware, firmware, or software on the device. Alternatively, or in conjunction with exploit code, a malicious application may misuse any device, personal, or behavioral data to which it has been explicitly or implicitly granted access, such as contacts, clipboard data, or location services. Benign applications may still present vulnerabilities or weaknesses that malicious applications can exploit to gain unauthorized access to its data or functionality. Further, benign applications may place user privacy at risk by collecting more information than is necessary for the application to deliver functionality desired by the user.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_00549", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Data Field returned in the Response Message according to NIST Government Smart Card Interoperability Specification, Version 2.1 According to Government Smart Card Interoperability Specification, Version 2.1, Data Field returned in the Response Message: If the APDU result indicates success, Le number of bytes will be available to read from the smart card, i.e., the 8-byte challenge.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_00550", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Smart Card Technology_ New Methods for Computer Access Control say about 7.3 Expected Changes in the Appearance and Construction of the Smart Card? (Part 2) According to Smart Card Technology_ New Methods for Computer Access Control, 7.3 Expected Changes in the Appearance and Construction of the Smart Card: key pads and LCD displays which are flat and flush with the the card's surface. Future smart cards will probably have on-card power supplies, provided by solar cells, rechargeable batteries, or both. The thicker cards may be equipped with specialized interfaces which allow communication with peripheral IC memory cards, enhanced reader/writer devices, microprinters, personal computers, or other equipment. Figures 13 and 14 summarize some of the features of current smart cards and suggest several possibilities for smart cards of the future.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Smart Card Technology_ New Methods for Computer Access Control."}]}
{"id": "nist_00551", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Blockchain Networks_ Token Design and Management Overview say about 7 Conclusion? (Part 2) According to Blockchain Networks_ Token Design and Management Overview, 7 Conclusion: tainably deliver the necessary team or public efforts across organizational boundaries and to clearly articulate the vision and mission statements, trust assumptions, and supporting governance models. Data and process standardization is needed to provide clarity for building more interoperable protocols, developing supporting regulatory infrastructures for token ownership, and implementing software that handles complex and overwhelming tasks for users. The literature that has emerged on these challenges is rich, and efforts are being made to address them at an increasing pace. By relying on peer-to-peer networks and open standards instead of domain-specific and heterogeneous ecosystems, blockchain-enabled digital assets could bolster the accessibility and interoperability of financial, identity, authentication, and supply chain services. They have the potential to be integrated into third-party applications while maintaining data integrity and user control directly within their devices. This can facilitate online data exchange and transform business-making in partial- or zero-trust environments. Enabling more user-centric data security and privacy models can benefit both users and businesses. With many blockchain projects being explored or developed, organizations should consider what specific needs issuing tokenized representations of existing assets or creating new ones could help meet, who the parties involved are, which desirable features and processes the tokens should implement internally, and how they should be distributed and managed. In some cases, this pushes organizations to rethink their structures and approaches for identifying and managing risks. This includes finding alignments between individual and collective incentives and organizational design principles that allow for new efficiencies and joint opportunities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Blockchain Networks_ Token Design and Management Overview."}]}
{"id": "nist_00552", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations say about (f) Cryptographic Key, Message Interchange, and/or Certificate Formats -? According to Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations, (f) Cryptographic Key, Message Interchange, and/or Certificate Formats -: This section is used to state policies specifying conformance to specific standards and/or guidelines regarding 1) key management architectures and/or protocols, 2) key management message formats, 3) certificate formats and/or 4) RKN formats. 98 The Central Oversight Authority, Key Processing facilities, Service Agents, Client Nodes, and Tokens.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, token. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations."}]}
{"id": "nist_00553", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain C. Design Specifications for Vote-Tallying Programs according to NIST Effective Use of Computing Technology in Vote-Tallying According to Effective Use of Computing Technology in Vote-Tallying, C. Design Specifications for Vote-Tallying Programs: The most important quality that a vote-tallying applications program must possess is that it must operate correctly. At first glance, this may appear to be simply stating the obvious, but upon further reflection, it should be understood that it is not exactly a simple matter to state what is meant by correct, and it is extremely difficult to prove that a program does indeed possess this quality. (See example of Redford Township, Chapter IV.) Correctness implies, of course, that correctly marked ballots, in which only valid locations are marked and in which no overvotes are marked, are summed correctly; but it also implies that the program does exactly what the election administration intends it to do with ballots that are not so \"well-behaved.\" The program must ignore marks or holes on ballots in locations which have not been assigned to any offices or issues without affecting marks or holes in assigned locations (if that is what the administration intends) and it must throw out overvotes for offices or issues in which they occur without affecting the program's performance on correctly-voted offices or issues of the same ballot.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Effective Use of Computing Technology in Vote-Tallying."}]}
{"id": "nist_00554", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Bluetooth Security provide? (Section 94) | | 37 | Designate an individual to track the progress of Bluetooth security products and standards (perhaps via the Bluetooth SIG) and the threats and vulnerabilities with the technology. | An individual designated to track the latest technology enhancements, standards (perhaps via Bluetooth SIG), and risks will help to ensure the continued secure use of Bluetooth. | | \uf050 | | The list of controls in Table 4-3 is not intended to be fully comprehensive or authoritative. Rather, it lists those controls that are most directly supported by the Table 4-2 recommendations. 37 https://doi.org/10.6028/NIST.SP.800-53r4 Table 4-3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Bluetooth Security."}]}
{"id": "nist_00555", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Section 91) use system capabilities to maximize the ability of an organization to detect successful system compromises by an adversary and to limit the effects of such compromises (both detected and undetected). | | defense-in-depth | Information security strategy integrating people, technology, and operations capabilities to establish variable barriers across multiple layers and missions of the organization. | | designing for cyber resiliency and survivability | Designing systems, missions, and business functions to provide the capability to prepare for, withstand, recover from, and adapt to compromises of cyber resources in order to maximize mission or business operations. | | discussion | Statements used to provide additional explanatory information for security controls or security control enhancements. | | disinformation | The process of providing deliberately deceptive information to adversaries to mislead or confuse them regarding the security posture of the system or organization or the state of cyber preparedness. | | dual authorization [CNSSI 4009, Adapted] | The system of storage and handling designed to prohibit individual access to certain resources by requiring the presence and actions of at least two authorized persons, each capable of detecting incorrect or unauthorized security procedures with respect to the task being performed. | | enhanced security requirements | Security requirements that are to be implemented in addition to the basic and derived security requirements in NIST Special Publication 800-171. The additional security requirements provide the foundation for a defense-in-depth protection strategy that includes three mutually supportive and reinforcing components: (1) penetration-resistant architecture, (2) damage- limiting operations, and (3) designing for cyber resiliency and survivability .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_00556", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 98) rol not satisfied). However, the failure of a single control or, in some cases, the failure of multiple controls may not affect the overall security and privacy capability required by an organization. This is not to say that such controls do not contribute to the security or privacy of the system and/or organization (as defined by the security requirements and privacy requirements during the initiation phase of the system development life cycle) but rather that such controls may not support the particular security or privacy capability. Furthermore, every implemented security and privacy control may not necessarily support or need to support an organization-defined capability. When organizations employ the concept of capabilities, automated and manual assessments account for all security and privacy controls that comprise the security and privacy capabilities. Assessors are aware of how the controls work together to provide such capabilities. In this way, 48 A security capability or privacy capability is a combination of mutually reinforcing security controls or privacy controls (i.e., safeguards and countermeasures) implemented by technical means (i.e., functionality in hardware, software, and firmware), physical means (i.e., physical devices and protective measures), and procedural means (i.e., procedures performed by individuals). CHAPTER THREE PAGE 34 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 A r 5 I . NIST SP 800-53A REV. 5 ASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ when assessments identify a failure in a capability, a root cause analysis can be conducted to determine the specific control or controls that are responsible for the failure based on the established relationships among controls.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00557", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Computer Security Log Management provide? (Section 46) ontinuous supply of log data. Log generation and storage is complicated mainly by a high number of log sources, inconsistent log formats among sources, and a large volume of log data on a daily basis. Log management also involves protecting logs from breaches of their confidentiality and integrity, as well as supporting their availability. Another problem with log management is having network and system administrators perform regular, efficient, and effective analysis of log data. Key practices recommended to meet the main challenges in log management are as follows: - GLYPH&lt;c=31,font=/APONEK+Webdings&gt; Prioritize log management appropriately throughout the organization - GLYPH&lt;c=31,font=/APONEK+Webdings&gt; Establish policies and procedures for log management - GLYPH&lt;c=31,font=/APONEK+Webdings&gt; Create and maintain a secure log management infrastructure - GLYPH&lt;c=31,font=/APONEK+Webdings&gt; Provide proper training for all staff with log management responsibilities. A log management infrastructure consists of the hardware, software, networks, and media used to generate, transmit, store, analyze, and dispose of log data. 20 Most organizations have one or more log management infrastructures. 21 This section describes the typical architecture of a log management infrastructure and how its components interact with each other. It then describes the basic functions performed within a log management infrastructure. Next, it examines the two major categories of log management software: syslog-based centralized logging software and security information and event management software. The section also describes additional types of software that may be useful within a log management infrastructure. A log management infrastructure typically comprises the following three tiers: - GLYPH&lt;c=31,font=/APONEK+Webdings&gt; Log Generation. The first tier contains the hosts that generate the log data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Computer Security Log Management."}]}
{"id": "nist_00558", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-3 in Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders? (Part 174) Control AC-3: n. For SAML, projects like SimpleSAMLphp (https://simplesamlphp.org/) provide an implementation that is easy to deploy. It is also possible to perform this testing without installing additional tools. One method for SAML is to use Chrome Remote Debugging for Android devices: https://developers.google.com/web/tools/chrome-devtools/remote-debugging/. By logging the authentication flow in the Network pane of Chrome's developer tools, the SAML response can be extracted and viewed. The authentication flow with the SAML IdP configured in this practice guide consists of a series of calls to the SSO.ping URL at the IdP. Because the SAML POST binding is used, the final SSO.ping response includes an HTML form that submits the SAML response back to the AS.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, single sign-on, sso. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_00559", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is This publication is available free of charge from according to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile? This publication is available free of charge from: ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: csf, fips, security control. General security reference material without sensitive content. Source: Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile."}]}
{"id": "nist_00560", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Measurement Guide for Information Security_ Volume 1 \u2014 Identifying and Selecting Measures say about 4.3.2. Weighing Scale? According to Measurement Guide for Information Security_ Volume 1 \u2014 Identifying and Selecting Measures, 4.3.2. Weighing Scale: Information gained from modeling likelihood and impact can be combined with knowledge about organizational goals and existing controls to create a customized weighing scale to prioritize potential measures. Using a weighing scale with set parameters ensures consistency when prioritizing and selecting measures, even those that are unrelated to information security. Measures that are ultimately selected are useful for: - Identifying causes of unsatisfactory performance - Pinpointing areas for improvement - Facilitating consistent policy implementation - Redefining goals and objectives - Modifying security policies", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Measurement Guide for Information Security_ Volume 1 \u2014 Identifying and Selecting Measures."}]}
{"id": "nist_00561", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992 provide? (Section 95) development. The DES technology is exportable if it used only for authentication purposes and not for general data encryption; on the other hand, keys have to be stored in the clear at the end hosts. - -Public key encryption for C/R avoids the problem of storage of clear text keys at hosts. It was also felt that public key systems will scale better and over time may be preferred in many (but not all) contexts. Steve Kent recommended that, as part of the follow-on activities, we plan to track the work by the Internet Engineering Task Force as it provides an ability to interoperate between symmetric and public key systems. The PEM technology will be available soon. The use of PEM is recommended, initially with its current suite of algorithms. Later, the use of the proposed NIST suite of algorithms should be explored, including a rationalization of the problems (hash, signature, confidentiality algorithms) of interoperability and management of multiple algorithm suites (i.e. it has to work everywhere). PEM should be immediately employed by FIRST individuals and CERT for internal communication and for distribution of such things as security alerts and fixes. The concept of a security perimeter incorporates the ideas of router and gateway filtering - access control by protocol and by source/destination. There was some concern expressed about the utility of this mechanism since addresses can be forged, the functionality may be unduly limited, and the management of port access on a fine-grained basis may be difficult. While acknowledging limitations, there was substantial support for including security perimeters in the list of recommendations. The use of filters at this level helps to reduce the size of the problem.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992."}]}
{"id": "nist_00562", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain View all NIST CSF 2.0 Resources Here according to NIST NIST Cybersecurity Framework 2.0_ Small Business Quick-Start Guide According to NIST Cybersecurity Framework 2.0_ Small Business Quick-Start Guide, View all NIST CSF 2.0 Resources Here: <!-- image --> | Contact | Phone | |--------------------|---------| | Business Leader: | | | Technical Contact: | | | State Police: | | | Legal: | | | Bank: | | | Insurance: | |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, csf, fips. General security reference material without sensitive content. Source: NIST Cybersecurity Framework 2.0_ Small Business Quick-Start Guide."}]}
{"id": "nist_00563", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Protecting the Confidentiality of Personally Identifiable Information (PII) say about 6. What is a Privacy Impact Assessment (PIA)? When do I need to conduct a PIA?? (Part 2) According to Guide to Protecting the Confidentiality of Personally Identifiable Information (PII), 6. What is a Privacy Impact Assessment (PIA)? When do I need to conduct a PIA?: The Memorandum provided examples of system changes that create new privacy risks and trigger the requirement for a new PIA: - \uf03c Conversions -when paper-based records are to be converted to electronic systems - \uf03c De-Identified to Identifiable -when functions applied to an existing information collection change de-identified information into information in identifiable form - \uf03c Significant System Management Changes -when new uses of an existing information system, including application of new technologies, significantly change how information in identifiable form is managed in the system - \uf03c Significant Merging -when agencies adopt or alter business processes so that government databases holding information in identifiable form are merged, centralized, matched with other databases, or otherwise significantly manipulated - \uf03c New Public Access -when user-authenticating technology (e.g., password, digital certificate, biometric) is newly applied to an information system accessed by members of the public - \uf03c Commercial Sources -when agencies systematically incorporate into existing information systems databases of information in identifiable form purchased or obtained from commercial or public sources - \uf03c New Interagency Uses -when agencies work together on shared functions involving significant new uses or exchanges of information in identifiable form, such as the cross-cutting EGovernment initiatives - \uf03c Internal", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)."}]}
{"id": "nist_00564", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Situational Awareness for Electric Utilities? (Part 198) Control AM-1: ecial Operations, then click Push SAC Database. The Scheduling Push SAC Database dialogue box will appear. 1. Description Box 2. OK Button 3. Cancel Button 4. Repetition Lists 5. Start Time Options 6. Start Time Box Figure 2-64 Scheduling Push SAC Database <!-- image --> - Optional: Under Description, type a description for the operation. Include details such as the affected target, the purpose of the operation, etc. This description will appear in the list of scheduled operations. - Under Repetition, select the interval and value (if applicable). - Under Start Time (On Server), select Now or Specific Time. - Click OK to save changes. The operation will commence at the selected time. ## 2.14.2.15 Managing Devices and Gateways - Access the RUGGEDCOM CROSSBOW client workstation, launch CROSSBOW Client, and log in as a user with the necessary administrative privileges. - On the Field Layout tab, right-click the desired facility or gateway, and click Add Device, Add Gateway, or Add Subordinate Gateway (gateways only). The Device Properties or Gateway Properties dialogue box will appear. - Configure the identification properties (e.g., name, description) for the device/gateway. - Configure the connection properties (e.g., host name, user names, passwords) for the device/gateway. - Configure the interfaces available for the device/gateway. - Enable or disable the applications available for the device/gateway. - Configure the NERC CIP properties for the device/gateway. - Configure any advanced parameters associated with the device/gateway. - Click OK to save changes. ## 2.14.2.16 Connecting to a Device/Gateway - Access the RUGGEDCOM CROSSBOW client workstation, launch CROSSBOW Client, and log in as a user with the necessary administrative privileges. - If connecting to the device/gateway via a Station Access Controller, make sure to enter the host name and port number for the SAC during the login process.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Situational Awareness for Electric Utilities."}]}
{"id": "nist_00565", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2. Describe Contingency Operations according to NIST Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems According to Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems, 2. Describe Contingency Operations: (Briefly describe how operations were returned to normal conditions. Include approximate time to recover.) Name of Reporter: i \" Ctrl'-'. ' '?0i .*) %'a'/J K***&lt;ii\"''M ti'f ' d \":", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems."}]}
{"id": "nist_00566", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Keywords according to NIST Representation of PIV Chain-of-Trust for Import and Export According to Representation of PIV Chain-of-Trust for Import and Export, Keywords: enrollment record; Federal Information Processing Standards (FIPS) 201; HSPD-12; identification; identity infrastructure; Personal Identity Verification (PIV); PIV Architecture; PIV Card; PIV chain-of-trust; XML information sharing", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Representation of PIV Chain-of-Trust for Import and Export."}]}
{"id": "nist_00567", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings say about 3.3 The Challenges to the RP? (Part 2) According to 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings, 3.3 The Challenges to the RP: ntactic parsing and checking of validity period are usually straightforward operations. All other steps in the certificate processing more or less have problems related to scaling, i.e. handling of certificates from a high number of CAs. Management of information about CAs and their services (trustworthiness, quality of certificates, liability, possibility of enforcing liability, and trusted copy of public key) gets increasingly difficult with the number of CAs. The liability situation can in general only be safely assessed through agreements, but it would be difficult for an RP to have explicit agreements with all relevant CAs. A consortium of RPs, e.g. in an industry sector, may be able to find approaches to diminish the problem. The X.509v3 standard [16] defines syntax of certificates, but leaves many options, and only partly defines semantics of fields, attributes and extensions. Even though recommended profiles for X.509 certificates exist, certificates from different CAs often differ in content. This particularly applies to naming of subjects. An RP must either be able to use (parts of) names in a certificate directly for identification, or a name in a certificate must be reliably translated to a derived name that is useful to the RP. The security/quality of the translation process must preserve the quality of the certificate, i.e. the confidence in the derived name must be as if the derived name had been included in the certificate.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings."}]}
{"id": "nist_00568", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control UI-64 in Guidelines for the Secure Deployment of IPv6? (Part 65) Control UI-64: ns can obtain IPv6 addresses allocations globally through several regional registry services. ## 3.2.1 IPv6 Address Assignments IPv6 network prefix assignment is the first step in network deployment. Understanding several methods such as leftmost, rightmost, and centermost helps provide for flexibility and efficient aggregation of an assigned IPv6 block, as described in RFC 3531, A Flexible Method for Managing the Assignment of Bits of an IPv6 Address Block . If done without foresight, boundaries between sub-allocations become difficult to move, and future increases in the use of address space cannot be kept contiguous. The easiest but least flexible solution is to make block address assignment in order from the beginning of the organization's allocated IPv6 block. For example, if an organization is assigned the prefix 2001:0db8:9095::/48, prefixes can be distributed in simple sequential order: 2001:0db8:9095:0001::/64 2001:0db8:9095:0002::/64 2001:0db8:9095:0003::/64 This is the simplest way to distribute address assignments, but it lacks consideration for future needs and does not take into account grouping networks by site for clean routing aggregation. Additionally, this method makes it impossible to make an existing network assignment larger and keep its address space contiguous. RFC 3531 proposes a method to manage the assignment of bits of an IPv6 address block or range. First, the scheme defines parts of the IP address as p1, p2, p3, \u2026.pN in order, so that an IP address is composed of these parts contiguously. Boundaries between each part are based on the prefix assigned by the next level authority. Part (p1) is the leftmost part probably assigned to a registry, Part (p2) can be allocated to a large ISP or national registry. Part (p3) can be allocated to a large customer or a smaller provider, etc. Each part can be of different length. <!-- image --> | p1 | p2 | p3 | p4 | \u2026.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_00569", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Recommended Confidentiality Impact Level according to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices? Recommended Confidentiality Impact Level: The provisional confidentiality impact level recommended for most postal services information is low .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_00570", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Information Security Handbook_ A Guide for Managers say about 2.2.1 Information Security Strategic Planning? (Part 1) According to Information Security Handbook_ A Guide for Managers, 2.2.1 Information Security Strategic Planning: 2.2.1 Information Security Strategic Planning 'Strategic plans, annual performance plans, and annual program performance reports are the main elements of GPRA. Together these elements create a recurring cycle of reporting, planning, and execution.' 5 GPRA requires federal agencies to develop and submit to OMB and Congress a 'strategic plan for program activities' and 'prepare an annual performance plan covering each program activity set forth in the budget of such agency.' 6 Agencies are required to refresh their strategic plans within three years of submitting th previous strategic plans, while submitting performance plans is required annually. eir Agencies should integrate information security into the agency strategic planning processes by establishing and documenting information security strategies that directly support agency strategic and performance planning activities. The organization's information security strategy should establish a comprehensive framework to enable the development, institutionalization, assessment, and improvement of the agency's information security program. The information security strategy should support the overall agency strategic and performance plans and IT strategic plan (if applicable) with its content clearly traceable to these higher-level sources. Each agency should define the following for its information security program: 5 OMB, 'Office of Management and Budget Circular A-130 Appendix III,' 1996. 6 OMB, Section 306, 'Government Performance and Results Act' (GPRA), 1993.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_00571", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings say about Foreward? (Part 2) According to 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings, Foreward: t level may be one reason that DNSSEC deployment has been slow. A panel on Domain Keys Identified Mail (DKIM), which leverages the DNS for key distribution, was held on the second day of the workshop. DKIM would seem to provide the incentive for attacking the DNS, so perhaps DNSSEC deployment will become a more urgent requirement. Phillip Hallam-Baker's presentation on the DKIM panel, 'Achieving Email Security Luxury' proposed leveraging DKIM, XKMS, and the PKIX logotype extension to create a comprehensive and compelling solution for securing applications and the infrastructure. Another theme of the workshop was the convergence of PKI and other technologies. Jeffrey Altman's presentation highlighted progress in the convergence of PKI and Kerberos. A decade's efforts have produced PK-INIT, PK-CROSS, and PK-APP, forming a comprehensive suite of standards. PK-INIT and PK-APP allow users to leverage PKI certificates to obtain Kerberos credentials, and vice versa. PK-CROSS supports the establishment of Kerberos cross realm relationships with PKI credentials. The 'Identity Federation and Attribute-based Authorization through the Globus Toolkit, Shibboleth, GridShib, and MyProxy' presentation described the integration of the Grid PKIs, Security Assertion Markup Language (SAML), Kerberos, and one time passwords to support authorization decisions for Grid computing. Identifying and resolving revocation issues continues to be a topic of critical interest. This year's workshop featured two presentations at very different levels of abstraction. Kelvin Yiu's invited talk focused on challenges that had to be faced and compromises required to make revocation usable for consumers in the forthcoming Vista operating system. Santosh Chokhani explored some of the more arcane nuances of the X.509 standard, and their implications for real PKI deployments.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, pki. Contains security framework guidance for authentication systems. Source: 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings."}]}
{"id": "nist_00572", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessment of Access Control Systems say about 3.2 Protection Bits and Limitations? (Part 1) According to Assessment of Access Control Systems, 3.2 Protection Bits and Limitations: 3.2 Protection Bits and Limitations A protection bits (or owner/group/other) mechanism [FKC03] is commonly included in UNIX and UNIX-like operating systems. This mechanism is a simple and very common DAC control scheme that uses only a few bits of access control information attached to each file. These bits specify the defined permissions of read, write, and execute for different classes of users: 1. Owner: the file owner 2. Group: users belonging to the owner's group or project specified as the 'owning group' 3. Others: the rest of the world The access control system regulates access to a file by associating read (r), write (w), or execute (x) operations with each of these categories of users (Table 2). Table 2 - Permission Bits | Owner | Owner | Owner | Group | Group | Group | Other | Other | Other | |---------|---------|---------|---------|---------|---------|---------|---------|---------| | R | W | X | R | W | X | R | W | X | By default, the owner of the file is the one who created the file. The owner of the file is typically the only one besides the system administrator ('superuser' or 'root') who can modify the protection bits. Also note that there is only one group that is available for each file. The system administrator controls group memberships, so that as membership within these groups changes, so will the capabilities of users to access files. For example, File \\_a has the following protection bits: File\\_a: (rwx) (r-x) (--x) The protection bits indicate that the owner has read, write, and execute permission to file File\\_a ; the members of the group that is associated with the owner have read and execute permission to the file; and all other system users have execute permission to the file. The '-' marking indicates that the corresponding operation is denied on File\\_a .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Assessment of Access Control Systems."}]}
{"id": "nist_00573", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Use of ISO_IEC 24727 provide? (Section 21) upport multiple languages. ISO/IEC 24727-4 establishes the details for different stack configurations and features that enable clientapplications to interface with card-applications in different ways. Stack configuration choices range from performing all necessary services directly on a smart card to achieving the same functionality in a distributed network environment. The stacks defined are: + Full network stack - a configuration where the various ISO/IEC 24727 interfaces are implemented in a networked environment on different platforms. + Loyal stack - a configuration where ISO/IEC 24727-2 and ISO/IEC 24727-3 are implemented on the same platform. + Remote loyal stack - a configuration where a loyal stack is used on a platform that is remote from the client-application. + Opaque Integrated Circuit Card (ICC) stack - a configuration where the card-application implements and interprets the Generic Card Interface commands. + ICC resident stack - a configuration where the card-application accepts the SALII actions instead of ISO/IEC 7816 commands. + Remote ICC stack - a configuration where physical connection of the ICC is made to a different platform from the rest of the stack. While all of the above configurations are possible, this document will focus on only two: the Loyal stack and ICC resident stack. Figure 4 provides an illustration of how the two configurations are implemented to achieve the same results. Figure 4 - Comparison of Loyal and ICC Resident Stack <!-- image --> ISO/IEC 24727-5 defines test procedures that can be used to validate conformance assertions. The test procedures focus on testing the behaviors of interfaces for each component of the ISO/IEC 24727 architecture to ensure interoperable services, integrity reporting, and connectivity.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Use of ISO_IEC 24727."}]}
{"id": "nist_00574", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Personal Identity Verification Card Management Report? (Part 13) Control PD-12: could encode other values within that field. For example, the SP 800-73 data object tags could be represented in the Path even though 7816-15 does not specifically address naming data by tags or OIDs. An example 7816-15 EF.CD PIV certificate in ASN.1 syntax is show below: ``` 30 66 [ 30 33 Label: 'PIV Authentication Certificate' 0C 1E 50 49 56 20 41 75 74 68 65 6E 74 69 63 61 74 69 6F 6E 20 43 65 72 74 69 66 69 63 61 74 65 ACR: 'Read Always, PIN to Update' 30 11 30 06 03 02 00 80 05 00 30 07 03 02 00 40 04 01 80 Identifier: 36 Byte UID 30 26 04 24 29 23 BE 84 E1 6C D6 AE 52 90 49 F1 F1 BB E9 EB B3 A6 DB 3C 87 0C 3E 99 24 5E 0D 1C 06 B7 47 DE B3 12 4D C8 Referenced Value '5FC105' A1 07 30 05 04 03 5F C1 05 ] ``` ## 3.1.4 Monolithic 7816-15 Structures To reduce the number of data objects required for discovery and still use the features of 7816-15, it is possible to represent the contents of the discovery data structures within the EF.OD itself. There are some drawbacks to this approach because it requires a single data object to hold the discovery data for all objects, which can become burdensome for the parser if it is only interested in certain data types. This method also requires that the access control rules of the EF.OD be identical to those that all of the discovery data structures would have. For example, there could be no granularity in access control for each of the discovery data structures, as they would be contained in a single data object. ## 3.1.5 Transitioning from the CCC to 7816-15 Transitioning from the CCC to 7816-15 should be easy given that the two discovery mechanisms can coexist. The CCC even includes a field that denotes whether a 7816-15 structure exists on a card. The middleware discovery process could take the following steps: - \u0084 Attempt to read the CCC and its contents. - \u0084 If the first step fails, read the standard EF.DIR location and its contents. - \u0084 If the first step succeeds, determine if the PKCS#15 flag is set in the CCC.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Personal Identity Verification Card Management Report."}]}
{"id": "nist_00575", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report) say about MEANING? 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), MEANING: MIN Mini Misc N/A NBS NCSC NIST Non-aggreg NSA OMB Oper &amp; Und Oper OPNAVINST PC Pers Persn Phys PL 100-235 PRI Prod Prot Reg Resp Respon Risks S/W SAT Sec SEC Secur/AcquisSpecs Sel Spec Sys S/W &amp; Maint Sys Telecom TIS Und Devel US Userid Va Minimal Minicomputer Miscellaneous Not Applicable National Bureau of Standards (former designation of the National Institute of Standards and Technology) National Computer Security Center National Institute of Standards and Technology (formerly the National Bureau of Standards or NBS) Non-aggregated National Security Agency Office of Management and Budget Operational and Under development Operational Operation Navy Instruction Personal Computer Personnel Selection/Screening Personnel Physical and Environmental Protection Public Law No. 100-235 (same as CSA or ACT) Primary Production (, I/O Controls) Protection Regulation Assignment of Security Responsibility Responsibility Risk/Sensitivity Assessment System Software Controls Security Awareness and Training Security Secondary Security/Acquisition Specifications Selection Special System Software and Maintenance System Telecommunications Trusted Information Systems, Inc. Under Development United States User Identification Variance", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)."}]}
{"id": "nist_00576", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N say about Executive Summary? (Part 1) According to A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N, Executive Summary: Executive Summary Extensible 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. Data services include computational capabilities that allow the consumption, alteration, and management of data resources, and distribution of access rights to data resources. Data services can take on many forms, to include applications such as time and attendance reporting, payroll processing, and health benefits management, but also including system level utilities such as file management. To answer these questions, this document first describes XACML and NGAC, then compares them with respect to five criteria. The first criterion is the relative degree to which the access control functionality of a data service can be separated from a proprietary operational environment.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N."}]}
{"id": "nist_00577", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PM-01 in Assessing Security and Privacy Controls in Information Systems and Organizations? Control PM-01: INFORMATION SECURITY PROGRAM PLAN POTENTIAL ASSESSMENT METHODS AND OBJECTS:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00578", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does BioCTS 2012_ Advanced Conformance Test Architectures and Test Suites for Biometric Data Interchange Formats and Biometric Information Records say about Table of Contents? (Part 6) According to BioCTS 2012_ Advanced Conformance Test Architectures and Test Suites for Biometric Data Interchange Formats and Biometric Information Records, Table of Contents: 27 Annex A - Roadmaps of Biometric Data Interchange Formats and Conformance Testing | | Figure 2 5: 'Field' Class ...............................................................................................................................................11 | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Figure 2 6: 'Header' Class ...........................................................................................................................................11 | | Figure 2 7: 'Representation' Class ..............................................................................................................................12 | | Figure 2 8: 'Data Format' Class ..................................................................................................................................12 | | Figure 2 9: CBEFF Structure and Elements...................................................................................................................14 | | Figure 2 10: 'BIR, PatronFormat', 'DataFormat', and 'SecurityFormat' Classes ......................................................15 | | Figure 2-11: BioCTS 2012 for ISO/IEC High-Level Architecture ....................................................................................16 | | Figure 2 12: 'Field' and 'Subfield' Classes..................................................................................................................17 | | Figure 2 13: 'InformastionItem' and 'BinarySubField' Classes ..................................................................................17 | | Figure 2-14: 'Record' Class and Inheritance ...............................................................................................................18 | | Figure 2 15: BioCTS 2012 for AN-2011 High-Level Architecture ..................................................................................21 | | Table 2-1: Comparison of the Field Structure in the Standard and the Code...............................................................24 | | Figure 2.16: Generic AN-2011 Field Structure..............................................................................................................24 | | Figure 2.17: AN-2011 Field Structure Example............................................................................................................25 | | Figure A.1: 1G Biometric Data Formats and Associated CTMs....................................................................................28 | | Figure A.2: 2G Biometric Data Formats and Associated CTMs....................................................................................29 | | Figure B.1: Roadmap of CTSs for AN-2011 Transactions .............................................................................................30 | | Figure B.2: Roadmap of CTSs for ISO/IEC Data Interchange Formats .........................................................................31 | | Figure B.3:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: BioCTS 2012_ Advanced Conformance Test Architectures and Test Suites for Biometric Data Interchange Formats and Biometric Information Records."}]}
{"id": "nist_00579", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 7.5 Protecting Keys and Secrets according to NIST Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases According to Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases, 7.5 Protecting Keys and Secrets: Cryptographic keys are high-value assets in workloads, especially in environments where the owner of the keys is not in complete control of the infrastructure, such as public clouds, edge computing, and network functions virtualization (NFV) deployments. In these environments, keys are typically provisioned on disk as flat files or entries in configuration files. At runtime, workloads read the keys into random access memory (RAM) and use them to perform cryptographic operations like data signing, encryption/decryption, or Transport Layer Security (TLS) termination. Keys on disk and in RAM are exposed to conventional attacks like privilege escalation, remote code execution, and input buffer mismanagement. Keys can also be stolen by malicious administrators or be disclosed because of operational errors. For example, an improperly protected VM snapshot can be used by a malicious agent to extract keys. An HSM can be attached to a server and used by workloads to store keys and perform cryptographic operations. This results in keys being protected at rest and in use. In this model, keys are never stored on disk or loaded into RAM. If attaching an HSM to a server is not an option, or if keys are needed in many servers at the same time, an alternative option is to use a network HSM. Workloads send the payload that needs cryptographic processing over a network connection to the network HSM, which then performs the cryptographic operations locally, typically in an attached HSM. An HSM option is not feasible in some environments. Workload owners may not have access to a cloud or edge environment in order to attach their HSM to a hardware server. Network HSMs can suffer from network latency, and some workloads require an optimized response time. Additionally, network HSMs are often provided as a service by the cloud, edge, or NFV providers and are billed by the number of transactions. Cost is often a deciding factor for using a provider network HSM.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases."}]}
{"id": "nist_00580", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DS-3 in Cryptographic Key Management Workshop Summary -- June 8-9, 2009? (Part 35) Control DS-3: would like network security at no extra cost. Recall the days when we were told that the cost of safety was not justifiable in automobiles. We were told that the public would never pay for seat belts. Today, not only do we have seat belts, but we have front and rear air bags, side air bags, and someday soon perhaps upper and lower air bags. Yes, we pay more for our cars, but we expect safety to be built in. There may also be smaller leaps in security that could help solve our cryptographic key management problems. What if we had the capability to automatically validate key establishment protocols or even use provably-secure protocols? Quantum cryptography could also improve security by permitting us to easily distribute secret values in a secure manner. But, there is more to key management than key establishment. Many key management problems involve the secure generation, storage, access and recovery of the keys, either before or after they are distributed. - Leaps in ease of implementation, management, and use: We have already made significant progress in this area. Electronic distribution of wrapped keys led to an improvement over manually distributed keys, and public key-based key distribution led to an improvement over key wrapping. Today, PKI, even with all of its problems, provides a major leap ahead over previously used systems. But, we still seem to be repeating some of the mistakes of the past. We build systems, we implement them, and then we find out that the users consider them unacceptable. We must not wait until the last minute to get the user's opinion. We need to build prototypes of a system and test them with real users before we extensively field the final product. - We need to explore the advantages of alternative approaches like identity-based key management. - What if we had cloud key management?", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, key management. Contains security framework guidance for authentication systems. Source: Cryptographic Key Management Workshop Summary -- June 8-9, 2009."}]}
{"id": "nist_00581", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Study of OSI Key Management provide? (Section 150) The KMSAs have prior agreements but need to initialize cryptographic variables; - The KMSAs negotiate about the algorithms to use. The protocol uses the Kirq and Kirs PDUs to establish the algorithms. ``` Kirq ::= SEQUENCE { protocolVersion ProtocolVersion, secServGrpProp [0] IMPLICIT SecServGrpProp OPTIONAL, keyEchGrpProp CHOICE { [1] IMPLICIT AsymmKeyExchGrpProp, [2] IMPLICrT SymmKeyExchGrpProp } OPTIONAL } ``` - Kirs ::= SEQUENCE { stateResult StateResult, protocolVersion ProtocolVersion, secServGipAcc [0] IMPLICIT SecServGrpAcc OPTIONAL keyEchGrpAcc CHOICE { [1] IMPLICIT AsyminKeyExchGipAcc, [2] IMPLICrr SymmKeyExchGrpAcc } OPTIONAL) SecServGrpProp ::= SEQUENCE { confAlgs SEQUENCE OF Algorithmidentifier, icvAlgs SEQUENCE OF Algorithmidentifier) SecServGrpAcc ::= SEQUENCE { confAlg Algorithmidentifier, icvAlg Algorithmidentifier) - AsymmKeyExchGrpProp ::= SEQUENCE { keyExchMethods SEQUENCE OF Algorithmidentifier - possibly more declarations have to be put in) AsymmKeyExchGrpAcc ::= SEQUENCE { keyExchMethod Algorithmidentifier - possibly more declarations have to be put in) Both secServGrpProp and keyEchGrpProp are optional because there can be prior agreements between the KMSAs about the algorithms to use. The KMSAs may therefore have no need to send the information contained in secServGrpProp and keyEchGrpFTop. Before the initiating key manager performs a key exchange, it looks up in the SMIB whether there are prior agreements made with the peer system. Problems arise when a KMSA makes a priori agreements with several other KMSAs and the agreements include different types of algorithms. For example, KMSA A has made an agreement to use key exchange method diffieHellmanModel with KMSA B and the key exchange method described in NLSP with KMSA C. Since algorithm identifiers are not exchanged when the application association is opened, how can KMSA A when acting as the responding party know the syntax of the algorithm dependent data conveyed in the Nkrq PDU?", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: A Study of OSI Key Management."}]}
{"id": "nist_00582", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Framework for Emergency Response Officials (ERO)_ Authentication and Authorization Infrastructure say about Table of Contents? (Part 3) According to Framework for Emergency Response Officials (ERO)_ Authentication and Authorization Infrastructure, Table of Contents: | 5 OF .................................................................................... | | 2.2 | 2.2 | 8 COMPONENTS CREDENTIALING SERVICE CLASS COMPONENTS OF CREDENTIALVERIFICATION SERVICE CLASS ......................................................... | | 2.4 | 2.4 | 9 COMPONENTS OF TRUST FEDERATION SERVICE CLASS............................................................................... | | 3. | 11 LEVERAGING STANDARDS AND EMERGING SPECIFICATIONS................................................... | 11 LEVERAGING STANDARDS AND EMERGING SPECIFICATIONS................................................... | | 4. SUMMARY.......................................................................................................................................................12 | 4. SUMMARY.......................................................................................................................................................12 | 4.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Framework for Emergency Response Officials (ERO)_ Authentication and Authorization Infrastructure."}]}
{"id": "nist_00583", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Required Test Procedures: according to NIST Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements According to Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements, Required Test Procedures:: SCAP.T.4000.1: The tester SHALL import the SCAP source data stream and apply it to a known target, producing an SCAP result data stream. SCAP.T.4000.2: The tester SHALL validate the results produced using SCAPVal; the validation MUST NOT produce any errors. \uf0a8 CVE \uf0a8 OCIL \uf0a8 CVE \uf0a8 OCIL \uf0a8 CVE \uf0a8 OCIL SCAP.T.4000.3: The tester SHALL visually inspect the results to ensure the Asset Identification Fields are as expected. SCAP.R.4100: The product SHALL be able to correctly produce an SCAP result data stream conforming to the ARF specification for each XCCDF, OVAL, and OCIL component. SCAP Capability: \uf0fe ACS", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements."}]}
{"id": "nist_00584", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-3 in Data Integrity_ Recovering from Ransomware and Other Destructive Events? (Part 5) Control IP-3: These types of adverse events ultimately impact data integrity (DI). It is imperative for organizations to recover quickly from a DI attack and trust the accuracy and precision of the recovered data. The National Cybersecurity Center of Excellence (NCCoE) at the National Institute of Standards and Technology (NIST) built a laboratory environment to explore methods to recover from a data corruption event in various information technology (IT) enterprise environments. The example solution outlined in this guide describes the solution built in the NCCoE lab. It encourages effective monitoring and detection of data corruption in standard enterprise components as well as custom applications and data composed of open-source and commercially available components. The goals of this NIST Cybersecurity Practice Guide are to help organizations confidently: - \uf0a7 restore data to its last known good configuration - \uf0a7 identify the correct backup version (free of malicious code and data for data restoration) - \uf0a7 identify altered data as well as the date and time of alteration - \uf0a7 determine the identity/identities of those who alter data - \uf0a7 identify other events that coincide with data alteration - \uf0a7 determine any impact of the data alteration For ease of use, here is a short description of the different sections of this volume. - \uf0a7 Section 1: Summary presents the challenge addressed by the NCCoE project, with an in-depth look at our approach, the architecture, and the security characteristics we used; the solution demonstrated to address the challenge; benefits of the solution; and the technology partners that participated in building, demonstrating, and documenting the solution. The Summary also explains how to provide feedback on this guide. - \uf0a7 Section 2: How to Use This Guide explains how readers-business decision makers, program managers, and IT professionals (e.g., systems administrators)-might use each volume of the guide.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Recovering from Ransomware and Other Destructive Events."}]}
{"id": "nist_00585", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations say about Table of Contents? (Part 11) According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, Table of Contents: | | | D.3.1.14. Attachments.....................................................................................................................216 | | | D.3.1.15. C-SCRM Plan and Life Cycles ............................................................................................216 | | | D.4.1. C-SCRM Template ....................................................................................................................218 | | | D.4.1.1. Authority and Compliance..................................................................................................218 | | | D.4.1.2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_00586", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.2. MFA Requirements Assessment according to NIST Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information, 3.2. MFA Requirements Assessment: When deploying an MFA solution, all agencies should conduct a requirements assessment to help determine the MFA solution that will best meet agency needs. This assessment should include, but is not limited to, engaging with the applicable stakeholders discussed in this section.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, mfa. Contains security framework guidance for authentication systems. Source: Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information."}]}
{"id": "nist_00587", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Device Security_ Bring Your Own Device (BYOD) provide? (Section 107) --------------------------------------------------------------------------------------| | Kryptowire Cloud Service | Application Vetting | ID.RA-1: Asset vulnerabilities are identified and documented. | CA-2, CA-7, CA-8: Security Assessment and Authorization RA-3, RA-5: Risk Assessment SA-4: Acquisition Process SI-7: Software, Firmware, and Information Integrity | A.12.6.1: Control of technical vulnerabilities A.18.2.3: Technical Compliance Review | CSC 4: Continuous Vulnerability Assessment and Remediation | SP-RSK-002: Security Control Assessor SP-ARC-002: Security Architect OM-ANA-001: Systems Security Analyst | | Specific product used | Function | Applicable NIST Cybersecurity Framework Subcategories | Applicable NIST SP 800-53 Revision 5 Controls | ISO/IEC 27001:2013 | CIS 6 | Applicable NIST SP 800-181 NICE Framework Work Roles (2017) | |-------------------------|------------|------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|--------------------------------------------|------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | | ID.RA-3: Threats, both internal and external, are identified and documented.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_00588", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IA-4 in NIST_SP_800-53r5_Security_Privacy_Controls? (Part 1) Control IA-4: IDENTIFIER MANAGEMENT Control: Manage system identifiers by: a. Receiving authorization from [Assignment: organization-defined personnel or roles] to assign an individual, group, role, service, or device identifier; b. Selecting an identifier that identifies an individual, group, role, service, or device; c. Assigning the identifier to the intended individual, group, role, service, or device; and d. Preventing reuse of identifiers for [Assignment: organization-defined time period]. Discussion: Common device identifiers include Media Access Control (MAC) addresses, Internet Protocol (IP) addresses, or device-unique token identifiers. The management of individual identifiers is not applicable to shared system accounts. Typically, individual identifiers are the usernames of the system accounts assigned to those individuals. In such instances, the account management activities of AC-2 use account names provided by IA-4. Identifier management also addresses individual identifiers not necessarily associated with system accounts. Preventing the reuse of identifiers implies preventing the assignment of previously used individual, group, role, service, or device identifiers to different individuals, groups, roles, services, or devices. Related Controls: AC-5, IA-2, IA-3, IA-5, IA-8, IA-9, IA-12, MA-4, PE-2, PE-3, PE-4, PL-4, PM-12, PS- 3, PS-4, PS-5, SC-37. Control Enhancements: (1) IDENTIFIER MANAGEMENT | PROHIBIT ACCOUNT IDENTIFIERS AS PUBLIC IDENTIFIERS Prohibit the use of system account identifiers that are the same as public identifiers for individual accounts. Discussion: Prohibiting account identifiers as public identifiers applies to any publicly disclosed account identifier used for communication such as, electronic mail and instant CHAPTER THREE PAGE 136 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization, token. Contains security framework guidance for authentication systems. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00589", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Electronic Health Records on Mobile Devices provide? (Section 102) allow enterprise connection security to enable certificate-based authentication to the AP. The APs assist in facilitating mobile device connectivity to each of the remote health organization networks. Each connected mobile device can then securely connect to the EHR server by using the AP connection. This section will describe how to configure the APs with IPs, media access control (MAC) address filtering, and certificate-based access control. NIST SP 1800-1C: Securing Electronic Health Records on Mobile Devices 32 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 1 . . System requirements \u25aa \u25aa \u25aa Two Cisco RV220W APs At least version 1.0.6.6 and up firmware A PC to connect to and configure the web-based interface You will also need the following parts of this guide: \u25aa \u25aa \u25aa Section 3.1, Hostnames Section 10.2.1, MDM Setup Section 7.1, Cisco Identity Services Engine 8.1.1 Cisco RV220 AP Setup We assume that you have a functional internet connection via Ethernet. 1. Connect the Ethernet cable from the internet to the wide area network (WAN) port of the RV220W. 2. Connect one end of a different Ethernet cable to one of the local area network (LAN)(Ethernet) ports on the back of the unit. 3. Connect the other end to an Ethernet port on the PC that will be used to run the web-based device manager. 4. Connect the power line and turn on the power switch. More detailed procedures for installing the Cisco\u00ae RV220W Network Security Firewall are available from the Cisco installation guide at administration/guide/rv220w_ag_78-19743.pdf. 8.1.2 Post-Setup Tasks 1. Use a PC to connect to a LAN port of the Cisco RV220W. If Dynamic Host Configuration Protocol (DHCP) is enabled, the PC should receive an IP address, and the PC becomes a DHCP client of the RV220W.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Securing Electronic Health Records on Mobile Devices."}]}
{"id": "nist_00590", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services say about Appendix D. Applying the PNT Profile to Cybersecurity Risk Management? (Part 1) According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services, Appendix D. Applying the PNT Profile to Cybersecurity Risk Management: Appendix D. Applying the PNT Profile to Cybersecurity Risk Management The PNT Profile can be used to augment an organization's pre-existing risk management program. This section further tailors the PNT Profile in context of a few notional fault scenarios to illustrate how the guidance can be applied to assess and manage PNT related risks in the context of a loss or degradation of PNT data or services. Organizations using the PNT data have the responsibility for mitigating temporary PNT disruptions . An effective PNT risk management strategy provides a dynamic and flexible approach to control risks in evolving environments. A comprehensive risk management strategy requires proper preparation, which is further detailed in Appendix E. Organizations are encouraged to apply the PNT Profile with their risk management approach from concept to acquisitions to acceptance, integration, and deployment, to operations and maintenance. Leveraging the organization's existing risk management program enables a system-level shared context. Furthermore, setting priorities for privacy and security risk management affords additional assurance from component to system implementation. Each organization selects PNT Profile Subcategories, the cybersecurity outcomes relevant to their mission and business objectives and implements associated controls proportional to their risk exposure. The organization verifies and validates the implementation throughout the PNT system lifecycle. A PNT system lifecycle can include the consideration of the acquisition, integration, deployment, operations and maintenance, repair, and replacement of PNT components and services. A comprehensive, well-documented, and disciplined risk management process for PNT systems allows for continuous monitoring of threats, likelihoods, and impacts, in order to provide efficient identification and analysis of risks and effectiveness of the controls applied to manage those risks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_00591", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Note according to Engineering Trustworthy Secure Systems? Note: Vulnerability can exist in anywhere throughout the life cycle of a system, such as in the CONOPS, procedures, processes, requirements, design, implementation, utilization, and sustainment of the system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_00592", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to SIMfill Use and Development say about 6. Code Modifications? (Part 1) According to Guide to SIMfill Use and Development, 6. Code Modifications: 6. Code Modifications SIMfill can be modified by users to fit their specific needs. The java classfiles are included in the distribution. They can also be studied to gain further insight into SIMfill's operation. The key components of SIMfill are listed in Figure 15. Note that modifications made to the code may also require changes to the schema definitions and reference test data. Table 2: Key SIMfill Components | Identifier | Component | |---------------------|------------------------------------------------------------------------------------------| | com.simfill.gui | The classes for the model, controller, and view components comprising the user interface | | com.simfill | The classes for the registry and the parser thread | | com.simfill.SimFill | The entry point of the application | | com.simfill.PCSC | The PC/SC abstraction layer | | com.simfill.gsm | The classes for internal data objects | One foreseeable change is to have SIMfill support an EF directly as a named EF, such as those shown in Table 1, in lieu of using the generic EF, RAW, which is identified and populated through its16-bit file identifier. To make such a change, several steps are required. The first step is to define the schema description for the new XML data entry, using the W3C conventions. Updating the XML schema file, data.xsd, with that definition allows an XML file containing the new data to be created and validated, and sets the foundation for the remaining steps. The second step is to add new states to the parsing automaton embodied in the DataXMLHandler class.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to SIMfill Use and Development."}]}
{"id": "nist_00593", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways provide? (Section 12) | | Brian Williams | VMware | The Technology Partners/Collaborators who participated in this build submitted their capabilities in response to a notice in the Federal Register. Respondents with relevant capabilities or product components were invited to sign a Cooperative Research and Development Agreement (CRADA) with NIST, allowing them to participate in a consortium to build this example solution. We worked with: | Technology Partner/Collaborator | Build Involvement | |-----------------------------------|---------------------------------------------------------------------------| | Cisco | Cisco Firepower Threat Defense (FTD) Cisco Identity Services Engine (ISE) | | Eclypsium | Eclypsium Administration and Analytics Service | | Forescout | Forescout Platform | | IBM | IBM Code Risk Analyzer IBM MaaS360 with Watson | | Lookout | Lookout Mobile Endpoint Security | | Microsoft | Microsoft Endpoint Configuration Manager | | Tenable | Nessus Tenable.io Tenable.sc | | VMware | VMware vRealize Automation SaltStack Config | The terms 'shall' and 'shall not' indicate requirements to be followed strictly to conform to the publication and from which no deviation is permitted.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_00594", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 say about MISCELLANEOUS PUBLICATIONS AND WEBSITES? (Part 1) According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171, MISCELLANEOUS PUBLICATIONS AND WEBSITES: MISCELLANEOUS PUBLICATIONS AND WEBSITES - [DOD ACQ] Department of Defense , Defense Acquisition University (2020) , DAU Glossary of Defense Acquisition Acronyms and Terms. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | [GAO 19-128] | U.S. Government Accountability Office (2018) Weapons Systems Cybersecurity: DOD Just Beginning to Grapple with Scale of Vulnerabilities. (GAO, Washington, DC), Report to the Committee on Armed Services, U.S. Senate, GAO 19-128. | |----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [NARA CUI] | National Archives and Records Administration (2019) Controlled Unclassified Information (CUI) Registry . https://www.archives.gov/cui | | [NIST CSF] | National Institute of Standards and Technology (2018) Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1. (National Institute of Standards and Technology, Gaithersburg, MD). https://doi.org/10.6028/NIST.CSWP.04162018 | | [NIST TRUST] | National Institute of Standards and Technology (2019) Roots of Trust Project .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_00595", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways? (Part 21) Control AM-1: ts. Our implementation of Lookout MES was integrated with IBM MaaS360. Lookout MES shared custom device attributes, such as device threat, with MaaS360, which could in turn provide policy enforcement. The Lookout for Work mobile client was able to provide firmware and application vulnerability assessment for mobile endpoints. Administrators could use Lookout to see which vulnerabilities were affecting deployed endpoints and find risk grades (i.e., A, B, C, D, or F) for installed applications. ## 4.2.8 Microsoft Endpoint Configuration Manager Microsoft Endpoint Configuration Manager was used in this build to perform configuration management, including software and firmware patching, for Windows-based hosts. Our implementation of Endpoint Configuration Manager included Windows Server Update Services (WSUS), an update service primarily used for downloading, distributing, and managing updates for Microsoft Windowsbased systems. The example build used Microsoft Endpoint Configuration Manager to demonstrate the identification of endpoints utilizing Heartbeat discovery and Windows Domain discovery methods, the patching of Windows endpoints via Microsoft updates and third-party update sources, and the deployment of custom scripts to endpoints. ## 4.2.9 Tenable.io In the example build, Tenable.io was used to provide vulnerability scanning and reporting for Docker container images. Containers are built from images and vulnerabilities are patched in images, not deployed containers, so images are the focus of scanning. Tenable.io scanned the repository of a Red Hat OpenShift cluster in the lab environment. Tenable.io was scheduled to routinely pull the latest images from the OpenShift cluster and perform vulnerability scans on them. Scan information was reported in the container security section of the Tenable.io Web Console. Administrators could see vulnerability information for containers deployed in their respective networks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_00596", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio say about 3.1.2. Risk Appetite and Risk Tolerance? (Part 2) According to Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio, 3.1.2. Risk Appetite and Risk Tolerance: defined at the enterprise level and risk tolerance at the enterprise or organization level, risk appetite is interpreted at the organizational and system levels to develop specific ICT risk tolerance. Risk tolerance represents the specific level of risk deemed acceptable within the risk appetite set by senior leadership (while recognizing that such tolerance can be influenced by legal or regulatory requirements). 11 Risk tolerance is interpreted and applied by the receiving custodians of the risk management discipline (e.g., cybersecurity, financial, legal, privacy) at the organization or system level. Risk appetite and risk tolerance are related but distinct in a similar manner to the relationship between governance and management activities. Risk appetite statements define the overarching risk guidance, and risk tolerance statements define the specific application of that direction. This means that risk tolerance statements are always more specific than the corresponding risk appetite statements. Together, risk appetite and risk tolerance statements represent risk limits, help communicate risk expectations, and improve the focus of risk management efforts. They also help to address other factors, such as findings from internal audits or external reports. The definition of these risk parameters places the enterprise in a better position to identify, prioritize, treat, and monitor risks that may lead to unacceptable loss. Risk tolerance should always stay within the boundaries established by senior leadership and within the parameters of and informed by legal and regulatory requirements.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio."}]}
{"id": "nist_00597", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is FR according to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)? FR: 6.60 The CKMS design shall specify how, and the circumstances under which, keys and metadata can be output from a cryptographic module and the form in which they are output.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_00598", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Information Security Handbook_ A Guide for Managers provide? (Section 230) -----|------------| | 5. Budget and Resources Are information security resources (internal FTEs and funding) allocated to protect information and information systems in accordance with assessed risks? | | | | | | | | 6. Systems and Projects Inventory Are IT projects and systems identified in an inventory and is the information about the IT projects and systems relevant to the investment management process? Is there an inventory of systems as required by FISMA? | | | | | | | | 7. IT Security Metrics Are IT security metrics collected agency-wide and reported? | | | | | | | | 8. Enterprise Architecture and the Federal Enterprise Architecture Security and Privacy Profile Are system- and enterprise-level information security and privacy requirements and capabilities documented within the agency's Enterprise Architecture? Is that information used to understand the current risks to the agency's mission? Is that information used to help program and agency executives select the best security and privacy solutions to enable the mission? 74 | | | | | | | | 9. Critical Infrastructure Protection Plan If required in your agency, is there a documented critical infrastructure and key resources protection plan that meets the requirements of HSPD-7 | | | | | | | | 10. Life Cycle Management Is there a system life cycle management process that requires each system to be C&A?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_00599", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does De-Identifying Government Datasets_ Techniques and Governance say about Table of Contents? (Part 10) According to De-Identifying Government Datasets_ Techniques and Governance, Table of Contents: | | 5.2.3. Data | 73 | 5.2.3. Data | 5.2.3. Data | | 5.3. Evaluating De-Identifcation | 74 | 5.3. Evaluating De-Identifcation | 5.3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: De-Identifying Government Datasets_ Techniques and Governance."}]}
{"id": "nist_00600", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Data Integrity_ Recovering from Ransomware and Other Destructive Events provide? (Section 20) assumes that IT professionals have experience implementing security products within the enterprise. While we used a suite of commercial products, this guide does not endorse these particular products. Your organization can adopt this solution or one that adheres to these guidelines in whole, or you can use this guide as a starting point for tailoring parts of it to recover from attacks on DI. Your organization's security experts should identify the products that will best integrate with your existing tools and IT system infrastructure. We hope you will seek products that are congruent with applicable standards and best practices. Section 3.5, Technologies, lists the products we used and maps them to the cybersecurity controls provided by this reference solution. A NIST Cybersecurity Practice Guide does not describe 'the' solution, but a possible solution. This is a draft guide. We seek feedback on its contents and welcome your input. Comments, suggestions, and success stories will improve subsequent versions of this guide. Please contribute your thoughts to ds-nccoe@nist.gov. The following table presents typographic conventions used in this volume. | Typeface/ Symbol | Meaning | Example | |--------------------|------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------| | Italics | filenames and pathnames references to documents that are not hyperlinks, new terms, and placeholders | For detailed definitions of terms, see the NCCoE Glossary. | | Bold | names of menus, options, command buttons and fields | Choose File > Edit .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Recovering from Ransomware and Other Destructive Events."}]}
{"id": "nist_00601", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information provide? (Section 11) ll likely need to integrate with one or both of these technologies. As agencies around the country begin to implement MFA solutions, the approaches they use require careful consideration and planning. This document provides a general overview of MFA, outlines design principles and architecture considerations for implementing MFA to protect CJI, and offers specific examples of use cases that agencies face today. It also outlines how CAD/RMS and message switch technologies can support standards and best practices that provide agencies with maximum optionality to implement MFA in a way that promotes security, interoperability, usability, and cost savings. Credential compromises represent a critical and pervasive cybersecurity threat, serving as a gateway for malicious actors to infiltrate networks and systems, thus gaining access to sensitive data. Whether through phishing, brute-force attacks, or exploiting vulnerabilities in authentication mechanisms, credential compromise poses a significant risk to organizations and individuals alike. To mitigate this threat, version 5.9.2 and subsequent versions of the Federal Bureau of Investigation (FBI) Criminal Justice Information Services (CJIS) Security Policy [1] require multi-factor authentication (MFA) for all users when accessing criminal justice information (CJI). Both criminal and non-criminal justice agencies that receive CJI are subject to this requirement. In this document, we refer to these organizations generically as agencies . As agencies around the country begin to implement this requirement, they face several challenges that require careful consideration and planning. The purpose of this document is to help agencies identify and address their MFA implementation needs by providing insight into MFA architectures and how they can be used to meet law enforcement-specific use cases.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, mfa. Contains security framework guidance for authentication systems. Source: Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information."}]}
{"id": "nist_00602", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways provide? (Section 51) er to prompt Tenable to scan devices newly connected to the network. Cisco ISE could then ingest this scan data to find the Common Vulnerability Scoring System (CVSS) scores of device vulnerabilities. An ISE policy was written to apply a quarantine action, via SGTs, to any device with a CVSS score equal to or greater than 7 (corresponding to high and critical vulnerabilities). - \uf0a7 Cisco pxGrid was configured to share contextual information about authenticated devices to the firewall. Cisco ISE was utilized to apply SGTs to devices as they were assessed for vulnerabilities. These SGTs were then passed to the lab firewall via pxGrid, where they could be used in custom firewall rules. pxGrid was also used to share communications between Forescout and Cisco ISE. Forescout could apply a quarantine tag to observed devices, which would then be shared with ISE. In this build, we utilized Eclypsium Administration and Analytics Service to provide agent-based identification of hardware and firmware for our laptop, desktop, and server endpoints while also monitoring the firmware for vulnerable or end-of-life versions. Eclypsium monitored laptop and virtual machine (VM) firmware integrity, and alerted if a component or its associated firmware changed. It also monitored endpoints for known security vulnerabilities from out-of-date firmware. Finally, we utilized Eclypsium's beta firmware update script, which automatically finds the latest known Basic Input/Output System (BIOS) firmware version for the system, downloads the update, and executes it to update the BIOS. In this build the Forescout platform was configured to perform endpoint discovery by detecting endpoints and determining software information about those endpoints based on a set of attributes. Forescout also provided the capability to isolate or restrict assets that cannot be patched and to respond to emergency scenarios, such as providing an emergency mitigation or deploying an emergency patch.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_00603", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PS-140 in Computer Security Division 2003 Annual Report? (Part 37) Control PS-140: June 2003 | | NIST IR 6981 | Policy Expression and Enforcement for Handheld Devices | May 2003 | | NIST IR 6985 | COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) | April 2003 | ## INFORMATION TECHNOLOGY LABORATORY BULLETINS WRITTEN BY THE CSD | October 2002 | Security Patches And The CVE Vulnerability Naming Scheme: Tools To Address Computer System Vulnerabilities | |----------------|--------------------------------------------------------------------------------------------------------------| | November 2002 | Security For Telecommuting And Broadband Communications | | December 2002 | Security of Public Web Servers | | January 2003 | Security Of Electronic Mail | | February 2003 | Secure Interconnections for Information Technology Systems | | March 2003 | Security For Wireless Networks And Devices | | June 2003 | ASSET: Security Assessment Tool For Federal Agencies | | July 2003 | Testing Intrusion Detection Systems | | August 2003 | IT Security Metrics | <!-- image --> ## GUEST RESEARCH INTERNSHIPS AT NIST O pportunities are available at NIST for 6 to 24 month internships within the CSD.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Computer Security Division 2003 Annual Report."}]}
{"id": "nist_00604", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Status Report on the First Round of the NIST Post-Quantum Cryptography Standardization Process provide? (Section 48) stablishment Schemes Using Integer Factorization Cryptography, National Institute of Standards and Technology, Gaithersburg, Maryland, September 2014, 121pp. https://doi.org/10.6028/NIST.SP.800-56Br1 | | [4] | NIST Workshop on Cybersecurity in a Post-Quantum World, National Institute of Standards and Technology, Gaithersburg, Maryland, April 2-3, 2015, Post-Quantum-World. | | [5] | L. Chen, S. Jordan, Y.K. Liu, D. Moody, R. Peralta, R. Perlner, D. Smith- tone, Report on Post-Quantum Cryptography , NISTIR 8105, National Institute of Standards and Technology, Gaithersburg, Maryland, April 2016, 10pp. | | [6] | D. Moody, Post-Quantum Cryptography Standardization: Announcement and outline of NIST's Call for Submissions , PQCrypto 2016, Fukuoka, Japan, February 24-26, 2016, NIST-s-Call-for-Submis. | | [7] | 'Post-Quantum Cryptography: Proposed Requirements and Evaluation Criteria,' 81 Federal Register 50686 (August 2, 2016), pp. 50686-50687. https://federalregister.gov/a/2016-18150. | | [8] | 'Announcing Request for Nominations for Public-Key Post-Quantum Cryptographic Algorithms,' 81 Federal Register 92787 (December 20, 2016), pp. 92787-92788. https://federalregister.gov/a/2016-30615. | | [9] | 'Establishment of NIST Smart Grid Advisory Committee and Solicitation of Nominations for Members,' 75 Federal Register 7 (January 12, 2010), pp. | | | 1595-1596. https://federalregister.gov/a/2010-344 [accessed 2/25/14]. | |------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [10] | U.S. Department of Commerce.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the First Round of the NIST Post-Quantum Cryptography Standardization Process."}]}
{"id": "nist_00605", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Information Technology Security Services say about 4. IT Security Services Life Cycle? (Part 1) According to Guide to Information Technology Security Services, 4. IT Security Services Life Cycle: 4. IT Security Services Life Cycle The IT security services life cycle provides IT security decision makers and managers with a six-phase process by which they can select, implement, and manage IT security services. This chapter details the various life-cycle phases and the issues and decisions within each phase. As Figure 4-1 illustrates, the security services life cycle has both a linear and iterative component. It proceeds linearly from initiation to implementation to closeout, but the assessment, solution, and operations phases must continually occur for an IT security service to succeed. Figure 4-1. IT Security Services Life Cycle <!-- image --> The six phases are described as follows: - \u0083 Phase 1: Initiationthe need to initiate the services life cycle is recognized. Section 4.1 discusses potential triggers for this phase. - \u0083 Phase 2: Assessmentbefore decision makers can implement a service and select a service provider, an accurate portrait of the current environment must be developed. Section 4.2 discusses Phase 2 and the importance of creating and gathering appropriate metrics. - \u0083 Phase 3: Solutiondecision makers choose the appropriate solution from the viable options identified during the assessment phase. Section 4.3 discusses the business cases and implementation plans. - \u0083 Phase 4: Implementationthe service and service provider are implemented during the implementation phase. Section 4.4 guides decision makers through service agreement development and service implementation. - \u0083 Phase 5: Operationsthe service is operational, the service provider is fully installed, and constant assessment of the service level and performance is made. Section 4.5 discusses the importance of metrics in monitoring service level and performance. - \u0083 Phase 6: Closeoutthe environment changes, the need for the service diminishes, or performance deficiencies are noted necessitating a replacement or termination of the IT security service.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guide to Information Technology Security Services."}]}
{"id": "nist_00606", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events say about 4.1.1 High-Level Architecture? (Part 1) According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events, 4.1.1 High-Level Architecture: 4.1.1 High-Level Architecture The DI solution is designed to address the security Functions and Subcategories described in Table 3-1 and is composed of the capabilities illustrated in Figure 4-1. Figure 4-1 DI Detect &amp; Respond High-Level Architecture <!-- image --> - Integrity monitoring provides capabilities for comparing current system states against established baselines. . - Event detection provides capabilities for detecting ongoing events and can be composed of intrusion detection, malware detection, user anomaly detection, and others, depending on the established threat model of the organization. - L ogging records and stores all the log files produced by components within the enterprise. - Forensics/analytics provides the capability to probe/analyze logs and machines within the enterprise to learn from DI events. - Mitigation and containment allows responding to DI events by containing and limiting the threat's ability to affect the system. - Reporting provides the capability to report on all activities within the enterprise and within the reference architecture for analysis by a security team. These capabilities work together to provide the Detect and Respond Functions for DI. The integrity monitoring capability collects integrity information prior to attacks so that when an attack happens, records of all file/system changes are preserved. In combination with event detection, these records not only function as a tool to inform recovery but also as early indicators of compromise. Event detection uses these records and its own mechanisms to actively detect events as they happen and to take appropriate action through other components of the reference architecture. Logging collects information from event detection and integrity monitoring for use in response functions. Mitigation and containment provides capabilities to stop ongoing attacks and limit their effect on the system.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events."}]}
{"id": "nist_00607", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Summary Report for \u201cWorkshop on Updating Manufacturer Guidance for Securable Connected Product Development\u201d say about The use of robust frameworks and the adoption of open standards are crucial for effectively managing risks across heterogeneous environments.? According to Summary Report for \u201cWorkshop on Updating Manufacturer Guidance for Securable Connected Product Development\u201d, The use of robust frameworks and the adoption of open standards are crucial for effectively managing risks across heterogeneous environments.: Throughout the workshop, the importance of established frameworks and open standards was discussed as beneficial to enhancing IoT security and reducing threats. Real-world examples showcased how these tools can effectively mitigate cybersecurity threats while considering interactions between mitigations and device properties. It was noted that there are emerging examples of standards organizations using threat frameworks to discuss risk management. Open standards were discussed as crucial in fostering interoperability and resilience, particularly within OT and ICS environments. Participants underscored the value of standards in making vulnerability advisories more actionable through enhanced communication across various systems. The need for clear, informative references and robust use case examples was also highlighted, emphasizing their role in clarifying specific points and supporting industry best practices. As topics of discussion, privacy compliance and risk management emerged as important yet distinct areas of focus. The discussions noted the challenges in defining authority for privacy and managing privacy risks and the value of frameworks such as the NIST Privacy Framework to address these challenges. Additionally, there was a recognized need for a product baseline and specific security controls at varying levels to enhance overall cybersecurity efforts. Participants noted that clear and direct communication, along with formalized sections within documents, would further support the effective implementation of best practices and ensure a comprehensive approach to cybersecurity.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Summary Report for \u201cWorkshop on Updating Manufacturer Guidance for Securable Connected Product Development\u201d."}]}
{"id": "nist_00608", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2004 Annual Report say about INFORMATION TECHNOLOGY LABORATORY BULLETINS WRITTEN BY THE CSD? According to Computer Security Division 2004 Annual Report, INFORMATION TECHNOLOGY LABORATORY BULLETINS WRITTEN BY THE CSD: | October 2003 | Information Technology Security Awareness, Training, Education, and Certification | |----------------|------------------------------------------------------------------------------------------------------------------------------------------| | November 2003 | Network Security Testing | | December 2003 | Security Considerations in the Information System Development Life Cycle | | January 2004 | Computer Security Incidents: Assessing, Managing, And Controlling The Risks | | March 2004 | Federal Information Processing Standard (FIPS) 199, Standards For Security Categorization Of Federal Information And Information Systems | | April 2004 | Selecting Information Technology Security Products | | May 2004 | Guide For The Security Certification And Accreditation Of Federal Information Systems | | June 2004 | Information Technology Security Services: How To Select, Implement, And Manage | | July 2004 | Guide For Mapping Types Of Information And Information Systems To Security Categories | | August 2004 | Electronic Authentication: Guidance For Selecting Secure Techniques | | September 2004 | Information Security Within the System Development Life Cycle | February 2004 April 04 August 04 December 03", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2004 Annual Report."}]}
{"id": "nist_00609", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI) provide? (Section 20) This Directive established a federal policy to create and use government-wide secure and reliable forms of identification for federal employees and contractors. It further defined secure and reliable forms of identification as ones that - - \uf0b7 Are issued based on sound criteria for verifying an individual's identity; - \uf0b7 Are strongly resistant to identity fraud, tampering, counterfeiting, and terrorist exploitation; - \uf0b7 Can be rapidly authenticated electronically; and - \uf0b7 Are issued only by providers whose reliability has been established by an official accreditation process. NIST developed and published Federal Information Processing Standard (FIPS) 201, Personal Identity Verification (PIV) of Federal Employees and Contractors, and several Special Publications providing additional specifications in response to [HSPD-12]. These documents provide the foundation for Government personal identification, verification, and access control systems. Appendix A.1 of FIPS 201-2 states the following: '\u2026[HSPD-12] requires that all cards be issued by providers whose reliability has been established by an official accreditation process.' To determine consistency in operations of issuers of PIV Cards, NIST developed a set of attributes as the basis of reliability assessment and published the first version of this document in July 2005. Subsequent lessons learned in various agencies' implementation, experience in credential management and PIV Card issuance together with the evolution of PIV Card issuing organizations motivated NIST to develop an updated methodology that is objective, efficient, and resulted in a consistent and repeatable authorization decisions. These developments led NIST to publish the first revision to SP 800-79 (i.e., SP 800-79-1) in June 2008. In 2013, FIPS 201 was superseded by FIPS 201 revision 2 (FIPS 201-2). FIPS 201-2 incorporates additional lessons learned from PIV Card issuers and allows for mobile device-integrated PIV credentials.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization, credential management. Contains security framework guidance for authentication systems. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_00610", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Operational Technology (OT) Security provide? (Section 288) s can manipulate OT processes to cause physical damage. Table 21 provides an overview of potential OT threat events and leverages MITRE\u2019s ATT&CK\u00ae for Industrial Control Systems [ATTACK-ICS]. Table 21. Examples of potential threat events Threat Event Denial of control Manipulation of control Spoofed reporting message Theft of operational information Description Temporarily prevents operators and engineers from interfacing with process controls. An affected process may still be operating during the period of control loss but not necessarily in a desired state. Unauthorized changes made to programmed instructions in PLCs, RTUs, DCS, or SCADA controllers, alarm thresholds changed, or unauthorized commands issued to control equipment. These changes could potentially result in damage to equipment (if tolerances are exceeded), premature shutdown of processes (e.g., prematurely shutting down transmission lines), an environmental incident, or even disabled control equipment. False information sent to an OT system operator, either for evasion or to impair process control. The adversary could make the defenders and operators think that other errors are occurring in order to distract them from the actual source of the problem (i.e., alarm floods). Adversaries may steal operational information for personal gain or to inform future operations. 179 NIST SP 800-82r3 September 2023 Threat Event Loss of safety Loss of availability Guide to Operational Technology (OT) Security Description Adversaries may target and disable safety system functions as a prerequisite to subsequent attack execution or to allow future unsafe conditionals to go unchecked. Adversaries may leverage malware to delete or encrypt critical data on HMIs, workstations, or databases. Numerous OT incidents have been reported and documented. Descriptions of these events help demonstrate the severity of the threat sources, vulnerabilities, and impacts within the OT domain.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, adversary. Contains technical security guidance that could inform defensive posture. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_00611", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automation Support for Security Control Assessments_ Software Asset Management say about 2.6.1 Process for Identifying Needed Controls? (Part 1) According to Automation Support for Security Control Assessments_ Software Asset Management, 2.6.1 Process for Identifying Needed Controls: 2.6.1 Process for Identifying Needed Controls In Volume 1 of NISTIR 8011, Section 3.5.2, Tracing Security Control Items to Capabilities, describes the process used to determine the controls needed to support a capability. In short, the two steps are: 1. Use an automated keyword search of the control text to identify control items that might support the capability. See keyword rules used for SWAM in Appendix B. 2. Manually identify those that do support the capability (true positives) and ignore those that do not (false positives). Completion of the above two steps produces three sets of controls: 1. Control items in the low, moderate, and high baselines that support the SWAM capability (listed individually in Section 3.3 on SWAM Control (Item) Security Assessment Plan Narrative Tables and Templates, and listed by security baseline in Section 3.4 on Control Allocation Tables). 2. Control items in the low, moderate, and high baselines selected by the keyword search, but manually determined to be false positives (listed in Appendix C). 20 A risk scoring methodology is necessary to score and prioritize defects but risk scoring is out of scope for this publication. 3. Control items not in a baseline, and not analyzed further after the keyword search, including: - a. Program management (PM) controls, because PM controls do not apply to individual systems; - b. Not selected controls-controls that are in SP 800-53 but are not assigned to (selected in) a baseline; and - c. Privacy controls. The unanalyzed controls are listed in Appendix D, in case the organization wants to develop automated tests. To implement whitelisting/blacklisting in general, and software whitelisting/blacklisting in particular, SWAM may rely on some other capabilities. The controls that support whitelisting and blacklisting are not included in SWAM if the supporting controls are more central to the other capability.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_00612", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Public Laws according to NIST Security Architecture Design Process for Health Information Exchanges (HIEs) According to Security Architecture Design Process for Health Information Exchanges (HIEs), Public Laws: Public Law 104-191, Health Insurance Portability and Accountability Act (HIPAA) of 1996, August 21, 1996. Public Law 107-347, E-Government Act of 2002 (Title III: Federal Information Security Management Act [FISMA] of 2002), December 17, 2002. Public Law 111-5, American Recovery and Reinvestment Act of 2009 (ARRA) (Title XIII, Health Information Technology for Economic and Clinical Health [HITECH] Act of 2009), February 17, 2009.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Architecture Design Process for Health Information Exchanges (HIEs)."}]}
{"id": "nist_00613", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Control Baselines for Information Systems and Organizations say about 3.13 PROGRAM MANAGEMENT FAMILY? (Part 2) According to Control Baselines for Information Systems and Organizations, 3.13 PROGRAM MANAGEMENT FAMILY: | | | | PM-2 | Information Security Program Leadership Role | | | | | | PM-3 | Information Security and Privacy Resources | x | | | | | PM-4 | Plan of Action and Milestones Process | x | | | | | PM-5 | System Inventory | | | | | | PM-5(1) | INVENTORY OF PERSONALLY IDENTIFIABLE INFORMATION | x | | | | | PM-6 | Measures of Performance | x | | | | | PM-7 | Enterprise Architecture | x | | | | | PM-7(1) | OFFLOADING | | | | | | PM-8 | Critical Infrastructure Plan | x | | | | | PM-9 | Risk Management Strategy | x | | | | | PM-10 | Authorization Process | x | | | | | PM-11 | Mission and Business Process Definition | x | | | | | PM-12 | Insider Threat Program | | | | | | PM-13 | Security and Privacy Workforce | x | | security | | | PM-14 | Testing, Training, and Monitoring | x | | | | | PM-15 | Security and Privacy Groups and Associations | | |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Control Baselines for Information Systems and Organizations."}]}
{"id": "nist_00614", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to IPsec VPNs say about C.4 Section 9.1 Case Study Alternative Using iked on OpenBSD? According to Guide to IPsec VPNs, C.4 Section 9.1 Case Study Alternative Using iked on OpenBSD: The following lists the contents of the same configuration that was provided for Appendix C.1 but using OpenIKED on OpenBSD. Note that this IKE daemon does not support AES-GCM for IKE, only for ESP. The order of the keywords matter. ```", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to IPsec VPNs."}]}
{"id": "nist_00615", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does De-Identifying Government Datasets_ Techniques and Governance provide? (Section 91) edge of statistics and computation techniques. Agencies can rely on de-identification standards to provide standardized terminology, procedures, and performance criteria for de-identification efforts. Agencies can adopt existing de-identification standards or create their own. De-identification standards can be prescriptive or risk-based. De-identification standards assist agencies with the process of de-identifying data prior to public release. Without standards, data owners may be unwilling to share data, as they may be unable to assess whether a procedure for de-identifying is sufficient to minimize privacy risk. Standards can increase the availability of individuals with appropriate training by identifying a specific body of knowledge and practice that training should address. Absent standards, agencies may forego opportunities to share data. De-identification standards can help practitioners develop a community, as well as certification and accreditation processes. Standards decrease uncertainty and provide data owners and custodians with best practices to follow. Courts can consider standards as acceptable practices that should generally be followed. In the event of litigation, an agency can point to the standard and say that it followed good data practice. A prescriptive de-identification standard specifies an algorithmic procedure that - if followed - results in data that are de-identified to a previously established benchmark. This approach focuses on the process of de-identification rather than on the specific properties of the de-identified data. The Safe Harbor method of the HIPAA Privacy Rule [3] is an example of a prescriptive deidentification standard. The intent of the Safe Harbor method is to 'provide covered entities with a simple method to determine if the information is adequately de-identified' [118].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: De-Identifying Government Datasets_ Techniques and Governance."}]}
{"id": "nist_00616", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cell Phone Forensic Tools_ an Overview and Analysis say about Report Generation? According to Cell Phone Forensic Tools_ an Overview and Analysis, Report Generation: After a successful acquisition has taken place the examiner then has the opportunity to create a customized report of findings that pertain to the case. To finalize the report, the export option is selected, which allows specific data fields to be incorporated into the report. Figure 78 gives a snapshot of the Report Wizard that allows examiners to select the data fields for the finalized report. Figure 78: Report Wizard <!-- image --> The examiner has the choice of exporting the final report in the formats illustrated below in Figure 79. Figure 79: Report Output Type <!-- image --> Figure 80 and Figure 81 are snapshots of the final generated report. Figure 80: Report Excerpt <!-- image --> Figure 81: Report Excerpt <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_00617", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control UM-1 in A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification? (Part 36) Control UM-1: Physical Token - Cardholder Binding (Strong or Weak depending upon PIN size) | | | object verified PUM-8: The cardholder presents a live sample of biometric data under the supervision of an attendant (e.g., Security Guard) | | |---------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 6.2.2 - OCC-AUTH - Authentication Using On-Card Biometric Comparison | (It is assumed that a signed biometric object containing the biometric template and the unique identifier exists in the card (though not read) ) A live sample of the biometric is presented directly on the card.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification."}]}
{"id": "nist_00618", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings say about 2.2 Canada's Secure Channel? (Part 3) According to 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings, 2.2 Canada's Secure Channel: erent government programs). It is likely though that individuals will opt for a manageable number of epasses , supporting a more consistent experience in their authentication to government. Note also that no personal information about an individual is maintained centrally to support the epass service; personal information about a user is retained within the context of their relationship within a program.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_00619", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings say about 7 SUMMARY? According to 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings, 7 SUMMARY: In this paper, we have identified several pitfalls for certification paths. We have identified various solutions that are secure, interoperable, standards compliant, realizable using commercial products, and meet the operational constraints of the various PKIs. Specifically, we have identified the following: - /square4 Self-issued certificates can lead to circularity. Not checking revocation status of self-issued certificates or using an untrusted public key to verify signatures to remove the circularity is non-compliant with the standards. There are several standardscompliant alternatives to remove circularity. - /square4 Standards do not provide any constraints for trust models to support usage of indirect CRLs. This can lead to insecurity. We have proposed indirect CRL trust model constraints and associated extensions. - /square4 Standards do not provide guidance on matching EE certification paths and CRL or OCSP Responder certification paths. This lack of guidance could lead to insecure results. We have provided a solution that can reduce the computational complexity for certification path development while enhancing security. We recommend that TA driven trust models for OCSP Responders not be used since they do not scale to crosscertified and Bridge environments, due to use of different relying party TAs. - /square4 While the solutions presented in this paper are illustrated using simple examples of circularity, the solutions are applicable to mitigate convoluted circularities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, sso. Contains security framework guidance for authentication systems. Source: 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings."}]}
{"id": "nist_00620", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-4 in Guide to Operational Technology (OT) Security? Control SI-4: (5) SYSTEM MONITORING | SYSTEM-GENERATED ALERTS", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_00621", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report) say about TABLE OF CONTENTS? (Part 8) 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), TABLE OF CONTENTS: | | | | | | D. | Document | Overview | | | | | | | 1-3 | | | | | | | | | | | | | E. | Additional | Sources | of | | Information | | | | 1-4 | | | | | | | | | | | | II. | DESCRIPTION OF THE CSPP REVIEW PROCESS . | DESCRIPTION OF THE CSPP REVIEW PROCESS . | DESCRIPTION OF THE CSPP REVIEW PROCESS .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)."}]}
{"id": "nist_00622", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements provide? (Section 49) tems Instructions 20 Distributed Denial of Service 1. No previously identified vulnerabilities and predisposing conditions apply, only new vulnerabilities and predisposing conditions (may) apply. 2. Some, but not all previously considered vulnerabilities and predisposing conditions apply, and new vulnerabilities and predisposing conditions apply. 3. Some, but not all previously considered vulnerabilities and predisposing conditions apply, but no new vulnerabilities and predisposing conditions apply. 4. All previously considered vulnerabilities and predisposing conditions still apply, and new vulnerabilities and predisposing conditions apply. How does the IoT device affect likelihood(s) of occurrence determinations as part of a risk assessment? Risk impact is dependent on two components: likelihood of occurrence and magnitude of impact. As per CNSSI No. 4009, likelihood of occurrence 'is a weighted risk factor based on an analysis of the probability that a given threat is capable of exploiting a given vulnerability (or set of vulnerabilities).' [CNSSI] Determination of likelihood as part of a risk assessment is therefore based on identified threat sources and events as well as vulnerabilities and pre-disposing conditions. Threat sources, events, and vulnerabilities identified for the IoT device must be used in the assessment of likelihood. Likelihood of occurrence can often be expressed in a relative way (e.g., low, medium, or high likelihood of occurrence). As part of a risk assessment, the effect of an IoT device on likelihood of occurrence can be expressed as being greater , lower , or equal to the likelihood of occurrence without the IoT device. For example, an IoT device being connected to a system may create new possible connections (e.g., cellular data connections) that may increase the likelihood of a remote actor being able to exploit a vulnerability.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements."}]}
{"id": "nist_00623", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2 provide? (Section 39) -------------------------------------------|---------------------------------------------------------------------------------------------------------| | Element Definition | A data stream. This element contains the links to all of the components that comprise this data stream. | A data stream. This element contains the links to all of the components that comprise this data stream. | A data stream. This element contains the links to all of the components that comprise this data stream. | | Properties | Properties | Properties | Properties | | Name | Type | Count | Property Definition | | id | literal - ID | 1 | The identifier for the data stream. This identifier MUST be globally unique (see Section 3.1.3). | | use-case | literal - token | 1 | The use case represented by the data stream. The value MUST be one of the following: CONFIGURATION, VULNERABILITY, INVENTORY, or OTHER. The value selected MUST indicate which type of content is being represented as defined in Section 5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2."}]}
{"id": "nist_00624", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Family: Supply Chain Risk Management according to NIST Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer, Family: Supply Chain Risk Management: Description: A systematic process for managing cyber supply chain risk exposures, threats, and vulnerabilities throughout the supply chain and developing risk response strategies to the risks presented by the supplier, the supplied products and services, or the supply chain. [SP 800-53].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer."}]}
{"id": "nist_00625", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SC-30(4) in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Control SC-30(4): Monitor Logs (CM2104) Behavior Validation Detect", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_00626", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study say about Table of Contents? (Part 6) According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study, Table of Contents: .................................................................................. | 3.3 SECURITY AWARENESS PROGRAMS ................................................................................... | 12 | | 3.3.1 | Program Size............................................................................................................. | 12 | | 3.3.2 | Team Size .................................................................................................................. | 14 | | 4 CONCLUSION................................................................................................................... 17 | 4 CONCLUSION................................................................................................................... 17 | 4 CONCLUSION................................................................................................................... 17 | | REFERENCES............................................................................................................................ 18 | REFERENCES............................................................................................................................ 18 | REFERENCES............................................................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study."}]}
{"id": "nist_00627", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Secure Web Services say about 6.3.2 XML? (Part 2) According to Guide to Secure Web Services, 6.3.2 XML: ser with illegitimate entity references - Enforce validation. An attacker may be able to subvert the validate command called by the XML application when it has loaded the schema cache with namespaces. Attackers do this by using a root element from a different namespace to redirect xsi:schemaLocation to point to their own schema, in which they include the declaration &lt;xs:any namespace=##any,, processContents='skip'/&gt; .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Secure Web Services."}]}
{"id": "nist_00628", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Attribute Based Access Control (ABAC) Definition and Considerations say about 1.4 Notes on Terminology? (Part 2) According to Guide to Attribute Based Access Control (ABAC) Definition and Considerations, 1.4 Notes on Terminology: erent roles, and may inherit different privileges tied to those roles. The person may establish different personas for each organization or role and amass different attributes related to each persona. For example, an individual may work for Company A as a gate guard during the week and may work for Company B as a shift manager on the weekend. The subject attributes are different for each persona. Although trained and qualified as a Gate Guard for Company A, while operating in her Company B persona as a shift manager on the weekend she does not have the authority to perform as a Gate Guard for Company B. Authentication is not the same as access control or authorization. Authentication is the act of verifying that the subject has been authorized to use the presented identifier by a trusted identity provider organization. Access control or authorization , on the other hand, is the decision to permit or deny a subject access to system objects (network, data, application, service, etc.) Note that ABAC can be used without identification information, and authentication method is not addressed in this document. The terms access control and authorization are used synonymously throughout this document. Privileges represent the authorized behavior of a subject; they are defined by an authority and embodied in policy or rules. For the purposes of this document, the terms privileges and authorizations are used interchangeably in that they are meant to convey one's authority and implicit approval to access one or more objects. Environment conditions are dynamic factors, independent of subject and object, that may be used as attributes at decision time to influence an access decision. Examples of environment conditions include time, location, threat level, and temperature. Policy, rules, and relationships govern allowable behavior within an organization, based on the privileges of subjects and how resources or objects are to be protected under which environment conditions.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Guide to Attribute Based Access Control (ABAC) Definition and Considerations."}]}
{"id": "nist_00629", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Guide to IPsec VPNs? (Part 161) Control HA-1: r confidentiality and integrity protection and for key exchange involves choosing encryption and integrity protection algorithms, 56 key lengths, DH groups for key exchange, and IKE and ESP lifetimes. For up-to-date policies and advice on these settings, see NIST SP 800-131A [18] and FIPS 140 [13][14] as well as the recommendations of the IETF for IKE [25] and ESP [63]. Note that these documents will be updated over time or be obsoleted for newer publications. The IKE protocol sends just a few packets per hour, so it makes sense to be extra cautious and pick strong algorithms with large enough keys and, specifically, a strong DH group. Approved DH groups are identified in NIST SP 800-56A [64]. The bulk of the CPU power of an IPsec host will be spent on IPsec, not IKE. In IKE, the most CPU-intensive operation is the DH calculation. When an IPsec host has hundreds or thousands of IKE (re)connections, choosing the right DH group becomes very important. The use of strong key sizes is recommended for IKE. The performance impact of larger key sizes is minimal because IKE traffic is negligible compared to IPsec traffic. For IPsec (ESP), the key 56 Only FIPS-validated implementations of NIST-approved algorithms shall be used. size can have a significant impact on performance. In general, use larger key sizes for IPsec if performance is not an issue. For ESP, the choice of algorithms for confidentiality and integrity protection should also take performance into account. Using an AEAD algorithm that can provide both confidentiality and integrity protection in a single operation, such as AES-GCM, will give better performance than using non-AEAD algorithms that require separate operations (e.g., AES-CBC for encryption and HMAC for integrity protection). It is important to estimate the processing resources that the cryptographic computations will require during peak usage. It is uncommon to use 192-bit AES keys, and this key length is optional in [25].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Guide to IPsec VPNs."}]}
{"id": "nist_00630", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems say about RECOVERY? According to Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems, RECOVERY: j '\u2022 t 5 '7 ?.:--:;fji: 3^0 ku ;Ci --7 ijf.-t' 0 7 f&gt;i. :\u00bb'.-f,-:' e Q-.-ir-V'ti .'Anol??T^'J ;&amp; ;7x^:'.&gt;t\u00bb :\u2022' .\"Xiv \u00bb\u2022 i \u2022' ', \"iJ''.- :}r=!5&gt;47 n^'.''' ':':^j,ts\u00ab\"^ ln.7S? 3id ft Wfrlfj4--. i.&gt; o.i iv&lt;vt t*fb ;(\u00ab .'x-yrjssit -ISiltXti %nk,&lt;:TpO ir^u -J:jsbxt\u00bbmjv XXf\u00bbW '' '^sjvoasrj: fit?!? ' u&amp;Xq ^ *ji;^ 5&lt;7 i^sits \u2022?\u00bbtixr xill?^ .rk himM$mi:K , -:i9Sfsa\u00abi:Jrj ' 'vv '' ^0 v-v*v\\*&gt;!&gt;a-s 'k tii jeM? 5,0 &lt;\u00bb\u00ab ?-ir3'y&lt;3 ' ''- ' rik' XSOTDSl^ \u202230.^:420^ 5'd ^ \u00abi&gt;o \u00ab\u00bb-:}; jiciqatif .. ^5\u00ab3ljf' 4 . ^ 1^1 ' ''&lt;9ifjr \u2022", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems."}]}
{"id": "nist_00631", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Section 342) gency official for privacy, senior accountable official for risk management or risk executive [function]; control assessors; system security or privacy officer; and the continuous monitoring program). The authorization package 128 includes the following: - Executive summary; - Security and privacy plans; 129 130 127 Authorization packages for common controls that are not system-based may not include a security or privacy plan, but do include a record of common control implementation details. 128 The authorizing official determines what additional supporting information, artifacts, or references may be required in the authorization package. The additional documentation may include, for example, risk assessments, contingency plans, or SCRM plans. 129 [SP 800-18] provides guidance on system security plans. Guidance on privacy plans will be addressed in a planned publication specific to privacy plans. 130 In accordance with [OMB A-130], the information system security plan and the privacy plan may be integrated into one consolidated document. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ - Security and privacy assessment reports; 131 and - Plans of action and milestones. The executive summary provides a consolidated view of the security and privacy information in the authorization package. The executive summary identifies and highlights risk management issues associated with protecting information systems and the environments in which the systems operate. The summary provides the essential information needed by the authorizing official to understand the security and privacy risks to the organization's operations and assets, individuals, other organizations, and the Nation.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_00632", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Appendix B: Generation of Other Quantities according to NIST Digital Signature Standard (DSS) According to Digital Signature Standard (DSS), Appendix B: Generation of Other Quantities: This appendix contains routines for the supplementary processes required for the implementation of this standard. Appendix B.1 is needed to produce the inverse of the per-message secret k (see Section 6.3 and Appendices A.2.1 and A.2.2) and the inverse of the signature portion s that is used during signature verification (see Section 6.4). The routines in Appendix B.2 are required to convert between bit strings and integers when implementing this standard. Appendix B.3 contains probabilistic primality tests to be used during the generation of RSA key pairs. Appendices B.4 and B.5 contain algorithms required during the Lucas probabilistic primality test of Appendix B.3.3 to check for a perfect square and to compute the Jacobi symbol. Appendix B.6 contains the Shawe-Taylor algorithm for the construction of primes. Appendix B.7 provides a process to perform trial division as required by the random prime generation routine in Appendix B.6. The sieve procedure in Appendix C.8 is needed by the trial division routine in Appendix B.7. The trial division process in Appendix B.7 and the sieve procedure in Appendix B.8 have been extracted from ANS X9.80 [23], Prime Number Generation, Primality Testing, and Primality Certificates . Appendix B.9 is required during the generation of RSA key pairs. Appendix B.10 provides a method for constructing provable primes for RSA (see Appendix A.1.2.2 and A.1.4).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Digital Signature Standard (DSS)."}]}
{"id": "nist_00633", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information provide? (Section 59) link to the CAD/RMS system. 6. The CAD/RMS system redirects the officer's browser to the IdP to authenticate. 7. Since the officer has an active session with the IdP, they do not need to authenticate. The IdP redirects the officer's browser to the CAD/RMS system with a SAML assertion. 8. The CAD/RMS system validates the assertion and logs in the officer. 9. The officer submits a query to the CAD/RMS system. 10. The CAD/RMS system sends a WS-Trust Security Token Request to the IdP, including the SAML assertion it received earlier in the onBehalfOf element to indicate that the request is for a token to present to the message switch on behalf of the previously authenticated user. 11. The IdP creates a new SAML assertion with the officer as the subject and with a suitable audience parameter for the message switch. The IdP returns this SAML assertion to the CAD/RMS system in a WS-Trust Request Security Token Response message. 12. The CAD/RMS system sends this new SAML assertion and the query to the message switch. 13. The message switch validates the assertion and extracts the user's identity and attributes. The message switch can use these attributes to authorize the query. This section considers the case where the CAD/RMS system is a client/server application hosted at the county level and accessed through a 'thick client' software application installed on the MDC. For this section, we also assume that county users authenticate to a state-hosted IdP. The thick client introduces a challenge for SAML integration. The common SAML SSO interactions rely on web functionality such as HTTP redirect and POST messages and the use of a browser for interactive authentication to the IdP. However, the MDC operating systems typically provide mechanisms for thick client applications to interact with the web browser that can be used to implement SAML and other authentication and authorization protocols like OIDC and OAuth.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, multi-factor. Contains security framework guidance for authentication systems. Source: Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information."}]}
{"id": "nist_00634", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Considerations for Voice Over IP Systems say about 5.2.5 IPsec usage within SIP? According to Security Considerations for Voice Over IP Systems, 5.2.5 IPsec usage within SIP: IPsec may also be used to provide security for SIP signaling at the network layer. This type of security is most suited to securing SIP hosts in a SIP VPN scenario (SIP user agents/proxies) or between administrative SIP domains. IPsec works for all UDP, TCP and SCTP based SIP signaling. IPsec may be used to provide authentication, integrity and confidentiality for the transmitted data and supports end-to-end as well as hop-by-hop scenarios. At this time there is no default cipher suite for IPsec defined in SIP. Note that RFC 3261 does not describe a framework for the use of IPsec and no requirement is given as to how the key management is to be realized, or which IPsec header and mode is to be used. One accepted protocol for key management is Internet Key Exchange (IKE), a hybrid protocol based on the Internet Security Association and Key Management Protocol (ISAKMP), the Oakley Key Determination Protocol (RFC 2412) and the Secure Key Exchange Mechanism for the Internet (SKEME). The IKE protocol provides automated cryptographic key exchange and management mechanisms for IPsec. IKE is used to negotiate security associations (SAs) for use with its own key management exchanges (called Phase 1) and for other services such as IPsec (called Phase 2). IKE is particularly used in the establishment of VPNs.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_00635", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-200901022 in Assessing Enhanced Security Requirements for Controlled Unclassified Information? (Part 9) Control PD-200901022: g related to an audited event. | | authentication [FIPS 200, Adapted] | Verifying the identity of a user, process, or device, often as a prerequisite to allowing access to resources in a system. | | availability [44 USC 3552] | Ensuring timely and reliable access to and use of information. | | baseline configuration | A documented set of specifications for a system or a configuration item within a system that has been formally reviewed and agreed on at a given point in time and which can only be changed through change control procedures. | | bidirectional authentication | Two parties authenticating each other at the same time. Also known as mutual authentication or two-way authentication. | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | boundary | Physical or logical perimeter of a system. | |------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | component | See system component. | | confidentiality [44 USC 3552] | Preserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00636", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT) say about Table 13 - Network Security Standards? (Part 29) According to Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT), Table 13 - Network Security Standards: | Recommendation ITU-T X.1362 : Simple encryption procedure for Internet of things (IoT) environments Specifies encryption with associated mask data (EAMD) for the Internet of things devices. It describes EAMD and how it provides a set of security services for traffic using EADM. | Approved Standard | | LoRaWAN | LoRa Alliance | Link layer/Physical Layer LoRaWAN is a wireless protocol for IoT applications that is available in integrated circuits. The protocol specification is built on top of the LoRa technology developed by the LoRa Alliance. It uses unlicensed radio spectrum in the Industrial, Scientific and Medical (ISM) bands to enable low power, wide area, bi-directionally secure communication between remote sensors and gateways connected to the network. | Approved Standard Market Acceptance | | MQTT Link Dec 2015 | MQTT | MQTT is a machine-to-machine (M2M)/' Internet of Things' connectivity protocol. Note: References to other protocols. Authentication of Clients by the Server: Implementations can choose how to make use of the content of these fields. They may provide their own authentication mechanism, use an external authentication such as LDAP or OAuth tokens, or leverage operating system authentication mechanisms. | Guidance Available Approved Standard | | Network Security: Standards that provide security requirements and guidelines on processes and methods for the secure management, operation and use of information, information networks, and their inter-connections. | Network Security: Standards that provide security requirements and guidelines on processes and methods for the secure management, operation and use of information, information networks, and their inter-connections. | Network Security: Standards that provide security requirements and guidelines on processes and methods for the secure management, operation and use of information, information networks, and their inter-connections.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token, sso. Contains security framework guidance for authentication systems. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_00637", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 14) effectiveness of security and privacy controls associated with systems and their environments of operation and to provide credible and meaningful inputs to the organization\u2019s risk management process. A well- executed assessment helps determine the validity of the controls contained in the organization\u2019s security and privacy plans and subsequently employed in organizational systems and environments of operation. Control assessments facilitate a cost-effective approach to managing risk by identifying weaknesses or deficiencies in systems, thus enabling the organization to determine appropriate risk responses in a disciplined manner that is consistent with organizational mission and business needs. SP 800-53A is a companion guideline to [SP 800-53] Security and Privacy Controls for Systems and Organizations. Each publication provides guidance for implementing specific steps in the Risk Management Framework (RMF).1 SP 800-53 and [SP 800-53B] address the Select step of the RMF and provide guidance on security and privacy control selection (i.e., determining the controls needed to manage risks to organizational operations and assets, individuals, other organizations, and the Nation). SP 800-53A addresses the Assess and Monitor steps of the RMF and provides guidance on the security and privacy control assessment processes. SP 800-53A also includes guidance on how to build effective assessment plans and how to analyze and manage assessment results. SP 800-53A provides a process that allows organizations to tailor the assessment procedures outlined in the guidance. Tailoring involves customizing the assessment procedures to match the characteristics of the system and its environment of operation more closely.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, rmf, fips. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00638", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain NISTIR 7511 Revision 3, Security Content Automation Protocol (SCAP) Version 1.2 according to NIST Computer Security Division 2013 Annual Report According to Computer Security Division 2013 Annual Report, NISTIR 7511 Revision 3, Security Content Automation Protocol (SCAP) Version 1.2: Validation Program Test Requirements This report defines the requirements and associated test procedures necessary for products 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).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2013 Annual Report."}]}
{"id": "nist_00639", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SA-12(12) in Security and Privacy Controls for Information Systems and Organizations? (Part 1) Control SA-12(12): INTER-ORGANIZATIONAL AGREEMENTS CRITICAL INFORMATION SYSTEM COMPONENTS IDENTITY AND TRACEABILITY PROCESSES TO ADDRESS WEAKNESSES OR DEFICIENCIES Trustworthiness Criticality Analysis O O O \u221a \u221a \u221a W: Moved to SR Family. W: Moved to SR-5. W: Moved to SR-6. W: Incorporated into SR-3. W: Moved to SR-3(1). W: Moved to SR-3(2). W: Incorporated into SR-5(1). W: Moved to SR-5(2). W: Incorporated into RA-3(2). W: Moved to SR-7. W: Moved to SR-4(3). W: Moved to SR-6(1). W: Moved to SR-8. W: Incorporated into MA-6 and RA-9. W: Moved to SR-4(1) and SR-4(2). W: Incorporated into SR-3. W: Incorporated into SA-8. W: Incorporated into RA-9. CRITICAL COMPONENTS WITH NO VIABLE ALTERNATIVE SOURCING W: Incorporated into SA-20. Development Process, Standards, and Tools QUALITY METRICS SECURITY AND PRIVACY TRACKING TOOLS CRITICALITY ANALYSIS O O O O THREAT MODELING AND VULNERABILITY ANALYSIS W: Incorporated into SA-11(2). ATTACK SURFACE REDUCTION CONTINUOUS IMPROVEMENT AUTOMATED VULNERABILITY ANALYSIS REUSE OF THREAT AND VULNERABILITY INFORMATION USE OF LIVE DATA INCIDENT RESPONSE PLAN ARCHIVE SYSTEM OR COMPONENT MINIMIZE PERSONALLY IDENTIFIABLE INFORMATION Developer-Provided Training Developer Security and Privacy Architecture and Design FORMAL POLICY MODEL SECURITY-RELEVANT COMPONENTS FORMAL CORRESPONDENCE INFORMAL CORRESPONDENCE CONCEPTUALLY SIMPLE DESIGN O O O O W: Incorporated into SA-3(2). O O O O O O O O O O \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a APPENDIX C PAGE 456 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, incident response. Contains technical security guidance that could inform defensive posture. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00640", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols say about 8.2.1.3 KEY-ID? According to Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols, 8.2.1.3 KEY-ID: The key identifier field (KEY-ID) identifies the cryptographic key used to protect the TPDU.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols."}]}
{"id": "nist_00641", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Section 77) establishment transaction. That is, when a key-establishment scheme uses both a static key pair and an ephemeral key pair, they shall be generated using the same set of domain parameters. If p is a prime number, then GF ( p ) denotes the finite field with p elements, which can be represented by the set of integers {0 , 1 , \u2026, p -1}. The addition and multiplication operations for GF ( p ) can be realized by performing the corresponding integer operations and reducing the results modulo p . The multiplicative group of non-zero field elements is denoted by GF ( p ) * . In this Recommendation, an FFC key-establishment scheme requires the use of public keys that are restricted to a (unique) cyclic subgroup of GF ( p ) * with prime order q (where q divides p - 1). If g is a generator of this cyclic subgroup, then its elements can be represented as {1, g mod p , g 2 mod p , \u2026, g q -1 mod p }, and 1 = g q mod p . Domain parameters for an FFC scheme are of the form ( p, q, g {, SEED, counter }), where p is the (odd) prime field size, q is an (odd) prime divisor of p - 1, and g is a generator of the cyclic subgroup of GF ( p ) * of order q . The optional parameters, SEED and counter , are described below. Two classes of domain parameters are approved for FFC key agreement: a class of 'safe' domain parameters that are associated with approved safe-prime groups, and a class of 'FIPS 186 14 -type' domain parameters that conform to one of the FIPS 186-type parametersize sets that are listed in Table 1. The safe-prime groups approved for use by U.S. Government applications are listed in Appendix D. The associated domain parameters have the form ( p , q = ( p - 1)/2, g = 2) for specific choices of p .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}]}
{"id": "nist_00642", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for API Protection for Cloud-Native Systems provide? (Section 21) (e.g., the exact versions of common software being run, internal names of systems for future pivot attacks). Trusting unverified inputs is one of a major class of recurring security bugs in software. There are at least two levels of verification that APIs need to consider: - Validating that the input is syntactically correct - Ensuring that valid input is not malicious A service must validate that each request (i.e., input) matches the API's definition, all expected fields are present and of the correct type, and no unexpected fields are present. For example, an API definition may say, 'The 'name' field is required and must be a non-empty string less than 100 characters long,' which must be verified at runtime on every request. The lack of input validation results in a variety of risks, including: - Impacting the availability of APIs - o The 'query of death' (QoD) [24] is a DoS attack via specially crafted requests that trigger pathological worst-case behavior in the server (i.e., the server itself may crash due to bad input handling). - Invalid or malicious data being stored in the system, which can cause latent issues (e.g., failure to restart during recovery, crashes when accessing invalid records) - Unanticipated error handling during request processing, which leaks internal information While the input may satisfy 'syntactic' validation, it also needs to be verified as non-malicious before it is used. Malicious input is any input that is syntactically valid but attempts to get the system to misbehave, potentially in a way that can be exploited to trigger an attack. Extending the 'name' example above, a caller may send a request that contains a name field with a string less than 100 characters (i.e., valid), but that string may be a Structured Query Language (SQL) injection attack.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for API Protection for Cloud-Native Systems."}]}
{"id": "nist_00643", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-3 in Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders? (Part 28) Control AC-3: ator is registered with an RP, a new key pair is created and associated with the RP's application ID, which is derived from the domain name in the URL where the registration transaction was initiated. During authentication, the application ID is again derived from the URL of the page that is requesting authentication, and the authenticator will sign the authentication challenge only if a key pair has been registered with the matching application ID. The FIDO Facet specification enables sites to define a list of domain names that should be treated as a single application ID to accommodate service providers that span multiple domain names, such as google.com and gmail.com. The application ID verification effectively prevents the most common type of phishing attack, in which the attacker creates a new domain and tricks users into visiting that domain instead of an intended RP where the user has an account. For example, an attacker might register a domain called 'googleaccts.com' and send emails with a pretext to get users to visit the site, such as a warning that the user's account will be disabled unless some action is taken. The attacker's site would present a login screen identical to Google's login screen to obtain the user's password (and OTP, if enabled) credentials and to use them to impersonate the user to the real Google services. With FIDO, the authenticator would not have an existing key pair registered under the attacker's domain, so the user would be unable to return a signed FIDO challenge to the attacker's site. If the attacker could convince the user to register the FIDO authenticator with the malicious site and then sign an authentication challenge, the signed FIDO assertion could not be used to authenticate to Google because the RP can also verify the application ID associated with the signed challenge, and it would not be the expected ID.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, single sign-on, sso. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_00644", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Head Start on Assurance_ Proceedings of an Invitational Workshop on Information Technology (IT) Assurance and Trustworthiness, March 21-23, 1994 say about ATTENDEES? (Part 3) According to A Head Start on Assurance_ Proceedings of an Invitational Workshop on Information Technology (IT) Assurance and Trustworthiness, March 21-23, 1994, ATTENDEES: la -Dave t, KY 14850 (^7)277.20*20 Jwi^di4oof*&gt; com \u20aci7\\Kkl MTTE6Ciiif5Pr*i\u00ab' ^5 Coh^-itt ^UlxatK V;\\;i|l m^oOs^ :. ruc MvrEJb.edf|i^i^ B S ' I i'rev'&amp;:^afeVi-&gt;ffc &lt;Of\u00abs orR. ' [ViliSDO, UK '\u00ab4\u00abM ' = : : . ''' gfe|tt\u00bb^'W|t || '''BE S' A. t&lt;Ni Stlo^fntS t1to':\u00bb\u00bbv{ 63^? I i22 &gt;!4J^.Jif|j|(t^^^^ absRIaol BUugl&amp;MgBto# i f wttf^O snO OCEOr \u00bb, ^g^uvi 00i!0iitv (01&gt;&gt; WKf3.t\u00bb\u00ab.\u00bb\u00abW'?ri5\u00ab ,Wmriw|5Cl oco^AVjijihm^ tK i\u00bbb0 ijnx^iirfbciw dd.u^ ^ -awmiE md OdOt CIM ',^&gt;OOwo5^ moo.8i}'\u00bbTO\u00bb? isi^ $bui&amp;Z}0 \u00bb2u4ttrsl tendifeH \" \u00bb vioJoftflDoT cckiik\u00bbx.mm (m .^w4t\u00bb(iji^ vlsS'C ,*' ' SS3* W44fl VT}gi\u00a3in,ti:^^ ^ &gt; K\u2122 ^ ' Y^ biin^a I22DE P ; i*: 'g", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Head Start on Assurance_ Proceedings of an Invitational Workshop on Information Technology (IT) Assurance and Trustworthiness, March 21-23, 1994."}]}
{"id": "nist_00645", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Operational Technology (OT) Security provide? (Section 181) t can be handed out by a receptionist \u2022 Denying needed access to the OT system because of a temporary inability of the sensing device to acknowledge a legitimate user \u2022 Being socially acceptable. Users consider some biometric authentication devices more acceptable than others. For example, retinal scans may be considered very low on the scale of acceptability, while thumbprint scanners may be considered high on the scale of acceptability. Users of biometric authentication devices will need to take social acceptability for their target group into consideration when selecting among biometric authentication technologies. When token-based access control employs biometric verification, the access control system should conform to the requirements of NIST SP 800-76-2 [SP800-76-2]. OT-Specific Recommendations and Guidance While biometrics can provide a valuable authentication mechanism, organizations may need to carefully assess the technology for use with 104 NIST SP 800-82r3 September 2023 Guide to Operational Technology (OT) Security industrial applications. Physical and environmental issues within OT environments may decrease the reliability of biometric authorized authentication. Organizations may need to coordinate with system vendors or manufacturers regarding their specific physical and environmental properties and biometric authentication requirements. 6.2.1.4.3. Smart Card Authentication Smart cards come in a variety of form factors, from USB devices to embedded chips on cards the size of credit cards that can be printed and embossed. Smart cards can be customized, individualized, and issued in-house or outsourced to service providers who manufacture hundreds or thousands per day.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, token. Contains security framework guidance for authentication systems. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_00646", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.3 Implementation according to NIST 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings According to 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings, 2.3 Implementation: While there is no requirement to do so, the 'obvious' way to implement a site SLCS is via MyProxy [14]. We discuss the MyProxy solution further in this section, but it is also worth mentioning Microsoft's Windows Server 2003 which also contains features to run a CA, but will not, as far as the authors are aware, be able to contact an external VO attribute server to add attributes to the certificates. By using MyProxy we can bridge many of the site authentication infrastructures in use to the GSI/PKI world. MyProxy can be configured to provide certificates generated by an internal or external CA. We can also support advanced users who have long-term certificates by enabling them to upload proxies generated from their certificates (they are not permitted to upload the certificates and private keys themselves, by the CA's policy). This was the approach taken in the ShibGrid project [18]; see also Shibboleth discussion in section 2.7. For users who do not have long-term certificates, the service generates short term certificates and keys. MyProxy can also support SASL [12] (allowing Kerberos [19] authentication), PAM (allowing LDAP [29], RADIUS[16] and many other authentication systems) and PubCookie. Although it is simple to use the MyProxy command-line tools to leverage this functionality, this could potentially present users with quite a barrier to overcome. Many of the target audience traditionally balk at security in general, certificates in particular, and anything that cannot be clicked with a mouse. Therefore, we aim to simplify the process as much as possible, and hide the certificate/proxy process. For our own site's authentication infrastructure, Microsoft Active Directory (which happily, for the purposes of this work, is", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_00647", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Small Business Information Security_ The Fundamentals provide? (Section 5) | 6 | | | 2.1 | ELEMENTS OF RISK .......................................................................................................................6 | | | | 2.2 | MANAGING YOUR RISKS ................................................................................................................8 | | | | | \u2022 Identify what information your business stores and uses ...............................................8 | | | | | \u2022 Determine the value of your information........................................................................8 | | | | | \u2022 Develop an inventory.....................................................................................................10 | | | | | \u2022 Understand your threats and vulnerabilities.................................................................11 | | | | 2.3 | WHENYOUNEED HELP ................................................................................................................14 | | | 3 | SAFEGUARDING YOUR INFORMATION...................................................................................................15 | SAFEGUARDING YOUR INFORMATION...................................................................................................15 | | | | 3.1 IDENTIFY ...................................................................................................................................16 | 3.1 IDENTIFY ...................................................................................................................................16 | | | | | \u2022 Identify and control who has access to your business information...............................16 | | | | | \u2022 Conduct Background Checks..........................................................................................16 | | | | | \u2022 Require individual user accounts for each employee.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Small Business Information Security_ The Fundamentals."}]}
{"id": "nist_00648", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PA-220 in Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)? (Part 181) Control PA-220: ented the reference design, or have questions about applying it in your environment, please email us at mobile-nccoe@nist.gov. All comments are subject to release under the Freedom of Information Act. National Cybersecurity Center of Excellence National Institute of Standards and Technology 100 Bureau Drive Mailstop 2002 Gaithersburg, MD 20899 Email: nccoe@nist.gov ## NATIONAL CYBERSECURITY CENTER OF EXCELLENCE The National Cybersecurity Center of Excellence (NCCoE), a part of the National Institute of Standards and Technology (NIST), is a collaborative hub where industry organizations, government agencies, and academic institutions work together to address businesses' most pressing cybersecurity issues. This public-private partnership enables the creation of practical cybersecurity solutions for specific industries, as well as for broad, cross-sector technology challenges. Through consortia under Cooperative Research and Development Agreements (CRADAs), including technology partners-from Fortune 50 market leaders to smaller companies specializing in information technology security-the NCCoE applies standards and best practices to develop modular, adaptable example cybersecurity solutions using commercially available technology. The NCCoE documents these example solutions in the NIST Special Publication 1800 series, which maps capabilities to the NIST Cybersecurity Framework and details the steps needed for another entity to re-create the example solution. The NCCoE was established in 2012 by NIST in partnership with the State of Maryland and Montgomery County, Maryland. To learn more about the NCCoE, visit To learn more about NIST, visit https://www.nist.gov. ## NIST CYBERSECURITY PRACTICE GUIDES NIST Cybersecurity Practice Guides (Special Publication 1800 series) target specific cybersecurity challenges in the public and private sectors.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_00649", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Email according to Blockchain Networks_ Token Design and Management Overview? Email: blockchain-token-paper@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain Networks_ Token Design and Management Overview."}]}
{"id": "nist_00650", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Zero Trust Architecture provide? (Section 110) tener acceso a los tokens y dispositivos de la empresa, lo que afectar\u00eda a la velocidad y eficacia de los procesos empresariales. - [1] Cam-Winget N. (ed.), Appala S., Pope S., Saint-Andre P. (2019). Using Extensible Messaging and Presence Protocol (XMPP) for Security Information Exchange. (Internet Engineering Task Force (IETF)), IETF Solicitud de observacioines ( Request for Comments RFC) 8600. https://doi.org/10.17487/RFC8600 - [2] Software Defined Perimeter Working Group \u00abSDP Specification 1.0\u00bb. (2014). Cloud Security Alliance. - [3] Stanton B., Theofanos M. F., Spickard Prettyman S., Furman S. (2016). Security Fatigue. IT Professional 18(5): 26-32. https://doi.org/10.1109/MITP.2016.84 - [4] Strouble D., Shechtman G. M., Alsop A. S. (2009). Productivity and Usability Effects of Using a Two-Factor Security System. SAIS 2009 Proceedings (AIS, Charleston, SC), p. 37. Disponible en http://aisel.aisnet.org/sais2009/37 - [5] Weidman J., Grossklags J. (2017). I Like It but I Hate It: Employee Perceptions Towards an Institutional Transition to BYOD Second-Factor Authentication. Proceedings of the 33rd Annual Computer Security Applications Conference (ACSAC 2017) (ACM, Orlando, FL), pp. 212-224. ", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Zero Trust Architecture."}]}
{"id": "nist_00651", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain CONTACT: according to NIST Computer Security Division 2014 Annual Report According to Computer Security Division 2014 Annual Report, CONTACT:: Mr. Andrew Regenscheid (301) 975-5155 andrew.regenscheid@nist.gov <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_00652", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security say about 2.4 Summary of Key Recommendations? (Part 1) According to Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security, 2.4 Summary of Key Recommendations: 2.4 Summary of Key Recommendations The following list presents some of the key recommendations from this section of the document. - \uf03c To support confidentiality, integrity, and availability, all of the components of telework and remote access solutions, including client devices, remote access servers, and internal servers accessed through remote access, should be secured against a variety of threats. (Section 2.1) - \uf03c Before designing and deploying telework and remote access solutions, organizations should develop system threat models for the remote access servers and the resources that are accessed through remote access. (Section 2.1) - \uf03c 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. (Section 2.1) 15 A similar network can be set up for third-party-controlled devices if desired, or the same network used for both BYOD and third-party-controlled devices. However, often this is not necessary because there are already contractual agreements and technical checks in place to ensure that these devices are secured in accordance with the organization's policies. - \uf03c Organizations should plan their remote access security on the assumption that the networks between the telework client device and the organization cannot be trusted. (Section 2.1) - \uf03c Organizations should assume that client devices will become infected with malware and plan their security controls accordingly. (Section 2.1) - \uf03c Organizations should carefully consider the balance between the benefits of providing remote access to additional resources and the potential impact of a compromise of those resources.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security."}]}
{"id": "nist_00653", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Web Transactions_ TLS Server Certificate Management say about Appendix C Mapping to the Cybersecurity Framework? (Part 8) According to Securing Web Transactions_ TLS Server Certificate Management, Appendix C Mapping to the Cybersecurity Framework: | NIST SP 800-53 Rev. 4 | NIST SP 800- 181 Work Roles | |------------------------------------|----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Protect (PR) | Identity Management, Authentication and Access Control (PR.AC) | PR.AC-1: Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users, and processes.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, identity management. Contains security framework guidance for authentication systems. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_00654", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to NIST Test Personal Identity Verification (PIV) Cards Version 2? http: //smime2.nist.gov/PIVTest/RSA2048CA.crl ldap://smime2.nist.gov/cn=Test%20RSA%202048-", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_00655", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance say about Media Protection? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance, Media Protection: Media protection solutions enable a manufacturer to restrict the use of portable media within the manufacturing system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance."}]}
{"id": "nist_00656", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DR-1 in Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events? (Part 102) Control DR-1: , read and click I accept the license terms. <!-- image --> <!-- image --> 8. Click Next. 9. In the Install Rules section, note and resolve any further conflicts. <!-- image --> 10. Click Next. 11. In the Setup Role section, select SQL Server Feature Installation. 12. Click Next. 13. In the Feature Selection section, select the following: - a. Database Engine Services - b. Client Tools Connectivity - c. Client Tools Backwards Compatibility - d. Client Tools SDK - e. Management Tools - Basic - f. Management Tools - Complete - g. SQL Client Connectivity SDK - h. Any other desired features <!-- image --> <!-- image --> 14. Click Next. 15. In the Instance Configuration section, select Default instance. <!-- image --> 16. Click Next. 17. In the Server Configuration section, click Next. 18. In the Database Engine Configuration section, make sure Mixed Mode is selected. 19. Add all desired users as Administrators under Specify SQL Server Administrators by pressing Add Current User. - a. For Domain accounts, type in $DOMAINNAME\\$USERNAME into Enter the object names to select textbox. - b. Click OK. - c. For local computer accounts, click on locations and select the computer's name. - d. Click OK. - e. Type the username into the Enter the object names to select textbox. - f. Once you are finished adding users, click Next. <!-- image --> <!-- image --> 20. In the Ready to install section, verify the installation and click Install. <!-- image --> 21. Wait for the install to finish. 22. Click Close. <!-- image --> ## 2.4.2 Open Port on Firewall 1. Open Windows Firewall with Advanced Security. <!-- image --> 2. Click Inbound Rules. 3. Click New Rule. <!-- image --> 4. Select Port. 5. Click Next. 6. Select TCP and Specific local ports. 7. Type 1433 into the text field. 8. Click Next. 9. Select Allow the connection. <!-- image --> <!-- image --> 10. Click Next. 11. Select all applicable locations. <!-- image --> 12. Click Next. 13. Name the rule Allow SQL Access.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events."}]}
{"id": "nist_00657", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cell Phone Forensic Tools_ an Overview and Analysis Update provide? (Section 143) ults from applying the scenarios listed at the left of the table to the devices across the top. Additional information can be found in NISTIR 7250 Cell Phone Forensic Tools: An Overview and Analysis . Table 30: SIM Card Results Matrix - External Reader | | SIM | SIM | SIM | |-----------------------|-------|-------|-------| | Scenario | 5343 | 8778 | 1144 | | Basic Data | Meet | Below | Below | | Location Data | Meet | Meet | Meet | | EMS Data | Meet | Meet | Meet | | Foreign Language Data | Meet | Meet | Meet | Quantaq's USIMdetective version 1.3.1 19 can acquire information from SIM cards via a PC/SCcompatible reader. The USIMdetective software provides examiners with the ability to acquire, examine and generate customized reports including data such as the Card Identity (ICCID), Stored Dialing Numbers (ADN), Fixed Dialing numbers (FDN), Subscriber Number (MSISDN), Last Numbers Dialed (LND), SMS and EMS Messages, Subscriber Identity (IMSI), Ciphering Key (Kc) and Location Information (LOCI). Once proper connectivity is established with the SIM, the examiner is prompted for the correct PIN, if the SIM is protected, before acquisition begins. If the SIM does not contain a PIN acquisition begins by clicking OK as illustrated below in Figure 51. Figure 51: Acquisition Wizard <!-- image --> After a successful acquisition, the entire SIM contents can be saved and stored in USIMdetective's proprietary format for later processing. USIMdetective uses an internal hashing facility to ensure the integrity of case data and detect whether tampering occurred during storage. USIMdetective uses SHA1 and MD5 integrity checks to ensure that the original file is consistent with the reopened case file. Figure 52 provides a snapshot of the User Interface, which provides the examiner with a self-explanatory interface to supported functions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis Update."}]}
{"id": "nist_00658", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to SSL VPNs say about 3.6 Summary? (Part 2) According to Guide to SSL VPNs, 3.6 Summary: best product it is recommended to identify the remote access needs and the applications that require remote access. - \u0084 Each SSL VPN supports different protocols via proxy and application translation. In addition, some SSL VPN products have concentrated their efforts and expertise in supporting certain protocols and applications. It is crucial to make sure that the SSL VPN provides the necessary proxies and application translators for the applications that require remote access. - \u0084 SSL VPN manageability features such as status reporting, logging, and auditing should provide adequate capabilities for the organization to effectively operate and manage the SSL VPN and to extract detailed usage information. - \u0084 The SSL VPN high availability and scalability features should support the organization's requirements for failover, load balancing, and throughput. State and information sharing is recommended to keep the failover process transparent to the user. - \u0084 SSL VPN portal customization should allow the organization to control the look and feel of the portal and to customize the portal to support various devices such as PDAs and smart phones. - \u0084 SSL VPN authentication should provide the necessary support for the organization's current and future authentication methods and to leverage existing authentication databases. SSL VPN authentication should also be tested to ensure interoperability with existing authentication methods. - \u0084 Some organizations, such as Federal agencies, have strict requirements for encryption and integrity protection. SSL VPNs should support the required algorithms for symmetric encryption, key exchange, and hash functions. All cryptographic algorithms and modules must be FIPS-approved. - \u0084 SSL VPNs should be evaluated to ensure they provide the level of granularity needed for access controls. Access controls should be capable of applying permissions to users, groups, and resources, as well as integrating with endpoint security controls.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Guide to SSL VPNs."}]}
{"id": "nist_00659", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain CIPSO LABEL FORMAT according to NIST Standard Security Label for GOSIP_ an Invitational Workshop According to Standard Security Label for GOSIP_ an Invitational Workshop, CIPSO LABEL FORMAT: | 8 bits | 8 bits | 32 bits | 8 bits | 8 bits | ? bits | 8 bits | 8 bits | ? bits | |---------------|---------------|----------------------|----------|------------|-----------|----------|------------|------------| | 134 | 6-40 | 1 \u2022 OxffTfffff 1-255 | 1-34 | ? | \u2022 \u2022 \u2022 | 1-255 | 1-34 | \u2022 | | option number | option length | DOI | Ug id | tag length | info (kid | tag id | tag length | info field |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Standard Security Label for GOSIP_ an Invitational Workshop."}]}
{"id": "nist_00660", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain CRL Distribution Points : according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, CRL Distribution Points :: ldap://smime2.nist.gov/cn=Test%20ECC%20P- 256%20CA%20for%20Test%20PIV%20Cards,ou=Test%20CA,o=Test%20Certificates%2 02010,c=US?certificateRevocationList;binary", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_00661", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Category according to Guidelines for Smart Grid Cybersecurity? Category: Common Technical Requirements", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_00662", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PS-201 in Trustworthy Email? (Part 73) Control PS-201: xt mail messages are submitted by a sender, transmitted hop-by-hop over a series of relays and delivered to a receiver. Any successful man-in-themiddle can intercept such traffic and read it directly. Any bad actor, or organizationally privileged actor, can read such mail on the submission or delivery systems. Email transmission security can be assured by encrypting the traffic along the path . \ufffde Transport Layer Security protocol (TLS) [RFC5246] protects confidentiality by encrypting bidirectional traffic and prevents passive monitoring. TLS relies on public key cryptography and uses X.509 certificates [RFC5280] to encapsulate the public key, and the Certificate Authority (CA) system to issue certificates and authenticate the origin of the key . In recent years the CA system has become the subject of attack and has been successfully compromised on several occasions. 1718 \ufffde DANE protocol [RFC6698] is designed to overcome problems in the CA system by providing an alternative channel for authenticating public keys using DNSSEC. \ufffd e result is that the same trust relationships used to certify IP addresses can be used to certify servers operating on those addresses the mechanisms that combine to improve the assurance of email transmission security are described in section 5.2. Encryption at the transport layer gives assurance of the integrity of data in transit, but senders and receivers who want end-to-end assurance, (i.e., mailbox to mailbox) of confidentiality have two alternative mechanisms for achieving this: S/MIME [RFC5750] and OpenPGP [RFC4880]. Both protocols are capable of signing (for authentication) and encryption (for confidentiality) . \ufffde S/MIME protocol is deployed to sign and/or encrypt message contents, using keys stored as X.509 certificates and a PKI (See Section 2.4.2) while OpenPGP uses a different certificate and a Web-of-Trust model for authentication of identities (See Section 2.4.3).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, certificate authority. Contains security framework guidance for authentication systems. Source: Trustworthy Email."}]}
{"id": "nist_00663", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Blockchain for Access Control Systems provide? (Section 27) ty, and processing speed, and it is often impossible to store extensive interaction history or employ heavy-weight security functions (e.g., microservice of mesh service for SecDevOps implementation). General AC management requirements, such as allowing runtime policy rule changes and policy administration delegation, may further complicate the design of the blockchain AC system, especially the consensus mechanisms and smart contract functions [IR7874]. Any vulnerability of a blockchain AC system on the level of the entire system or an underlying function of a smart contract can be hacked (e.g., reentrancy vulnerability) or misused. For instance, the publicly available smart contract's byte code might generate erroneous system state data that will be securely logged on the blockchain. The only way to fix errors is to delete, correct, and redeploy the entire smart contract. Thus, it is necessary for smart contracts to be correctly deployed (i.e., they work as intended by the developer and cannot be exploited by attackers). Optimizing smart contract codes can effectively reduce potential vulnerabilities and ensure the efficient execution of contracts. For instance, running smart contracts in parallel can speed up contract execution but requires the consideration of how to execute contracts that depend on each other at the same time (especially for dynamic AC policy models). Further, smart contracts might require communicating with out-of-chain services, such as receiving AC data from a PIP host, and rely on the oracle of off-chain resources from trusted third parties to retrieve the data and then push them to the blockchain at predetermined times. Although existing oracles are well-tested, their use may introduce a potential point of failure (e.g., an oracle might be unable to push out or provide erroneous data) [KLG].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Blockchain for Access Control Systems."}]}
{"id": "nist_00664", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Federal S_MIME V3 Client Profile say about 2.2.1 Sending Signed Messages? According to Federal S_MIME V3 Client Profile, 2.2.1 Sending Signed Messages: - S/MIME implementations MUST be able to generate SignerInfo including signed attributes. - S/MIME implementations MUST be able to generate SMIMECapabilities and signingTime attributes. - S/MIME implementations SHOULD be able to generate signingCertificate attributes. - S/MIME implementations MUST be able to include user certificates and appropriate CRLs. - S/MIME implementations MUST be able to generate multipart/signed (i.e., \"clear\") messages. - S/MIME implementations MUST be able to request return signed receipt messages (as specified in [RFC 2634]) where the receipt goes to the message originator. (Requesting a return signed receipt where the receipt is directed to a third party is out of scope for this profile, and thus claims to conformance will not be tested. However, correctly responding to the reception of such a signed receipt request is required, as stated in Clause 2.3.2)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Federal S_MIME V3 Client Profile."}]}
{"id": "nist_00665", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 9.4 Security Testing Mail Servers according to NIST Guidelines on Electronic Mail Security According to Guidelines on Electronic Mail Security, 9.4 Security Testing Mail Servers: Periodic security testing of public mail servers is critical. 64 Without periodic testing, there is no assurance that current protective measures are working or that the security patch just applied by the m server administrator is functioning as advertised. Although a variety of security testing techniques e vulnerability scanning is the most common. Vulnerability scanning assists a mail server administrator in identifying vulnerabilities and verifying whether the existing security measures are effective. Penetration testing is also used, but less frequently and usually only as part of an overall penetration test of the organization's network. ail xists, 65", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, penetration test. Contains technical security guidance that could inform defensive posture. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_00666", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices say about Confidentiality? According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Confidentiality: The confidentiality impact level is the effect of unauthorized disclosure of subsidies information on the ability of responsible agencies to pay government funds to affect the production or prices of various goods to benefit the public benefit. In many cases, unauthorized disclosure of subsidies information will have only a limited adverse effect on agency operations, assets, or individuals. Special Factors Affecting Confidentiality Impact Determination : Some information associated with applications for subsidies includes information covered by the provisions of the Privacy Act of 1974. (The Privacy Act Information provisional impact levels are documented in the Personal Identity and Authentication information type.) Unauthorized disclosure of large volumes of information protected under the Privacy Act can be expected to have a serious effect on public confidence in the agency. Also, premature unauthorized disclosure of planned subsidies policies can affect financial/commodities markets, with associated potential adverse effects on the U.S. economy and serious adverse effects on public confidence in the agency. This can result in assignment of a moderate impact level to such information. Recommended Confidentiality Impact Level : The provisional confidentiality impact level recommended for most subsidies information is low .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_00667", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? (Part 42) Control HA-1: cate. In this case the attribute certificate holds the serial number and issuer name of the user's public key certificate e.g. {x509serialNumber=123456 + x509issuer = {OU=Some CA, O=Some Org, C=US}. The limitations of this method are that the user must be PKI enabled, which of course, many are not; and that, depending upon the contents of the user's public key certificate, the user might be identified via this. Finally, the holder can be identified indirectly by reference to the hash of a public key that they hold. This is now effectively a random number, giving good privacy protection. The user can prove ownership of the attribute certificate by digitally signing a challenge provided by the origin authentication server, which can then provide this AC to the target site. The restrictions are that the user needs to be using some form of asymmetric cryptography, has generated their own private/public key pair, has created a self signed certificate with a random DN and does not have a corresponding X.509 public key certificate identifying him/her. The main limitation from a privacy perspective is that the target site can profile the user, without knowing the actual identity of the user, since the same public key hash is used each time. In all these cases there is a trade-off between the 'degree of anonymity' and the 'quality of issuance'. At one extreme we have dynamically generated Shibboleth short lived signed SAML attribute assertions that ## 4th Annual PKI R&amp;D Workshop -- Proceedings provide anonymity but require a trusted directory to store the user's attributes. At the other extreme we have long lived ACs where each attribute authority can issue its own attributes in a controlled manner, but without any privacy protection.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_00668", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.9.3.2 OCC Reset according to NIST Personal Identity Verification (PIV) of Federal Employees and Contractors According to Personal Identity Verification (PIV) of Federal Employees and Contractors, 2.9.3.2 OCC Reset: Both fingerprints used for OCC SHALL be replaced during an OCC reset. OCC reset MAY be performed in person at an issuing facility or a supervised remote identity proofing station:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Personal Identity Verification (PIV) of Federal Employees and Contractors."}]}
{"id": "nist_00669", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Section 288) nding on how security and privacy responsibilities are allocated organization-wide. Common control providers may be system owners when the common controls are resident within an organizational system. 119 A privacy program plan is a formal document that provides an overview of an agency's privacy program, including a description of the structure of the privacy program; the role of the senior agency official for privacy and other privacy officials and staff; the strategic goals and objectives of the privacy program; the resources dedicated to the privacy program; and the program management controls and common controls in place or planned for meeting applicable privacy requirements and managing privacy risks. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ has oversight responsibility for common controls in place or planned for meeting applicable privacy requirements and managing privacy risks and is responsible for assessing those controls. At the discretion of the organization, privacy controls that are designated as common controls may be assessed by an independent assessor. In all cases, however, the senior agency official for privacy retains responsibility and accountability for the organization's privacy program, including any privacy functions performed by independent assessors. Privacy plans and privacy control assessment reports are made available to systems owners whose systems inherit privacy controls that are designated as common controls.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, fips, security control. General security reference material without sensitive content. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_00670", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Checklist according to Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements? Checklist: A document that contains instructions or procedures for configuring an IT product to an operational environment, for verifying that the product has been configured properly, and/or for identifying unauthorized configuration changes to the product. Also referred to as a security configuration checklist, lockdown guide, hardening guide, security guide, security technical implementation guide (STIG), or benchmark.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements."}]}
{"id": "nist_00671", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Related Controls according to NIST_SP_800-53r5_Security_Privacy_Controls? Related Controls: AC-3, AU-2, AU-6, AU-9, AU-12, PE-3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00672", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Training & Awareness Course Compendium provide? (Section 100) disaster recovery plan design using project teams, the selection of alternative procedures, and basic documentation standards. Class participation and team utilization of concepts will be emphasized. Upon completion of the course, participants will be able to apply improved project and time management skills for managing the planning project, use improved verbal and written communications skills and techniques to communicate with organization management and disaster recovery teams, develop the basic design of the disaster recovery plan, produce standardized documentation of the plan, and use improved management report presentation techniques and skills to assist in gaining plan approval. COURSE TITLE: Implementing and Testing the Disaster Recovery Plan COURSE LENGTH: 2.5 DAYS Disaster Recovery Institute 1810 Craig Road, Suite 213 St. Louis, MO 63146-4761 Bill Langendoerfer: (314) 434-2272 This course is designed for those who have limited experience in the area of disaster recovery planning. It was developed for prospective contingency planners, operations managers, data communications managers, disaster planning and recovery team members, and others who will be involved in the development or management of the contingency planning and recovery functions. The course will prepare participants to develop the detailed procedures within the disaster recovery plan and be prepared to teach those procedures when training other disaster recovery teams. Other topics to be explored include the development of a testing and assessment program, as well as periodic maintenance of the plan. Class participation and team utilization of concepts will be emphasized.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Computer Security Training & Awareness Course Compendium."}]}
{"id": "nist_00673", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Report on the Privilege (Access) Management Workshop provide? (Section 13) report, work needs to be done to formalize any terminology beyond that being proposed by organized committees such as the Identity, Credential, and Access Management (ICAM) Subcommittee and the AASC. To have a clear notion of the meaning and scope of privilege management, we start by considering how access control works at a high level, as shown in Figure 1. Figure 1. High-Level View of Access Control <!-- image --> Figure 2 depicts the real-time framework for access control in more detail, introducing terminology that is used in this report. Figure 2. High-Level View of Real-Time Access Control <!-- image --> In Figure 2, the Access Controller of Figure 1 is split into two parts-Policy Enforcement Point and Policy Decision Point-and Attribute and Policy Information replaces Access Control Data. The meanings of the Policy Enforcement Point and Policy Decision Point (as described in Annex A: Authorization and Attributes Glossary) are as follows: - \uf0b7 Policy Decision Point (PDP): A system entity that makes authorization decisions for itself or for other system entities that request such decisions. - \uf0b7 Policy Enforcement Point (PEP): A system entity that requests and subsequently enforces authorization decisions . 'Attribute and policy information' is being used in a very general sense and is intended to have the same scope as access control data. Thus, it includes any form of information that can be used for access control. For example, it includes traditional access control lists (ACLs.) For an ACL, the attribute might be a group or user name while the policy 2 is implicit. In this context, 'policy' denotes digital policy-policy that can be processed by computer. The rationale for this scope of the terminology is to enable discussion without having to deal with the details of the many forms of access control data, while at the same time distinguishing the main categories of access control data-attributes and policies. A user is a person, process, or device.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: A Report on the Privilege (Access) Management Workshop."}]}
{"id": "nist_00674", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AU-16(3) in NIST_SP_800-53r5_Security_Privacy_Controls? Control AU-16(3): STORE ON COMPONENT WITH DIFFERENT OPERATING SYSTEM Non-repudiation ASSOCIATION OF IDENTITIES VALIDATE BINDING OF INFORMATION PRODUCER IDENTITY CHAIN OF CUSTODY VALIDATE BINDING OF INFORMATION REVIEWER IDENTITY DIGITAL SIGNATURES Audit Record Retention LONG-TERM RETRIEVAL CAPABILITY Audit Record Generation SYSTEM-WIDE AND TIME-CORRELATED AUDIT TRAIL STANDARDIZED FORMATS CHANGES BY AUTHORIZED INDIVIDUALS QUERY PARAMETER AUDITS OF PERSONALLY IDENTIFIABLE INFORMATION Monitoring for Information Disclosure USE OF AUTOMATED TOOLS REVIEW OF MONITORED SITES UNAUTHORIZED REPLICATION OF INFORMATION Session Audit SYSTEM START-UP CAPTURE AND RECORD CONTENT REMOTE VIEWING AND LISTENING Alternate Audit Logging Capability Cross-Organizational Audit Logging IDENTITY PRESERVATION SHARING OF AUDIT INFORMATION DISASSOCIABILITY \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a \u221a O S S S O/S S W: Incorporated into SI-7. O O S S S S S O O/S O O/S S S W: Incorporated into AU-14. S W: Moved to AU-5(5). O O O O APPENDIX C PAGE 435 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ TABLE C-4: ASSESSMENT, AUTHORIZATION, AND MONITORING FAMILY CONTROL NUMBER CONTROL NAME CONTROL ENHANCEMENT NAME IMPLEMENTED BY ASSURANCE", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00675", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CA-6 in NIST_SP_800-53r5_Security_Privacy_Controls? (Part 3) Control CA-6: cess. The intra-organization joint authorization process is most relevant for connected systems, shared systems, and systems with multiple information owners. T h s i p u b Related Controls: AC-6. (2) AUTHORIZATION | JOINT AUTHORIZATION \u2014 INTER-ORGANIZATION l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I Employ a joint authorization process for the system that includes multiple authorizing officials with at least one authorizing official from an organization external to the organization conducting the authorization. Discussion: Assigning multiple authorizing officials, at least one of whom comes from an external organization, to serve as co-authorizing officials for the system increases the level of independence in the risk-based decision-making process. It implements the concepts of separation of duties and dual authorization as applied to the system authorization process. Employing authorizing officials from external organizations to supplement the authorizing official from the organization that owns or hosts the system may be necessary when the external organizations have a vested interest or equities in the outcome of the authorization decision. The inter-organization joint authorization process is relevant and appropriate for connected systems, shared systems or services, and systems with multiple information owners. The authorizing officials from the external organizations are key stakeholders of the system undergoing authorization. Related Controls: AC-6. References: [OMB A-130], [SP 800-37], [SP 800-137].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00676", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Information Security Handbook_ A Guide for Managers say about Acknowledgements? According to Information Security Handbook_ A Guide for Managers, Acknowledgements: NIST would like to 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. The 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: Ron Ross, Tim Grance, and Marianne Swanson, NIST. Nadya Bartol, Joe Nusbaum, Laura Prause, Will Robinson, Karen Kent, and Randy Ewell, BAH, In addition, special thanks are due those contractors who helped craft the Handbook, prepare drafts, and review materials: Nadya 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_00677", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report_ Authentication Diary Study say about IV. Coping mechanisms? (Part 17) According to Report_ Authentication Diary Study, IV. Coping mechanisms: my RSA token, I am likely to just scribble a note on a piece of paper and remember it the next day, hopefully. So, it definitely changes my behavior. That's a good question. I had not thought of that. Same thing, like it makes me less likely to, if I'm at the airport and I close my laptop to go to the restroom or whatever, and I have 15 minutes before the plane's going to board or 10 minutes or something like that, if I have to re-authenticate and dig out that RSA token, again, then it'll make me less likely to take advantage of just a few minutes because it's that, again that kind of level of effort. [\u2026] I mean if there's something I have to get done, then of course, I will do it. But, as far as, \"Oh, let me just taking advantage of every last second,\" you're less likely to do that because there's a cost associated with taking advantage of that time. [\u2026] We know people are sensitive to small, local costs and when I hear myself describing the fact that, oh, well me going upstairs to get the thing is going to prevent me from doing one e-mail, it sounds kind of silly, but that's what happens.' (P11) - 'Well, let's say I'm working on a Word document and I have to refer to somebody's e-mail just to see one of their comments or an attachment of something I sent myself or somebody sent me. I'd have to really stop my work for five minutes. And if I'm on a roll with something, it's\u2026 [\u2026] Yeah. It just breaks everything. So instead of having to stop, go do this and then come back, and then try and get back in the flow of things, I'll just keep going. I'll just skip it and maybe come back later. [...] Every time I do that and wait for incentives here to check my e-mail, I'll get like five or six e-mails that probably people would have preferred a more immediate response.' (P19) - B. Authentication's unintended effects on work habits &gt; Doing things less frequently 1.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token, sso. Contains security framework guidance for authentication systems. Source: Report_ Authentication Diary Study."}]}
{"id": "nist_00678", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Managing Information Security Risk_ Organization, Mission, and Information System View say about DEVELOPING COMMON INFORMATION SECURITY FOUNDATIONS? According to Managing Information Security Risk_ Organization, Mission, and Information System View, DEVELOPING COMMON INFORMATION SECURITY FOUNDATIONS: COLLABORATION AMONG PUBLIC AND PRIVATE SECTOR ENTITIES In developing standards and guidelines required by FISMA, NIST consults with other federal agencies and offices as well as the private sector to improve information security, avoid unnecessary and costly duplication of effort, and ensure that NIST publications are complementary with the standards and guidelines employed for the protection of national security systems. In addition to its comprehensive public review and vetting process, NIST is collaborating with the Office of the Director of National Intelligence (ODNI), the Department of Defense (DoD), and the Committee on National Security Systems (CNSS) to establish a common foundation for information security across the federal government. A common foundation for information security will provide the Intelligence, Defense, and Civil sectors of the federal government and their contractors, more uniform and consistent ways to manage the risk to organizational operations and assets, individuals, other organizations, and the Nation that results from the operation and use of information systems. A common foundation for information security will also provide a strong basis for reciprocal acceptance of security assessment results and facilitate information sharing. NIST is also working with public and private sector entities to establish mappings and relationships between the security standards and guidelines developed by NIST and the International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC). \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Managing Information Security Risk_ Organization, Mission, and Information System View."}]}
{"id": "nist_00679", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Examine according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, Examine: [SELECT FROM: system and communications protection policy and procedures; procedures for network disconnect; system design documentation; system configuration settings; system audit records; system security plan; other relevant documents or records]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00680", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Derived PIV Application and Data Model Test Guidelines say about 1.1 Background? According to Derived PIV Application and Data Model Test Guidelines, 1.1 Background: Federal Information Processing Standard (FIPS) 201, Personal Identity Verification (PIV) for Federal Employees and Contractors [FIPS201], specified a common set of identity credentials for the purpose of Homeland Security Presidential Directive 12 [HSPD12] in a smart card form factor, known as the PIV Card. [FIPS201] originally required that all PIV credentials and associated keys be stored on the PIV Card, and although the use of the PIV Card for electronic authentication works well with traditional desktop and laptop computers, it is not optimized for mobile devices. 1 In response to the growing use of mobile devices within the Federal Government, [FIPS201] was revised to permit the issuance of an additional credential specifically for mobile devices. This PIV credential is called a Derived PIV Credential, for which the corresponding private key is stored in a cryptographic module within a mobile device. The use of this Derived PIV Credential is restricted to provide PIV-enabled authentication services on mobile devices in order to authenticate the credential holder to remote systems.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_00681", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST provide? (Section 51) k or subnotebook computer may be a better choice as the host for the ERN. This portability must be weighed against the negative factor of limited connection capabilities to a network or other devices. In any case, an operating system that supports user-friendly Graphical User Interface (GUI) is essential for the ERN. The Macintosh and the PC, whether a desktop or a light-weight portable model, running in an environment with windows offer a compelling combination of affordability and software availability. If a multimedia capability is also a requirement for the ERN, these computers are the most desirable for the development and delivery of multimedia capabilities. This will be the model configuration, but not the required configuration, for the NIST ERN as illustrated in Figure 1. As an option, a scanner with associated OCR software may be added to this configuration to provide an alternative for making ERN entries in cases where software tools for ERN entries cannot adequately meet the users' needs. Figure 1. A System Configuration for the NIST ERN <!-- image --> This section presents the functional specifications of the basic ERN as described in Section 2.3.1. The specifications are provided in three subsections starting with the ERN input capability, followed by storage and retrieval considerations, and concluding with a discussion on security aspects of the ERN. The ERN should utilize a user-friendly interface. The acceptance of the ERN depends to a great extent on the tools that are provided for users to make notebook entries that include text, graphics, images, equations, etc. Not only must the appropriate tools be provided and easy to use, but they need to be integrated as a package. Due to the multiple input possibilities and different forms of storage, this integration of tools will not be a trivial task. Since word processors are so common, textual input is easily supported.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST."}]}
{"id": "nist_00682", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Building Secure Microservices-based Applications Using Service-Mesh Architecture say about 4.4 Configuration for Identity and Access Management? (Part 3) According to Building Secure Microservices-based Applications Using Service-Mesh Architecture, 4.4 Configuration for Identity and Access Management: n identity certificate. In many systems, this can be achieved by attesting the instance against the system's orchestration engine, and by using other local proofs (e.g. secrets retrieved from an HSM). The same care should be taken in provisioning the signing certificate for the Service Mesh control plane's certificate management system. That signing certificate should be retrievable only by the Service Mesh control plane and only after some form of attestation has been done against it. Recommendation for Secure Naming Service (SM-DR17): If the certificate used for mTLS carries server identity, then the Service Mesh should provide a secure naming service that maps the server identity to the microservice name that is provided by the secure discovery service or DNS. This requirement is needed to ensure that the server is the authorized location for the microservices and to protect against network hijacking. If the certificate used for mTLS carries the service identity, no additional secure naming service is required. This also ensures that when the microservice is ported to a different network domain (different cluster or different cloud location), the identity and associated access control policies need not be defined again for the new location. Setting up certificates for microservices based on service identity enables two communicating services to establish a secure communication channel but does not specify whether they are allowed to communicate at all in the place. To specify this, a feature to define policies for allowed inbound and outbound traffic for each microservice node is required. Recommendation for Granular Identity (SM-DR18): Each microservice should have its own identity, and all instances of this service should present the same identity at runtime. This allows for access policy at the level of microservice in a given namespace.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Building Secure Microservices-based Applications Using Service-Mesh Architecture."}]}
{"id": "nist_00683", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders provide? (Section 160) installed in several ways on CentOS 7 using yum . Yum is a package manager on the CentOS 7 platform that automates software processes, such as installation, upgrade, and removal, in a consistent way. - Download the Java Development Kit (JDK) in the appropriate format for your environment, from Oracle's website; for CentOS, the Red Hat Package Manager (RPM) download can be used: - As root, install the RPM by using the following command, substituting the actual version of the downloaded file: - Alternatively, the JDK can be downloaded in .tar.gz format and unzipped in the appropriate location (i.e., /usr/share on CentOS 7). ``` rpm -ivh jdk-8u151-linux-x64.rpm ``` The alternatives command maintains symbolic links determining default commands. This command can be used to select the default Java command. This is helpful even in cases where there are multiple installations of Java on the system. - Use the following command to select the default Java command: ``` alternatives --config java ``` There are three programs that provide 'java.' - *+ 2 java-1.8.0-openjdk.x86\\_64 (/usr/lib/jvm/java-1.8.0-openjdk- ``` Selection Command -----------------------------------------------1 /usr/java/jre1.8.0_111/bin/java 1.8.0.131-3.b12.el7_3.x86_64/jre/bin/java) 3 /usr/java/jdk1.8.0_131/jre/bin/java ``` Enter to keep the current selection[+], or type selection number: This presents the user with a configuration menu for choosing a Java instance. Once a selection is made, the link becomes the default command systemwide. - To make Java available to all users, the JAVA\\_HOME environment variable is set by using the following command: - For cryptographic functions, download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 8 from - ", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, single sign-on. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_00684", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Trustworthy Email provide? (Section 48) fashion, across networks via Mail Transfer Agents (MTAs). MTAs communicate using the Simple Mail Transfer Protocol (SMTP) described below and act as both client and server, depending on the situation. For example, an MTA can act as a server when accepting an email message from an end user's MUA, then act as a client in connecting to and transferring the message to the recipient domain's MTA for final delivery . MTAs can be described with more specialized language that denotes specific functions: - Mail Submission Agents (MSA): An MTA that accepts mail from MUAs (usually after authenticating the sender) and begins the transmission process by sending it to a MTA for further processing. Often the MSA and first -hop MTA is the same process, just fulfilling both roles. - Mail Delivery Agent (MDA): An MTA that receives mail from an organization's inbound MTA and ultimately places the message in a specific mailbox. Like the MSA, the MDA could be a combined in-bound MTA and MDA component. Mail servers may also perform various security functions to prevent malicious email from being delivered or include authentication credentials such as digital signatures (see Sender Policy Framework Section 4.3 and DomainKeys Identified Mail (DKIM) Section 4.5). \ufffdese security functions may be provided by other components that act as lightweight MTAs or these functions may be added to MTAs via filters or patches. An email message may pass through multiple MTAs before reaching the final recipient. Each MTA in the chain may have its own security policy (which may be uniform within an organization but may not be uniform) and there is currently no way for a sender to request a particular level of security for the email message. However, there is work in progress 1 for specifying how a client can request the use of TLS for message transmission. In addition to MUAs and MTAs, an organization may use one or more special purpose components for a particular task.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Trustworthy Email."}]}
{"id": "nist_00685", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Government Smart Card Interoperability Specification, Version 2.1 say about Appendix C-GSC Data Model? (Part 6) According to Government Smart Card Interoperability Specification, Version 2.1, Appendix C-GSC Data Model: Login Information File / Buffer | | EF 4000 | Verify CHV | |-----------------------------------|-----|-----------|--------------| | Data Element (TLV) | Tag | Type | Max. Bytes | | User ID | 40 | Variable | 60 | | Domain | 41 | Variable | 60 | | Password | 42 | Variable | 20 | | Error Detection Code | FE | LRC | 1 | | Card Information File / Buffer | | EF 5000 | Always Read | Always Read | |----------------------------------|-----|-----------------|---------------|---------------| | Data Element (TLV) | Tag | Type | | Max. Bytes | | Issuer ID | 50 | Variable | | 32 | | Issuance Counter | 51 | Variable | | 4 | | Issue Date | 52 | Date (YYYYMMDD) | | 8 | | Expiration Date | 53 | Date (YYYYMMDD) | | 8 | | Card Type | 54 | Variable | | 32 | | Demographic Data Load Date | 55 | Date (YYYYMMDD) | | 8 | | Demographic Data Expiration Date | 56 | Date (YYYYMMDD) | | 8 | | Card Security Code | 57 | Fixed Text | | 32 | | Card ID AID | 58 | Variable | | 32 | <!-- image --> | Card Information File / Buffer | | EF 5000 | Always Read | |----------------------------------|-----|-----------|---------------| | Data Element (TLV) | Tag | Type | Max.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_00686", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Domain Name System-Based Electronic Mail Security provide? (Section 43) ure of communications and confidentiality protection by encrypting communications. The project's demonstration of DNSSEC and DANE protocols also supports communications and control network integrity. It does this by demonstrating operationally feasible mechanisms for refusing connections to or message delivery from sources that do not implement a specified set of DNS security extensions. Rigorous adherence to a minimum security configuration can be used to enforce isolation of networks from entities that do not conform to the network's security requirements. The Detect Function develops and implements the appropriate activities needed to identify in a timely manner the occurrence of a cybersecurity event. Examples of outcome categories within this function addressed by the project include Security Continuous Monitoring and Detection Processes. The Security Continuous Monitoring Category supports an outcome in which information systems and assets are monitored at discrete intervals to identify cybersecurity events and to verify the effectiveness of protective measures. While not a classic example of continuous monitoring, the project's platform has the ability to automatically check all DNS responses for correct digital signatures. The DE.CM-1 subcategory under Security Continuous Monitoring supports monitoring of networks to detect potential cybersecurity events. While not a classic example of continuous monitoring, the demonstrated capability of the project's platform to automatically check all inbound DNS responses for valid digital signatures permits identification of attempts to spoof systems using bogus DNS data. Automatic signing and signature validation for email permits continuous checking for false sender identities and modification of message content. NIST SP 800-53, referred to by this subcategory, requires monitoring of inbound and outbound communications traffic for unauthorized conditions (SI-4 [4]).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_00687", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control BE-4 in IT Asset Management? (Part 118) Control BE-4: cvss_base = stripped(str(row[12])) risk_factor = stripped(str(row[13])) if int(id) > int(last_id): #print \"Greater!\" last_id = id openvas_state.seek(0,0) openvas_state.write(str(last_id)) new_record_count = new_record_count + 1 csv_writer.writerow([id, task, subnet, host, port, nvt, type, results_description, report, nvts_name, nvts_description, cve, cvss_base, risk_factor]) ``` ``` json_dict = {'id': id, 'task': task, 'subnet': subnet, 'host': host, 'port': port, 'nvt': nvt, 'type': type, 'results_description': results_description, 'report': report, 'nvts_name': nvts_name, 'nvts_description': nvts_description, 'cve': cve, 'cvss_base': cvss_base, 'risk_factor': risk_factor} json.dump(json_dict, jsonfile, sort_keys = True, indent = 4, ensure_ascii = False) #print \"ID: %s LAST: %s\" % (id, last_id), print \"\\n\" db_conn.close() csvfile.close() jsonfile.close() print \"Wrote %s new records.\" % new_record_count ``` ## /opt/splunkforwarder/etc/system/local/server.conf ``` [sslConfig] sslKeysfilePassword = $1$JnofjmZL66ZH [lmpool:auto_generated_pool_forwarder] description = auto_generated_pool_forwarder quota = MAX slaves = * stack_id = forwarder [lmpool:auto_generated_pool_free] description = auto_generated_pool_free quota = MAX slaves = * stack_id = free [general] pass4SymmKey = $1$cTZL0iMNoPRH serverName = openvas ``` ## /opt/splunkforwarder/etc/system/local/outputs.conf ``` [tcpout] defaultGroup = splunkssl [tcpout:splunkssl] compressed = true server = loghost:9997 sslCertPath = $SPLUNK_HOME/etc/certs/openvas.lab5.nccoe.gov.pem sslPassword = $1$JnofjmZL66ZH sslRootCAPath = $SPLUNK_HOME/etc/certs/CAServerCert.pem sslVerifyServerCert = true ``` ## /opt/splunkforwarder/etc/system/local/inputs.conf ``` [default] host = openvas index = openvas sourcetype = openvas [monitor:///home/mike/openvas_results.csv] ``` ## 3.7 Puppet Enterprise Puppet Enterprise enforces a configuration baseline on servers and workstations.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IT Asset Management."}]}
{"id": "nist_00688", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RA-1 in Securing Wireless Infusion Pumps in Healthcare Delivery Organizations? (Part 58) Control RA-1: edical devices with wireless LAN \u25aa remote access for external vendor support The NCCoE build uses Cisco Adaptive Security Appliances (ASA) as virtual router and firewall devices within the network. Each defined zone in the hospital network that we built has its own ASA, with two interfaces to protect each zone. As we considered how many ASAs to use, we opted for a tradeoff between the complexity of the configuration and the number of interfaces on a single ASA. 2.1.1 Cisco ASA Baseline Configuration In our environment, all ASAs are virtualized and are based on Cisco\u2019s Adaptive Security Virtual Appliance (ASAv) product. In your environment, the responsible person would complete installation by following the Cisco Adaptive Security Virtual Appliance (ASAv) Quick Start Guide, 9.6 [2]. We imported the virtual appliance called asav-vi.ovf, assigning the first interface to the management network, the second interface to the wide area network (WAN), and the third interface to the local area network (LAN). For an unknown reason, the show version command did not work in the console; as a workaround, we configured Secure Shell (SSH) [3] access and ran the command via SSH instead. NIST SP 1800-8C: Securing Wireless Infusion Pumps 4 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P 1 8 0 0 - 8 . . Next, we configured the ASA with a baseline-configuration template that allows all outbound traffic, as well as only related inbound traffic as allowed by the stateful firewall. Internet Control Message Protocol (ICMP) [4] enables troubleshooting with ping and traceroute tools. Authenticated OSPF automated routing tables as we added or removed ASAs in the network. In your production environment, you may wish to make different decisions in your baseline configuration. All ASAs have an additional management interface on 192.168.29.0/24.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Wireless Infusion Pumps in Healthcare Delivery Organizations."}]}
{"id": "nist_00689", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security say about 2.2.3 Remote Desktop Access? (Part 1) According to Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security, 2.2.3 Remote Desktop Access: 2.2.3 Remote Desktop Access A remote desktop access solution gives a teleworker the ability to remotely control a particular PC at the organization, most often the user's own computer at the organization's office, from a telework client device. The teleworker has keyboard and mouse control over the remote computer and sees that computer's screen on the local telework client device's screen. Remote desktop access allows the user to access all of the applications, data, and other resources that are normally available from their PC in the office. Figure 2-3 shows the basic remote desktop access architecture. A remote desktop access client program or web browser plug-in is installed on each telework client device, and it connects directly with the teleworker's corresponding internal workstation on the organization's internal network. Figure 2-3. Remote Desktop Access Architecture <!-- image --> There are two major styles of remote desktop access: direct between the telework client and the internal workstation, and indirect through a trusted intermediate system. However, direct access is often not possible because it is prevented by many firewalls. For example, if the internal workstation is behind a firewall performing network address translation (NAT), the telework client device cannot initiate contact with the internal workstation unless either the NAT allows such contact 14 or the internal workstation initiates communications with the external telework client device (e.g., periodically checking with the client device to see if it wants to connect). Indirect remote desktop access is performed through an intermediate server. This server is sometimes part of the organization's firewall, but is more often run by a trusted commercial or free third-party service outside the organization's network perimeter.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security."}]}
{"id": "nist_00690", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Vetting the Security of Mobile Applications say about Table of Contents? (Part 9) According to Vetting the Security of Mobile Applications, Table of Contents: | Managed and Unmanaged Apps .................................................................. | 21 | | | 5.2 | App Whitelisting and App Blacklisting...........................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Vetting the Security of Mobile Applications."}]}
{"id": "nist_00691", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.9 SWAM Actual State and Desired State Specification according to NIST Automation Support for Security Control Assessments_ Software Asset Management According to Automation Support for Security Control Assessments_ Software Asset Management, 2.9 SWAM Actual State and Desired State Specification: For information on the actual state and the desired state specification for SWAM, see the assessment criteria notes section of the defect check tables in Section 3.2. Note that many controls in SWAM refer to developing and updating an inventory of software on devices (or other inventories). Note also, that per the SP 800-53A 22 definition of test , testing of the SWAM controls implies the need for specification of both an actual state inventory and a desired state inventory, so that the test can compare the two inventories. The details of the comparison are described in the defect check tables in Section 3.2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_00692", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about Test? According to Assessing Security Requirements for Controlled Unclassified Information, Test: [SELECT FROM: processes for security at alternate work sites; mechanisms for supporting alternate work sites; security requirements employed at alternate work sites; means of communication between personnel at alternate work sites and security personnel]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00693", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cell Phone Forensic Tools_ an Overview and Analysis provide? (Section 149) t) The following scenarios were conducted on a Cingular GSM Motorola MPx220 running Microsoft Windows Mobile 2004 for Pocket PC Phone Edition. PDA Seizure version 3.0.3.89 was used for acquisition. Connectivity and Retrieval: The data contents of the device were successfully acquired with or without the SIM present. If internal memory authentication mechanisms are applied, the proper pass-phrase must be provided in order for the ActiveSync connection to take place. Basic subscriber and service provider information (e.g., IMEI, ICCID, MSISDN) were not found. Network carrier and the phone number was found in the \\Windows directory and reported. The reported memory size is consistent with the total memory size of the device. (Meet) PIM Applications: PIM data was not found (i.e., Address Book, Calendar, Tasks, Memos). (Miss) Dialed/Received Phone Calls: Dialed/received phone calls were not found. (Miss) SMS/MMS Messaging: SMS messages were not found. Textual content of all active incoming MMS messages were found and reported. MMS attachments were not found. Deleted MMS messages were not found. (Below) Internet Messaging: All data content associated with sent and received email messages was found and reported. Deleted messages were not found. (Below) Web Applications: Visited URLs and search engine queries were found and reported. Textual Web content pertaining to visited URLs was not found. No graphical images of visited sites were found. (Below) Text File Formats: Data content associated with text files (i.e., . txt , . doc , . pdf ) was found and reported. Deleted text files were not found. (Below) Graphics File Formats: Graphics file (i.e., . bmp , . jpg , . gif , . png , . tif ) data content was found and reported. . png files were found but not displayed in the graphics library. Deleted graphics files were not found. (Below) Compressed File Archive Formats: Compressed data file (i.e., . zip , . rar , . exe , . tgz ) content was found and reported.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_00694", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Note according to Engineering Trustworthy Secure Systems? Note: Scope includes the system, system elements, information items, or artifacts that will be verified against applicable requirements, security characteristics, or other security properties. Each verification action description includes what will be verified (e.g., actual system, model,", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_00695", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings provide? (Section 107) es (EECs) [16] and proxy certificates [42]. In brief, these certificates allow a user to assert a globally unique identifier (i.e., a distinguished name from the X.509 identity certificate). We note that in Grid scenarios there is often an organizational separation between the certificate authorities (CAs), which are the authorities of identity (authentication) and the authorities of attributes (authorization). For example, in the case of the Department of Energy (DOE) SciDAC program [36], a single CA, the DOE Grids CA [6], serves a broad community of users, while the attributes and rights for those users are determined by their individual projects (e.g., National Fusion Grid, Earth Systems Grid, or Particle Physics Data Grid). Authorization in the Globus Toolkit is by default based on access control lists (ACLs) located at each resource. The ACLs specify the identifiers of the users allowed to access the resource. Also, higher-level services (such as CAS [32]) that provide richer authorization policies exist as optional configurations. As is discussed later, the GridShib project enhances the authorization options of the Globus Toolkit by adding standards-based attribute exchange for both authorization policies and service customization. Shibboleth[37] provides cross-domain single sign-on and attribute-based authorization while preserving user privacy. Developed by Internet2/MACE [19], Shibboleth is based in large part on the OASIS Security Assertion Markup Language (SAML). The SAML 1.1 browser profiles [17,21,34] define two functional components, an Identity Provider and a Service Provider 2 . The Identity Provider (IdP) creates, maintains, and manages user identity, while the Service Provider (SP) controls access to services and resources. An IdP produces and issues SAML assertions to SPs upon request.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings."}]}
{"id": "nist_00696", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Usability of PIV Smartcards for Logical Access provide? (Section 2) Gallagher, Under Secretary of Commerce for Standards and Technology and Director | INTRODUCTION............................................................................................................................................3 | INTRODUCTION............................................................................................................................................3 | INTRODUCTION............................................................................................................................................3 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| | PREVIOUS PIV STUDIES.............................................................................................................................4 | PREVIOUS PIV STUDIES.............................................................................................................................4 | PREVIOUS PIV STUDIES.............................................................................................................................4 | | 3.1 | PARTICIPANTS ..........................................................................................................................................5 | | | 3.2 | INSTRUCTIONAL MATERIALS ...................................................................................................................7 | | | 3.3 | EQUIPMENT..............................................................................................................................................7 | | | 3.3.1 | Card .................................................................................................................................................7 | | | 3.3.2 | Card Readers....................................................................................................................................9 | | | 3.4 SETTING .................................................................................................................................................10 | 3.4 SETTING .................................................................................................................................................10 | | | 3.5 | TASKS ....................................................................................................................................................10 | | | 3.6 | TIMELINE OF ACTIVITIES........................................................................................................................10 | | | 3.6.1 | Smartcard Installation Phase..........................................................................................................11 | | | 3.6.2 | Smartcard Use Phase .....................................................................................................................11 | | | 3.6.3 | Study Wrap-Up Phase....................................................................................................................12 | | | 3.7 DATA COLLECTION METHODS ..............................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Usability of PIV Smartcards for Logical Access."}]}
{"id": "nist_00697", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Comments on this publication may be submitted to: according to NIST A Framework for Designing Cryptographic Key Management Systems According to A Framework for Designing Cryptographic Key Management Systems, Comments on this publication may be submitted to:: National Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930 Email: ckmsdesignframework@nist.gov SP 800-130 August 2013", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_00698", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms provide? (Section 81) rganizations having special security needs and desiring to augment the base security and key-management services, and suggests additional features that may be desirable to implement and use. 74 SP 800-130, A Framework for Designing Cryptographic Key Management Systems . 75 SP 800-152, A Profile for U. S. Federal Cryptographic Key Management Systems (CKMS) . In addition to providing design requirements to be incorporated into a CKMS design, SP 800-152 provides requirements for a Federal CKMS (FCKMS) to be operated by a service provider that may be a federal agency or a third party operating an FCKMS under contract for one or more federal agencies and their contractors. This Profile is intended to - Assist CKMS designers and implementers in supporting appropriate cryptographic algorithms and keys, selecting the metadata associated with the keys, and selecting protocols for protecting sensitive U.S. federal computing applications and data; - Establish requirements for testing, procurement, installation, configuration, administration, operation, maintenance, and usage of the FCKMS; - Facilitate an easy comparison of one CKMS with another by analyzing their designs and implementations in order to understand how each meets the Framework (i.e., SP 800-130) and Profile (e.g., SP 800-152) requirements; and - Assist in understanding what is needed to evaluate, procure, install, configure, administer, operate, and use an FCKMS that manages the key information that is used to protect sensitive and valuable data obtained, processed, stored, and used by U.S. federal organizations and their contractors. A PKI is a security infrastructure that creates and manages public-key certificates to facilitate the use of public-key (i.e., asymmetric-key) cryptography. To achieve this goal, a PKI needs to perform two basic tasks: 1.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, key management, sso. Contains security framework guidance for authentication systems. Source: Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms."}]}
{"id": "nist_00699", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case provide? (Section 189) PN users and add those users requiring remote access to this group. For instance, a group called VPN-users was created in our AD server and a user vpnuser01 was added to this group. <!-- image --> 3. Launch the Network Policy Server console. Create a new Radius client for your firewall device by clicking on Radius Clients &gt; New . 4. Enter the IP address of the Interface on the ASA. This is typically the Default Gateway of the subnet where the AD/Radius server is in. Enter a strong passphrase for Shared secret. The image below shows a Radius client created for our Cisco-ASA firewall. <!-- image --> 5. Click on Network Policies under Polices . Create a Network Policy here corresponding to the Radius client setup earlier. The image below shows network policy created for the Cisco-ASA client. Ensure the policy is enabled. 6. Click ADD under Conditions tab to add the following two conditions at a minimum. Add more conditions as per your requirement. - VPN-Users security group created earlier. - Client IPv4 Address: IP address of the Radius client created earlier. <!-- image --> <!-- image --> 7. Select the authentication methods under Constraints as shown below. This is as per Cisco documentation. 82 <!-- image --> 8. Click Standard under Radius Attributes under Settings tab. Set the following attributes - Framed Protocol= PPP - Service-Type= Framed - Class = &lt; Name of group policy &gt;. This policy is configured in the Firewall for VPN <!-- image --> Below are the high-level steps for configuring Secure Remote Access in the FMC (Firepower Management Console). 1. Login to the FMC Web interface. Click on Licenses &gt; Smart Licenses &gt; Verify if either AnyConnect Plus or AnyConnect VPN license has been enabled (if not already). 2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case."}]}
{"id": "nist_00700", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does PIV Data Model Test Guidelines provide? (Section 220) Note: - Since the ECDSA keys do not have any size res rictions based on dates, this test case does not apply | | Expected Result(s) | The key sizes used adhere to the time period for use requirement. | | Purpose | Confirms that the digital signature certificate asserts the appropriate purpose of the key contained in the certificate. | |--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Reference(s) | 1. FIPS201, Section 5.4.2.1 2. AS07.02.05 | | Precondition | 1. A valid PIV card is inserted into the contact reader. 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 through card handle. 4. A digital signature key and corresponding certificate are present on the PIV card. | | Test Steps | 1. Set cardHandle := <<valid card handle>> cate from 2. Set OID := <<Digital Signature Certifi (2.16.840.1.101.3.7.2.1.0)>> 3. Call pivGetData w/ \u2022 (IN) cardHandle \u2022 (IN) OID \u2022 (OUT) data 4.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_00701", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Storage Encryption Technologies for End User Devices say about 3.2 Protection Provided by Storage Encryption Technologies? (Part 5) According to Guide to Storage Encryption Technologies for End User Devices, 3.2 Protection Provided by Storage Encryption Technologies: e and the user has been authenticated to the storage encryption solution, malware could access decrypted files and transfer copies of them to external hosts or extract sensitive information from them. Other examples are an attacker disabling or reconfiguring storage encryption, malware installing a keylogger that captures passwords used for storage encryption authentication, or malware acquiring a copy of a storage encryption key from the device's memory (for software-based storage encryption solutions). Organizations should also be aware that they should not rely on storage encryption technologies to protect data without regularly maintaining the encryption solution. For example, if an attacker acquires a lost, stolen, or retired device protected by storage encryption technology, and a vulnerability in the storage encryption technology is discovered in the future, the attacker may be able to exploit it to access the protected data.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit, malware. Contains technical security guidance that could inform defensive posture. Source: Guide to Storage Encryption Technologies for End User Devices."}]}
{"id": "nist_00702", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 613) informa\ue000on security and privacy responsibili\ue000es]. PE-02 PHYSICAL ACCESS AUTHORIZATIONS ASSESSMENT OBJECTIVE: Determine if: PE-02_ODP PE-02a.[01] PE-02a.[02] PE-02a.[03] PE-02b. PE-02c. PE-02d. frequency at which to review the access list detailing authorized facility access by individuals is de\ufb01ned; a list of individuals with authorized access to the facility where the system resides has been developed; the list of individuals with authorized access to the facility where the system resides has been approved; the list of individuals with authorized access to the facility where the system resides has been maintained; authoriza\ue000on creden\ue000als are issued for facility access; the access list detailing authorized facility access by individuals is reviewed <PE-02_ODP frequency>; individuals are removed from the facility access list when access is no longer required. CHAPTER FOUR PAGE 331 Reference produced from open data h\ue003ps://github.com/usnistgov/oscal-content NIST SP 800-53A, REV. 5 ASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS PE-02 PHYSICAL ACCESS AUTHORIZATIONS POTENTIAL ASSESSMENT METHODS AND OBJECTS: PE-02-Examine [SELECT FROM: Physical and environmental protec\ue000on policy; procedures addressing physical access authoriza\ue000ons; authorized personnel access list; authoriza\ue000on creden\ue000als; physical access list reviews; physical access termina\ue000on records and associated documenta\ue000on; system security plan; other relevant documents or records]. PE-02-Interview [SELECT FROM: Organiza\ue000onal personnel with physical access authoriza\ue000on responsibili\ue000es; organiza\ue000onal personnel with physical access to system facility; organiza\ue000onal personnel with informa\ue000on security responsibili\ue000es]. PE-02-Test [SELECT FROM: Organiza\ue000onal processes for physical access authoriza\ue000ons; mechanisms suppor\ue000ng and/or implemen\ue000ng physical access authoriza\ue000ons].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00703", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-11 in Guidelines for Smart Grid Cybersecurity? (Part 363) Control SI-11: sues that arise in the design, deployment, and use of smart grid systems and that should be considered by system designers, implementers, purchasers, integrators, and users of smart grid technologies. In discussing the relative merits of different technologies or solutions to problems, these design considerations do not recommend specific solutions or requirements. The intention is to highlight important issues that can serve as a means of identifying and formulating requirements and high-level designs for key protocols and interfaces that are missing and need to be developed. 7.2 EVIDENT AND SPECIFIC CYBERSECURITY PROBLEMS This section documents specific cybersecurity problems in the smart grid by describing field cases that explain the operational, system, and device issues. The problems listed are intentionally not ordered or categorized in any particular way. 7.2.1 Authenticating and Authorizing Utility Users This section identifies three examples of authenticating and authorizing users that is unique for the smart grid. The three examples include authenticating and authorizing utility users to substation intelligent electronic devices (IEDs), to outdoor field equipment, and to meters. In each of these examples, role-based, rather than unique user-based access control is commonly used and passwords are shared among organizational users with the same role. Also common across all of the examples is the volume of devices, leading to the same password often being used across all devices and seldom changed. Control of authentication and authorization can be centrally managed for substation IEDs, outdoor field equipment, and to meters across the utility, and is updated promptly to ensure that only intended users can authenticate to intended devices and perform authorized functions. 34 In the case of substation IEDs, passwords are often stored locally on the device, with different passwords allowing different authorization levels.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_00704", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Conducting Risk Assessments say about 2.3.2 Assessment Approaches? (Part 3) According to Guide for Conducting Risk Assessments, 2.3.2 Assessment Approaches: y insignificant, while the difference between risks scored 36 and 70 is relatively significant). The role of expert judgment in assigning values is more evident than in a purely quantitative approach. Moreover, if the scales or sets of bins provide sufficient granularity, relative prioritization among results is better supported than in a purely qualitative approach. As in a quantitative approach, rigor is significantly lessened when subjective determinations are buried within assessments, or when significant uncertainty surrounds a determination of value. As with the nonnumeric categories or levels used in a well-founded qualitative approach, each bin or range of values needs to be clearly defined and/or characterized by meaningful examples. Independent of the type of value scale selected, assessments make explicit the temporal element of risk factors. For example, organizations can associate a specific time period with assessments of likelihood of occurrence and assessments of impact severity. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guide for Conducting Risk Assessments."}]}
{"id": "nist_00705", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Required Test Procedures: according to NIST Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements According to Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements, Required Test Procedures:: SCAP.T.3800.1: The tester SHALL manually inspect the vendor-identified machine-readable output and ensure that CPE naming data is correct according to the CPE specification. The tester will do this by choosing a minimum of 30 vendor and product names in the product output that are also included in the official CPE Dictionary. SCAP.R.3900: The product SHALL allow users to locate configuration issue items using CCE IDs. SCAP Capability: \uf0fe ACS", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements."}]}
{"id": "nist_00706", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4. Define a Specific Plan and Process according to NIST NIST Cryptographic Standards and Guidelines Development Process According to NIST Cryptographic Standards and Guidelines Development Process, 4. Define a Specific Plan and Process: NIST has several approaches that it may use to meet the needs for cryptographic standards or guidelines. These include adopting or adapting existing SDO-produced standards, encouraging and participating in the development of new standards by SDOs, or developing NIST standards - which, in some cases, may involve holding a competition. NIST will solicit input from stakeholders in determining the most appropriate approach for a particular standard or guideline. After making a decision, NIST will publicly state and explain the reason for this determination. Options include:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Cryptographic Standards and Guidelines Development Process."}]}
{"id": "nist_00707", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DS-3 in Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches? (Part 102) Control DS-3: Click Next . <!-- image --> 12. Copy the API Hostname into the labeled field. 13. Click Next. 14. Copy in the Integration and Secret Keys into the relevant fields and click Next . 15. Click Next. 16. Configure Duo's integration options according to the needs of your organization. Note that Bypass Duo authentication when offline will allow users to skip the two-factor authentication when offline, which increases the availability of their files but may increase risk. <!-- image --> <!-- image --> <!-- image --> 17. Click Next . 18. Leave Enable Smart Card support unchecked. 19. Click Next . <!-- image --> 20. Leave Enable UAC Elevation Protection unchecked. <!-- image --> ## 21. Click Next . <!-- image --> 22. Click Install . <!-- image --> 23. Click Finish . 24. Installation should now be complete. Users registered on the Duo Dashboard with a linked phone will be allowed access to the system. ## 2.7.2 Registering a Duo User 1. Login to the Duo Admin Dashboard. 2. Click Add New &gt; User from the drop-down menu on the right. 3. Enter a username for the user. <!-- image --> <!-- image --> 4. Click Add User. 5. This will lead you to that user's information page, where additional information (full name, email, phone number) and Duo authenticators (phone numbers, 2 Factor Authentication (2FA) hardware tokens, WebAuthn, etc.) can be associated with that username. Note: A user will not be able to log into a Duo protected system unless the user is registered and has an authentication device associated with their username. ## 2.8 Dispel Dispel is a network protection and user access tool that we used to provide a Virtual Desktop Infrastructure (VDI) capability. A typical deployment of Dispel is done in a largely managed fashion, with a specific deployment being tailored to a network setup. The deployment in the NCCoE laboratory may not be the best setup for any given network.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token, sso. Contains security framework guidance for authentication systems. Source: Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches."}]}
{"id": "nist_00708", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance provide? (Section 91) uthoritiative server installers shall use an approved random bit generator (as discussed in [SP 800-90A]) to create and configure an initial, random secret string for use with TSIG in transactions. 3. Authoritative servers shall be configured to generate and sign zone data with a key pair that is consistent with the key size recommendations for digital signatures as specified in Part 1. 4. Authoritative servers shall be configured to generate and sign the key set with a key pair that is consistent with the key sizes recommended for digital signatures, as specified in Part 1. 5. Authoritative servers shall be configured to generate and use a random secret string for zone transfer-message authentication (via TSIG) between primary and secondary servers. The security strength of the random bit generator process shall support the security strength required by the servers. 6. Authoritative servers shall be configured to generate and use a separate shared secret string for dynamic update-message authentication (via TSIG). The security strength of the random bit generator process shall support the security strength required by the servers. 1. Recursive caching server installers shall configure DNS servers to be DNSSECaware. 2. Recursive caching server installers shall install at least one public key used for DNSSEC validation. The key(s) shall be kept up-to-date to insure successful validations. 1. Client systems shall be configured to send DNS queries to a DNSSEC-enabled caching recursive server. 2. Client systems should be configured to use DNSSEC-enabled applications, if they are available. The System Administrator is the individual who runs the DNS application on a day-today basis and interacts with the end user. 1. The organization security policy regarding the Authoritative servers shall be enforced. 2. Cryptographic keys shall be protected as specified in Part 1. 3.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance."}]}
{"id": "nist_00709", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-8(5) in Automation Support for Security Control Assessments_ Software Vulnerability Management? (Part 16) Control CM-8(5): | The defect check to assess whether this sub-capability is operating effectively is defined as follows: | Defect Check ID | Defect Check Name | Assessment Criteria Notes | Selected | |-------------------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| | VUL-Q03 | Low completeness- metric | The completeness metric is not a device - level defect but is applied to any collection of devices such as those in an authorization boundary.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Vulnerability Management."}]}
{"id": "nist_00710", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Message Authentication Code (MAC) Validation System_ Requirements and Procedures say about 5.1 Validate Suboption? (Part 3) According to Message Authentication Code (MAC) Validation System_ Requirements and Procedures, 5.1 Validate Suboption: rt the status of the validation testing to the DUT by sending a completion message. Tests involving the following types of key and data combinations are performed in the Binary Validate Suboption: I. - (1) Selected key and data combinations (without a MAC) which are related to those given in Appendix B of NBS Special Publication 500-20, Validating the Correctness of Hardware Implementations of the NBS Data Encryption Standard [9], except that the data consists of the given data with one to eight ASCII hexadecimal ones appended. 235 tests of this type are performed. - (2) Selected key and data combinations (without a MAC) which are related to those generated by the DES Maintenance Test as specified in NBS Special Publication 500-61, Maintenance Testing for the Data Encryption Standard [10], except that the data consists of the generated data with one to eight ASCII hexadecimal ones appended. 192 tests of this type are performed. - (3) Key and data combinations (without a MAC) which are randomly generated. At least 100 tests of this type are performed. Some of these combinations consist of data whose length is not a multiple of 64 bits so that the DUT must correctly pad the data in the MAC computation. - (4) Key and data combinations (with a MAC) which are randomly generated. At least 100 tests of this type are performed. Approximately half of the MACs are randomly chosen to be incorrect.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Message Authentication Code (MAC) Validation System_ Requirements and Procedures."}]}
{"id": "nist_00711", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Examine according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, Examine: [SELECT FROM: system media protection policy and procedures; system use policy; procedures for media usage restrictions; rules of behavior; system audit records; system design documentation; system configuration settings; system security plan; other relevant documents or records]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00712", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Digital Identity Guidelines_ Federation and Assertions say about 5.5. Discovery and Registration? (Part 2) According to Digital Identity Guidelines_ Federation and Assertions, 5.5. Discovery and Registration: anaging discovery and registration. When an RP joins the ecosystem, it registers itself with the trusted service, downloads the CSP's verification keys, and receives an identifier to use with wallets. When the CSP issues attribute bundles to the subscriber-controlled wallet, the subscriber-controlled wallet is informed where it can find the list of valid RP identifiers within the ecosystem. When the RP connects to the wallet, the wallet can verify the RP's identifier without the RP having to register itself directly with the wallet. Likewise, the RP can trust the wallet's verification keys by verifying the CSP's signature over the wallet's verification keys or identifier. - 5.6. Authentication and Attribute Disclosure The decision of whether a federation transaction proceeds and, therefore, an assertion is issued and attributes are released to the RP SHALL be determined by the subscriber acting in the role of the authorized party. The decision MAY be augmented by the use of allowlists and blocklists to allow the wallet to help the subscriber make a decision based on configured policies and trust agreements. The subscriber-controlled wallet MAY remember the subscriber's decision to allow for future actions at the same RP without separate authorization from the subscriber. The use of a stored authorization decision does not supersede the requirement for wallet activation, as discussed in Sec. 5.4. The subscriber-controlled wallet MAY provide a mechanism to remember a disclosure decision by the authorized party (i.e., the subscriber) to apply to future requests from the same RP. If such a mechanism is provided, the subscriber-controlled wallet SHALL disclose to the authorized party that the storage mechanism is in use and SHALL allow the authorized party to revoke such remembered access at a future time. The subscriber-controlled wallet SHOULD provide a means to selectively disclose a subset of the attributes in the attribute bundle from the CSP.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Digital Identity Guidelines_ Federation and Assertions."}]}
{"id": "nist_00713", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0 say about Monitoring Change? According to NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0, Monitoring Change: Privacy risk management is not a static process. An organization monitors how changes in its business environment-including new laws and regulations and emerging technologies-and corresponding changes to its systems, products, and services may be affecting privacy risk, and iteratively uses the practices in this appendix to adjust accordingly. (GV.MT-P1) 23 The NIST PRAM uses organizational costs such as non-compliance costs, direct business costs, reputational costs, and internal culture costs as drivers for considering how to assess individual impact. Id. at Worksheet 3, Impact Tab. 24 See NIST SP 800-30, Rev. 1, Guide for Conducting Risk Assessments at [12] p. 14. 25 The NIST PRAM uses a semi-quantitative approach based on a scale of 1-10. 26 The NIST PRAM provides various prioritization representations, including a heat map. See [3] Worksheet 3. 27 The NIST PRAM provides a process for responding to prioritized privacy risks. Id. at Worksheet 4. 28 See NIST SP 800-37, Rev. 2 [7]. 29 See NIST SP 800-53 as updated [10].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0."}]}
{"id": "nist_00714", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IA-5 in NIST_SP_800-53r5_Security_Privacy_Controls? (Part 8) Control IA-5: owing rules: [Assignment: organization-defined binding rules]. Discussion: Authentication requires some form of binding between an identity and the authenticator that is used to confirm the identity. In conventional approaches, binding is established by pre-provisioning both the identity and the authenticator to the system. For example, the binding between a username (i.e., identity) and a password (i.e., authenticator) is accomplished by provisioning the identity and authenticator as a pair in the system. New authentication techniques allow the binding between the identity and the authenticator to be implemented external to a system. For example, with smartcard credentials, the identity and authenticator are bound together on the smartcard. Using these credentials, systems can authenticate identities that have not been pre-provisioned, dynamically provisioning the identity after authentication. In these situations, organizations can anticipate the dynamic provisioning of identities. Pre-established trust relationships and mechanisms with appropriate authorities to validate identities and related credentials are essential. Related Controls: AU-16, IA-5. (11) AUTHENTICATOR MANAGEMENT | HARDWARE TOKEN-BASED AUTHENTICATION [Withdrawn: Incorporated into IA-2(1) and IA-2(2).] (12) AUTHENTICATOR MANAGEMENT | BIOMETRIC AUTHENTICATION PERFORMANCE For biometric-based authentication, employ mechanisms that satisfy the following biometric quality requirements [Assignment: organization-defined biometric quality requirements]. Discussion: Unlike password-based authentication, which provides exact matches of user- input passwords to stored passwords, biometric authentication does not provide exact matches. Depending on the type of biometric and the type of collection mechanism, there is likely to be some divergence from the presented biometric and the stored biometric that serves as the basis for comparison.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00715", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Data Field returned in the Response Message according to NIST Government Smart Card Interoperability Specification, Version 2.1 According to Government Smart Card Interoperability Specification, Version 2.1, Data Field returned in the Response Message: If the immediately preceding APDU has indicated that additional data is available, the data field of an immediately following Get Response APDU will contain this data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_00716", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.5 Attack Computers according to NIST An Industrial Control System Cybersecurity Performance Testbed According to An Industrial Control System Cybersecurity Performance Testbed, 3.5 Attack Computers: Separate computers can be used for developing attack vectors on the various industrial processes described in this document. Computing resources that will be used for penetration testing are described in the following sections.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: attack vector, penetration test. Contains technical security guidance that could inform defensive posture. Source: An Industrial Control System Cybersecurity Performance Testbed."}]}
{"id": "nist_00717", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is NOTICE according to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities? NOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities."}]}
{"id": "nist_00718", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Guidelines for Storage Infrastructure say about 3.3.1 Physical Access? (Part 2) According to Security Guidelines for Storage Infrastructure, 3.3.1 Physical Access: twork ports, and management workstations. Communication cables are also a vulnerability. A sophisticated attacker can potentially tap into the storage communication by physically accessing the cables. Another physical access method involves replacing peripheral components, such as the keyboard and mouse, with infected components (e.g., infiltrating an infected keyboard that includes a 'keylogger' component that transmits sensitive data, such as usernames and passwords, or infects the system with malware).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, malware. Contains technical security guidance that could inform defensive posture. Source: Security Guidelines for Storage Infrastructure."}]}
{"id": "nist_00719", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Criticality Analysis Process Model_ Prioritizing Systems and Components say about Executive Summary? (Part 2) According to Criticality Analysis Process Model_ Prioritizing Systems and Components, Executive Summary: , criticality analysis is referenced in several NIST special publications including those addressing risk management, system security engineering, and supply chain risk management. The Model references and uses the outputs and artifacts of risk management, information security, project management, system design, safety, privacy, and other activities that an organization may already be performing. To reduce potential redundancy and duplication, the Model identifies integration points with these existing processes. The Criticality Analysis Process Model is structured to logically follow how organizations design and implement projects and systems and can be adapted to fit organizations' unique practices. The Model consists of five main processes: - A. Define Criticality Analysis Procedure(s) where the organization develops or adopts a set of procedures for performing a criticality analysis. - B. Conduct Program-Level Criticality Analysis where the program manager defines, reviews, and analyzes the program to identify key activities that are vital to reaching the objectives of the program and for reaching the overall goals of the organization. - C. Conduct System/Subsystem-Level Criticality Analysis where the system designer reviews and analyzes the system or subsystem from the point of view of its criticality to the overall organizational goals. - D. Conduct Component/Subcomponent-Level Criticality Analysis where the system or component engineer reviews and analyzes component or subcomponent from the point of - view of its criticality to a specific system or subsystem of which these components and subcomponents are a part. - E. Conduct Detailed Review of Criticality for Processes B, C, and D where the program manager or a collaborative group analyzes baseline criticality analysis results to create final criticality levels for Systems/Subsystems and Components/Subcomponents.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Criticality Analysis Process Model_ Prioritizing Systems and Components."}]}
{"id": "nist_00720", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2014 Annual Report? (Part 214) Control HA-3: Questions Federal Acquisition Regulation | ICT | Information and Communications Technol- ogies | | FBI FCCX | Federal Bureau of Investigation Federal Cloud Credential Exchange | IEEE | Institute of Electrical and Electronics Engineers | | FDCC FedRAMP | Federal Desktop Core Configuration Federal Risk and Authorization | INCITS | InterNational Committee for Information Technology Standards | | FHE | Management Program | IP | Internet Protocol Internet Protocol Version 6 | | | fully homomorphic encryption | IPv6 | | | FIPS | Federal Information Processing Standard Forum of Incident Response and Security | IR | Interagency or Internal Report Internet Service Provider | | FIRST | Teams | ISP IT | information technology | | FirstNet | First Responder Network Authority | ITL | Information Technology Laboratory | | | Federal Information Security Management | IUT | Implementation under test | | FISMA FISSEA | Act Federal Information Systems Security | IV&V ISPAB | Independent Verification and Validation Information Security and Privacy Advisory | | FITSI FPE | Federal IT Security Institute format-preserving encryption | ISIMC | Information Security and Identity Management Committee's | | FVAP | Federal Voting Assistance Program | ISO | International Organization for Standardization", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, identity management. Contains security framework guidance for authentication systems. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_00721", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS) provide? (Section 167) ther. - a. It should be made clear that a subject can be trusted (even partially) only^if it is started in a known state, e.g., at a specified entry point, with specified initial values for some data. Except that a trusted subject is itself very analogous to an entire trusted system (or vice versa) and thus might be usefully modelled in terms of secure initial states and security-preserving state transformations this principle doesn't seem to fit too well into, say, the original Bell &amp; La Padula model [Bell75] ; it may call for some additional rules in the model in a B2 or higher class system. In any case, one might have to explicitly define a trusted subject as an entity that has more internal structure (e.g, the code it is to execute) than the uninterpreted subjects of the original Bell &amp; La Padula model - b. A system that enforces the Biba model has what on first glance appears to be an inherent complication: any data, including the executing code that a subject reads must have an integrity label that is a superset (dominates) either of the subject's labels. Thus, for instance, any code or data (other than any in the output GDI's) that a transaction to be run in, say, \"cashier role\" needs to access must contain \"cashier role\" in its label. On second glance this actually makes sense: such a transaction is certified to operate properly only if it takes data from a cashier and no-one else; any data that does not contain the \"cashier role\" marking could have been modified (supplied by) some other kind of person. (Note that \"operates properly\" here includes the notion that it is inherently improper for a transaction to accept data from anyone other than one of its authorized users.) In any system there are large portions of software and read-only data that a transaction program needs to use and can in general rely on since they are supplied by the manufacturer and \"certified\" through use.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)."}]}
{"id": "nist_00722", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Notional Supply Chain Risk Management Practices for Federal Information Systems say about 3.2.6 Operational Contract Execution? (Part 1) According to Notional Supply Chain Risk Management Practices for Federal Information Systems, 3.2.6 Operational Contract Execution: 3.2.6 Operational Contract Execution Once a system becomes operational, the operating environment may change. Changes include, but are not limited to, suppliers, elements, delivery processes, and business processes. These changes may alter, add, or reduce ICT supply chain risks. During operations, acquirers should continue to perform ICT SCRM, including the assessment of foundational enterprise practices. The acquirer will need to ensure that the integrator or supplier understands supply chain risk and provides information on applicable changes to the element, environment, vulnerabilities, and patches on an ongoing basis. The following activities will help the acquirer maintain supply chain oversight and improve processes for future procurements: - Collect, analyze, record, and disseminate ICT SCRM lessons learned within the project and within the larger organization(s). This information will help enhance immediate project performance and provide input into the enterprise ICT SCRM process; - Collect information on whether the trade-offs that were made during the procurement with regards to mitigating ICT supply chain risks substantially increased that risk; - Identify gaps that were not addressed in past projects and how they can be filled; - Monitor and periodically (or continuously if appropriate) reevaluate changes in the risk environment that impact the supply chain including technology innovation, operational environment, regulatory environment, etc. Respond to change where appropriate through modifying ICT SCRM requirements or if needed, modifying relationships with integrators or suppliers. Note: (1) Use information as available, including information from commercial sources, U.S. government agencies, and intelligence information as appropriate.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Notional Supply Chain Risk Management Practices for Federal Information Systems."}]}
{"id": "nist_00723", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Derived Personal Identity Verification (PIV) Credentials provide? (Section 83) _\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Standards (PKCS) #10 format over PKIX-CMP. The Entrust Datacard Managed CA returns the signed DPC certificate to the Entrust IdentityGuard service. Issuing the DPC in this test scenario is based upon the subscriber's ownership of a PIV credential and DPC eligibility. In this example solution, the MyID CMS fulfills the role of a PIV Card issuer, a prerequisite to enrollment for a DPC, having been configured with profiles that were compatible with the test PIV Cards used in the example implementation. Next, we uploaded test PIV identities to the MyID CMS through a specialized application that included required PIV data to be stored on the card. An Issue Card workflow completed the PIV issuance within the MyID Desktop administrative console. PIV holders were eligible for a Derived PIV when the identities were mapped to a local MyID group. See Figure 5-9 for a screenshot of the test PIV Card user. Figure 5-9 Test PIV Card User <!-- image --> \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ The DPC issuance process begins with a DPC applicant using the PKI-AUTH authentication mechanism from Section 6.2.3.1 of FIPS 201-2 [1] at the MyID Self-Service Kiosk. Once the applicant's PIV Card is inserted into the kiosk, the applicant is prompted for the PIV Card PIN as depicted in Figure 5-10. After successful PIV Card authentication, the kiosk transmits PIV Card information to the MyID CMS through secure transport, where a job is created to handle the second phase of issuance to the end point. Figure 5-10 Kiosk Workflow <!-- image --> The DPC issuance process requires the use of the Identity Agent mobile application or the self-service application to complete the workflow.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_00724", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Government Smart Card Interoperability Specification, Version 2.1 say about 6.4.1 Grammar Rules? (Part 6) According to Government Smart Card Interoperability Specification, Version 2.1, 6.4.1 Grammar Rules: in the APDU between the GSC-IS Default and the Cryptoflex card are the CLA byte and the P1 parameter. Therefore, only two tuples are necessary since the rest of the APDU is defined by the GSC-IS VCEI. The tuples required to define this SELECT DF command for the Cryptoflex card would be: Table 6-8: Derived Select DF Tuple | # | C-Byte | C-Byte | C-Byte | V-Byte | Description | Description | Description | Tuple | |-----|----------|----------|----------|----------|---------------------|---------------|------------------|---------| | | S | P | FC | | Function, Parameter | V/D | Value/Descriptor | | | 1 | 0 | 1 | 1 | C0 | Select File, CLA | V | 'C0' | 11C0 | | 2 | 0 | 3 | 1 | 00 | Select File, P1 | V | '00' | 3100 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_00725", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Intrusion Detection and Prevention Systems (IDPS) provide? (Section 169) include network forensic analysis tools, anti-malware technologies (antivirus software and antispyware software), and firewalls and routers. This section provides guidance on selecting IDPS products. It first discusses the identification of general requirements that the IDPS products should meet. Next, it provides sets of criteria that can be used to evaluate four aspects of IDPS technologies: security capabilities, performance, management, and life cycle cost. Finally, the section concludes with a brief discussion of performing hands-on and paper evaluations of products, and when each evaluation technique is most appropriate. This section assumes that an organization has already determined that a particular type of IDPS technology-network-based, wireless, network behavior analysis (NBA), or host-based-is needed. A comparison of the technology types, which can be helpful for selecting the one most appropriate for a particular need, is provided in Section 8. Organizations should use risk management techniques to identify the security controls necessary to mitigate risk to an acceptable level. Although it may be tempting to simply choose a product, using a risk management process to choose the most effective blend of controls enhances an organization's security posture. An explanation of the risk management process is outside the scope of this document; NIST SP 800-30, Risk Management Guide for Information Technology Systems , contains additional information on it. Before evaluating IDPS products, organizations should first define the general requirements that the IDPS solution and products should meet. The features provided by IDPS products and the methodologies that they use vary considerably, so a product that best meets one organization's requirements might not be suitable for meeting another organization's requirements.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Guide to Intrusion Detection and Prevention Systems (IDPS)."}]}
{"id": "nist_00726", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain core attributes according to NIST Digital Identity Guidelines_ Federation and Assertions According to Digital Identity Guidelines_ Federation and Assertions, core attributes: The set of identity attributes that the CSP has determined and documented to be required for identity proofing and to provide services.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Digital Identity Guidelines_ Federation and Assertions."}]}
{"id": "nist_00727", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Verifying Business Identity : according to NIST A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems According to A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems, Verifying Business Identity :: This use case considers a system to issue and manage public identifiers and credentials for businesses. It could follow either a top-down authority model, such as a system owned by some central authority (e.g., government, chamber of commerce) that identity proofs businesses, or a bottomup authority model (e.g., applications that self-register in an application store). Once originated in the system, businesses have identifiers and can be issued credentials for certificates, accreditations, and other types of verifiable information that will serve for authentication during commercial interactions. Additionally, businesses can become credential issuers with respect to their staff members. In turn, staff members can build verifiable presentations proving that they act on behalf of their company. From an architectural standpoint, identifiers and credentials are both stored in a common onchain registry, allowing for any participant to publicly verify the information of a given business. The solutions proposed by the Global Legal Entity Identifier Foundation, uPort [74], and VON [55] illustrate this use case.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, identity management. Contains security framework guidance for authentication systems. Source: A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems."}]}
{"id": "nist_00728", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is WiMAX Forum according to Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective? WiMAX Forum: The WiMAX Forum is an industry-led, not-for-profit organization formed to certify and promote the compatibility and interoperability of broadband wireless products based upon the harmonized IEEE 802.16/ETSI (European Telecommunications Standards Institute) HiperMAN standard.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective."}]}
{"id": "nist_00729", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance) provide? (Section 223) ----------------------------------------------------------------------------------------------------------------------------------------| | Reference(s) | 1. SP 800-73-4 Part 2, Section 3.2.2 2. AS05.01, AS05.23 through AS05.27 , and AS05.24A-R4 | | Precondition(s) | 1. PIV Application PIN and Global PIN (if supported) reset retry counter values (maximum number of PIN tries allowed) are recorded. 2. PIV Card Application PIN is recorded. 3. Global PIN (if supported) is recorded. 4. The IUT is placed within the reading range of the contactless reader. 5. There exists a valid PC/SC connection between the test system and the contactless reader. 6. No other contactless card is within the proximity of the reader. 7. The PIV Card Application is the currently selected application on the card. 8. There exists a valid VCI connection to the card. 9. No application is currently connected to the PIV Card Application. | | Test Scenario | 1. Repeat test steps from C.2.2.1, with the exception of steps 1 (selecting PIV Card Application) and 3 (PUK tests), using the '0C' CLA byte 2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)."}]}
{"id": "nist_00730", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Verification and Test Methods for Access Control Policies_Models say about Privilege leakage? According to Verification and Test Methods for Access Control Policies_Models, Privilege leakage: Privilege (i.e. action and resource pair) leakage refers to situations in which a subject is able to access resources that are prohibited by the safety requirements. Such leakage may cause either the privilege escalation from one resource domain or class to prohibited ones such as leakage from lower to higher ranks of an MLS policy, or privilege leak such as from one role to other prohibited ones of an RBAC policy. Privilege leakage can be caused by mistaken privilege assignment directly or careless privilege inheritance indirectly.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Verification and Test Methods for Access Control Policies_Models."}]}
{"id": "nist_00731", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-1 in Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers? (Part 183) Control CM-1: out the magfido Files and Directories This section provides additional information regarding files referenced and/or modified by StrongKey to implement FIDO U2F MFA for these example implementations. If you are familiar with Magento, then you may skip this section; others may find this section to be helpful in understanding what must be done to integrate FIDO U2F into their Magento instance in a production environment. Magento includes several boilerplate/configuration files: composer.json and registration.php are those that must be included in every Magento module because they identify the module to the Magento system. The etc folder contains configuration files: - \uf0a7 module.xml is a boilerplate file. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ - \uf0a7 di.xml tells Magento to override the default PaymentInformationManagement.php file with StrongKey \u02bc s custom version (named PIMOverrideFidoAuthenticate.php ). - \uf0a7 extension\\_attributes.xml tells Magento that purchase-transaction data sent to the server may have signature data appended to it, which can be identified by the attribute name signature . - \uf0a7 etc/frontend/di.xml adds an AdditionalConfigProvider that supplies the MFA modal dialogue with the file name loading.gif . - \uf0a7 routes.xml tells Magento that this module defines controllers that will handle uniform resource locator (URL) requests to fidou2fauthenticator. The api folder contains interface files describing valid functions of the models FidoService and RiskAssessor . The interface files are named FidoServiceInterface.php and RiskAssessorInterface.php . The block folder contains server-side logic to generate views displayed by the browser.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, mfa, sso. Contains security framework guidance for authentication systems. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_00732", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Block Cipher Modes of Operation_ the CCM Mode for Authentication and Confidentiality provide? (Section 21) may be considered as the parameter of the formatting function that determines the value of q .) The value of n , in turn, determines the maximum number of distinct nonces, namely, 2 8 n . Thus, the fourth condition amounts to a tradeoff between the maximum number of invocations of CCM under a given key and the maximum payload length for those invocations. The formatting of the input data ( N , A , P ) into a sequence of blocks B 0 , B 1 , \u2026, B r is presented in the following three sections: in Section A.2.1, the formatting of the nonce and control information such as length indicators is specified; in Section A.2.2, the formatting of A is specified; in Section A.2.3, the formatting of P is specified. B B B B The leading octet of the first block of the formatting, B 0, contains four flags for control information: two single bits, called Reserved and Adata , and two strings of three bits, to encode the values t and q . The encoding of t is [( t -2)/2]3, and the encoding of q is [ q -1]3. Thus, for example, if the MAC length is 8 octets, then t is encoded as 011. Note that the encoding 000 in both cases does not correspond to a permitted value of t or q . The Reserved bit is reserved to enable future extensions of the formatting; it shall be set to '0'. The Adata bit is '0' if a =0 and '1' if a &gt;0. The ordering of the flags within the octet is given in Table 1. B Table 1: Formatting of the Flags Octet in B 0 | Bit number | 7 | 6 | 4 | 3 | 2 | 1 | 0 | |--------------|----------|-------|---------------|-----|-----|-----------|-----| | Contents | Reserved | Adata | [( t -2)/2] 3 | | | [ q -1] 3 | | The remaining 15 octets of the first block of the formatting are devoted to the nonce and the binary representation of the message length in q octets, as given in Table 2. B Table 2: Formatting of B 0 | Octet number | 0 | 1 ...", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Block Cipher Modes of Operation_ the CCM Mode for Authentication and Confidentiality."}]}
{"id": "nist_00733", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.1.3 Six Control Categories. according to NIST Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls, 4.1.3 Six Control Categories.: As to controls, NBS has provided detailed discussion of six basic control categories and indicated the general problems that each will address. Included are: * Data Validation - -Consistency and reasonableness checks - -Data entry validation - -Validation during processing - -Data element dictionary/ directory * User Identity Verification * Authorization * Journal ling * Variance Detection * Encrjrption", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls."}]}
{"id": "nist_00734", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector provide? (Section 194) I | Introduction of malicious software | PROTECT (PR) Protective Technology DETECT (DE) Anomalies and Events Detection Security Continuous Monitoring | | I | Unintended use of service | IDENTIFY (ID) ID.AM-2: Software platforms and applications within the organization are inventoried.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, continuous monitoring. General security reference material without sensitive content. Source: Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector."}]}
{"id": "nist_00735", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Conducting Risk Assessments say about COMMON TERMS AND DEFINITIONS? (Part 19) According to Guide for Conducting Risk Assessments, COMMON TERMS AND DEFINITIONS: s provided by security controls planned or in place. | | Risk Assessment Methodology | A risk assessment process, together with a risk model, assessment approach, and analysis approach. | | Risk Assessment Report | The report which contains the results of performing a risk assessment or the formal output from the process of assessing risk. | | Risk Assessor | The individual, group, or organization responsible for conducting a risk assessment. | | Risk Executive (Function) [CNSSI No. 4009] | An individual or group within an organization that helps to ensure that: (i) security risk-related considerations for individual information systems, to include the authorization decisions for those systems, are viewed from an organization-wide perspective with regard to the overall strategic goals and objectives of the organization in carrying out its missions and business functions; and (ii) managing risk from individual information systems is consistent across the organization, reflects organizational risk tolerance, and is considered along with other organizational risks affecting mission/business success. | | Risk Factor | A characteristic used in a risk model as an input to determining the level of risk in a risk assessment. | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | Risk Management [NIST SP 800-39] [CNSSI No.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Guide for Conducting Risk Assessments."}]}
{"id": "nist_00736", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for Managing the Security of Mobile Devices in the Enterprise say about 5.3.2. Integration of EMM into the Enterprise Service Infrastructure? According to Guidelines for Managing the Security of Mobile Devices in the Enterprise, 5.3.2. Integration of EMM into the Enterprise Service Infrastructure: Both large and small enterprises may connect their EMM system to existing enterprise infrastructure services to improve the security management of mobile devices. Such services support authentication, identification, and access control to enterprise networks and resources. The Remote Authentication Dial-In User Service (RADIUS) is a standard network authentication service protocol that provides authentication of access credentials followed by policy-based network resource assignments (e.g., Internet Protocol [IP] address, permitted network connection time). Directory services, such as Microsoft's Active Directory, map network resources (e.g., volumes, printers, users, devices) to network addresses. Enterprise systems use the Lightweight Directory Access Protocol (LDAP) to communicate with directory services. Another set of services enables remote connectivity via a VPN to enterprise systems. By integrating an EMM with enterprise backend infrastructure services such as RADIUS or directory services, an organization can enable finer-grained management of mobile device access to mission-critical enterprise resources. System administrators can set policy-based configurations for mobile devices to constrain access to sensitive resources, depending on mobile device conditions (e.g., connection from a public WiFi network or user-managed device running a corporate application). When enterprises deploy an EMM without integrating it with their backend security infrastructure, mobile device connections to the enterprise network may be managed via global passphrases for connection to the enterprise WiFi network. Mobile devices with WiFi network access can then reach any of the services on the enterprise network, meaning that when a device is connected to the WiFi network, it can access everything on the typical enterprise network.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Guidelines for Managing the Security of Mobile Devices in the Enterprise."}]}
{"id": "nist_00737", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to Computer Security Division 2005 Annual Report? http: //csrc.nist.gov/sec-cert Contacts: Dr. Ron Ross (301) 975-5390 ron.ross@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2005 Annual Report."}]}
{"id": "nist_00738", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control MA-3 in Guide to Operational Technology (OT) Security? Control MA-3: (2) MAINTENANCE TOOLS | INSPECT MEDIA", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_00739", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance say about 1.3.3 Single or Multi-Use Keys? According to Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance, 1.3.3 Single or Multi-Use Keys: A major thrust from Part 1 of this Recommendation is that, in general, keys shall not be used for multiple cryptographic purposes. For example, the same key shall not be used to generate a digital signature and to establish other keying material (see [SP 800-57 Part 1, Sec. 8.1.5.1.1.2 ] for the rare exceptions to this guidance). It is less clear as to whether a digital signature key, for example, can be used only for a specific application (e.g., signing e-mail) or for multiple applications (e.g., for both signing e-mail and signing documents). In some cases, it may be acceptable for an application to share keys with other applications. In other cases, sharing keys may not be desirable. For example, best practices indicate that a server's TLS keys should not be used to support other applications. Even where keys are used to perform the same cryptographic operation (e.g., digital signatures), sharing keys may be inappropriate because one application could be providing one service (e.g., authentication), while a second application could be providing a different service (e.g., non-repudiation). It is important to remember that it may be a bad idea to use keys for multiple applications. An agency should perform a risk assessment when considering the use of the same key for multiple applications.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance."}]}
{"id": "nist_00740", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Random Number Generation Using Deterministic Random Bit Generators say about 11 Assurance? (Part 2) According to Recommendation for Random Number Generation Using Deterministic Random Bit Generators, 11 Assurance: ation. However, this level of testing is outside the scope of this Recommendation. Note that any entropy input used for testing (either for validation testing or health testing) may be publicly known. Therefore, entropy input used for testing shall not be used for normal operational use.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Number Generation Using Deterministic Random Bit Generators."}]}
{"id": "nist_00741", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography say about 6.4.2.3.2 Recipient Obtains Assurance Directly from the Claimed Owner (i.e., the Other Party)? (Part 2) According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography, 6.4.2.3.2 Recipient Obtains Assurance Directly from the Claimed Owner (i.e., the Other Party): ssurance to party V that party U possesses the private key corresponding to PubKeyU (the public key that was associated with party U when that key pair is used during the keyagreement transaction). 4. The KAS2-bilateral-confirmation scheme in Section 8.3.3.4 can be used to provide assurance to each party that the other party possesses the correct private key that corresponds to the other party's public key; i.e., when bilateral key-confirmation is successful, party U obtains assurance that party V possesses the private key corresponding to PubKeyV (the key pair that was associated with party V and that was used during the key-agreement transaction), and party V obtains assurance that party U possesses the private key corresponding to PubKeyU (the key pair that was associated with party U and that was used during the key-agreement transaction). 5. The KTS-OAEP-Party\\_V-confirmation scheme in Section 9.2.4.2 can be used to provide assurance to party U (the key-transport sender) that party V (the key-transport receiver) possesses the private key corresponding to PubKeyV (the key pair that was associated with party V and that was used during the key-agreement transaction). The recipient of a public key (or agents trusted to act on the recipient's behalf) shall determine whether or not using one of the key-establishment schemes in this Recommendation to obtain assurance of possession through key confirmation is sufficient and appropriate to meet the security requirements of the recipient's intended application(s). Other approved methods (e.g., see Section 5.4.4 of SP 800-57-Part 1) of directly obtaining this assurance of possession from the owner are also allowed. If obtaining assurance of possession directly from the owner is not acceptable, then assurance of possession shall be obtained indirectly as discussed in Section 6.4.2.3.1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography."}]}
{"id": "nist_00742", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Technical Guide to Information Security Testing and Assessment provide? (Section 97) ible for damages incurred by the organization being assessed. External entities should also understand and comply with the organization's applicable policies and operational and security requirements. In addition to those listed above, the responsibilities for external assessors include: - GLYPH&lt;c=31,font=/DGCOEC+Webdings&gt; Coordinating and communicating with the organization being assessed - GLYPH&lt;c=31,font=/DGCOEC+Webdings&gt; Ensuring that proper authority is granted, and maintaining a signed copy of the assessment plan to ensure all updates are documented - GLYPH&lt;c=31,font=/DGCOEC+Webdings&gt; Signing and abiding by any required nondisclosure agreements - GLYPH&lt;c=31,font=/DGCOEC+Webdings&gt; Properly protecting data in accordance with the organization's regulations, including handling, transmission, storage, and deletion of all collected data and resulting reports. The environment in which assessors operate differs according to the techniques being used. For many types of tests, assessors can operate either onsite or offsite, with onsite testing defined as testing executed at the organization's location. Placing assessors offsite, however, may make the test more realistic (e.g., when applying the covert testing approach). For examinations, assessors are generally located onsite so they can easily access the organization's security documentation, logs, and other information. For assessments performed by third parties, the organization will need to determine the appropriate level of physical access (e.g., unrestricted, escorted). For technical assessments conducted from within the network-such as security configuration reviews and vulnerability scanning-assessors should be provided network access either onsite, through an encrypted virtual private network (VPN) tunnel, or via a dedicated connection from a trusted environment such as an approved test lab.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technical Guide to Information Security Testing and Assessment."}]}
{"id": "nist_00743", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for the Secure Deployment of IPv6 provide? (Section 201) pe of tunneling is used. Ensuring that address selection policy is correctly specified can affect other assumptions about security. The address selection rules can help enable some attacks on privacy. By probing a host with requests that come from different source addresses and observing what source addresses the target uses for replies, one can extract information about the set of addresses used by the target. If an attacker were to compromise and modify the address selection policy table, this could cause a manin-the-middle or DOS attack. This can be mitigated by applying best practices of desktop and server security (e.g., malware filtering in web and e-mail content, patching processes, removal of administrative rights from end-users, etc.), methods that apply equally to IPv6 and IPv4. Experience using the rules described above for address selection has unveiled several problematic configurations, which require further attention. When a link has more than one router, or a site border router is connected to more than one ISP, multiple prefixes can be used. If the prefix of a source address does not correspond to the connection used, the packet may be dropped because of ingress filtering, or an asymmetrical route may be established, and returned packets may be dropped due to packet filtering. This problem is even worse in the case in which one of the routers is not globally connected but only connected to a closed network segment. Prefix renumbering increases the complexity of this, because choices of appropriate prefixes are not static. The longest prefix match rule can always distinguish currently allocated global addresses from unique local addresses, but this will become an issue when global addresses with a leading one bit begin to be allocated. Applications may need to have better control over address selection in certain cases. One case is choosing between temporary and permanent addresses; another is between home and care-of addresses.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_00744", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog say about Table of Contents? (Part 4) According to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog, Table of Contents: | PROTECTION.................................................................................... 17 | | | (CRY) Cryptography Capabilities and Support..............................................17 | | | (KEY) Cryptographic Key Management ........................................................17 | | | (STO) Secure Storage ..................................................................................18 | | (STX) | Secure Transmission ..........................................................................18 | | LA - LOGICAL ACCESS TO INTERFACES..........................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog."}]}
{"id": "nist_00745", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities say about 2.1.1.4 Access Complexity (AC)? (Part 2) According to The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities, 2.1.1.4 Access Complexity (AC): is a person or entity whose direct actions take advantage of the software security configuration issue. A user may be malicious or non-malicious. In contrast, an attacker is always malicious. Table 3. Access Complexity Scoring Evaluation | Metric Value | Description | |----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | High (H) | Active Exploitation: Specialized access conditions exist for active exploitation. For example: \u2022 The vulnerability makes it only slightly easier for an attack to succeed.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities."}]}
{"id": "nist_00746", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2014 Annual Report say about NIST Technical Series Publications FIPS, SPs, NISTIRs, and ITL Bulletins? (Part 4) According to Computer Security Division 2014 Annual Report, NIST Technical Series Publications FIPS, SPs, NISTIRs, and ITL Bulletins: for ISO/IEC 27001 and 15408 | August 2014 | | SP 800-16 Revision 1 (Second Draft) (Third Draft) | A Role-Based Model For Federal Information Technology/ CyberSecurity Training | October 2013 March 2014 | | NIST INTERAGENCY OR INTERNAL REPORTS (NISTIRs) | NIST INTERAGENCY OR INTERNAL REPORTS (NISTIRs) | NIST INTERAGENCY OR INTERNAL REPORTS (NISTIRs) | |--------------------------------------------------|-------------------------------------------------------------------------|--------------------------------------------------| | Publication Number | Publication Title | Draft Released Date | | NISTIR 8023 | Risk Management for Replication Devices (RDs) | September 2014 | | NISTIR 8018 | Public Safety Mobile Application Security Requirements Workshop Summary | July 2014 | | NISTIR 8014 | Considerations for Identity Management in Public Safety Mobile Networks | July 2014 | | NISTIR 8006 | NIST Cloud Forensic Science Challenges | June 2014 | | NISTIR 7981 | Mobile, PIV, and Authentication | March 2014 | | NISTIR 7977 | NIST Cryptographic Standards and Guidelines Development Process | February 2014 | | NISTIR 7966 | Security of Automated Access Management Using Secure Shell (SSH) | August 2014 | | NISTIR 7924 (Second Draft) | Reference Certificate Policy | May 2014 | | NISTIR 7863 | Cardholder Authentication for the PIV Digital Signature Key | December 2013", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, identity management. Contains security framework guidance for authentication systems. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_00747", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Internet Messaging according to Cell Phone Forensic Tools_ an Overview and Analysis? Internet Messaging: N.A. - The Nokia 6200 does not support email. (NA)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_00748", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain SI-2 FLAW REMEDIATION according to NIST Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, SI-2 FLAW REMEDIATION: Supplemental C-SCRM Guidance: The output of flaw remediation activities provides useful input into the ICT/OT SCRM processes described in Section 2 and Appendix C. Enterprises should require their prime contractors to implement this control and flow down this requirement to relevant sub-tier contractors.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_00749", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain ALARMS according to NIST Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS) According to Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS), ALARMS: Any event that results in an entry in the security variance log, also generates an alarm count. When the count exceeds a threshold, corrective action is initiated. In the early days of the system, when it owned all of the lines, the corrective action was to disable the terminal and send a message to it about the variance. Since management action was required to enable the terminal again, this was a powerful mechanism for informing management of the alarm condition. Today, the system employs a network shared with other systems and applications. Though it can still disable the port, it cannot really disable the terminal. Therefore the threshold is now set to ten rather than the old two. While no longer as effective in notifying management of the variance, the control is still effective in limiting exhaustive attacks. Today, corrective action relies more heavily upon the information in the variance journal.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)."}]}
{"id": "nist_00750", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)? (Part 183) Control PD-12: | | ## Table G.2: Controls and Assessment Procedures for Derived PIV Credential Issuers (DPCIs) This table specifies the controls and assessment procedures for the Derived PIV Credential and its related token. The controls in this section are mapped to the PCI controls in G.1 to assist issuers that intend to issue both types of credentials. Unlike for a PIV Card Issuer, not all issuer controls are applicable to a Derived PIV Credential Issuer. Certain issuer controls are applicable to only LOA-3 or to only LOA-4 Derived PIV Credentials and therefore must be implemented by the issuer only if they are issuing that level of a Derived PIV Credential. This is represented via the ' applicability ' column within this table. Controls with an applicability column marked with DPCI (e.g., without LOA-4 or 3 postfix) apply to both LOA-3 and LOA-4 Derived PIV Credential.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, token. Contains security framework guidance for authentication systems. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_00751", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case say about Prerequisites? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case, Prerequisites: Windows 2012 R2 server (preferably two for redundancy) up to date on patches, static IP address assigned with primary DNS server set to 127.0.0.1 (localhost) 1. Launch the Windows Server Manager and click on Add Roles and Features 2. Click ' Next ' at the first page as shown below <!-- image --> 3. Select Role Based or Feature Based Installation under Installation Type 4. Select Active Directory Domain Services and DNS Server to install. Click Next. <!-- image --> <!-- image --> 5. Click Next on the Features screen, leave the default options selected, 6. Click Next on the AD DS screen and the following DNS Server screen as well. 7. Verify your settings on the Confirmation screen. Click Install to proceed. <!-- image --> <!-- image --> 8. Wait till the installation process completes and shows an Installation succeeded message. Hit Close button. 9. Launch Server Manager again and click on Promote this server to a domain controller . 10. Select Add a new forest on the Deployment Configuration step, as this would be a new domain controller in a new forest. Mention a Root Domain name as applicable to your environment. <!-- image --> <!-- image --> 11. Set a Directory Services Restore Mode password in the next step. Click Next 12. Under ' DNS Options ' leave the default options selected. Click Next <!-- image --> <!-- image --> 13. Confirm the NETBIOS domain name under Additional Options . Click Next . 14. Leave the default folder paths as it is Under Paths . Click Next <!-- image --> <!-- image --> 15. Confirm all the settings On the Review Options page. Click Next . 16. Click Install on the Prerequisites Check to launch the installation process. The server will auto reboot upon completion. 17. Login with domain administrator credentials upon reboot. Open Server Manager and click on Active Directory Users and Computers under Tools to manage your AD. <!-- image --> <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case."}]}
{"id": "nist_00752", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to SSL VPNs provide? (Section 166) Lightweight Directory Access Protocol | | MAC | Message Authentication Code | | MIB | Management Information Base | | MPPE | Microsoft Point to Point Encryption | | MS-CHAP | Microsoft Challenge Handshake Authentication Protocol | | MTU | Maximum Transmission Unit | | NAT | Network Address Translation | | NetBEUI | NetBIOS Extended User Interface | | NetBIOS | Network Basic Input/Output System | | NIST | National Institute of Standards and Technology | | OMB | Office of Management and Budget | | PAP | Password Authentication Protocol | | PC | Personal Computer | | PDA | Personal Digital Assistant | | PGP | Pretty Good Privacy | | PIN | Personal Identification Number | | PKI | Public Key Infrastructure | | POP | Point of Presence | | PPP | Point-to-Point Protocol | | PPTP | Point-to-Point Tunneling Protocol | | QoS | Quality of Service | | RADIUS | Remote Authentication Dial-In User Server | | RC4 | Rivest Cipher 4 | | RCP | Remote Copy Protocol | | RFC | Request for Comment | | RMON | Remote Monitoring | | RSA | Rivest Shamir Adleman | | S/MIME |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Guide to SSL VPNs."}]}
{"id": "nist_00753", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guidelines for Securing Radio Frequency Identification (RFID) Systems? (Part 131) Control ES-1: odify and amplify signals in unintended and potentially harmful ways, and - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Legitimate radios with which the RF subsystem communication will cause interference. Applicability: All environments in which the organization deploying RFID systems determines the location of the RF equipment (which excludes many consumer and supply chain applications). ## Benefits: - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Reduced risk of interference with legitimate radios - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Reduced risk of eavesdropping and unauthorized RF subsystem transactions - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Mitigation of HERF/HERO/HERP ## Weaknesses: - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Tag location cannot always be controlled, such as when tags are used to track mobile items (e.g., hospital cart) or items in transit (e.g., pallet on a truck). - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Radio interference may persist even if the tags or readers are placed in a new location that is still sufficiently close to other radios. 43 ## 5.2.3 Secure Disposal of Tags Control: Secure disposal involves physically or electronically destroying tags, as opposed to just discarding them, when they are no longer needed to perform their intended function. Physical destruction may involve manual tearing or shredding using a paper shredder. Electronic destruction can be accomplished by using a tag's kill feature or using a strong electromagnetic field to render a tag's circuitry permanently inoperable. When a tag supports an electronic disabling mechanism, it usually is the preferred way to disable a tag before it is disposed because it can be accomplished without touching each tag, thereby reducing the cost of the effort. The kill feature is also discussed in Section 5.3.3.3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: rmf, fips, security control. General security reference material without sensitive content. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_00754", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Security Considerations for Voice Over IP Systems? (Part 84) Control HA-1: voice into digital data and back again, and may also compress and decompress the data for more efficient transmission. Firewall Control Proxy - component that controls a firewall's handling of a call. The firewall control proxy can instruct the firewall to open specific ports that are needed by a call, and direct the firewall to close these ports at call termination. H.323 - The International Telecommunications Union (ITU) standard for packetswitched network voice and video calling and signaling. Jitter - non-uniform delays that can cause packets to arrive and be processed out of sequence Latency - time delay in processing voice packets. Media gateway - the interface between circuit switched networks and IP network. Media gateways handle analog/digital conversion, call origination and reception, and quality improvement functions such as compression or echo cancellation. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Media Gateway Control Protocol - common protocol used with media gateways to provide network management and control functions. PSTN - the public switched telephone network. QoS -Quality of Service - a network property that specifies a guaranteed throughput level. Session Initiation Protocol (SIP) - A standard for voice and video over a packet switched network developed by IETF. Sniffer - a network monitoring tool, usually a software tool running on a PC.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_00755", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Considerations for Identity Management in Public Safety Mobile Networks say about 3. Identity Management Guidance &amp; Frameworks? According to Considerations for Identity Management in Public Safety Mobile Networks, 3. Identity Management Guidance &amp; Frameworks: This section introduces the relevant identity management guidance from both public and private entities. Federal guidance includes OMB M-04-04, E-Authentication Guidance for Federal Agencies, NIST SP 800-63-2, Electronic Authentication Guideline , and HSPD-12, Policy for a Common Identification Standard for Federal Employees and Contractors , alongside its associated standards. Industry guidance includes information from the National Public Safety Telecommunications Council (NPSTC) and the Alliance for Telecommunications Industry Solutions (ATIS) guidance and frameworks.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, identity management, sso. Contains security framework guidance for authentication systems. Source: Considerations for Identity Management in Public Safety Mobile Networks."}]}
{"id": "nist_00756", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cell Phone Forensic Tools_ an Overview and Analysis Update say about Scenario Results - Cell Phones? (Part 2) According to Cell Phone Forensic Tools_ an Overview and Analysis Update, Scenario Results - Cell Phones: Table 13: Results Matrix | | Device | Device | Device | Device | Device | Device | |----------------------------|---------------|--------------|---------------|-------------|------------|------------| | Scenario | Ericsson T68i | Motorola V66 | Motorola V300 | Nokia 6610i | Nokia 6200 | Nokia 7610 | | Connectivity and Retrieval | Meet | Meet | Meet | Meet | Meet | Meet | | PIM Applications | Below | Below | Below | Below | Below | Below | | | Device | Device | Device | Device | Device | Device | |---------------------------------|---------------|--------------|---------------|-------------|------------|------------| | Scenario | Ericsson T68i | Motorola V66 | Motorola V300 | Nokia 6610i | Nokia 6200 | Nokia 7610 | | Dialed/Received Phone Calls | Below | Below | Below | Below | Below | Miss | | SMS/MMS Messaging | Below | Below | Below | Below | Below | Miss | | Internet Messaging | Miss | NA | Below | NA | NA | Miss | | Web Applications | Miss | NA | Miss | Below | Miss | Miss | | Text File Formats | NA | NA | Miss | Below | Below | Below | | Graphics File Formats | Miss | NA |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis Update."}]}
{"id": "nist_00757", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6.1 W and W -1 according to NIST Recommendation for Block Cipher Modes of Operation_ Methods for Key Wrapping According to Recommendation for Block Cipher Modes of Operation_ Methods for Key Wrapping, 6.1 W and W -1: Algorithm 1 below specifies the wrapping function, W, for KW-AE (see Sec. 6.2) and KWP-AE (see Sec. 6.3), using the same KEK and designated cipher function.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Block Cipher Modes of Operation_ Methods for Key Wrapping."}]}
{"id": "nist_00758", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography? (Part 2) Control HA-3: uted using ephemeral keys in a Diffie-Hellman primitive. | | Z s | Acomponent of the shared secret (represented as a byte string) that is computed using static keys in a Diffie-Hellman primitive. | The following notations are used for FFC and ECC in this Recommendation. Note that the notation sometimes differs between the two scheme types due to the differing notations used in the two standards on which this Recommendation is based (i.e., ANS X9.42 and ANS X9.63). FFC: | GF(p) | The finite field with p elements, where p is an (odd) prime number. The elements of GF ( p ) can be represented by the set of integers {0 , 1 , \u2026, p - 1}. The addition and multiplication operations for GF ( p ) can be realized by performing the corresponding integer operations and reducing the results modulo p . | |------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | GF ( p ) * | The multiplicative group of non-zero field elements in GF ( p ). | | g | An FFC domain parameter; the selected generator of the multiplicative subgroup of prime order q in GF ( p ) * . | | k mod p | The modular reduction of the (arbitrary) integer k by the (positive) integer p (the modulus ) . For the purposes of this Recommendation, j = k mod p is the unique integer satisfying the following two conditions: 0 \uf0a3 j < p , and k - \uf020 j is a multiple of p . In short, j = k - \uf0eb k / p \uf0fb p . | | p | An FFC domain parameter; an odd prime number that determines the size of the finite field GF ( p ).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}]}
{"id": "nist_00759", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings provide? (Section 62) organization management service (VOMS) [5] was developed by the European Data Grid project to allow for attribute-based authorization to the Globus Toolkit job management services. It uses X.509 attribute certificates [7] in a push mode to assert attributes in a modified version of the Globus Toolkit. We believe that Shibboleth, with its use of SAML, will be more easily interoperable with Web services-based technologies emerging in the Grid community. VOMS also does not support a pseudonymous mode, nor does it have any other provisions for privacy support. The Community Authorization Service (CAS) [17] is similar to Shibboleth in its use of SAML assertions. However CAS operates at the level of capabilities rather than attributes; that is, instead of expressing abstractly what someone is, CAS expresses explicitly what actions they are allowed to take. CAS also does not support a pseudonymous mode or have any other provision for privacy. Akenti [22] and PERMIS [2] are authorization systems that have been integrated with the Globus Toolkit through the use of authorization callouts [13,28]. Both Akenti and PERMIS allow for the use of X.509 attribute certificates to make attribute-based authorization decisions. We envision our work as being complementary to these systems. Our focus falls on the technology to transport SAML assertions from the Shibboleth attribute authority to the Globus Toolkit-based services, whereas these systems are designed primarily as authorization decision makers. We envision a mode of operation in which these systems can be used to provide rich authorization capabilities using Shibboleth-issued SAML assertions in addition to the X.509 attribute certificates they use today. The Signet privilege management system [21] is being developed by a working group of the Internet2 Middleware Initiative.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_00760", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Labels for Open Systems_ an Invitational Workshop provide? (Section 36) six classes: - (1) FIXED LABEL association: the requirement that an application association should be able to be created all of whose A-PDUs are visibly associated with a single security label (i.e. labelled field = the whole association); - (2) FIXED label-set association: the requirement that an application association should be able to be created all of whose A-PDUs are visibly associated with a single set of security labels (i.e. labelled field = the whole association); - (3) variable label association: the requirement that an application association should be able to be created each A-PDUs of which are visibly associated with a single security label, but not necessarily the same one (i.e. labelled field = one A-PDU); - (4) variable label-set association: the requirement that an application association should be able to be created each A-PDUs of which are visibly associated with a single set of security labels, but not necessarily the same one (i.e. labelled field - one A-PDU); - (5) multiple label association: the requirement that an application association should be able to be created each a-pdu of which is divided into a number of fields each visibly associated with one of many security labels (i.e. labelled field = a fraction of an A-PDU); and, - (6) multiple label-set association: the requirement that an application association should be able to be created each a-pdu of which is divided into a number of fields each visibly associated with one of many sets of security labels (i.e. labelled field = a fraction of an A-PDU). The position in the communications architecture at which the access control service is provided may be at a layer below the application layer. 1 Thus there is a gap between the position at which access control is required (the application layer) and the position at which it is provided. This latter layer (or sublayer), at which data labelling is manifest in the layer protocol and service, will be referred to as the (L)-layer.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Security Labels for Open Systems_ an Invitational Workshop."}]}
{"id": "nist_00761", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Policy Machine_ Features, Architecture, and Specification provide? (Section 30) s origins with military and civilian government security policy, where individuals are assigned clearances and messages, reports, and other forms of data are assigned classifications [San94]. The security level of user clearances and of data classifications govern whether an individual can gain access to data. For example, an individual can read a report, only if the security level of the report is classified at or below his or her level of clearance. Defining MAC for a computer system requires assignment of a security level to each subject and each object. Security levels form a strict hierarchy such that security level x dominates security level y, if and only if, x is greater than or equal to y within the hierarchy. The U.S. military security levels of Top Secret, Secret, Confidential, and Unclassified are a good example of a strict hierarchy. Access is determined based on assigned security levels to subjects and objects and the dominance relation between the subject's and object's assigned security. The security objective of MAC is to restrict the flow of information from an entity at one security level to an entity at a lesser security level. Two properties accomplish this. The simple security property specifies that a subject is permitted read access to an object only if the subject's security level dominates the object's security level. The \uf0e9 -property specifies that a subject is permitted write access to an object only if the object's security level dominates the subject's security level. Indirectly, the \uf0e9 -property, also referred to as the confinement property, prevents the transfer of data from an object of a higher level to an object of a lower classification and is required to maintain system security in an automated environment. These two properties are supplemented by the tranquility property, which can take either of two forms: strong and weak.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, secret, top secret. Contains guidance on protecting sensitive government information. Source: Policy Machine_ Features, Architecture, and Specification."}]}
{"id": "nist_00762", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Intrusion Detection and Prevention Systems (IDPS)? (Part 200) Control ES-1: is being monitored because the real-world activity is likely to contain different types of malicious activity, and it is sometimes unclear whether or not the detected activity was actually malicious. Prevention capabilities are generally not tested in real-world environments because they can easily cause disruptions to benign activity. It is very difficult to duplicate real-world environments in lab environments, so organizations performing IDPS testing generally need to do their testing separately in each environment. - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Test Availability. There are no standard IDPS test suites available. Organizations performing IDPS testing need to find ways to generate both malicious activity (to see how well the products identify them) and benign activity (to put the product under normal or heavy loads). The malicious activity should accurately reflect the composition of recent threats against the organization's systems and networks; accordingly, it can take considerable time to identify those threats and acquire tests for them. The tests also need to take into account all detection methodologies used by the IDPSs, because usually different types of tests are needed to properly evaluate the effectiveness of each 55 For more information on the challenges of IDPS testing, see NIST Interagency Report (IR) 7007, An Overview of Issues in Testing Intrusion Detection Systems. It is available at Although it is focused primarily on testing network-based IDPSs, most of the testing problems it discusses are applicable to testing any type of IDPS technology. methodology. 56 Typically it takes a combination of carefully selected tools and custom-written attack scripts to build a reasonable test suite. Each tool and script should be reviewed and tested to ensure that it performs the tests properly. - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Lab Environment Resources.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Intrusion Detection and Prevention Systems (IDPS)."}]}
{"id": "nist_00763", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Enhanced Security Requirements for Controlled Unclassified Information say about Table of Contents? (Part 4) According to Assessing Enhanced Security Requirements for Controlled Unclassified Information, Table of Contents: | PHYSICAL PROTECTION................................................................................................................... | 17 | | 3.11 | RISK ASSESSMENT........................................................................................................................... | 17 | | 3.12 | SECURITY ASSESSMENT .................................................................................................................. | 22 | | 3.13 | SYSTEMANDCOMMUNICATIONSPROTECTION............................................................................. | 23 | | 3.14 | SYSTEMANDINFORMATIONINTEGRITY......................................................................................... | 26 | | REFERENCES .................................................................................................................................. | REFERENCES .................................................................................................................................. | 32 | | APPENDIXA GLOSSARY................................................................................................................ | APPENDIXA GLOSSARY................................................................................................................", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00764", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Building a Cybersecurity and Privacy Learning Program say about 2.4.1.2. Qualitative Measurements? According to Building a Cybersecurity and Privacy Learning Program, 2.4.1.2. Qualitative Measurements: Qualitative measurements are based on descriptive data, for example, data collected through observations, interviews, focus groups, or open-ended text fields in surveys and can provide insight into the learning experience . Some common examples of qualitative learning program data include: - Instructor/presenter observations and feedback - Attitude surveys related to workforce support for the cybersecurity and privacy culture - Open-ended feedback or survey fields - Detailed reports from participants, such as written feedback sent to the program - Focus group discussions with participants, instructors, or other stakeholders - Observations of learning program instruction and interactions - Observations and analyses of instructional case studies - Interviews with participants, instructors, or other stakeholders - Suggestion box submissions", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Building a Cybersecurity and Privacy Learning Program."}]}
{"id": "nist_00765", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control II-4 in 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)? (Part 132) Control II-4: erally, sensitivity means the ## characteristic of an asset that implies it is valuable to the organization using it. It also implies that the asset is vulnerable to accidental or deliberate threats. The determination of unclassified information sensitivity is a management judgment. Agencies are expected to use this part of the CSPP to provide a general description of the value of the information, the reasons for the sensitivity, and the areas within which the information may be vulnerable. Agencies should not provide information which is specific or detailed enough that its disclosure would pose a major threat if the CSPP were to be disclosed. Reviewers look for: - an overview of the generic types of information handled by the system (s) - a general statement of the potential damage which might occur through error, unauthorized disclosure or modification, or unavailability; and - a statement of generic threats to which the system or information may be particularly vulnerable. Sufficient information should be provided to determine the general relevance and potential effectiveness of the security controls specified, when viewed in the context of the system functions and operational environment. Particular care should be taken by the reviewer to understand the nature of the system sensitivities in light of the foregoing discussions of the functions carried out by the system and the environment in which it operates. It is only the combination of functions, environment, and sensitivity which leads management to recognize requirements to establish security controls. ## General Description of Information Sensitivity Agencies are to provide a general description of the types of information handled by the system and the perceived needs for protective measures.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)."}]}
{"id": "nist_00766", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ID-19 in Securing Telehealth Remote Patient Monitoring Ecosystem? (Part 276) Control ID-19: | Cybersecurity Framework v1.1 Subcategory | Device Cybersecurity Capabilities | Manufacturer Nontechnical Supporting Capabilities | HIPAA Security Rule Mapping to Cybersecurity Framework Subcategory | |--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|----------------------------------------------------------------------| | | \uf0a7 Ability to create an organizationally defined system use notification message or banner to be displayed on the IoT device.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_00767", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols say about 8.2.3 Protected Data? According to Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols, 8.2.3 Protected Data: The data field contains a TPDU or concatenated set of TPDUs as per ISO 8073 or ISO 8602.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols."}]}
{"id": "nist_00768", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Domain Name System-Based Electronic Mail Security provide? (Section 269) access-control: ::0/0 refuse # access-control: ::1 allow # access-control: ::ffff:127.0.0.1 allow + access-control: 192.168.3.0/23 allow # if given, a chroot(2) is done to the given directory. # i.e. you can chroot to the working directory, for example, @@ -376,7 +380,7 @@ # you start unbound (i.e. in the system boot scripts). And enable: # Please note usage of unbound-anchor root anchor is at your own risk # and under the terms of our LICENSE (see that file in the source). -# auto-trust-anchor-file: \"/usr/local/etc/unbound/root.key\" + auto-trust-anchor-file: \"/usr/local/etc/unbound/root.key\" # File with DLV trusted keys. Same format as trust-anchor-file. # There can be only one DLV configured, it is trusted from root down. @@ -614,7 +618,7 @@ remote-control: # Enable remote control with unbound-control(8) here. # set up the keys and certificates with unbound-control-setup. -# control-enable: no + control-enable: yes # Set to no and use an absolute path as control-interface to use # a unix local named pipe for unbound-control. ``` ``` ``` ``` 9831 IN A 185.49.140.60 ns.nlnetlabs.nl. 9831 IN AAAA 2a04:b900::8:0:0:60 ;; Query time: 581 msec ;; SERVER: ::1 ;; WHEN: Thu May 12 05:58:20 2016 ;; MSG SIZE rcvd: 209 # CD unset: [rdolmans@unbound ~]$ drill txt bogus.nlnetlabs.nl @::1 ;; ->>HEADER<<- opcode: QUERY, rcode: SERVFAIL, id: 14388 ;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;; bogus.nlnetlabs.nl.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_00769", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Section 438) ishes a list of foreign individuals and entities determined to have violated, attempted to violate, conspired to violate, or caused a violation of U.S. sanctions on Syria or Iran pursuant to EO 13608. It also lists foreign persons who have facilitated deceptive transactions for or on behalf of persons subject to U.S. sanctions. Collectively, such individuals and companies are called 'Foreign Sanctions Evaders' or 'FSEs.' Transactions by U.S. persons or within the United States involving FSEs are prohibited. 4. The System for Award Management (SAM) Exclusions: The SAM contains the electronic roster of debarred companies excluded from federal procurement and nonprocurement programs throughout the U.S. Government (unless otherwise noted) and from receiving federal contracts or certain subcontracts and from certain types of federal financial and non-financial assistance and benefits. The SAM system combines data from the Central Contractor Registration, Federal Register, Online Representations and Certification Applications, and the Excluded Parties List System. It also reflects data from the Office of the Inspector General's exclusion list (GSA) (CFR Title 2, Part 180). 5. The List of Foreign Financial Institutions Subject to Correspondent Account PayableThrough Account Sanctions (the 'CAPTA List'): The CAPTA List replaced the list of Foreign Financial Institutions Subject to Part 561. It includes the names of foreign financial institutions subject to sanctions, certain prohibitions, or strict conditions before a U.S. company may do business with them. 6. The Persons Identified as Blocked: Pursuant to 31 CFR 560 and 31 CFR 560.304, property and persons included on this list must be blocked if they are in or come within the possession or control of a U.S. person. 7. The BIS Unverified List: Parties listed on the Unverified List (UVL) are ineligible to receive items subject to the Export Administration Regulations (EAR) by means of a license exception. 8.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_00770", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Study of Federal Agency Needs for Information Technology Security say about NIST and Non-NIST Participants? According to A Study of Federal Agency Needs for Information Technology Security, NIST and Non-NIST Participants: | Ms. Judy Bloom, U.S. Department of Justice | |-------------------------------------------------------------------------------------| | Mr. Ed Borodkin, National Computer Security Center | | Mr. Richard W. Carr, National Aeronautics Space Administration | | Ms. Dorothea de Zafra, Department of Health & Human Services, Public Health Service | | Mr. Donald Franklin, Department of Veterans Affairs | | Mr. Bill Garvin, Social Security Administration | | Mr. Dennis Gilbert, NIST/CSL | | Ms. Irene Gilbert Perry, NIST/CSL | | Mr. John Haines, Department of the Interior | | Mr. John Ippolito, Comsis | | Ms. Rhonda Joseph, Department of Transportation | | Mr. William G. Logan, Department of Health and Human Services | | Mr. Vic Maconochy, National Computer Security Educators | | Mr. Nick Pantiuk, Grumman Data Systems | | Ms. Sadie Pitcher, Department of Commerce | | Mr. Dennis Steinauer, NIST/CSL |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of Federal Agency Needs for Information Technology Security."}]}
{"id": "nist_00771", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology provide? (Section 9) | Purpose and Scope ........................................................................................ | 1 | | | 1.2 | Changes from Previous Versions.................................................................... | 1 | | | 1.3 | Publication Structure.......................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology."}]}
{"id": "nist_00772", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Study of OSI Key Management provide? (Section 87) .l macro is defined in the Directory Authentication Framework [ISO 9594-8]. As already mentioned the parameters associated with an algorithm can be referenced using the ASN.l ANY DEFINED BY construct. The following ASN.l definitions appear in a protocol that has to be algorithm independent: ``` Algorithmidentifier ::= SEQUENCE { algorithm OBJECT IDENTIFIER, parameters ANY DEFINED BY algorithm OPTIONAL} ``` The protocol entity chooses the algorithm by giving the ASN.l variable algorithm the Object Identifier value of tiie selected algorithm. The field parameters contains the parameters associated with the selected algorithm. The ASN.l data type Algorithmidentifier is defined in [ISO 9594-8]. The following gives an illustration of what kind of data that is sent when the ASN.l data type Algorithmidenttiier appears in an application layer protocol identifying DES used in cbc mode: Figure 5.10.1:2 Data sent when DES is used in cbc mode <!-- image --> By separating from the protocol the parameters relevant for a certain algorithm, nothing algorithm specific needs to be defined in the protocol. This gives a security domain the possibility to choose the algorithms it finds appropriate to use. It also gives the security domain the possibility to use a publicly available key management protocol in combination with its own secret cryptographic algorithms. Another advantage is that the user of the protocol is given the possibility to choose another algorithm when the one being used is broken. As already mentioned, the algorithm specific parameters are defined in a security register. Another way to achieve algorithm independence is by using the concept of document types. In order to understand how document types can be used, parts of the FTAM standard [ISO 8571-2] [ISO 8571-4] are studied.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: A Study of OSI Key Management."}]}
{"id": "nist_00773", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about Interview? According to Assessing Security Requirements for Controlled Unclassified Information, Interview: [SELECT FROM: personnel with responsibilities for defining least privileges; personnel with information security responsibilities; system administrators]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00774", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain USE OF AUTOMATION IN THE EXECUTION OF THE RMF according to NIST NIST_SP_800-37r2_Risk_Management_Framework According to NIST_SP_800-37r2_Risk_Management_Framework, USE OF AUTOMATION IN THE EXECUTION OF THE RMF: Organizations should maximize the use of automation , wherever possible, to increase the speed, effectiveness, and efficiency of executing the steps in the Risk Management Framework (RMF). Automation is particularly useful in the assessment and continuous monitoring of controls, the preparation of authorization packages for timely decision-making, and the implementation of ongoing authorization approaches-together facilitating a real-time or near real-time risk-based decision-making process for senior leaders. Organizations have significant flexibility in deciding when, where, and how to use automation or automated support tools for their security and privacy programs. In some situations, automated assessments and monitoring of controls may not be possible or feasible. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, rmf, fips. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_00775", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DR-1 in Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events? (Part 40) Control DR-1: e information for the resolution of this vulnerability. ## 5.3.5.3 Other Considerations This use case highlights the need for a response-oriented build to collaborate with an identify-oriented build. Identification and resolution of vulnerabilities in custom code are sometimes feasible only through gathering information after the vulnerability has been exploited. This build provides the mechanisms to gather such information, but it is ultimately up to the security team to resolve the vulnerability and learn from the attack. ## 5.3.6 File Modification via Malicious Insider ## 5.3.6.1 Scenario The following scenario was simulated to test the architecture's defense against malicious file and backup modification. A malicious insider is assumed to have stolen administrator-level credentials through non-technical means. The insider, using these credentials, uses remote Windows PowerShell sessions to uniformly modify employee stock information to their benefit across several machines. This attack will also target the enterprise \u02bc s backup system to modify all records of the previous stock information. It is expected that the aspects of the build described above will mitigate the ability of the user to target and modify enterprise data and backups. The method of securing administrator credentials will be considered out of scope for this solution. ## 5.3.6.2 Resolution The build has several layers of defense against this use case. The integrity monitoring capability detects changes to files and backups caused by a malicious insider. When forwarded to the logging and reporting capabilities, the build can report on these changes. Irregularities or differences from the normal backup schedule are important indicators of a compromise. When the security team is alerted to a malicious insider, they can use the mitigation and containment capability to disable the insider's access.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events."}]}
{"id": "nist_00776", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings provide? (Section 384) for a formula f is a triple ( C ; t; \u2030 ) where C is a set of certifi cates, t , 0 is a time instance and \u2030 is an evaluation. We give the semantics of a formula f over an interpretation ( C ; t; \u2030 ) . For any certifi cate C let C:val be the validity time interval of C . For a given set C of certifi cates and time t , let C t = f C 2 Cj t 2 C:val g : C t denotes the set of certs valid at time t and P C t ( Q; \u00a1 ; -; v ) denotes the PDS constructed from the set of certs C t as described in previous section. We defi ne the satisfi ability relation j = between an interpretation and a FTPL formula as follows: ( C ; t; \u2030 ) j = authoriz e ( i; j; d; e ) if the PDS constructed from set of certifi cates C t , P C t can go from confi guration h \u2030 ( i ) ; / i to the confi guration h \u2030 ( j ) ; / i , with authorization variable v \u00b6 e , at the end of the computation, when d = 1 i.e. h \u2030 ( i ) ; / i ) / h \u2030 ( j ) ; / i . If d = 0 the PDS P C t can reach either the above confi guration or the confi guration h \u2030 ( j ) ; \u00a5 i . Note that if the key \u2030 ( i ) directly/indirectly issues term \u2030 ( j ) with greater delegation and authorization rights than specifi ed by d and e respectively, the authorize predicate still holds true. ( C ; t; \u2030 ) j = resolve ( p; q ) if the PDS P C t can go from confi guration corresponding the name p , to the confi guration corresponding the term \u2030 ( q ) . <!-- formula-not-decoded --> <!-- formula-not-decoded --> X f is true at an instance of time t iff f is true in the next instance of time t +1 . ( C ;t; \u2030 ) j = f U [ t 1 ;t 2 ] g iff 9 t 0 2 [ t + t 1 ; t + t 2 ] such that ( C ;t 0 ; \u2030 ) j = g and 8 t 00 : t \u00b7 t 00 &lt; t 0 ( C ;t 00 ; \u2030 ) j = f . f U [ t 1 ;t 2 ] g is true at time t , iff formula f is true from time t to t 0 , where at t 0 , g will be true and t 0 \u00a1 t should be within bounds of [ t 1 ; t 2 ] .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_00777", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Accuracy, Integrity, and Security in Computerized Vote-Tallying say about 2 . 7 California Attorney General's Report? (Part 3) According to Accuracy, Integrity, and Security in Computerized Vote-Tallying, 2 . 7 California Attorney General's Report: counties with 'sloppy procedures' have failed to test computer equipment as required by the state, according to Robert Naegele, a technical consultant to the state and the Federal Election Commission. Each county must run ' logic and accuracy tests ' of its system before and after the vote count.\" [13]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Accuracy, Integrity, and Security in Computerized Vote-Tallying."}]}
{"id": "nist_00778", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guidelines for Securing Radio Frequency Identification (RFID) Systems? (Part 114) Control ES-1: unexpected or unintended signal and field cancellation, interference, summation, or resonance. This makes it difficult to accurately predict specific localized field levels from radiated power alone. Some factors that may warrant additional examination of electromagnetic radiation hazards include: - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; The use of RFID equipment that has not been certified by the FCC or that has been modified to operate outside of FCC mandated limits 36 (both of which are illegal in the US but may be legal in other countries), and - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Operating RFID equipment in environments in which signal reflections and other electromagnetic effects can focus radiation in unintended ways. 37 ## 4.4.2 Computer Network Attacks RFID technology represents a new attack vector on an enterprise network. Once RFID systems are implemented, a possibility exists that attackers could reach non-RFID and enterprise subsystem computers through a reader, although no such attack is known to have successfully occurred to date. If the system involves wireless handheld readers, then the wireless link between the reader and the networked middleware servers is another point of entry. Once RFID servers are compromised, they can be used to launch attacks on other networked systems. Attack possibilities include the introduction of malware (e.g., a worm or virus) or the exploits of a single adversary compromising one computer at a time. Once additional systems are compromised, all types of adverse consequences to the IT infrastructure are possible, including loss of confidentiality, integrity, and availability. While the risk of network compromise through an RFID interface is considered low, it is possible, especially as the number of RFID reader, middleware, and enterprise applications increases.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, attack vector, malware. Contains technical security guidance that could inform defensive posture. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_00779", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SA-12 in NIST_SP_800-53r5_Security_Privacy_Controls? Control SA-12: SUPPLY CHAIN PROTECTION [Withdrawn: Incorporated into SR Family.] Control Enhancements: (1) SUPPLY CHAIN PROTECTION | ACQUISITION STRATEGIES / TOOLS / METHODS [Withdrawn: Moved to SR-5.] (2) SUPPLY CHAIN PROTECTION | SUPPLIER REVIEWS [Withdrawn: Moved to SR-6.] (3) SUPPLY CHAIN PROTECTION | TRUSTED SHIPPING AND WAREHOUSING [Withdrawn: Incorporated into SR-3.] (4) SUPPLY CHAIN PROTECTION | DIVERSITY OF SUPPLIERS [Withdrawn: Moved to SR-3(1).] (5) SUPPLY CHAIN PROTECTION | LIMITATION OF HARM [Withdrawn: Moved to SR-3(2).] (6) SUPPLY CHAIN PROTECTION | MINIMIZING PROCUREMENT TIME [Withdrawn: Incorporated into SR-5(1).] (7) SUPPLY CHAIN PROTECTION | ASSESSMENTS PRIOR TO SELECTION / ACCEPTANCE / UPDATE [Withdrawn: Moved to SR-5(2).] (8) SUPPLY CHAIN PROTECTION | USE OF ALL-SOURCE INTELLIGENCE [Withdrawn: Incorporated into RA-3(2).] (9) SUPPLY CHAIN PROTECTION | OPERATIONS SECURITY [Withdrawn: Moved to SR-7.] (10) SUPPLY CHAIN PROTECTION | VALIDATE AS GENUINE AND NOT ALTERED [Withdrawn: Moved to SR-4(3).] (11) SUPPLY CHAIN PROTECTION | PENETRATION TESTING / ANALYSIS OF ELEMENTS, PROCESSES, AND ACTORS [Withdrawn: Moved to SR-6(1).] (12) SUPPLY CHAIN PROTECTION | INTER-ORGANIZATIONAL AGREEMENTS [Withdrawn: Moved to SR-8.] (13) SUPPLY CHAIN PROTECTION | CRITICAL INFORMATION SYSTEM COMPONENTS [Withdrawn: Incorporated into MA-6 and RA-9.] (14) SUPPLY CHAIN PROTECTION | IDENTITY AND TRACEABILITY [Withdrawn: Moved to SR-4(1) and SR-4(2).] (15) SUPPLY CHAIN PROTECTION | PROCESSES TO ADDRESS WEAKNESSES OR DEFICIENCIES [Withdrawn: Incorporated into SR-3.]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00780", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Conformance Test for FDDI Medium Access Control (MAC) say about 0) cn a CO D O \u00b7H &gt; 0) a u \u00b70 0) 3 C \u00b7H 4J C o u? (Part 7) According to A Conformance Test for FDDI Medium Access Control (MAC), 0) cn a CO D O \u00b7H &gt; 0) a u \u00b70 0) 3 C \u00b7H 4J C o u: Get this value from Tester The operative Target Token Rotation Time. Tester's Requested TTRT. lUT's Requested TTRT. Highest Bidding Value of Tester in Claim Token Process Lowest Bidding Value of Tester in Claim Token process FCS field for the frame transmitted. FCS field for the frame received.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, token. Contains security framework guidance for authentication systems. Source: A Conformance Test for FDDI Medium Access Control (MAC)."}]}
{"id": "nist_00781", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services provide? (Section 133) | Verify that operational PNT data performance baselines and expected data flows for relevant external PNT information systems, the organization's PNT system, and applications dependent on PNT data are captured, developed, and maintained to detect events. When practical, comply with standards-based solutions for data formatting, message formatting, and message transmission to facilitate interoperability and integration. | DHS CISA 1.d GPS ICD-870 3.1 IEEE 1588 Annex J IETF CMP IMO 1575 D, D.1, D.2 NIST SP 800-53 Rev.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_00782", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Privacy Controls for Information Systems and Organizations provide? (Section 617) principle of accountability and traceability states that it is possible to trace security-relevant actions (i.e., subject-object interactions) to the entity on whose behalf the action is being taken. The principle of accountability and traceability requires a trustworthy infrastructure that can record details about actions that affect system security (e.g., an audit subsystem). To record the details about actions, the system is able to uniquely identify the entity on whose behalf the action is being carried out and also record the relevant sequence of actions that are carried out. The accountability policy also requires that audit trail itself be protected from unauthorized access and modification. The principle of least privilege assists in tracing the actions to particular entities, as it increases the granularity of accountability. Associating specific actions with system entities, and ultimately with users, and making the audit trail secure against unauthorized access and modifications provide non-repudiation because once an action is recorded, it is not possible to change the audit trail. Another important function that accountability and traceability serves is in the routine and forensic analysis of events associated with the violation of security policy. Analysis of audit logs may provide additional information that may be helpful in determining the path or component that allowed the violation of the security policy and the actions of individuals associated with the violation of the security policy. Related Controls: AC-6, AU-2, AU-3, AU-6, AU-9, AU-10, AU-12, IA-2, IR-4. (23) SECURITY AND PRIVACY ENGINEERING PRINCIPLES | SECURE DEFAULTS Implement the security design principle of secure defaults in [Assignment: organization- defined systems or system components].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00783", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.3.3 Identity Management and Access Control (PR.AC) according to NIST Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector According to Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector, 5.3.3 Identity Management and Access Control (PR.AC): To implement identity management and access control, the project team focused on PR.AC-1, PR.AC-4, and PR.AC-7 Subcategories. PR.AC-1 specifies, '[i]dentities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users and processes.' PR.AC-4 specifies, '[a]ccess permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties.' PR-AC7 specifies, '[u]sers, devices, and other assets are authenticated commensurate with the risk of the transaction.'", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization, identity management. Contains security framework guidance for authentication systems. Source: Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector."}]}
{"id": "nist_00784", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Standard Security Label for GOSIP_ an Invitational Workshop say about B. The TMDF \"labeling\" solution? (Part 2) According to Standard Security Label for GOSIP_ an Invitational Workshop, B. The TMDF \"labeling\" solution: SCPs within the Domains are of no concern of the TMDF. Each SCP will have its own security policy and these SCP security policies (e.g., MAC policies) may require the traditional sensitivity labels. | | Table I: Types of Security Labels | Table I: Types of Security Labels | |-----------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Major Class of Labels | Sub-Labels | Function | | Sensitivity | | Used by the BLFSP Reference Monitor to determine if a subject should have access to an object. | | | hierarchical | Indicate \"classification level\", e.g. Top Secret. Secret, or Confidential. These labels correspond to the security risk of having the information compromised. | | | non-hierarchical | Indicate \"compartments\". Compartments are subgroups of a classification level (e.g. artillery, armor, infantry or Army, Navy and Air Force). These labels do NOT exist independently of the classification level. | | Separation | | Used by the TMDF reference monitor to determine if a Domain has possession of a resource. |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, top secret. Contains guidance on protecting sensitive government information. Source: Standard Security Label for GOSIP_ an Invitational Workshop."}]}
{"id": "nist_00785", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Third-Round Report of the SHA-3 Cryptographic Hash Algorithm Competition say about 4.1.4 Distinguishing Attacks and Differential Properties? (Part 2) According to Third-Round Report of the SHA-3 Cryptographic Hash Algorithm Competition, 4.1.4 Distinguishing Attacks and Differential Properties: wing that these components do not behave in an ideal way, and thus potentially undermining these proofs. Table 6 shows the bestknown distinguishing attacks and differential-property analyses. Table 6. Best Known Distinguishing Attacks and Differential Properties for the Finalists and SHA-2 | Algorithm | Target | Rounds | Fraction of Target Analyzed | CF Call | Reference | |------------------------|----------|----------|-------------------------------|-----------|-------------| | Block Cipher | 7/14 | 50% | 2 232 | [43] | BLAKE-256 | | Gr\u00f8stl-256 Permutation | 9/10 | 90% | 2 368 | | [44] | | Compression Function | 42/42 | 100% | 2 304 | [39] | JH | | Permutation | 24/24 | 100% | 2 1579 | [45] | Keccak | | Permutation | 14/24 | 58% | 2 255.77 | [46] | | | Compression Function | 37/72 | 52% | 2 511.2 | [47] | Skein | | Compression Function | 36/72 | 50% | 2 454 | [48] | | | SHA-2 Hash Function | 46/64 | 72% | 2 46 | | [49] | Note that for BLAKE, Gr\u00f8stl, and SHA-2, which have both 256- and 512-bit functions, this table applies only to the 256-bit functions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Third-Round Report of the SHA-3 Cryptographic Hash Algorithm Competition."}]}
{"id": "nist_00786", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices say about Confidentiality? According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Confidentiality: The confidentiality impact level associated with the executive information type is associated with executive functions. The effects of loss of confidentiality of policies and guidance during the formative stage can result in attempts by affected entities and other interested parties to influence and/or impede the policy and guidance development process. Premature public release of formative policies and guidance before internal coordination and review can result in unnecessary damage to public confidence in the executive office. These consequences may occur when the release includes unedited internal commentary and discussion. Recommended Confidentiality Impact Level : The provisional confidentiality impact level recommended for executive functions information is low .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_00787", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PM-5 in Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)? (Part 16) Control PM-5: Yikes! router also provides MUD support for MUD-capable IoT devices that emit MUD URLs via DHCP. Future work may be done to support MUD-capable devices that emit MUD URLs via X.509 or LLDP. The Yikes! router receives the MUD URL emitted by the device, retrieves the MUD file associated with that URL, and configures traffic filters (firewall rules) on the router to enforce the communication limitations specified in the MUD file for each device. The Yikes! router requires access to the internet to support secure API access to the Yikes! cloud service. Last, the Yikes! router also provides integrated support for threat signaling by incorporating GCA Quad9 threat agent (see Section 7.2.13) and GCA Quad9 MUD manager (see Section 7.2.14) capabilities. Both the Quad9 threat agent and the Quad9 MUD manager are components of the open-source software Q9Thrt. See Section 7.3.1.3 for a description of Build 2\u2019s threat-signaling architecture and more information on Q9Thrt. 7.2.7 Certificates DigiCert provisioned a Premium Certificate for signing the MUD files. The Premium Certificate supports the key extensions required to sign and CMS structures as required in the MUD specification. Further information about DigiCert\u2019s CertCentral web-based platform, which allows provisioning and managing publicly trusted X.509 certificates, is in Section 6.2.8. 7.2.8 IoT Devices This section describes the IoT devices used in the laboratory implementation. There are two distinct categories of devices: devices that can emit a MUD URL in compliance with the MUD specification, i.e., MUD-capable IoT devices; and devices that are not capable of emitting a MUD URL in compliance with the MUD specification, i.e., non-MUD-capable IoT devices. 7.2.8.1 MUD-Capable IoT Devices The project used several MUD-capable IoT devices: BeagleBone Black (devkit), NXP i.MX 8M (devkit), Raspberry Pi (devkit), and Samsung ARTIK 520 (devkit).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_00788", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet say about AN-2013 Annex G: Mapping to the NIEM IEPD? (Part 2) According to Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet, AN-2013 Annex G: Mapping to the NIEM IEPD: | N o t e s | Imp. Required | Imp. Support | Supporte d Range | Test Result | E n c . | |---------------------------------------------------|----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------| | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | | TX.1 - Tran saction: Required Record Types | 5.1, 5.3.1, Annex G | There may be multiple records in a transaction of each record type other than Type-1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet."}]}
{"id": "nist_00789", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is DEBUG according to Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)? DEBUG: :GENERAL::/etc/osmud/create_ip_fw_rule.sh -s lan -d", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_00790", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Identity and Access Management for Electric Utilities say about Enable enrollment? (Part 69) According to Identity and Access Management for Electric Utilities, Enable enrollment: t not have the \u201caccess this computer from the network\u201d user right on domain controllers. \u2013 Fail \uf0a7 Allow log on locally \u2022 Unauthorized accounts must not have the \u201callow log on locally\u201d user right. \u2013 (CCE-25228-8) \u2013 Fail \uf0a7 Back up files and directories \u2022 Unauthorized accounts must not have the \u201cback up files and directories\u201d user right. \u2013 (CCE-25380-7) \u2013 Fail \uf0a7 Bypass traverse checking \u2022 Unauthorized accounts must not have the \u201cbypass traverse checking\u201d user right. \u2013 (CCE-25271-8) \u2013 Fail \uf0a7 Change the system time \u2022 Unauthorized accounts must not have the \u201cchange the system time\u201d user right. \u2013 (CCE-24185-1) \u2013 Fail T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . \uf0a7 Change the time zone \u2022 Unauthorized accounts must not have the \u201cchange the time zone\u201d user right. \u2013 (CCE-24632-2) \u2013 Fail \uf0a7 Force shutdown from a remote system NIST SP 1800-2C: Identity and Access Management for Electric Utilities 345 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . \u2022 Unauthorized accounts must not have the \u201cforce shutdown from a remote system\u201d user right. \u2013 (CCE-24734-6) \u2013 Fail \uf0a7 Increase a process working set \u2022 Unauthorized accounts must not have the \u201cincrease a process working set\u201d user right. \u2013 (CCE-24162-0) \u2013 Fail \uf0a7 Load and unload device drivers \u2022 Unauthorized accounts must not have the \u201cload and unload device drivers\u201d user right. \u2013 (CCE-24779-1) \u2013 Fail \uf0a7 Log on as a batch job \u2022 Unauthorized accounts must not have the \u201clog on as a batch job\u201d user right. \u2013 (CCE-23386-6) \u2013 Fail \uf0a7 Restore files and directories \u2022 Unauthorized accounts must not have the \u201crestore files and directories\u201d user right.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_00791", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-4009 in NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3? (Part 21) Control SI-4009: The group exchanges information within and between systems to include security domains.' | | Term | Sources | Security and Privacy Fabric | Comments | |--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Community risk for privacy | | Add - privacy fabric | 'Probability that a particular vulnerability will be exploited within an interacting population and adversely impact some members of that population.' | | Compartmentalization (see DHHS meaning) | | | 'A nonhierarchical grouping of sensitive information used to control access to data more finely than with hierarchical security classification alone.' | | Compromise - As applied to privacy | | Especially re- identification | 'Disclosure of information to unauthorized persons, or a violation of the security policy of a system in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object may have occurred.' | | Compromising Emanations (for privacy data) | | | 'Unintentional signals that, if intercepted and analyzed, would disclose the information transmitted, received, handled, or otherwise processed by information systems equipment.' | | CND | | Different for privacy fabric?", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3."}]}
{"id": "nist_00792", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-3(4) in NIST_SP_800-53r5_Security_Privacy_Controls? (Part 8) Control AC-3(4): CCESS CONTROL Enforce attribute-based access control policy over defined subjects and objects and control access based upon [Assignment: organization-defined attributes to assume access permissions]. Discussion: Attribute-based access control is an access control policy that restricts system access to authorized users based on specified organizational attributes (e.g., job function, identity), action attributes (e.g., read, write, delete), environmental attributes (e.g., time of day, location), and resource attributes (e.g., classification of a document). Organizations can create rules based on attributes and the authorizations (i.e., privileges) to perform needed operations on the systems associated with organization-defined attributes and rules. When users are assigned to attributes defined in attribute-based access control policies or rules, they can be provisioned to a system with the appropriate privileges or dynamically granted access to a protected resource. Attribute-based access control can be implemented as either a mandatory or discretionary form of access control. When implemented with mandatory access controls, the requirements in AC-3(3) define the scope of the subjects and objects covered by the policy. Related Controls: None. (14) ACCESS ENFORCEMENT | INDIVIDUAL ACCESS CHAPTER THREE PAGE 27 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization, sso. Contains security framework guidance for authentication systems. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00793", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TE-1 in Mobile Device Security_ Bring Your Own Device (BYOD)? (Part 27) Control TE-1: ites - phishing protection risky URLs - application forensics - application binaries (Android only) - application inventory (Android only) zIPS also collects some information that cannot be disabled. These items include: - device root/jailbreak status - USB debug mode status (Android only) - developer mode status (Android only) - 3 rd party app store presence (Android only) - mobile OS-specific vulnerability status (e.g., Stagefright) - device encryption status (Android only) - device protection status - screen lock status zIPS must collect certain data items to properly communicate with the zConsole. These items include: - user credentials (email address, Zimperium-specific password) - mobile network operator - mobile network country code - device operating system - device push token - hash of local z9 database - time and name of threat detection when a threat occurs ## 4.7.3 Application Vetting: Kryptowire Kryptowire collects certain pieces of device information through the MaaS360 REST API for analytics and application association purposes. The data collected includes: - MDM device ID - MDM device name - MDM username - last MDM sync date - MDM enrollment data - enterprise and non-app store installed applications ## 4.7.4 VPN: Palo Alto Networks The Palo Alto Networks VPN uses information about the device as it establishes VPN connections.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: token, sso. Contains security framework guidance for authentication systems. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_00794", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 134) m accounts (or roles) with access to [Assignment: organization- defined security functions or security-relevant information] use non-privileged accounts or roles, when accessing nonsecurity functions. Discussion: Requiring the use of non-privileged accounts when accessing nonsecurity functions limits exposure when operating from within privileged accounts or roles. The inclusion of roles addresses situations where organizations implement access control policies, such as role-based access control, and where a change of role provides the same degree of assurance in the change of access authorizations for the user and the processes acting on behalf of the user as would be provided by a change between a privileged and non- privileged account. Related Controls: AC-17, AC-18, AC-19, PL-4. (3) LEAST PRIVILEGE | NETWORK ACCESS TO PRIVILEGED COMMANDS Authorize network access to [Assignment: organization-defined privileged commands] only for [Assignment: organization-defined compelling operational needs] and document the rationale for such access in the security plan for the system. Discussion: Network access is any access across a network connection in lieu of local access (i.e., user being physically present at the device). Related Controls: AC-17, AC-18, AC-19. (4) LEAST PRIVILEGE | SEPARATE PROCESSING DOMAINS Provide separate processing domains to enable finer-grained allocation of user privileges. Discussion: Providing separate processing domains for finer-grained allocation of user privileges includes using virtualization techniques to permit additional user privileges within a virtual machine while restricting privileges to other virtual machines or to the underlying physical machine, implementing separate physical domains, and employing hardware or software domain separation mechanisms. Related Controls: AC-4, SC-2, SC-3, SC-30, SC-32, SC-39.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00795", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to Computer Security Division 2006 Annual Report? http: //csrc.nist.gov/fissea/ Contacts: Mr. Mark Wilson (301) 975-3870 mark.wilson@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2006 Annual Report."}]}
{"id": "nist_00796", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about Determine if:? According to Assessing Security Requirements for Controlled Unclassified Information, Determine if:: A.03.06.02.ODP[01]: the time period to report suspected incidents to the organizational incident response capability is defined . A.03.06.02.ODP[02]: authorities to whom incident information is to be reported are defined . A.03.06.02.a[01]: A.03.06.02.a[02]: system security incidents are tracked. system security incidents are documented. A.03.06.02.b: suspected incidents are reported to the organizational incident response capability within &lt;A.03.06.02.ODP[01]: time period&gt; . A.03.06.02.c: incident information is reported to &lt;A.03.06.02.ODP[02]: authorities&gt; . A.03.06.02.d: an incident response support resource that offers advice and assistance to system users on handling and reporting incidents is provided.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00797", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Security Considerations for Voice Over IP Systems? (Part 9) Control HA-1: ress resolution). The user initially reports their location to a registrar, which may be integrated into a proxy or redirect server. This information is in turn stored in the external location server. Messages from endpoints must be routed through either a proxy or redirect server. The proxy server intercepts messages from endpoints or other services, inspects their 'To:' field, contacts the location server to resolve the username into an address and forwards the message along to the appropriate end point or another server. Redirect servers perform the same resolution functionality, but the onus is placed on the end points to perform the actual transmission. That is, Redirect servers obtain the actual address of the destination from the location server and return this information to the original sender, which then must send its message directly to this resolved address (similar to H.323 direct routed calls with gatekeeper). The SIP protocol itself is modeled on the three-way handshake method implemented in TCP (see Figure 6). We will consider the setup here when a proxy server is used to mediate between endpoints. The process is similar with a redirect server, but with the extra step of returning the resolved address to the source endpoint. During the setup process, communication details are negotiated \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ between the endpoints using Session Description Protocol (SDP), which contains fields for the codec used, caller's name, etc. If Bob wishes to place a call to Alice he sends an INVITE request to the proxy server containing SDP info for the session, which is then forwarded to Alice's client by Bob's proxy, possibly via her proxy server. Eventually, assuming Alice wants to talk to Bob, she will send an 'OK' message back containing her call preferences in SDP format. Then Bob will respond with an 'ACK'.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_00798", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Domain Name System-Based Electronic Mail Security say about 3.2.1 Outlook? According to Domain Name System-Based Electronic Mail Security, 3.2.1 Outlook: To use digital signatures and encryption, both the sender and recipient must have a mail application that supports the S/MIME standard. Outlook supports the S/MIME standard. Instructions for user-driven cryptographic functions vary from version to version and platform to platform. Accessing digital signature on an Outlook Help page usually provides the necessary operator instructions. The example instructions provided here are for Outlook 2016 for Windows 10 and Outlook for Mac 2011.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_00799", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Attribute Considerations for Access Control Systems provide? (Section 25) e role Job Lead wants to access information in organization B , except organization B uses the term Task Lead to denote the equivalent role. Table 1 shows an example of a subject's attributes. Table 1: Subject attribute example | Subject attribute Name | Attribute Value | Policy Applied a | |--------------------------|-----------------------------------------------------|-----------------------------------------| | Company ID | ID numbers (e.g., Organization A) | Subject and Administrator object access | | Division | Division name (e.g., Software Development Division) | Subject and Administrator object access | | Group | Group name (e.g., Testing group) | Subject and Administrator object access | | Name | Person's name (e.g., Joe Smith) | Subject and Administrator object access | | Authorization | Authorization level (e.g., 1) | Administrator object access | | Role | Role ID (e.g., Job Lead, (or Task lead)) | Administrator object access | | Training ID | Training label (e.g., Minimum Requirement) | Administrator object access | a Policy Applied column lists the type of policy rules which require this attribute for the evaluations of access permission if multiple policies are applied to the access control system. As subject attributes may be provisioned by different authorities (e.g., human resources , security , organization leadership , etc.), methods for obtaining authoritative data must be regulated.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Attribute Considerations for Access Control Systems."}]}
{"id": "nist_00800", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Blockchain Networks_ Token Design and Management Overview provide? (Section 18) tion Submission................................................................................ | Transaction Submission................................................................................ | 29 | | | 4.2.1 | Meta Transactions..............................................................................29 | | | | 4.2.2 | Smart Contract-Based Access Control...............................................30 | | | | 4.2.3 | Blockchain Node Permissioning .........................................................30 | | | 4.3 | Transaction Viewability .................................................................................", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, token. Contains security framework guidance for authentication systems. Source: Blockchain Networks_ Token Design and Management Overview."}]}
{"id": "nist_00801", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-02(04) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control SI-02(04): automated patch management tools are employed to facilitate \ufb02aw remedia\ue000on to <SI-02(04)_ODP components>. POTENTIAL ASSESSMENT METHODS AND OBJECTS:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00802", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography? (Part 11) Control HA-3: nding authority shall verify the owner's intent to associate a specific identifier chosen for the owner and the public key; the means for accomplishing this is beyond the scope of this Recommendation. The binding authority shall also obtain assurance of the validity of the domain parameters associated with the owner's key pair, the arithmetic validity of the owner's static public key, and the owner's possession of the static private key corresponding to that static public key (see Section 5.5.2, Section 5.6.2.2.1 [method 1], and Section 5.6.2.2.3, respectively.) As an alternative to reliance upon a binding authority, trusted associations between identifiers and static public keys may be established by the direct exchange of this information between entities using a mutually trusted method (e.g., a trusted courier or a face-to-face exchange). In this case, each entity receiving an identifier and the associated static public key shall be responsible for obtaining the same assurances that would have been obtained on their behalf by a binding authority (see the previous paragraph). Entities shall also be responsible for maintaining (by cryptographic or other means) the trusted associations between any identifiers and static public keys received through such exchanges. If an entity engaged in a key-establishment transaction owns a static key pair that is employed during the transaction, then the identifier used to label that party shall be one that has a trusted association with the static public key of that key pair. If an entity engaged in a keyestablishment transaction contributes only an ephemeral public key during the transaction, but an identifier is still desired/required for that party, then a non-null identifier shall be selected/assigned in accordance with the requirements of the protocol relying upon the transaction.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}]}
{"id": "nist_00803", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices say about Availability? According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Availability: The availability impact level is based on the specific mission and the data supporting that mission, not on the time required to re-establish access to social services information. The effects of disruption of access to most social services information or information systems would have, at most, a limited adverse effect on agency operations, agency assets, or individuals. Recommended Availability Impact Level: The provisional availability impact level recommended for social services information is low .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_00804", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Criticality Analysis Process Model_ Prioritizing Systems and Components say about Process A - Criticality Analysis Procedure Definition? (Part 1) According to Criticality Analysis Process Model_ Prioritizing Systems and Components, Process A - Criticality Analysis Procedure Definition: Process A - Criticality Analysis Procedure Definition The Project Manager reviews the organization's strategic plan, risk management plan, and other documentation and determines that the organization does not have any formal criticality analysis procedures. The Project Manager does not have the authority nor the time and ability to perform a criticality analysis of the entire organization, which would be ideal. However, it is early enough in the ERP project that an analysis can be written into the project plan prior to and concordant with system procurement and implementation. A.1 The Project Manager delegates to an employee with business analysis training, the process of integrating criticality analysis activities into the project plan. The Business Analyst 9 uses the Criticality Analysis Process Model in this publication to determine appropriate tasks, roles, and responsibilities based on Processes B, C, D, and E of the Model. The Project Manager and Business Analyst coordinate with a legal representative to identify laws, regulations, and organizational policies which may impact the project; they discuss with the rest of the project team how the criticality analysis may align with or impact their normal activities and discuss ways to address any concerns they have. The Business Analyst works with the project team to compare the guidance in the Related Processes Outside of Criticality Analysis in each Process and Sub-process description 9 In the context of this document, any role mentioned, such as 'Business Analyst,' is not a specific title but a role of a person engaged in the program. with the organization's existing processes to ensure that security engineering and risk management processes are appropriately integrated and planned for.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Criticality Analysis Process Model_ Prioritizing Systems and Components."}]}
{"id": "nist_00805", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Domain according to Foundations of a Security Policy for Use of the National Research and Educational Network? Domain: A logical structure, group or sphere of influence over which control is exercised.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Foundations of a Security Policy for Use of the National Research and Educational Network."}]}
{"id": "nist_00806", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 7. Characterization and Analysis of Measurement Data according to NIST Manufacturing Profile Implementation Methodology for a Robotic Workcell According to Manufacturing Profile Implementation Methodology for a Robotic Workcell, 7. Characterization and Analysis of Measurement Data: After each tool has been installed or a configuration measurement is performed, the data from the experiment is analyzed to determine if the manufacturing process performance was negatively impacted. This analysis is performed with an approach called exploratory data analysis (EDA), and is described in great detail in the NIST Engineering Statistics Handbook [12]. This analysis process requires the workcell to be characterized for proper comparative analysis to be performed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Manufacturing Profile Implementation Methodology for a Robotic Workcell."}]}
{"id": "nist_00807", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Information Security Handbook_ A Guide for Managers say about 4.5 Managing Change? According to Information Security Handbook_ A Guide for Managers, 4.5 Managing Change: It is necessary to ensure that the program, as structured, continues to evolve as new technology and associated security issues emerge. Training needs will shift as new skills and capabilities become necessary to respond to new architectural and technology changes. A change in the organizational mission and/or objectives can also influence ideas on how best to design training solutions and content. Emerging issues, such as homeland defense, will also impact the nature and extent of security awareness and training activities necessary to keep users informed and/or trained about the latest threats, vulnerabilities, and countermeasures. New laws and court decisions may also impact agency policy that, in turn, may affect the development and/or implementation of awareness and training material. Finally, as security policies evolve, awareness and training material should reflect these changes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_00808", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for Access Control System Evaluation Metrics say about 4.2.10 Adaptable to the implementation and evolution of AC policies? (Part 5) According to Guidelines for Access Control System Evaluation Metrics, 4.2.10 Adaptable to the implementation and evolution of AC policies: ed flexible if the security policy can interpose atomically on any operation performed by the system, allowing the operation to proceed, denying the operation, or even injecting operations of its own. In such a system, the access request decision of the security policy relies on the knowledge of the entire current system state, which includes the history of the system. Because it is possible to interpose on all access requests, it is possible to modify the existing security policy and to revoke any previously granted access. The suggested approach for the needed flexibility is to identify the system state that is potentially security relevant and to control operations that affect or are affected by that state. The degree of flexibility in such a system will depend upon the completeness of both the set of controlled operations and the current system state that is available to the security policy, as well as the granularity of the controlled operations. | | | Is the AC system capable of dynamically interposing AC rules based on the system states?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Access Control System Evaluation Metrics."}]}
{"id": "nist_00809", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Analyzing Collusion Threats in the Semiconductor Supply Chain provide? (Section 16) ductor life cycle, and the motivation for the attacks. Other motivations can be analyzed through this methodology as well. The methodology provides a relative risk-based score to help plan mitigation. In the future, NIST plans to extend this work to analyze the supply chain threats related to 3D heterogeneous integration and integrate different hardware vulnerabilities into the framework, which will help the stakeholders to improve their threat mitigation techniques and implement more secure and robust designs. Addressing these hardware and supply chain security issues is essential to safeguard national interests and promote economic stability. - [1] DARPA (2020) DARPA Selects Teams to Increase Security of Semiconductor Supply Chain. Available at - [2] DARPA (2021) Expanding Domestic Manufacturing of Secure, Custom Chips for Defense Needs. Available at https://www.darpa.mil/news-events/2021-03-18 - [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 - [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 - [5] Wolfe F (2020) Aether Spy Next-Generation Multi-Function Radar to Advance, Northrop Grumman Says. Defense Daily . Available at - [6] CISA (2020) Defining Insider Threats.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Analyzing Collusion Threats in the Semiconductor Supply Chain."}]}
{"id": "nist_00810", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.3.6.3 Other Considerations according to NIST Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events According to Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events, 5.3.6.3 Other Considerations: A significant trade-off between memory and frequency of backups occurs when implementing a secure storage solution for backups. As WORM space may be limited by the number of disks purchased or by a cloud service's limitations, it is important for organizations to consider the cost of storing all backups in secure storage, especially for organizations that frequently take backups to reduce the loss of data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_00811", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Section 4) on provides enhanced security requirements to help protect CUI associated with critical programs or high value assets in nonfederal systems and organizations from the advanced persistent threat (APT). The SP 800-172 enhanced security requirements are designed to protect confidentiality, integrity and availability of information. <!-- image --> NIST SP 800-172A, Assessing Enhanced Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the enhanced security requirements in SP 800-172. Knowing what requirements to implement is important, but it is also important to understand how to evaluate the organization's implementation. Both publications work handin-hand for full implementation. ht ps:/ csrc.nist.gov/projects/protecting-control ed-unclas <!-- image --> ified-information Protecting information from unauthorized modification [SP 800-171] Security Requirement: Security outcomes levied on a nonfederal organization to ensure adequate measures are taken to protect the confidentiality of CUI being processed, stored, or transmitted. <!-- image --> <!-- image --> Important Note: The security requirements in NIST SP 800-171 are only applicable to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. Protecting information from unauthorized access and disclosure Preventing disruption in how information is accessed <!-- image --> 2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program. SP 800-171 security requirements are organized into 17 families, as illustrated in the table below. Each family is further broke n down into requirements related to the family's general security topic (see the example at the bottom of the page).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer."}]}
{"id": "nist_00812", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Confidentiality according to NIST Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Confidentiality: The confidentiality impact level is the effect of unauthorized disclosure of water resource management information on the ability of responsible agencies to promote the effective use and management of the nation's water resources. The consequences of unauthorized disclosure of most water resource management information would have, at most, a limited adverse effect on agency operations, agency assets, or individuals. Special Factors Affecting Confidentiality Impact Determination : There may be some cases for which moderate confidentiality impact is associated with unauthorized disclosure of business/industry development. For example, unauthorized disclosure of details of current agency water resource management activities and plans may focus opposition and/or give an unfair advantage to competing interests. Consistent premature disclosure of agency plans may cause significant degradation in mission capability. Recommended Confidentiality Impact Level : The provisional confidentiality impact level recommended for water resource management information is low .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_00813", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain NIST CYBERSECURITY PRACTICE GUIDES according to NIST Securing Property Management Systems According to Securing Property Management Systems, NIST CYBERSECURITY PRACTICE GUIDES: NIST Cybersecurity Practice Guides (Special Publication 1800 series) target specific cybersecurity challenges in the public and private sectors. They are practical, user-friendly guides that facilitate the adoption of standards-based approaches to cybersecurity. They show members of the information security community how to implement example solutions that help them align with relevant standards and best practices, and provide users with the materials lists, configuration files, and other information they need to implement a similar approach. The documents in this series describe example implementations of cybersecurity practices that businesses and other organizations may voluntarily adopt. These documents do not describe regulations or mandatory practices, nor do they carry statutory authority.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Property Management Systems."}]}
{"id": "nist_00814", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance say about Incident Management? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance, Incident Management: Incident management tools enable a manufacturer to document, track, and coordinate the mitigation of an adverse event in manufacturing system devices or networks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance."}]}
{"id": "nist_00815", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Device Security_ Cloud and Hybrid Builds provide? (Section 23) ich the user and device are authorized Privacy issues can be complex and difficult to implement, particularly since these issues often span a broad range of topics, from law and policy to technology. Although privacy protections are listed within our desired capabilities, these goals are out of scope for this publication and will be addressed in subsequent efforts. In the meantime, organizations may want to follow a more comprehensive privacy engineering effort to satisfy these goals, such as National Institute of Standards and Technology Internal Report 8062, An Introduction to Privacy Engineering and Risk Management in Federal Systems [8]. Finally, the breadth of technologies in this building block was intentionally limited to organizations that have entered into a National Cybersecurity Excellence Partnership (NCEP) with the NCCoE, meaning that only NCEP partners of the NCCoE were allowed to participate in the build phase of this project. We anticipate significantly expanding on the technologies used within the next phase of this MDS project by leveraging Cooperative Research and Development Agreements (CRADAs) with other interested collabor ators. Organizations wishing to participate in future efforts should visit the NCCoE's website for more information about participating. The following assumptions exist for this project: - Both the cloud and hybrid builds are highly dependent on Microsoft's cloud platform, including Microsoft Office 365 and Microsoft Intune.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Cloud and Hybrid Builds."}]}
{"id": "nist_00816", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Key Management Documents say about 9.2. end-sys-addr? According to Secure Data Network Systems (SDNS) Key Management Documents, 9.2. end-sys-addr: This parameter must be included on the request primitive and is passed on the indication primitive. It contains the address of the end system which has no SDNS component and which uses this SDNS component as a gateway.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_00817", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Subject Key Identifier : according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Subject Key Identifier :: B2:BE:E0:D2:D4:99:E4:2E:BC:FC:EF:05:D9:A2:8A:41:8B:4E:10:8B", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_00818", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance) provide? (Section 79) ference data (PIN) in the command data field of the command does not satisfy the criteria in Section 2.4.3 of Part 2 of SP 800-73-4, then the PIV Card Application shall return the status word '6A 80'. If the reset retry counter authentication data (PUK) in the command data field of the command does not match reference data associated with the PUK and the new reference data (PIN) in the command data field of the command does not satisfy the criteria in Section 2.4.3 of Part 2 of SP 800-73-4, then the PIV Card Application shall return either status word '6A 80' or '63 CX'. If the PIV Card Application returns status word '6A 80', then the retry counter associated with the PIN shall not be reset, the security status of the PIN's key reference shall remain unchanged, and the PUK's retry counter shall remain unchanged. VE05.33.01: The vendor shall state in its documentation that the card supports the assertion made in AS05.33. TE05.33.01: The tester shall review and validate that the vendor's documentation includes the information required in VE05.33.01 and the tester shall also validate that card inplements the RESET RETRY COUNTER card command in a manner consistent with AS05.33 by ensuring the following conditions: - (a) If the new reference data (PIN) in the command data field of the command satisfies the criteria in Section 2.4.3 of Part 2 of SP 800-73-4, but the reset retry counter authentication data (PUK) in the command data field of the command does not match reference data associated with the PUK, then the PIV Card Application returns the status word '63 CX'. - (b) If the reset retry counter authentication data (PUK) in the command data field of the command matches reference data associated with the PUK, but the new reference data (PIN) in the command data field of the command does not satisfy the criteria in Section 2.4.3 of Part 2 of SP 800-73-4, then the PIV Card Application returns the status word '6A 80'.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)."}]}
{"id": "nist_00819", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Government Smart Card Interoperability Specification, Version 2.1? (Part 60) Control HA-1: required to access a value in the container. The required list of authenticators is returned by gscBsiGcGetContainerProperties( ). The calling application is responsible for constructing this object. The BSIAuthenticator class is defined as follows: ``` public class gov.gsc.classes.BSIAuthenticator { //FIELDS: protected int accessMethodType; ``` ``` protected int keyIDOrReference; protected byte[] authValue; //CONSTRUCTORS: public BSIAuthenticator() { accessMethodType = 0; keyIDOrReference = 0; authValue = ''; } public BSIAuthenticator( int int byte[] { accessMethodType = amType; keyIDOrReference = keyIDOrRef; authValue = authVal; } amType, keyIDOrRef, authVal ) //ACCESSORS: public int getAccessMethodType() { return accessMethodType; } public void setAccessMethodType(int type) { accessMethodType = type; } public int getKeyIDOrReference() { return keyIDOrReference; } public void setKeyIDOrReferece(int keyIDOrRef) { keyIDOrReference = keyIDOrRef; } public byte[] getAuthValue() { return authValue; } public void setAuthValue(byte[] auth) { authValue = auth; } } ``` ## The fields of the BSIAuthenticator class are: accessMethodType: Access Method Type (see Table 3-1 in Section 3.1). keyIDOrReference: Key identifier or reference of the authenticator. This is used to distinguish between multiple authenticators with the same Access Method Type. authValue: Authenticator, can be an external authentication cryptogram or PIN. If the authenticator value is NULL, then BSI is in charge of gathering authentication information and authenticating to the card. ## Return codes: BSI\\_OK BSI\\_BAD\\_HANDLE BSI\\_BAD\\_AID BSI\\_ACR\\_NOT\\_AVAILABLE BSI\\_SC\\_LOCKED BSI\\_BAD\\_AUTH BSI\\_CARD\\_REMOVED BSI\\_PIN\\_BLOCKED BSI\\_TERMINAL\\_AUTH BSI\\_UNKNOWN\\_ERROR ## F.2.2 gscBsiUtilConnect() Purpose: Establish a logical connection with the card inserted in a specified reader. BSI\\_TIMEOUT\\_ERROR will be returned if a connection cannot be established within a specified time.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_00820", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Glossary of Computer Security Terminology provide? (Section 180) Printing Office. (NCSC-TG-004-88) | | primary distribution | The initial targeted distribution of or access to technical documents authorized by the controlling DOD office. (DODD 5230.24) | | principle of least privilege | The granting of the minimum access authorization necessary for the performance of required tasks. (FIPS PUB 39; AR 380-380) | | print suppression/ print suppress | To eliminate the printing of characters In order to preserve their secrecy; for example, the characters of a password as it is keyed at the input terminal. (FIPS PUB 39; AR 380-380) | | privacy | 1) The right of an Individual to self-determination as to the degree to which personal information will be shared among other individuals or organizations. This includes the right of individuals and organizations to control the collection, storage, and dissemination of personal or organizational Information. (AR 380-380) | - 2) a. The right of an individual to selfdetermination as to the degree to which the individual Is willing to share with others information about himself that may be compromised by unauthorized exchange of such information among other individuals or organizations. b. The right of individuals and organizations to control the collection, storage, and dissemination of their information or information about themselves.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Glossary of Computer Security Terminology."}]}
{"id": "nist_00821", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Considerations for Code Signing provide? (Section 7) tion software signing. Please note that these examples are for illustrative purposes; they neither reflect all instantiations of each use case nor are they comprehensive of all code signing use cases. Secure distribution of firmware is an example of a software supply chain where all aspects of the code signing activity-software development, authorization of the code to be signed, administration of the CSS, and development of the verifier-are typically under the control of a single organization. A typical work flow includes a team of developers who track contributions to the project in a version control system before the code is passed along to a build system. During development, the CSS might sign non-production versions with development or test keys. These signatures would be used in testing but would not be used for verifying code in fielded products. When the code is ready to be shipped, the developers submit it for signing. An authorized approver (or multiple approvers) examine the code per organization policy and submit the code, along with an approval. The CSS inspects the package (code, approvals, and metadata) to determine whether all requirements are met. The package is then signed with a production key. This key can be unique per project. All production keys are centrally held, likely in a hardware security module (HSM). Each corresponding public key is securely installed in the verifier component on the platform for which the firmware is intended. Device drivers are privileged processes that run close to a computer's system kernel, controlling and communicating with hardware components. A typical personal computer will have several hardware devices with associated drivers. While drivers are typically developed by the associated hardware vendor, all other aspects of the code signing activity are still typically controlled by a central authority.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Security Considerations for Code Signing."}]}
{"id": "nist_00822", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SR-1 in Attribute-based Access Control for Microservices-based Applications using a Service Mesh? (Part 11) Control SR-1: rd to revoke a user's access once a JWT is issued. Community standards, such as Internet Engineering Task Force (IETF) Request for Comments (RFC) for OAuth2 Introspection, can be used to address this. An example of an authorization policy that will enable the sidecar itself to make an access control decision based on claims in the JWT and enforce it, without calling on an external authorization system, is given below: apiVersion: security.istio.io/v1beta1 kind: AuthorizationPolicy metadata: name: backend namespace: product spec: action: ALLOW rules: - from: - source: principals: [\"cluster.local/ns/product/sa/frontend\"] to: - operation: methods: [\"GET\"] paths: [\"/info*\"] - operation: methods: [\"POST\"] paths: [\"/data\"] when: - key: request.auth.claims[iss] values: [\"accounts.google.com\"] Figure 4.1 - An example Istio authorization policy This allows the front end to call specific methods on the backend only if the request has an EUC attached issued by 'accounts.google.com.' EUAZ-SR-3 : All application traffic should carry end user credentials, and there should be a policy in the mesh enforcing that credentials are present. This is recommended even if the application is enforcing authentication and authorization independently of the mesh because these organization-wide controls allow functionalities like audit to be built on top of the mesh at a lower cost to central teams responsible for compliance and controls. ## 4.5.3 Model-based Authorization Policies The service-level authorization policies and a use case of end-user authorization policies that uses JWT are natively implemented in the proxies. Since these cannot be used for resourcelevel authorization policies, support for model-based authorization policies is needed as well. As already alluded to in Section 4.5.2, this requires a call from the proxy to an external authorization server, which holds the model-based authorization engine to obtain an access decision.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Attribute-based Access Control for Microservices-based Applications using a Service Mesh."}]}
{"id": "nist_00823", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is This publication is available free of charge from according to Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective? This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.IR.8074v2", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective."}]}
{"id": "nist_00824", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-1 in Derived Personal Identity Verification (PIV) Credentials? (Part 84) Control AC-1: | | 7 | Biometric activation is out- side the bounds of NIST SP 800-157. | Biometric activation is out- side the bounds of NIST SP 800-157. | Biometric activation is out- side the bounds of NIST SP 800-157. | ## 6 Future Build Considerations Mobile technologies such as DPC are constantly evolving. This project seeks to keep reasonable pace with the changing mobile landscape while sustaining an attainable scope bound by current policies. Moving forward, we will consider additional challenges for future DPC projects, including: - \uf0a7 Application EnablementTo leverage DPCs, an organization needs to enable applications on its mobile devices and from the relying-party perspective. Mobile device application development is complicated by the various operating systems, cryptographic token options, and third-party software development kits provided by software containers. Further, modifying the source code of third-party closed mobile applications can be difficult or impossible. Relying parties face similar challenges with legacy systems that can be difficult to make ready for DPCs. Future work might focus on adopting native embedded cryptographic tokens provided by hardware manufacturers and on using federations for relying parties such as cloud service providers. - \uf0a7 Architecture ExpansionIntegrate with an identity management system (IDMS), which retains identity data that is retrieved from authoritative sources, to provide DPC subscriber PIV eligibility status information. NIST SP 800-157 recommends that the issuer of the DPC prevent further use of the DPC when the subscriber is no longer eligible for a PIV Card. Integration with an IDMS would store the eligibility of the DPC subscriber to help determine when DPC should be revoked, and it allows for DPC status to remain independent of the PIV Card status.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: identity management, token. Contains security framework guidance for authentication systems. Source: Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_00825", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Criticality Analysis Process Model_ Prioritizing Systems and Components provide? (Section 68) l to help identify systems that may be further analyzed to scope the analysis. Ensure that the scope has definitive boundaries. Define any assumptions or constraints that will help limit the analysis. | |---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Inputs | Criticality Levels of Activity(ies) and/or Workflow Path(s) from Process B.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Criticality Analysis Process Model_ Prioritizing Systems and Components."}]}
{"id": "nist_00826", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6.2.3 Determine the Testing Tools according to NIST Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities According to Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities, 6.2.3 Determine the Testing Tools: The design team should specify the assessment tools and procedures needed to accomplish the test. The specific tools needed may vary greatly depending upon the scope of the test. Tools might range from specialized software or hardware tools (e.g., network sniffers, vulnerability scanners) to measurement and recording devices (e.g., stopwatches, cameras, video recorders) to checklists used to measure adherence to defined processes and procedures. Tools might also include items needed by the test team for logistical support (e.g., radios, cell phones, badges).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities."}]}
{"id": "nist_00827", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Related Controls according to NIST_SP_800-53r5_Security_Privacy_Controls? Related Controls: AU-2, AU-5, AU-6, AU-7, AU-9, AU-11, AU-12, AU-14, SI-4.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00828", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.3.8. Challenges Posed by Aggregation Techniques according to NIST De-Identifying Government Datasets_ Techniques and Governance According to De-Identifying Government Datasets_ Techniques and Governance, 4.3.8. Challenges Posed by Aggregation Techniques: Aggregation does not necessarily provide privacy protection, especially when data are presented in multiple data releases.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: De-Identifying Government Datasets_ Techniques and Governance."}]}
{"id": "nist_00829", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Analysis of First Responder Mobile and Wearable Devices say about Mitigations:? According to Security Analysis of First Responder Mobile and Wearable Devices, Mitigations:: Properly configured mobile devices that authenticate users or roles before providing access to sensitive information can prevent unauthorized access. For local authentication, a proximity token could be used. For instance, if an officer's badge contains a proximity token, and their badge is physically separated from the phone, the phone automatically locks and requires further authentication. Other forms of authentication may include biometric or behavioral authentication methods. In terms of mitigations for remote authentication scenarios, time-based session logouts and regular reauthentication may be useful.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Security Analysis of First Responder Mobile and Wearable Devices."}]}
{"id": "nist_00830", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does General Access Control Guidance for Cloud Systems say about 2 Cloud Access Control Characteristics? (Part 6) According to General Access Control Guidance for Cloud Systems, 2 Cloud Access Control Characteristics: the resource allocated to a consumer can be accessed by another co-located consumer or if the allocated resource, such as memory, is not wiped before being reallocated to another consumer. There is also a sense of location independence in that the consumer generally has no control over or knowledge of the exact location of the provided resources. Location may be specified at a higher level of abstraction (e.g., country, state, data center) that brings security concerns. Therefore, methods for implementing resource pooling while ensuring the isolation of shared resources should be considered in the AC design. 3. Rapid elasticity : Cloud services can be elastically provisioned and released-automatically, in some cases-to rapidly scale outward and inward commensurate with demands. To the consumer, services available for provisioning often appear to be unlimited and appropriated in any quantity at any time and are supported by adding new virtual machines (VMs) with specified computing resources. A challenge for AC design involves the capability to rapidly verify the security of new VMs and determine whether the newly added VMs are qualified to execute a specific task. 4. Measured service : Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, active end user accounts). Resource usage is monitored, controlled, and reported to provide transparency to both the provider and consumer of the utilized service. To maintain resource usage, cloud consumers should be authorized to review but not to modify their own metering data since this could lead to the falsification of payments required for cloud services. Thus, it is reasonable for AC to consider the protection of metering data. 5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: General Access Control Guidance for Cloud Systems."}]}
{"id": "nist_00831", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Stateless Hash-Based Digital Signature Standard provide? (Section 66) he content is performed at the application level. For example, in the Cryptographic Message Syntax [23], a digest of the content may be computed, and that digest is signed along with other attributes. In cases in which the content is not hashed at the application level, the pre-hash version of SLH-DSA signing (Section 10.2.2) may be used. To maintain the same level of security strength when the content is hashed at the application level or when using the pre-hash version of SLH-DSA, the digest that is signed needs to be generated using an approved hash function or XOF (e.g., from FIPS 180-4 [8] or FIPS 202 [6]) that provides at least 8\ud835\udc5b bits of classical security strength against both collision and second preimage attacks [6, Table 4]. 18 Verification of a signature created in this way will require the verify function to generate a digest from the message in the same way for input to the verification function. Even if it is feasible to compute collisions on the hash functions or XOF used to instantiate H \ud835\udc5a\ud835\udc60\ud835\udc54 , PRF , PRF \ud835\udc5a\ud835\udc60\ud835\udc54 , F , H , and T \ud835\udc59 , there is believed to be no adverse effect on the security of SLH-DSA. 19 However, if the input to the signing function is a digest of the content, then collisions on the function used to compute the digest can result in forged messages. In the pure version, the content to be signed is prepended with a one-byte domain separator, one byte that indicates the length of the context string, and the context string. The domain separator, which has a value of zero for pure signing, is included to prevent pre-hash signatures from verifying as pure signatures and vice versa. In the default case in which the context string 18 Obtaining at least 8\ud835\udc5b bits of classical security strength against collision attacks requires that the digest to be signed is at least 2\ud835\udc5b bytes in length. 19 As noted in Section 11, applications that require message-bound signatures may be adversely affected if it is feasible to compute collisions on H \ud835\udc5a\ud835\udc60\ud835\udc54 .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Stateless Hash-Based Digital Signature Standard."}]}
{"id": "nist_00832", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974 say about Approaches To PRIVACY and SECURITY in COMPUTER? According to Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974, Approaches To PRIVACY and SECURITY in COMPUTER: Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974 Clark R. Renninger, Editor Institute for Computer Sciences and Technology National Bureau of Standards Washington, D.C. 20234 <!-- image --> U.S. DEPARTMENT OF COMMERCE, Frederick B. Dent, Secretary NATIONAL BUREAU OF STANDARDS, Richard W. Roberts, Direcfor", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974."}]}
{"id": "nist_00833", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is https according to Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)? https: //nccoe-server2.micronets.net/micronets-mud/nist-", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_00834", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Section 171) forming the remaining actions. 4. Use the agreed-upon key-derivation method to derive secret keying material with the specified length from the shared secret value Z and other input (see Section 5.8). If the key-derivation method outputs an error indicator, destroy all copies of Z ; then output an error indicator, and exit this process without performing the remaining action. 5. Destroy all copies of the shared secret Z and output the derived keying material. Output: The derived keying material or an error indicator. dhEphem is summarized in Table 13. Table 13: dhEphem key-agreement scheme summary | | Party U | Party V | |----------------------------------------------------|----------------------------------------------------|-------------------------------| | ( p, q, g { , SEED, counter }) | ( p, q, g { , SEED, counter }) | Domain parameters | | N/A | N/A | Static data | | Ephemeral private key r U Ephemeral public key t U | Ephemeral private key r V Ephemeral public key t V | Ephemeral data | | Compute Z by calling FFC DH using r U and t V | Compute Z by calling FFC DH using r V and t U | Computation | | 1. Compute DerivedKeyingMaterial 2. Destroy Z | 1. Compute DerivedKeyingMaterial 2. Destroy Z | Derive secret keying material | This section describes the Ephemeral Unified Model scheme. Assurance of secure key establishment using this scheme can only be obtained when the assumptions in Section 6.1.2 are true. With the exception of key derivation, the Ephemeral Unified Model scheme is 'symmetric' in the actions of parties U and V.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}]}
{"id": "nist_00835", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1 provide? (Section 140) nyURI\" use=\"required\"/> </xsd:complexType> <xsd:simpleType name=\"valueTypeType\"> <xsd:annotation> <xsd:documentation xml:lang=\"en\"> Allowed data types for Values, just string, numeric, and true/false. </xsd:documentation> </xsd:annotation> <xsd:restriction base=\"xsd:string\"> <xsd:enumeration value=\"number\"/> <xsd:enumeration value=\"string\"/> <xsd:enumeration value=\"boolean\"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType name=\"valueOperatorType\"> <xsd:annotation> <xsd:documentation xml:lang=\"en\"> Allowed operators for Values. Note that most of these are valid only for numeric data, but the schema doesn't enforce that. </xsd:documentation> </xsd:annotation> <xsd:restriction base=\"xsd:string\"> <xsd:enumeration value=\"equals\" /> <xsd:enumeration value=\"not equal\" /> <xsd:enumeration value=\"greater than\" /> <xsd:enumeration value=\"less than\" /> <xsd:enumeration value=\"greater than or equal\" /> <xsd:enumeration value=\"less than or equal\" /> <xsd:enumeration value=\"pattern match\" /> </xsd:restriction> </xsd:simpleType> ``` ``` <xsd:simpleType name=\"interfaceHintType\"> <xsd:annotation> <xsd:documentation xml:lang=\"en\"> Allowed interface hint values. When an interfaceHint appears on the Value, it provides a suggestion to a tailoring or benchmarking tool about how to present the UI for adjusting a Value.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1."}]}
{"id": "nist_00836", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies provide? (Section 56) scope of the requirement to operate DNSSEC signed zones. SP 800-53's control SC-20 was required to be expanded to cover all FISMA information systems (including low-impact systems) in its revision 3. The plans were to ensure that all agency .gov domains were DNSSEC-signed by December 2009. OMB Memorandum M-11-33 includes 'Frequently Asked Questions on Reporting for the Federal Information Security Management Act and Agency Privacy Management.' The following frequently asked questions included with the Memorandum are relevant to cryptographic applications: Yes, for non-national security systems, DOD and ODNI are to incorporate OMB policy and NIST guidelines into their internal policies. For national security systems, the Joint Task Force Transformation Initiative (JTFTI) Interagency Working Group, with representatives from the Civil, Defense and Intelligence Communities (IC) started an on-going effort in FY2009 to produce a unified information-security framework for the Federal Government. Under this effort, DOD, ODNI and NIST jointly issued the following publications: - NIST SP 800-37, Revision 1 , Guide for Applying the Risk Management Framework to Federal Information Systems, February 2010. - NIST SP 800-38A, Recommendation for Block Cipher Modes of Operation, December 2001. - NIST SP 800-39, Managing Information Security Risk: Organization, Mission, and Information System View, March 2011. - NIST SP 800-53 Revision 3 30 , Recommended Security Controls for Federal Information Systems and Organizations, August 2009. Because these guidelines are jointly issued, DOD and ODNI policies for national security systems should incorporate these guidelines. Yes. For non-national security programs and information systems, agencies must follow NIST standards and guidelines unless otherwise stated by OMB. For legacy information systems, agencies are expected to be in compliance with NIST standards and guidelines 29 The Memorandum referenced an earlier version, Revision 1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, risk management framework, fips. General security reference material without sensitive content. Source: Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies."}]}
{"id": "nist_00837", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Report on the Privilege (Access) Management Workshop say about Considerations for Implementing Access Control? (Part 2) According to A Report on the Privilege (Access) Management Workshop, Considerations for Implementing Access Control: ce of errors, usage patterns, attempted policy violations, and so on; the access control system can play an important role in log generation, for example by logging granted and denied access requests. | |------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Bypass | If some or all of the access control decisioning and enforcement will be done at the application level, is the risk of bypassing the mechanism 12 commensurate with the risk tolerance of the enterprise? | | Complexity versus simplicity | A good balance between complexity and simplicity of the access control system's architecture provides what is needed in functionality at the lowest cost in mechanism. The simpler the architecture of the access control system, the less that can go wrong, the easier to identify and fix errors, and the lower the cost of making an access request. | 12 For example, bypass through authorized or unauthorized privileged operations in the operating system. | Delegation of administrative capabilities | It may be necessary or convenient for the access control system administrator to delegate privileges to other administrators. Will the access control system being considered make it easy and secure to do that?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Report on the Privilege (Access) Management Workshop."}]}
{"id": "nist_00838", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security for Dial-Up Lines provide? (Section 54) s used for dial-up access protection, except for encryption and inessage authentication. For the latter, the number of products and vendors is very large, and it would be impractical to list them all. The tables and their contents are as follows: - Table Is Port Protection Devices (for host-end user authentication) - Table 2s Controiled-access User \"Security\" Modems and Related Devices (includes multiplexers, port expanders, port contenders with security features, protocol converters, and modems with encryption capability) - Table 3s User Authentication Devices. - Table 4s Terminal Authentication Devices. The National Bureau of Standards (NBS) does not pro^/ide evaluations of canmercial products or services, ^fention of products in this publication in no way constitutes endorsement of them by NBS or the author. All products of the categories listed known to the author at time of writing have been included. / TABLE 1 PORT PROTECTION DEVICES | PRODUCT | VENDOR | NO. PORTS/LINES I PROTECTED | |---------------------------------------------|------------------------------------------------------------------------------------|-------------------------------| | GATEWAY | Adaloqic 1522 wistaria Lane Los Altos, CA 94022 (408) 996-8559 | | | AUDITOR ACC 1000 | Access Data Systems Inc. 766 Big Tree Dr. , #104 Longwood, FL 3 27 50 | 2 TO 128 | | SIGNALMAN SECURE 12 MODEM | Anchor Automation Inc 6913 Valljean Ave. Van Nuys, CA 91406 (818) \"997-7758 | | | NET/GUARD | Avant-Garde Computing 80 0 Commerce Parkway Mt.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security for Dial-Up Lines."}]}
{"id": "nist_00839", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Personal Identity Verification (PIV) of Federal Employees and Contractors provide? (Section 133) ails for the subject identifier will be specified in [SP 800-217]. Processing of a federation protocol is simpler for the RP since credential validation is tasked to the IdP. The IdP in turn relies on the CSP for managing the PIV identity account, and they are often the same entity. This simplicity is further exemplified by the use of federation technologies to provide authentication and authorization to mobile applications, smart devices, and other non-traditional applications. The use of federation can increase the usability of the system by allowing the cardholder to present their credentials to the IdP instead of separately to each RP. As a consequence, the IdP can provide a Single Sign-On experience for the subscriber by using one authenticated session to create assertions to multiple RPs. This appendix is normative. It provides compliance requirements for PIV validation, certification, and accreditation. [HSPD-12] requires that PIV credentials be issued by providers whose reliability has been established by an official accreditation process. Consistent assessment guidelines are established for PIV Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI) in [SP 800-79], which SHALL be followed by all credential issuers in order to achieve accreditation. The entire spectrum of activities in the PCI and DPCI accreditation methodology is divided into the following four phases: - initiation, - assessment, - accreditation, and - monitoring. The initiation phase involves communicating the goals of the assessment/accreditation to the key personnel of the PCI and DPCI organization and the review of documents, such as the PCI and DPCI operations plan.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, single sign-on. Contains security framework guidance for authentication systems. Source: Personal Identity Verification (PIV) of Federal Employees and Contractors."}]}
{"id": "nist_00840", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2005 Annual Report provide? (Section 57) is to recommend and explain tested, secure settings for Windows XP workstations with the objective of simplifying the administrative burden of improving the security of Windows XP systems. SP 800-68 discusses Windows XP and various application security settings in technical detail. The guide provides insight into the threats and security controls that are relevant for various operational environments, such as for a large enterprise or a home office. It describes the need to document, implement, and test security controls, as well as to monitor and maintain systems, on an ongoing basis. It presents an overview of the security components offered by Windows XP, and provides guidance on installing, backing up, and patching Windows XP systems. It discusses security policy configuration, provides an overview of the settings in the accompanying NIST security templates, and discusses how to apply additional security settings that are not included in the NIST security templates. It demonstrates securing popular office productivity applications, Web browsers, e-mail clients, personal firewalls, antivirus software, and spyware detection and removal utilities on Windows XP systems to provide protection against viruses, worms, Trojan horses, and other types of malicious code. This list is not intended to be a complete list of applications to install on Windows XP system, nor does it imply NIST's endorsement of particular commercial off-the-shelf (COTS) products. SP 800-68 will be finalized in November 2005. This CSD program is in cooperation with checklist development activities at the Defense Information Systems Agency, the National Security Agency and the Center for Internet Security, and is in the process of establishing participation agreements with vendors and other checklist-producing organizations.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: national security, defense information. Contains guidance on protecting sensitive government information. Source: Computer Security Division 2005 Annual Report."}]}
{"id": "nist_00841", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Acknowledgements according to NIST Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012, Acknowledgements: The editor would like to thank Suzanne Lightman, Kevin Stine (both NIST), and Mark Enstrom (Neustar) for being reviewers for this document.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012."}]}
{"id": "nist_00842", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings provide? (Section 299) ith base DN c=RTN ) Figure 1: Cross-Certification Between Trusting Partners <!-- image --> Figure 1 allows us to see more clearly the many and varied trust paths that can be formed. For instance, through certificate bridges and cross-certificates, the Government Institution should be able to trust digitally signed messages from the Enormous State University, regardless of whether the signer's certificate was issued from ESU's old or new PKI infrastructures. Additionally, cross-certificates would also allow the Government Institution to trust digitally signed messages from the Random Transoceanic Nation-this trust path may or may not be intentional or desired, as we will discuss later. Let us now look at the certificate/CRL directory configurations required to enable a relying party to easily discover and validate a trust path.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_00843", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP) say about References? (Part 1) According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP), References: References - [1] macOS Security Compliance Project (2023) macOS Security Compliance Project . Available at - [2] Quinn SD, Souppaya MP, Cook MR, Scarfone KA (2018) National Checklist Program for IT Products: Guidelines for Checklist Users and Developers. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-70, Rev. 4. - [3] 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 - [4] Joint Task Force (2020) Security and Privacy Controls for Information Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-53, Rev. 5. Includes updates as of December 10, 2020. - [5] Ross R, Pillitteri V, Dempsey K, Riddle M, Guissanie G (2020) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-171, Rev. 2, Includes updates as of January 28, 2021. - [6] Department of Defense (2023) DISA STIG for macOS . Available at - [7] Committee on National Security Systems (2014) Security Categorization and Control Selection for National Security Systems. (National Security Agency, Ft. Meade, MD), Committee on National Security Systems Instruction (CNSSI) No. 1253. Available at - [8] Center for Internet Security (2023) CIS Critical Security Controls Version 8 .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, national security. Contains guidance on protecting sensitive government information. Source: Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)."}]}
{"id": "nist_00844", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Smart Cards and Mobile Device Authentication_ an Overview and Implementation provide? (Section 10) dentity Number) first, to verify that the individual in possession of the card is the person to whom the card was issued. Incorrect PINs keep the card from functioning and eventually cause it to lock. Once the PIN is successfully entered, a dialogue between the PDA and smart card occurs, by which the PDA confirms that the card and the credentials of the user on the card are valid and correspond to that of the PDA owner. The underlying mechanism used to authenticate users via smart cards relies on a challenge-response protocol between the device and the smart card. The PDA challenges the smart card for an appropriate and correct response that can be used to verify that the card is the one originally enrolled by the device owner. The PDA relies on user 1 More information can be found at http://www.linuxnet.com/ credential information, obtained earlier from the smart card when the PDA owner initially enrolled the card with the device. The authentication mechanisms discussed in this report use a challenge-response protocol compliant with FIPS 196 to authenticate a user to the PDA. Figure 2 illustrates a typical exchange, omitting the requisite PIN satisfaction step that occurs. The upper part of the diagram shows the enrollment information exchange used to register a card (at right) with the PDA (at left), while the remainder show the exchanges used to verify the claimed identity. Figure 2: Challenge-Response Exchange <!-- image --> Before the smart card can be enrolled at the device, it must first be personalized for the user. The personalization step is essentially another enrollment process whereby a security administrator enrolls the user on the card (i.e., user enrollment), by populating it with the user's credentials, PIN, and other information.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Smart Cards and Mobile Device Authentication_ an Overview and Implementation."}]}
{"id": "nist_00845", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation say about E.2 Requirements? (Part 14) According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, E.2 Requirements: | | The advertised route is initially evaluated as invalid . There are two ROAs that cover this route, both of which have ASNs different from the route's origin. Only one of these ROAs | | | | Capability Requirement (CR) Identifier (ID) | Parent Requirement | Sub-Requirement 1 | Sub- Requirement 2 | Test Case | |-----------------------------------------------|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-------------------| | | | is deleted from the RPKI, so the route still evaluates as invalid .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_00846", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to General Server Security provide? (Section 9) | Maintaining | the Security of the Server...........................................................................6-1 | | | | 6.1 | Logging ....................................................................................................................6-1 | | | | | 6.1.1 Identifying Logging Capabilities and Requirements .....................................6-1 | | | | | 6.1.2 Reviewing and Retaining Log Files | ..............................................................6-2 | | | | 6.1.3 Automated Log File Analysis Tools ..............................................................6-3 | | | | 6.2 | Server Backup Procedures......................................................................................6-4 6.2.1 Server Data Backup Policies........................................................................6-4 | | | 6.3 | 6.2.2 Server Backup Types ...................................................................................6-5 6.2.3 Maintain a Test Server .................................................................................6-6 Recovering From a Security Compromise...............................................................6-6 | |------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | Security Testing Servers..........................................................................................6-8 | | 6.4 | 6.4.1 Vulnerability Scanning..................................................................................6-9 | | | 6.4.2 Penetration Testing ....................................................................................6-10 | | 6.5 | Remotely Administering a Server ..........................................................................6-11 | | Appendices | Appendices | | Appendix B-Acronyms and Abbreviations .......................................................................B-1 | Appendix B-Acronyms and Abbreviations .......................................................................B-1 | An organization's servers provide a wide variety of services to internal and external users, and many servers also store or process sensitive information for the organization.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, penetration test. Contains technical security guidance that could inform defensive posture. Source: Guide to General Server Security."}]}
{"id": "nist_00847", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CP-1 in Contingency Planning Guide for Federal Information Systems? (Part 111) Control CP-1: ilized. Recovery Phase activities focus on implementing recovery strategies to restore system capabilities, repair damage, and resume operational capabilities at the original or an alternate location. At the completion of the Recovery Phase, {system name} will be functional and capable of performing the functions identified in Section 2.1 of this plan. ## 4.1 Sequence of Recovery Activities The following activities occur during recovery of {system name}: Modify the following list as appropriate for the selected system recovery strategy. 1. Identify recovery location (if not at original location); 2. Identify required resources to perform recovery procedures; 3. Retrieve backup and system installation media; 4. Recover hardware and operating system (if required); and 5. Recover system from backup and system installation media. ## 4.2 Recovery Procedures The following procedures are provided for recovery of {system name} at the original location . Recovery procedures are outlined per team and should be executed in the sequence presented to maintain an efficient recovery effort. Provide general procedures for the recovery of the system from backup media. If an alternate location is part of the recovery strategy, include procedures for recovery to that site. Specific keystroke level procedures may be provided in an appendix. If specific procedures are provided in an appendix, a reference to that appendix should be included in this section. Teams or persons responsible for each procedure should be identified. ## 4.3 Recovery Escalation Notices/Awareness Provide appropriate procedures for escalation notices during recovery efforts. Notifications during recovery include problem escalation to leadership and status awareness to system owners and users. Teams or persons responsible for each escalation/awareness procedure should be identified. ## 5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Contingency Planning Guide for Federal Information Systems."}]}
{"id": "nist_00848", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1.3. Objective and Scope of This Document according to NIST A Data Protection Approach for Cloud-Native Applications According to A Data Protection Approach for Cloud-Native Applications, 1.3. Objective and Scope of This Document: All services (e.g., networking, security, monitoring) for microservices-based applications are provided by a centralized infrastructure called the service mesh, and the data plane for this service mesh - which performs all runtime tasks - consists of proxies. This document outlines a practical framework for effective data protection and highlights the versatile capabilities of WebAssembly (WASM) within service mesh architectures, multi-cloud environments, and hybrid (i.e., a combination of on-premises and cloud-based) infrastructures. By focusing on inline, network traffic analysis at layers 4-7, organizations can enhance security, streamline operations, and utilize adaptive data protection measures.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Data Protection Approach for Cloud-Native Applications."}]}
{"id": "nist_00849", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Smart Cards and Mobile Device Authentication_ an Overview and Implementation provide? (Section 37) ifd.o). Therefore, by just putting the new smart card reader driver with the ifd\\_server.c source file, and building them together, results in a BSC server that supports a different smart card reader. Card personalization involves populating information such as the user's name and credentials into files maintained on the smart card, before issuing to a user. In addition, the procedure usually entails recording a PIN on the card, which the user later enters to enable the card to confirm that the holder is the same person who was issued the card. The personalization procedure can also involve physical preparation of the card, such as imprinting pictures, names, and address information on the surface. In the case of programmable cards, additional programs and data files can be installed to enable specific functions for a user. Personalization of the Secure MMC token and Bluetooth Smart Card token is performed by an Enrollment Station. The Enrollment Station is a Windows platform that runs the CardEnroller application. The CardEnroller application performs the following tasks when personalizing a token: - Loads a Javacard applet, named Enroller, onto the XMC card - Sets the user PIN as selected by the user - Verifies the user PIN (required in subsequent operations) - Stores the private RSA key and the certificate containing the public key on the card - Generates a pair of RSA keys and obtains a corresponding X.509 certificate for the user. - Destroys its copy of the user private key The CardEnroller application also performs the functions of a Certificate Authority when obtaining a certificate, generating and signing the certificate itself. Its (root) certificate is exported to any PDAs needing to verify a user's credentials that it issues. In a production environment, this function would be performed by a Certificate Authority operating within a Public Key infrastructure for the organization.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, certificate authority, token. Contains security framework guidance for authentication systems. Source: Smart Cards and Mobile Device Authentication_ an Overview and Implementation."}]}
{"id": "nist_00850", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Guidelines for Storage Infrastructure say about 4.2.4 Continuous Data Protection? According to Security Guidelines for Storage Infrastructure, 4.2.4 Continuous Data Protection: DP-SS-R12 - Security considerations for using continuous data protection: Other than the functional benefits (e.g., improved RPO, finer-grained retention), the use of continuous data protection techniques (e.g., CDP, versioning of source data or of replicas in cloud file- and object-storage, and transaction log shipping) can also assist in improving forensics for sensitive data. While potentially extremely time consuming, replaying to previous versions of data can help learn more about the attack profile, its timing, etc.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Guidelines for Storage Infrastructure."}]}
{"id": "nist_00851", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Status Report on the Third Round of the NIST Post-Quantum Cryptography Standardization Process provide? (Section 11) referred to as the NIST Post-Quantum Cryptography Standardization Process hereafter in this document. NIST issued a public call for submissions to the PQC Standardization Process in December 2016 [4]. Prior to the November 2017 deadline a total of 82 candidate algorithms were submitted. Shortly thereafter, the 69 candidates that met both the submission requirements and the minimum acceptability criteria were accepted into the first round of the standardization process. Submission packages for the first-round candidates were posted online for public review and comment [5]. After a year-long review of the candidates, NIST selected 26 algorithms to move on to the second round of evaluation in January 2019 [6]. These algorithms were viewed as the most promising candidates for eventual standardization, and were selected based on both internal analysis and public feedback. During the second round, there was continued evaluation by NIST and the broader cryptographic community. After careful deliberation, NIST selected seven finalists and eight alternates to move on to the third round in July 2020 [7]. NIST's intent was to standardize a small number of the finalists at the end of the third round, as well as a small number of the alternate candidates after a fourth round. The third round began in July 2020 and continued for approximately 18 months. During the third round, there was a more thorough analysis of the theoretical and empirical evidence used to justify the security of the candidates. There was also careful benchmarking of their performance using optimized implementations on a variety of software and hardware platforms. Similar to the first two rounds, NIST also held the (virtual) Third NIST PQC Standardization Conference in June 2021. Each of the finalists and alternates were invited to present an update on their candidate algorithm. In addition, several researchers presented work that was relevant to the PQC standardization process.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Third Round of the NIST Post-Quantum Cryptography Standardization Process."}]}
{"id": "nist_00852", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record say about B.1 Record Type 18 - DNA Record Requirements and Test Assertions? (Part 74) According to Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record, B.1 Record Type 18 - DNA Record Requirements and Test Assertions: Support | Supported Range | Applicable to (T, X, B, B*, or X*) | | |----------------------------------------------------------|------------------------------------------------|----------------------------------|----------------------------------|----------------------------------|---------------------------------------------------------------------|----------------------------------|----------------------------------|----------------------------------|--------------------------------------|----------------------------------| | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | 8.18: Record Type-18: DNA record | | 18.009- Pedigree Information | | | | SID, FID, MID, PCM]- Value | | | | | | | | Value | | 1 | M | 18.009- PMS-Value | {InfoItem:3 in 18.009} MO[ASCII(K, U)] | | | | B* | | | RT18.29 - Field: 18.010- | 8.18.10 <Table 79 lists valid values for STY.> | 1 | M | 18.010- SCT-Value | {InfoItem:1 in 18.010} MO[0 to 11] | | | | B* | | | Sample Type Value | | 1 | O | 18.010- SMO-Value | {InfoItem:2 in 18.010} MO[ASCII(NS, WB, BP)] | | | | B* | | | RT18.30 - Field: 18.011- Sample Typing Information Value | 8.18.11 <Table 79", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record."}]}
{"id": "nist_00853", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to IPsec VPNs say about 7.2.7 Summary of Design Decisions? (Part 1) According to Guide to IPsec VPNs, 7.2.7 Summary of Design Decisions: 7.2.7 Summary of Design Decisions Table 2 provides a checklist that summarizes the major design decisions made during the first two phases of the IPsec planning and implementation process.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to IPsec VPNs."}]}
{"id": "nist_00854", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation say about Contents? (Part 2) According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, Contents: | 1 | Summary..............................................................................................1 | Summary..............................................................................................1 | |-----|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Challenge.......................................................................................................................2 | | | 1.2 | Solution..........................................................................................................................3 | | | 1.3 | Benefits..........................................................................................................................4 | | 2 | How to Use This Guide.........................................................................4 | How to Use This Guide.........................................................................4 | | | 2.1 | Typographic Conventions..............................................................................................6 | | 3 | Background..........................................................................................6 | Background..........................................................................................6 | | 4 | Approach ...........................................................................................10 | Approach ...........................................................................................10 | | | 4.1 | Audience......................................................................................................................10 | | | 4.2 | Scope ...........................................................................................................................10 | | | 4.3 | Assumptions................................................................................................................11 | | | 4.4 | Risk Assessment ..........................................................................................................12 | | | 4.4.1 | Threats ........................................................................................................................13 | | | 4.4.2 | Vulnerabilities .............................................................................................................15 | | | 4.4.3 | Risk..............................................................................................................................16 | | | 4.4.4 | Cybersecurity Framework Functions, Categories, and Subcategories Addressed by the SIDR Project.................................................................................................................16 | | 4.5 | Technologies................................................................................................................21 | Technologies................................................................................................................21 | | | 4.5.1 | ROV-Enabled Routers..................................................................................................23 | | | 4.5.2 | RPKI C A..........................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_00855", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Technology Assessment_ Methods for Measuring the Level of Computer Security provide? (Section 132) rol group ensures that all output is properly distributed. Determine that the terms of reference and established practices of the control group are adequate and relate to the size of the installation. Particular attention should be directed to ascertaining that the control group cannot be bypassed, except in circumstances subject to prior approval and, that in such cases, adequate alternative arrangements have been made for the performance of the necessary control activities. <!-- image --> Determine, through observation, that self-checking digits are being used on key codes not otherwise controlled. Ascertain, through the use of test data, that they are being effectively employed, either at the data conversion stage or as a computer edit routine. Verification Guide Excerpt [CIC75, p. 211] Reprinted with permission from Computer Audit Guidelines, 1975, published by the Canadian Institute of Chartered Accountants, Toronto, Canada. 6. Control group Control group receives input, verifies authorization, reconciles processing, distributes output, and ensures errors corrected. ( See Control Technique /J-J) 2. Self-checking digit Self-checking digits used on key codes not otherwise controlled. Next, non-processing controls sucli as manual controls or controls from other checklists are evaluated. The reason given for this step is that the control objectives and techniques listed are specific to computer-based systems. It is not clear, however, that \"traditional manual system controls\" warrant separate handling. For example, an example given of a manual system control is: \"Credit notes for returns and allowances should be approved by an employee who has no access to cash receipts or other company funds\" [p. 176] . This would seem readily encompassed by the general need for segregation of duties. It would seem both desirable and feasible to eliminate this step from an implementation of this methodology.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technology Assessment_ Methods for Measuring the Level of Computer Security."}]}
{"id": "nist_00856", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Information Security Handbook_ A Guide for Managers say about Q. What is role-based training?? According to Information Security Handbook_ A Guide for Managers, Q. What is role-based training?: - A. Individuals need security training based on their particular job functions. Over time, individuals acquire different roles relative to the use of IT within an organization or as they make a career move to a different organization. Sometimes they will be users of applications, in other instances they may be involved in developing a new system, and in some situations, they may serve on a source selection board to evaluate vendor proposals for IT systems. An individual's security knowledge and skills, and therefore training needs, change as their role changes. To address this reality, knowledge and skill needs have been categorized by job functions into six role-based specialties, which represent categories of generic organizational roles: Manage, Acquire, Design and Develop, Implement and Operate, and Review and Evaluate. Actual positions within your agency are then assigned to a role to determine the actual training requirements for that position. For example, personnel in positions with duties and tasks for contracting officer, contracting officer's technical representative, and source selection board member would be aligned with the 'acquire' role. The authorizing official, information security officer, and inspector general auditor are aligned with the 'review and evaluate' role, as they deal primarily with compliance activities.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_00857", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TD-7935 in Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach? (Part 11) Control TD-7935: d and these required audits may use up the Hmited audit resources available. In this case, the priority scheme may still be useful for determining audit approaches and where and when to focus efforts. If, on the other hand, additional audit resources are available for discretionary audits, the risk evaluation of the work priority scheme can be used to identify and rank the systems in greatest need of audit coverage. Ultimately, back-end qualifiers may need to be considered for the discretionary audits, as described in Section 3.5. ## 3.4.4 Risk Evaluation Levels and Dimensions As stated on pages 45 and 46, the work priority scheme expresses the risk concerns in terms of two levels and five dimensions. The risk concerns in Level I are reviewed first and those in Level II are reviewed second. Level I has one dimension and Level II has four dimensions. Each dimension is defined as a related set of characteristics which can estimate or measure the amount of risk posed by that dimension to a failure of the system. The chief concern of each dimension can be stated in the form of a question as follows: 1. What is the Impact/Criticality of the system to the organization? A poorly developed or controlled system that is mission critical could jeopardize an organization's basic operational or programmatic effectiveness; therefore, an impact/critical system commands audit attention. The larger the impact, the more important it is to audit. 2. How Complex is the system? (This includes size considerations.) The more complex the system, the more difficuh is communication and control, and consequently, the higher the risk of failure. The greater the chance for failure, the more important it is to audit the system. 3. How Stable is the system internally (structure) and externally (environment)? The less stable the system, the more difficult it is to develop procedures for communication and control, the greater the chance for failure, and the greater the need to audit. 4.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach."}]}
{"id": "nist_00858", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Secure Web Services? (Part 122) Control ES-1: ry to become a single point of failure. To remedy this, UDDI supports replication. Through replication, UDDI registries can support multiple nodes, where each node is an instance of the UDDI registry. This way, backup nodes can be used when an individual node is faced with a DoS attack. ## 3.8.2 Quality of Service Most Web services deployed do not provide guarantees for QoS. QoS defines what the expected level of performance a particular Web service will have. By prioritizing traffic, overall performance of the system 51 Software rejuvenation was first proposed by Y. Huang, C. Kintala, N. Kolettis, and N. D. Fulton in Software Rejuvenation: Analysis, Module and Applications , in Proc. of 25th Symposium on Fault Tolerant Computing, FTCS-25, pages 381-390, Pasadena, California, June 1995. can be improved, allowing the system to make informed decisions when faced with few resources. For example, a Web service operating on a saturated network may use prioritization to allow only the highest priority traffic to be processed while letting the other traffic wait until network traffic returns to normal. Standards are beginning to be developed and released to support availability of Web services. In particular, two competing standards are available that provide reliable messaging support: WS-Reliability and WS-ReliableMessaging, discussed in Section 3.8.3. Standards and techniques for providing QoS, detecting, resisting and recovering from DoS attacks are still under development. Sections 3.8.4 and 3.8.5 discuss two common design or implementation defects that can lead to a loss of availability without the malicious intent: deadlock and recursion. The standards state that other QoS parameters, such as rate of failure or average latency, are out of scope because they are usually dealt with by lower layer protocols.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Secure Web Services."}]}
{"id": "nist_00859", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Diabetes Treatment according to NIST Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT) According to Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT), Diabetes Treatment: Alice 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. Figure 7 - Diabetes Treatment/Allergen Identification <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_00860", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.5.1. Self-Monitoring of the ICD Operation according to NIST Design Alternatives for Computer Network Security According to Design Alternatives for Computer Network Security, 4.5.1. Self-Monitoring of the ICD Operation: The ICD should be designed in a manner that will detect with a high degree- of confidence any operational errors such as improper encipherment (in particular, the sending of clear text when it was intended to be enciphered), and an imbalance in the randomization; at least to the level of 1/0 statistics. Other tests are probably available, but are outside the scope of this investigation.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Design Alternatives for Computer Network Security."}]}
{"id": "nist_00861", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Managing the Security of Information Exchanges provide? (Section 6) ange information. An approach for securely managing information exchange between systems and organizations is presented. The following four phases of information exchange management are addressed: 1. Planning the information exchange: The participating organizations perform preliminary activities; examine all relevant technical, security, and administrative issues; and develop an appropriate agreement to govern the management and use of the information and how it is to be exchanged (e.g., via a dedicated circuit or virtual private network, database sharing, cloud- or web-based services, or simple file exchange). 2. Establishing the information exchange: The organizations develop and execute a plan for establishing the information exchange, including implementing or configuring appropriate security controls and developing and signing appropriate agreements. 3. Maintaining the exchange and associated agreements: The organizations actively maintain the security of the information exchange after it is established and ensure that the terms of the associated agreements are met and remain relevant, including reviewing and renewing the agreements at an agreed-upon frequency. 4. Discontinuing the information exchange: Information exchange may be temporary, or at some point, the organizations may need to discontinue the information exchange. Whether the exchange was temporary or long-term, the conclusion of an information exchange is conducted in a manner that avoids disrupting any other party's system. In response to an incident or other emergency, however, the organizations may decide to discontinue the information exchange immediately. This publication provides recommended steps for completing each phase with an emphasis on the security measures necessary to protect the shared data. Also included is information for selecting and developing appropriate information exchange agreements and agreement templates.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Managing the Security of Information Exchanges."}]}
{"id": "nist_00862", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control provide? (Section 46) PCC. The organizational risk tolerance of the ground segment (and the potential residual risk that may be inherited) may then be used in risk management of the space and user segments as appropriate. | [NIST-SP800-53r5] PM-9 | | ID.RM-3 : The organization's determination of risk tolerance is informed by its role in critical infrastructure and sector specific risk analysis | Organizations should determine their risk tolerance related to the ground segment. An organization may determine its risk tolerance across all the segments that it operates. Risk tolerance will be determined by the entire organization (to include the space and user segment), and the risks of the ground segment should be included in that determination, including the MOCand the PCC.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control."}]}
{"id": "nist_00863", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings say about 4.1 Performance Metrics? According to 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings, 4.1 Performance Metrics: We use a set of metrics to evaluate performance in terms of time and space. For time, we measure the number of cryptographic operations involved, the resulting CPU cycles, and the BGP convergence time: the time it takes the system to reachieve a stable state after a perturbation, such as a new route announcement, a route withdrawal, or a router reboot. For each security scheme, we compare its convergence time with convergence time that original BGP achieves for the same perturbation. (Given the distributed", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_00864", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to LTE Security provide? (Section 79) VoIP | Voice over IP | | VPN | Virtual Private Network | | WiMAX | Worldwide Interoperability for Microwave Access | | XRES | Expected result | | [1] | 3 rd Generation Partnership Project, Releases , http://www.3gpp.org/specifications/67-releases [accessed 12/13/17].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to LTE Security."}]}
{"id": "nist_00865", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Privacy Controls for Information Systems and Organizations provide? (Section 833) ive, and resilient system components and systems, including the application of the security design principles implemented as part of life cycle-based systems security engineering processes (see SA-8). Related Controls: CA-2, CP-4, IR-4, MA-2, MA-6, PE-16, PL-2, PM-9, PM-30, RA-3, RA-7, SA-8, SI-4. Control Enhancements: (1) SUPPLY CHAIN RISK MANAGEMENT PLAN | ESTABLISH SCRM TEAM CHAPTER THREE PAGE 364 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ Establish a supply chain risk management team consisting of [Assignment: organization- defined personnel, roles, and responsibilities] to lead and support the following SCRM activities: [Assignment: organization-defined supply chain risk management activities]. Discussion: To implement supply chain risk management plans, organizations establish a coordinated, team-based approach to identify and assess supply chain risks and manage these risks by using programmatic and technical mitigation techniques. The team approach enables organizations to conduct an analysis of their supply chain, communicate with internal and external partners or stakeholders, and gain broad consensus regarding the appropriate resources for SCRM. The SCRM team consists of organizational personnel with diverse roles and responsibilities for leading and supporting SCRM activities, including risk executive, information technology, contracting, information security, privacy, mission or business, legal, supply chain and logistics, acquisition, business continuity, and other relevant functions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00866", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is This publication is available free of charge from according to Transitioning the Use of Cryptographic Algorithms and Key Lengths? This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-131Ar2", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Transitioning the Use of Cryptographic Algorithms and Key Lengths."}]}
{"id": "nist_00867", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does PIV Data Model Test Guidelines provide? (Section 260) ------------------------------------------------------------------------------| | TE05.02.10.01 | 9.3.1 General Record Heade Conformance r | e Size of rection. The tester shall verify the larger size of the two fingerprint templates is recorded in th Scanned Image in X and Y Di | | TE05.02.11.01 | 9.3.1 General Record Heade Conformance r | The tester shall verify the Number of Views values is 2. | | TE05.02.12.01 | 9.3.1 General Record He Conforma ader nce | The tester shall verify the Reserved Byte value is 0. | | TE05.02.13.01 | 9.3.2 View Header Conformance | ber value of the The tester shall verify the View Num Single Finger View Record is 0. | | TE05.02.14.01 | Header 9.3.2 View Conformance | 0 or 2 and is The tester shall verify the value is either consistent with vendor reporting. | | TE05.02.16.01 | eader 9.3.2 View H Conformance | the Number of Minutiae is The tester shall verify that between 0 and 128. | | TE05.02.17.01 | Data 9.3.3 Fingerprint Minutiae | The tester shall verify minutia type is either 00b, 01b, or 10b. | | TE05.02.19.01 | 9.3.3 Fingerprint Minutia Data e | The tester shall verify that the value of Extended Data Block Length is zero. | | TE05.03.01.01 | 9.4.1 Facial Image Header Conformance 9.4.2 Facial Image Data Conformance | to verify The tester shall review the documentation compliance with the assertion. | | TE05.03.02.01 | r 9.4.2 Facial Image Data 9.4.1 Facial Image Heade Conformance Conformance | is The tester shall verify that the size of the record such that it will be in compliance with the assertion.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_00868", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Technology Assessment_ Methods for Measuring the Level of Computer Security provide? (Section 237) t it to meet the management, organization, and situation-specific characteristics, resources, needs, and objectives. The method must not obscure the mission. There are no absolute \"units\" of security. As a result, security \"measurements\" must be stated in relative terms. The background and scale against which this measurement takes place is that defined by security policy. A technology assessment on security evaluation would not be complete without an examination of policy impacts on the evaluation process. Security policy discussion is divided into two components: sensitivity distinctions and acceptance criteria. Sensitivity refers to the consequences of loss. The greater the potential loss if data (or equipment) is disclosed, changed, destroyed, or delayed [45] , the greater the sensitivity of that data (or equipment). It follows that the greater the sensitivity involved, the greater the need for security. Of course the need for, say, increased application security might be satisfied by system or installation controls, not application controls. There are two generic structural types of sensitivity distinction: horizontal and vertical. Both are typically used together. Horizontal distinctions are sometimes referred to as communities of interest. Examples of such horizontal categories for data include proprietary, financial, personal, medical, psychological, political, investigatory, system controls, test answers, and national security (perhaps further broken down as plans, capabilities, and intelligence sources). Vertical distinctions are sometimes referred to as security or sensitivity levels. Examples are Top Secret / Secret / Confidential / Unclassified as used in DoD and the Office of [45] Sensitivity is often interpreted as applying primarily (or only) to disclosure losses. This can be very misleading. Some organizations (e.g. many banks) regard data integrity (resistance to data modification or insertion) as the primary type of loss; others (e.g.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, secret, top secret. Contains guidance on protecting sensitive government information. Source: Technology Assessment_ Methods for Measuring the Level of Computer Security."}]}
{"id": "nist_00869", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Test Activity according to Mobile Device Security_ Bring Your Own Device (BYOD)? Test Activity: Attempt to directly access enterprise services, e.g., Exchange email server or corporate VPN, on a mobile device that is not enrolled in the EMM system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_00870", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance say about System Recovery Plan Document? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance, System Recovery Plan Document: The System Recovery Plan is designed to ensure the continuation of vital manufacturing/business processes in the event a cybersecurity incident occurs. Its purpose is to provide a structured approach for responding to cybersecurity incidents by leveraging the infrastructure inventory and configuration information relevant to the organization's IT and OT environments to restore operational capabilities. This plan has been developed to accomplish the following objectives: - limit the magnitude of any loss by minimizing the duration of a manufacturing interruption, - assess damage, repair the damage, and restore manufacturing system, - manage the recovery operation in an organized and effective manner, and - prepare personnel to respond effectively in system recovery situations.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance."}]}
{"id": "nist_00871", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Code Organization according to NIST Codes for Identification of Federal and Federally-Assisted Organizations According to Codes for Identification of Federal and Federally-Assisted Organizations, Code Organization: | 9530 | Advisory Council On Historic Preservation | |--------|--------------------------------------------------------------------| | 1141 | African Development Foundation | | 7200 | U.S. Agency for International Development | | 7400 | American Battle Monuments Commission | | 4602 | Appalachian Regional Commission | | 9532 | Architectural and Transportation Barriers Compliance Board | | 4965 | Arctic Research Commission | | 84AF | Armed Forces Retirement Home | | 97NH | United States Naval Home | | 8400 | United States Soldiers' and Airmen's Home | | 9560 | Barry Goldwater Scholarship and Excellence in Education Foundation | | 9563 | Financial Crisis Inquiry Commission | | 9568 | Broadcasting Board of Governors | | 9522 | Centennial of Flight Commission | | 5600 | Central Intelligence Agency | | 9565 | Chemical Safety and Hazard Investigation Board | | 7635 | Christopher Columbus Fellowship Foundation | | 9567 | Commission for the Preservation of America's Heritage Abroad | | 9537 | Commission of Fine Arts | | 9517 | Commission on Civil Rights |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Codes for Identification of Federal and Federally-Assisted Organizations."}]}
{"id": "nist_00872", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Glossary of Computer Security Terminology provide? (Section 51) e network. In this mode, system users need not be cleared for all types of compartmented information processed, but they must be fully cleared for at least the highest level of classified information. (NCSC'TG-004-88) - 2) Utilization of a resource-sharing computer system for the concurrent processing and storage of: (1) two or more types of SCI or (2) one type of SCI with other than SCI. For DON purposes, the compartmented mode should be considered equivalent to multilevel mode. (OPNAVINST 5239.1 A) Authority recognized by the DAA as having sufficient knowledge (individually or corporately) to make a valid determination. (AFR 205-16) Refers to a review and examination of records, procedures, and review activities at a site in order to assess the unclassified computer security posture and ensure compliance with this order. This review is normally conducted by the CPPC at an operations office having cognizance over the site and management responsibilities for implementing this Order. Forthose sites not reporting to an operations office, this review is normally conducted by the Office of ADP Management. (DOE 1360.2A) compromise compromising emanations - 1) The disclosure of classified data to persons who are not authorized to receive such data. (DOE 5637.1; DOE 5635.1 A) - 2) An unauthorized disclosure or loss of sensitive information. (FIPS PUB 39) - 3) [Passwords] Disclosing a password, or part of a password, to someone not authorized to know, have or use the password. (FIPS PUB 1 1 2) - 4) The known or suspected exposure of clandestine personnel, installations or other assets, or of classified information or material, to an unauthorized person. (NCSC-9) - 5) An unauthorized disclosure or loss of sensitive defense data. (OPNAVINST 5239.1 A; AR 380-380) - 6) A violation of the security policy of a system such that unauthorized disclosure ofsensitive information may have occurred.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, compartmented. Contains guidance on protecting sensitive government information. Source: Glossary of Computer Security Terminology."}]}
{"id": "nist_00873", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Identity and Access Management for Electric Utilities say about Java Application? (Part 3) According to Identity and Access Management for Electric Utilities, Java Application: tions through the database administrator login. The current version of AlertEnterprise products supports Oracle and Microsoft SQL Server databases. The NCCoE build also supports MySQL server database. To configure the database server, follow these steps: NIST SP 1800-2C: Identity and Access Management for Electric Utilities 156 Create a schema / system identifier (SID) per your naming convention in the database server. The steps to create a schema can be different with different database management systems. Refer to the administrators guide for the database management system installed at your landscape. Create a new user with full access to the created schema. Run the included SQL files, AlertReport471.ddl or AlertReport471.sql and AlertQuartz.sql, on the new schema created. This step should be performed while installing the AlertEnterprise application for the first time. 9.2.3.7 Avoiding Case-Sensitivity Issues in Alert DB To avoid case-sensitivity issues while using the search and sort functionalities in the AlertEnterprise applications, enable a \u201cCase Insensitiveness\u201d search in the database. By default, it is set as case- sensitive. Follow these steps to avoid case-sensitivity issues: Create a trigger to support case insensitiveness. /***********/ create or replace trigger set_nls_onlogon AFTER LOGON ON SCHEMA DECLARE BEGIN EXECUTE IMMEDIATE 'ALTER SESSION SET NLS_SORT=\"BINARY_CI\"'; EXECUTE IMMEDIATE 'ALTER SESSION SET NLS_COMP=\"LINGUISTIC\"'; END set_nls_onlogon; /************/ Restart the AlertEnterprise Application server. The effect may not be visible in some client tools, such as SQL Developer. To see the effect in the SQL Developer tool, follow these steps: Open SQL Developer, and click Tools > Preferences. Click Database > NLS, and perform the following actions: T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_00874", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Technical Solution Overview according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case, Technical Solution Overview: DBAN is a free open source data wiping utility allowing the ability to sanitize hard drives to ensure data is not left behind when drives are beginning decommissioned and prepared for removal from on-premise. DBAN and other hard drive sanitization tools only work with spinning hard drives, SSD hard drives and other flash media refer to vendors for specific directions for sanitizing media before removing from company control.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case."}]}
{"id": "nist_00875", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2016 NIST_ITL Cybersecurity Program Annual Report say about CONTACTS:? According to 2016 NIST_ITL Cybersecurity Program Annual Report, CONTACTS:: Mr. Rodney Petersen (301) 975-8897 nice.nist@nist.gov Ms. Danielle Santos (301) 975-5048 danielle.santos@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_00876", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Quick Start Guide for Populating Mobile Test Devices say about Appendix C-Mobile Device Data Example? (Part 2) According to Quick Start Guide for Populating Mobile Test Devices, Appendix C-Mobile Device Data Example: <!-- image --> Table 12: PIM data example | Data Objects | Data Properties | Data Value | |-------------------------------|------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Contacts/Address Book Entries | Regular length (up to 50 chars) | Eddie Van Halen, 5150515051 | | Contacts/Address Book Entries | Maximum length (over 50 chars) | John Jacob Jingle Heimer Schmidt That's My Name Too Whenever I Go Out The People Always Shout John Jacob Jingle Heimer Schmidt, 8988675309 | | Contacts/Address Book Entries | Special character (!, @, #, $, %, ^, &, *) | *, 8887771212 | | Contacts/Address Book Entries | Blank name | 8785551111 | | Contacts/Address Book Entries | Regular length with multiple metadata objects (e.g., graphic, email, URL, Address, Birthdate) supported by the device.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Quick Start Guide for Populating Mobile Test Devices."}]}
{"id": "nist_00877", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events say about Jennifer Cawthra? According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events, Jennifer Cawthra: National Cybersecurity Center of Excellence NIST Michael Ekstrom Lauren Lusty Julian Sexton John Sweetnam The MITRE Corporation McLean, Virginia", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events."}]}
{"id": "nist_00878", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Attribute-based Access Control for Microservices-based Applications using a Service Mesh say about Appendix A: List of Recommendations for deployment of an ABAC-based authentication and authorization framework for microservicesbased applications using a service mesh? (Part 4) According to Attribute-based Access Control for Microservices-based Applications using a Service Mesh, Appendix A: List of Recommendations for deployment of an ABAC-based authentication and authorization framework for microservicesbased applications using a service mesh: that is provided by the secure discovery service or DNS. This requirement is needed to ensure that the server is the authorized location for the microservices and to protect against network hijacking. | Service-level Authentication | | EAUN-SR-1 | A request authentication policy must, at the minimum, provide the following information and must be enforced by the sidecar proxy \u25cf Instructions for extracting the credential from the request \u25cf Instructions for validating the credential | End-user level Authentication | | SAUZ-SR-1 | A policy object describing service-to-service access should be in place for all services in the mesh. At a minimum, these policies should restrict access to the namespace level (e.g., 'services in namespace A can call services in namespace B').", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Attribute-based Access Control for Microservices-based Applications using a Service Mesh."}]}
{"id": "nist_00879", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Enhanced Security Requirements for Controlled Unclassified Information say about Abstract? According to Assessing Enhanced Security Requirements for Controlled Unclassified Information, Abstract: The protection of Controlled Unclassified Information (CUI) in nonfederal systems and organizations is important to federal agencies and can directly impact the ability of the Federal Government to successfully carry out its assigned missions and business operations. This publication provides federal agencies and nonfederal organizations with assessment procedures that can be used to carry out assessments of the requirements in NIST Special Publication 800172, Enhanced Security Requirements for Protecting Controlled Unclassified Information: A Supplement to NIST Special Publication 800-171 . The assessment procedures are flexible and can be tailored to the needs of organizations and assessors. Assessments can be conducted as 1) self-assessments; 2) independent, third-party assessments; or 3) government-sponsored assessments. The assessments can be conducted with varying degrees of rigor based on customer-defined depth and coverage attributes. The findings and evidence produced during the assessments can be used to facilitate risk-based decisions by organizations related to the CUI enhanced security requirements.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00880", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SR-11(3) in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? (Part 8) Control SR-11(3): ________________________________________________________ INTENDED EFFECT IMPACT ON RISK EXPECTED RESULTS The threat event may produce consequences, but those consequences cannot produce an impact. IMPEDE (includes contain, degrade, delay, and exert) Make it more difficult for the threat event to cause adverse impacts or consequences. For adversarial threats, this involves decreasing the adversary\u2019s return on investment (ROI) for the threat event. CONTAIN Restrict the effects of the threat event to a limited set of resources. The consequences of the threat event are less extensive than they might otherwise be. DEGRADE Decrease the expected consequences of the threat event. Because the consequences of the threat event are less severe than they would be without the mitigation, they could fail to produce an impact, or their impact could be lessened. DELAY Increase the amount of time needed for the threat event to result in adverse impacts. Because the consequences of the threat event occur later than they would without the mitigation, they could fail to produce an impact, or their impact could be lessened. EXERT Increase the level of effort or resources needed for an adversary to achieve a given result. Example: Subtle variations in critical software are implemented (synthetic diversity) and prevent the adversary\u2019s malware from compromising the targeted software. Reduce the likelihood of impact and reduce the level of impact. \u2022 Adversary activities are restricted in scope, fail to achieve full effect, do not take place in accordance with the adversary timeline, or require greater resources than the adversary had planned. Reduce the level of impact. Reduce the likelihood of impact, and/or reduce the level of impact. Reduce the likelihood of impact, and/or reduce the level of impact. Reduce the likelihood of impact. \u2022 The adversary can affect fewer resources than planned.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, adversary. Contains technical security guidance that could inform defensive posture. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_00881", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to NIST_SP_800-53r5_Security_Privacy_Controls? Discussion: In certain situations, such as during events that are defined in contingency plans,", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00882", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings say about 4th Annual PKI R&amp;D Workshop -- Proceedings? (Part 2) According to 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings, 4th Annual PKI R&amp;D Workshop -- Proceedings: e. The paranoid may regard this procedure as opening up a vulnerability itself - from there on, any local scripts (using the 'file:///' scheme) may change Mozilla's preferences for that profile. It could have been worse, though: we considered and rejected the idea of avoiding the creation of a temporary file by sending the Javascript program over HTTP - that would mean the user should allow script execution over the 'http://' scheme, which would open it up to abusive scripts from anywhere on the Internet. A limitation of our current engager implementations is that they cannot handle Proxy AutoConfiguration [11], which is quite popular. Since implementing this support would require a quite capable JavaScript interpreter, we have chosen to deal with it in future versions; we felt that for the purposes of proving the concept, it was not essential. Notice that engagers are just a convenience feature for users. They're obviously not necessary for the rest of the proxy to work, so long as the user changes the browser and Kapanga's proxy settings manually. That way, this whole system works even with browsers our implementation doesn't have specific engagers for. All that is required is that the browser must have proxy support. We've successfully run Kapanga in conjunction with many other browsers such as Konqueror, Opera and even Links (a console-based browser), just for kicks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_00883", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Can Great Seneca Accounting stop someone from turning on a camera or microphone? according to NIST Mobile Device Security_ Bring Your Own Device (BYOD) According to Mobile Device Security_ Bring Your Own Device (BYOD), Can Great Seneca Accounting stop someone from turning on a camera or microphone?: Malicious actors with access (authorized or unauthorized) to device sensors (microphone, camera, gyroscope, Global Positioning System receiver, and radios) can use them to conduct surveillance. It may be directed at the user, as when tracking the device location, or it may be applied more generally, as when recording any nearby sounds. Captured sensor data may be immediately useful to a malicious actor, such as a recording of an executive meeting. Alternatively, the attacker may analyze the data in isolation or in combination with other data to yield sensitive information. For example, a malicious actor can use audio recordings of on-device or proximate activity to probabilistically determine user inputs to touchscreens and keyboards, essentially turning the device into a remote keylogger.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_00884", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does National Online Informative References (OLIR) Program_ Overview, Benefits, and Use provide? (Section 1) <!-- image --> Overview, Benefits, and Use Nicole Keller Stephen Quinn Karen Scarfone Matthew C. Smith Vincent Johnson This publication is available free of charge from: <!-- image --> Overview, Benefits, and Use Nicole Keller Stephen Quinn Computer Security Division Information Technology Laboratory Karen Scarfone Scarfone Cybersecurity Matthew C. Smith Huntington Ingalls Industries Vincent Johnson Electrosoft Services, Inc. This publication is available free of charge from: February 2024 <!-- image --> U.S. Department of Commerce Gina M. Raimondo, Secretary National Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology Certain 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: National Online Informative References (OLIR) Program_ Overview, Benefits, and Use."}]}
{"id": "nist_00885", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identity and Access Management for Electric Utilities provide? (Section 304) re 9-23 Guardian Job Scheduler Triggers Field Map 9.3.3.10 Job Scheduler > Triggers Setup > Manual Configuration > Job Scheduler > Triggers. Click New, and create the PACSAD Trigger (Table 9-15). Table 9-15 Guardian Job Scheduler Triggers Name Description Type PACSAD Trigger PACSAD Trigger Reconciliation NIST SP 1800-2C: Identity and Access Management for Electric Utilities 190 Name Batch Size Number of Attempts PACSAD Trigger 100 3 Policy Designer for Users/Roles User policy New T h i s p u b l i c a t i o n System: Reconciliation From Reconciliation System Field Mapping Group User Type User Role PACS AD PACS AD PACSAD Field Map True True 9.3.3.11 Job Scheduler > Scheduler Setup > Manual Configuration > Job Scheduler > Scheduler. Click New, and enter the following fields, as shown in Figure 9-24. a. Job Type: Reconciliation Job b. Job Name: <Job Name> c. Select the Global checkbox d. Reconciliation for: Users e. Reconciliation Type: Incremental Reconciliation f. Reconciliation Triggers: PACSAD Trigger g. Select the schedule as Immediate, Once, Periodically, or Advance. For Periodically, specify the Start At, End At, and Rerun every (duration of job frequency, which should be no less than every 2 minutes). i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . NIST SP 1800-2C: Identity and Access Management for Electric Utilities 191 Figure 9-24 Guardian Reconciliation Job T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . Click Save. 9.4 AlertEnterprise Enterprise Guardian Configuration for the CA Build 9.4.1 System Type Import of DB Connector Log into the application. Go to Setup > Manual Configuration > Import/Export. Check System Types, and then click Import.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_00886", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Note according to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls? Note: No attempt has been made to make this even a representative bibliography. For further material, see Carlstedt [5], almost any of the other references, or any of several more comprehensive, although not necessarily current, bibliographies.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls."}]}
{"id": "nist_00887", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does U.S. Department of Justice Simplified Risk Analysis Guidelines provide? (Section 29) OF DATA 9a. STATE SENSITIVITY LEVEL OF APPLICATION - 9b. STATE CRITICALITY OF APPLICATION <!-- image --> AUTOMATED INFORMATION SYSTEM FACILITY (AIS) PRIORITIZATION OF APPLICATION SYSTEMS - 9A. APPROXIMATE RANKING OF SENSITIVITY OF APPLICATION SYSTEMS PROCESSED ATTHE AIS FACILITY. - 9a RANK CRITICALITY LEVEL OF EACH APPLICATION WITH RESPECT TO THE FUNCTIONS EACH AIS APPLICATION SUPPORTS. WORKFORM 4 PRIORITIZATION OF SENSITIVITY AND CRITICALITY OF APPLICATIONS Component Application Name System Owner Criticality of Application (please check one) Vital The organization could not accomplish its mission without the application. Important The application is necessary for the organization to perform its mission in a cost-effective and timely manner. Useful The application improves productivity or saves costs but is not essential to operations. Estimate of impact on organization if processing of application is interrupted for various periods of time. Application system owners are requested to estimate the loss if the application cannot be processed for the periods of time listed. The loss estimate should consider the impact on mission operations, the cost of using a manual back-up system, any idle manpower or equipment, and losses in the effectiveness and efficiency of the DOJ project. Please estimate the losses for each delay listed (hour to one month) as I, L, M, H, or C considering the following: I - Insignificant (less than $1,000). L - Low ($1,000 to $10,000). M - Moderate ($10,000 to $100,000). H - High ($100,000 to $1,000,000). C - Catastrophic (over $1,000,000). 1 Hour 1 Day 2 Weeks 2 Hours 2 Days 1 Month 4 Hours 1 Week Have plans been developed to process the application system elsewhere if processing is interrupted? Yes No If yes, describe the plans. - 3.1. Microcomputers/Personal Computers (PCs).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: U.S. Department of Justice Simplified Risk Analysis Guidelines."}]}
{"id": "nist_00888", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-3 in Data Integrity_ Recovering from Ransomware and Other Destructive Events? (Part 125) Control IP-3: ies you wish to exclude. For example, we chose to exclude C:\\Users\\*\\AppData because that provided many false flags of routine application data modification. 17. Check the box next to Stop Recursion . <!-- image --> <!-- image --> 18. Click Finish . 19. The rule created defines a space for the tasks we will create to search through. ## 2.11.2.2 Creating a Baseline Task 1. Click the Tasks link. 2. Click New Task . 3. Select Baseline Rule Task . <!-- image --> <!-- image --> 4. Click OK . 5. Enter a name for the baseline rule task. 6. Select a privileged user in Tripwire Enterprise to run the rule as. 7. Click Next . 8. Select All Baselines . <!-- image --> <!-- image --> 9. Click Next . 10. Expand Root Node Group &gt; Smart Node Groups &gt; System Tag Sets &gt; Operating System . 11. You can select specific types of operating systems to run the task on or specific machines. We selected Operating System to have it run on all applicable Windows machines. 12. Once you have made your selection, click Next . 13. Select Selected nodes with rule or rule group . 14. Click the rule you created earlier. <!-- image --> <!-- image --> 15. Click Next . 16. Decide how often the baseline task should be run. We set it to manually but you can also set a very specific schedule by choosing periodic . 17. Click Finish . 18. This rule will create baselines of the specified objects. Baselines are essentially versions of the file that check rules will compare against. Baselines should be primarily taken when the integrity of files are known to be good. <!-- image --> ## 2.11.2.3 Creating a Syslog Action 1. Click the Actions link. <!-- image --> 2. Click New Action . 3. Select Syslog Action . 4. Click OK . <!-- image --> 5. Enter a name for the Syslog Action. 6. Click Next . 7. Enter the IP address of the Tripwire Log Center server. 8. Enter the port that Tripwire Log Center receives TCP syslog messages on. 9. Enter a log name , a level , and a facility code per your needs.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Recovering from Ransomware and Other Destructive Events."}]}
{"id": "nist_00889", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Performance Assurance and Data Integrity Practices say about File Structure? (Part 2) According to Performance Assurance and Data Integrity Practices, File Structure: unt to achieve improved data reliability. 12. Reliability Through File Redundancy: Some file systems carry checksums over into the data base to assure that data quality does not deteriorate over time. The more advanced systems carry separate checksums, one for the control information and the other for the data values. 13. Reliability Through Input Redundancy: Additional redundancy can be built into input messages (at the cost of increasing the input character count) to provide context information for edit programs, to allow meaningful correction (in some instances), and to allow meaningful operator dialogs in an on-line system. This redundant information takes several forms: check words, double entries, check digits, and batch totals. 14. Redundancy for Audit: Within the data base, additional information can be carried in the record header to provide the basic parameters for certain types of integrity audits. Specifically, a record header could contain the identifier associated with the last program to update the record, the date of that last update, the time of that update, and the transaction sequence number causing the update. 15. Data Checks on Sequence: When processing input transactions, the effective date of the transaction can be processed by the computer to alert the control group in the event over-age transactions are being processed and in extreme cases to inhibit processing of ancient transactions. When the effective date of the transaction is compared against the effective date of the last transaction to update a data record, out of time sequence transactions can be recognized and manual intervention requested 16. Self-Defining Files for Integrity: One technique for handling very large files (in excess of a dozen full tape reels at 1600 bpi ) involves a file design with a directory on the front of every individual record. The directory describes the structure of the record and contains pointers to every data element contained in the record.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Performance Assurance and Data Integrity Practices."}]}
{"id": "nist_00890", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2011 Annual Report? (Part 59) Control HA-3: rocessing Standard (FIPS) 180-4, Secure Hash Standard (SHS) FIPS 180-3, Secure Hash Standard (SHS) , specifies secure hash algorithms (SHAs) called SHA-1, SHA-224, SHA-256, SHA-384 and SHA-512. These algorithms produce 160, 224, 256, 384, and 512-bit outputs, respectively, which are called message digests. Draft FIPS 180-4 provides a general procedure for creating an initialization hash value, adds two additional secure hash algorithms, SHA-512/224 and SHA-512/256, to the standard, and removes a restriction that padding must be done before hash computation begins, which was required in FIPS 180-3. SHA-512/224 and SHA512/256 may be more efficient alternatives to SHA-224 and SHA-256 on platforms that are optimized for 64-bit operations. Removing the restriction on padding operation in the secure hash algorithms will potentially allow more flexibility and efficiency in implementing the secure hash algorithms in many computer network applications. On February 11, 2011, NIST published a notice in the Federal Register (76 FR 7817) announcing the availability of draft FIPS 180-4 and soliciting comments on the draft standard. Comments were received and are being addressed. FIPS 180-4 is expected to be approved in the near future. NIST will submit the FIPS to the Secretary of Commerce for approval in the first half of FY2012. ## NIST Draft (revised) SP 800-107, Recommendation for Applications Using Approved Hash Algorithms SP 800-107 provides security guidelines for achieving the desired security strengths for cryptographic applications that employ the approved cryptographic hash functions specified in FIPS 180. The current version of this document was published in February 2009. Draft FIPS 180-4 added two new hash algorithms: SHA512/224 and SHA-512/256. SP 800-107 was revised to address the security properties of these new hash algorithms.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2011 Annual Report."}]}
{"id": "nist_00891", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007 say about Record-Level Requirements and Assertions? (Part 147) According to Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007, Record-Level Requirements and Assertions: | 2 | M | 14.006-JP2-JP2L- HLL | {14.006} EQ { Image Width} | 3 | |------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| | | | | 2 | M | 14.006-PNG-HLL | {14.006} EQ { Image Width} | 3 | | | | | 2 | M | 14.006-WSQ-HLL | {14.006} EQ { Image Width} | 3 | | 14.007-VLL | 19.1.7 | Field 14.007 shall contain the number of horizontal lines contained in the | 2 | M | 14.007-JPEGB- JPEGL-VLL | {14.007} EQ { Image Height } | 3 | | | | transmitted image.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007."}]}
{"id": "nist_00892", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Information Technology Security Services say about D.4.2.2 Establish a Incident Tracking System? According to Guide to Information Technology Security Services, D.4.2.2 Establish a Incident Tracking System: The team shall develop a system for &lt;organization name&gt; to locate pertinent information about previous incidents, links to documentation for known viruses and other malicious code, known vulnerabilities of systems, and key people to contact. The team shall develop an incident tracking system. The COTR will review the Tracking System.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Information Technology Security Services."}]}
{"id": "nist_00893", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i provide? (Section 101) for negotiation flow between STAs and APs during the discovery phase. 51 Beacon frames may be configured to transmit periodically from approximately every millisecond to every 66 seconds. Figure 5-5. Beacons Used During the Discovery Phases in an ESS <!-- image --> During the discovery phase, STAs and APs negotiate the following key security capabilities: - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; Confidentiality and integrity protocols for protecting unicast traffic - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; Authentication method for mutual authentication of the AP and AS - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; Cryptographic key management approach - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; Pre-authentication capabilities (described in more detail in Section 5.4.4). Confidentiality and integrity protocols for protecting multicast/broadcast traffic are dictated by the AP, since all STAs in a multicast group must use the same cipher suite. The specification of the confidentiality and integrity protocol, along with the chosen key length (if variable), is known as the cipher suite . The same cipher suite options are available for protecting unicast traffic and multicast and broadcast traffic. 52 The possible cipher suites allowed by the IEEE 802.11i amendment are as follows: - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; WEP, with either a 40-bit or 104-bit key - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; TKIP - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; CCMP, which is the default choice according to the 802.11i standard. In practice, many existing devices default to TKIP. 52 The WEP cipher suites are only valid as a group cipher suite in a Transition Security Network to allow pre-RSNA devices to join a BSS. They are not valid in an RSN. - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; Vendor-specific methods (to allow for flexibility and expansion).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i."}]}
{"id": "nist_00894", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2007 Annual Report provide? (Section 133) roposals on technical information system management audits, low power encryption, and signcryption, threeparty entity authentication, responsible vulnerability disclosure, and secure system design. Through its membership on CS1, where Dan Benigni serves as the nonvoting chair, and Richard Kissel is the NIST Primary with vote, NIST contributes to all CS1 national and international IT security standards efforts. NIST can also initiate IT security-related projects for national or international standardization through its membership on CS1. As an example, CSD staffer David Ferraiolo recently discussed initiating a new project in CS1 concerning an access control mechanism that can be embedded into operating systems. Dan Benigni also serves as CS1 Liaison to a new INCITS Study Group on Security Best Practices, whose charter is to study the security needs and requirements of the financial and insurance services industries, assess what is missing in current standards and practices, and make recommendations on an approach to create deployable best practices and frameworks for security in these industries. CS1 has created a task group called CS1.1 RBAC, with one national standards project called 'Requirements for the Implementation of RoleBased Access Control (RBAC)' INCITS Project 1794. This standard will provide implementation requirements for RBAC systems, which use RBAC components defined in INCITS 359-2004. The implementation requirements in this standard are intended to ensure the interchange of RBAC data (e.g., roles, permissions, users) and promote functional interoperability among RBAC services and applications. Within the next several months, this work will be ready for its first public review.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Computer Security Division 2007 Annual Report."}]}
{"id": "nist_00895", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to Security and Privacy Controls for Information Systems and Organizations? Discussion: System media includes both digital and non-digital media. Digital media includes", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_00896", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-37r2_Risk_Management_Framework provide? (Section 38) e official for risk management and risk executive (function); 14 and - Establishes responsibility and accountability for controls implemented within information systems and inherited by those systems. The RMF provides a dynamic and flexible approach to effectively manage security and privacy risks in diverse environments with complex and sophisticated threats, evolving missions and business functions, and changing system and organizational vulnerabilities. The framework is policy and technology neutral, which facilitates ongoing upgrades to IT resources 15 and to IT modernization efforts-to support and help ensure essential missions and services are provided during such transition periods. This publication describes the RMF and provides guidelines for managing security and privacy risks and applying the RMF to information systems and organizations. The guidelines have been developed: - To ensure that managing system-related security and privacy risk is consistent with the mission and business objectives of the organization and risk management strategy established by the senior leadership through the risk executive (function); - To achieve privacy protections for individuals and security protections for information and information systems through the implementation of appropriate risk response strategies; - To support consistent, informed, and ongoing authorization decisions, 16 reciprocity, and the transparency and traceability of security and privacy information; 11 Chapter 3 describes the seven steps and associated tasks in the RMF. 12 Section 2.6 describes the relationship between requirements and controls with respect to RMF execution. 13 [OMB FEA] provides guidance on the Federal Enterprise Architecture. 14 [OMB M-17-25] provides guidance on risk management roles and responsibilities. 15 IT resources refer to the information technology component of information resources defined in [OMB A-130].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_00897", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Criticality Analysis Process Model_ Prioritizing Systems and Components provide? (Section 60) | | Methods | Document Review; Group Decision Making | | Related processes outside of criticality analysis | [FIPS 199] [NIST SP 800-39] - (3.1) Framing Risk | 6 For further guidance on example security measures and metrics, see Appendix A of NIST SP 800-55 Revision 1, Performance Measurement Guide for Information Security.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Criticality Analysis Process Model_ Prioritizing Systems and Components."}]}
{"id": "nist_00898", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about REFERENCES? According to Assessing Security Requirements for Controlled Unclassified Information, REFERENCES: Source Assessment Procedures: SC-08, SC-08(01), SC-28, SC-28(01)", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00899", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control WE-125 in Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities? (Part 67) Control WE-125: g., SQL injec/t\\_i.ligaon) and Source Code Injec/t\\_i.ligaon (e.g., Cross Site Scrip/t\\_i.ligang (XSS)). Injec/t\\_i.ligaons enable the following security failures: IEX, TPR, ACE, and its sub-case RCE. Avoiding the BF DVR bugs (i.e., missing or erroneous veri/uniFB01ca/t\\_i.ligaon or under-restric/t\\_i.ligave or over-restric/t\\_i.ligave veri/uniFB01ca/t\\_i.ligaon) and faults (i.e., invalid data) guarantees safety from errors, such as Wrong Value , Inconsistent Value , and Wrong Type . ## 9.2. Memory Safety Memory safety has both temporal and spa/t\\_i.ligaal aspects that depend on pointer safety. Temporal memory safety ensures that an object memory is only accessed or used during its life cycle and only via its proper pointers (owners). Access is via BF MAD Dereference of a pointer to the object; use is via BF MUS Read or Write of object data. The /uniFB01rst opera-/t\\_i.ligaon over an allocated object must be BF MUS Ini/t\\_i.ligaalize Object , and the last one before it is deallocated must be BF MUS Clear (see Fig. 9). Memory safety ensures the proper access and use of memory in code. That is, pointers to objects are properly ini/t\\_i.ligaalized, dereferenced, reposi/t\\_i.ligaoned, or reassigned, and objects are properly allocated, ini/t\\_i.ligaalized, read, wri/t\\_t.ligaen, resized, cleared, or deallocated. It is addressed by the BF Memory Bugs Model (see Fig. 9) opera/t\\_i.ligaon /uniFB02ow and the BF MAD, MMN, and MUS classes (see BF MEM at [1]) that de/uniFB01ne why, where, and how memory safety could break. Examples of temporal memory safety are unini/t\\_i.ligaalized object, use a/f\\_t.ligaer deallocate (i.e., use a/f\\_t.ligaer free or use a/f\\_t.ligaer return in C), and double deallocate (i.e., double free in C) safety. The /uniFB01rst prevents the use of non-meaningful data values, the second prevents the use of data values via dangling pointers, and the third prevents the dealloca/t\\_i.ligaon of deallocated objects via dangling pointers.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities."}]}
{"id": "nist_00900", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Section 2) | 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 | In April, 2013, NIST published an update, Revision 4, to NIST Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organization .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, risk management framework, rmf. General security reference material without sensitive content. Source: Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations."}]}
{"id": "nist_00901", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 1 \u2013 General say about B.3 Conditions Under Which Keying Material Needs to be Recoverable? According to Recommendation for Key Management_ Part 1 \u2013 General, B.3 Conditions Under Which Keying Material Needs to be Recoverable: The decision as to whether to back up or archive keying material for possible key recovery should be made on a case-by-case basis and should be based on the list provided in Section 8.2.2.2. When the key-recovery operation is requested by the key's owner, the following actions shall be taken: 1. If a lost key may have been compromised, then the key shall be replaced as soon as possible after recovery in order to limit the exposure of the recovered key and the data it protects (see Section 8.2.3.1). This could include reapplying the protection on the protected data using the new key. 2. If the key becomes inaccessible or has been modified, but compromise is not suspected, then the key may be recovered and used as discussed in Section 9.4.2. The following subsections provide discussions to assist an organization in determining whether or not key recovery is needed. Although the following discussions address only the recoverability of keys, any of the key information (e.g., the metadata associated with the key) shall also be recoverable.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_00902", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is C Compiler according to Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI? C Compiler: Sun C Compiler Version: 2.0 Release: 20 May 1992", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI."}]}
{"id": "nist_00903", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2011 Annual Report provide? (Section 60) cifications in the reference. This involves testing the components of the algorithm to assure that they are implemented correctly. The Monte Carlo Test is designed to exercise the entire IUT . This test is designed to detect the presence of implementation flaws that are not detected with the controlled input of the Known Answer Tests. The types of implementation flaws detected by this validation test include pointer problems, insufficient allocation of space, improper error handling, and incorrect behavior of the IUT . The Multi-Block Message Test (MMT) is designed to test the ability of the implementation to process multi-block messages, which require the chaining of information from one block to the next. Automated security testing and test suite development are integral components of the CAVP . The CAVP encompasses validation testing for FIPS-approved and NIST-recommended cryptographic algorithms. Cryptographic algorithm validation is a prerequisite to the CMVP . The testing of cryptographic algorithm implementations is performed by independent third-party laboratories that are accredited as Cryptographic and Security Testing (CST) laboratories by the NIST National Voluntary Laboratory Accreditation Program (NVLAP). The CAVP develops and maintains a Cryptographic Algorithm Validation System (CAVS) tool that automates the cryptographic algorithm validation testing.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2011 Annual Report."}]}
{"id": "nist_00904", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Proceedings of the Privilege Management Workshop, September 1-3, 2009 provide? (Section 12) Accountability Act (HIPAA) will be the standard with which everyone must comply. This would take the pressure off the U.S. government and place responsibility onto the owners and stewards of the data. | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 60-80% of the medical practitioners are not from 'technical' backgrounds. Does that shift concerns away from privacy and onto availability of the health data? | Yes. The more medical practitioners rely on online data, the more this reliance will drive the requirements for availability guarantees. |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Proceedings of the Privilege Management Workshop, September 1-3, 2009."}]}
{"id": "nist_00905", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is https according to Enhancing Resilience of the Internet and Communications Ecosystem_ A NIST Workshop Proceedings? https: //doi.org/10.6028/NIST.IR.8192", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Enhancing Resilience of the Internet and Communications Ecosystem_ A NIST Workshop Proceedings."}]}
{"id": "nist_00906", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-11 in Guidelines for Smart Grid Cybersecurity? (Part 135) Control SI-11: ations for PEV potential privacy issues should be explored as technology solutions are deployed going forward. System and infrastructure architects and engineers should stay aware of potential issues. Section 5.9 Awareness and Training Organizations involved within the smart grid should provide privacy and information security training, supported by ongoing awareness communications, to their workers that have job responsibilities involving customer and energy usage data. Organizations should also consider providing information to their customers and the public to help them to better understand the privacy issues related to the smart grid, along with how the organization is working to mitigate the associated risks, and also steps the public can take to better protect their own privacy. Utilities, State PUCs/PSCs, Third Party providers, and consumer advocacy groups should consider using these as a starting point to help them effectively and efficiently plan for privacy education programs as they may relate to smart grid privacy. Section 5.10 Mitigating Privacy Concerns within the Smart Grid \uf0b7 Perform privacy impact assessments (PIAs). Any organization that collects personal information, or information that can reveal information about personal activities, can identify areas where privacy protections are necessary by performing a PIA. A PIA can be performed internal to the organization, or by an objective outside entity. \uf0b7 Perform Audits. An audit is a structured evaluation of a person, organization, system, process, enterprise, project or product. Audits can be used to determine compliance levels with legal requirements, to identify areas where policies are not being followed, and so on. An audit should ideally be performed by an objective entity that is not a member of the area being audited. 58 \uf0b7 Utilize the Privacy Use Cases. Use cases can help smart grid architects and engineers build privacy protections into the smart grid.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_00907", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 512) stems - CIS and TCS being the most likely applications. Care must be exercised by field resources who may have printouts, smart device displays, or laptop displays that contain customer personal data. Any reports on these non-operational activities should be assessed from a privacy perspective to ensure that if any personal data is included that appropriate safeguards are taken to limit exposure to authorized utility or Contracted Agent resources. 5.6 Data used to specify location could reveal personal data associated with the location. Determine what data is used in any reports and who has access to these reports in digital or print formats. Location- based information may be considered privacy information itself. 5.7 Access to personal data should be limited to only that necessary to accomplish job responsibilities. 5.8 Different applications keep information for differing periods of time. CIS might keep data about outages that impacted a specific customer in that specific customer's file for a long time. Some historical data can be very helpful to identifying future maintenance needs, assess equipment performance, or determine meter upgrade schedules. This data may be indefinitely held, but should be anonymized, i.e. stripped of personal data, so that it is associated with a meter number but not personal data or energy usage information. 5.9 Assess how long any reports generated on non-operational activities are retained. Create policy safeguards for any reports that must contain personal data. AICPA Principle Applies: X Notes 5.10 Management Principle X 5.11 Notice Principle X Policies and procedures should exist for the data collected, used, shared and stored for non- operational meter reading, configuration, or other activities. A position should exist with assigned accountability for ensuring such policies and procedures exist, are effectively communicated to all personnel, and are followed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_00908", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Integrating Cybersecurity and Enterprise Risk Management (ERM) say about 3.4 Prioritize Risks? (Part 1) According to Integrating Cybersecurity and Enterprise Risk Management (ERM), 3.4 Prioritize Risks: 3.4 Prioritize Risks After identifying and analyzing applicable risks and recording them in the cybersecurity risk register, the priorities of those risks should be determined and indicated. This is accomplished by determining the exposure presented by each risk (i.e., based on the likelihood that a threat event will occur and result in an adverse impact). 29 A cybersecurity risk can have adverse effects on achieving organizational objectives. Based on the analysis conducted using the processes described in Section 3.3, such effects could range from negligible to severe, so exposure determination is important. Additionally, since organizations have limited resources, it is helpful to sort the risks within the register in order of importance to prioritize risk response. In the cybersecurity risk register (CSRR) template in Figure 4, this result helps complete the priority column. 30 When completing the Priority column of the CSRR, consider the following: - How to combine the calculations of likelihood and impact to determine exposure 31 - How to determine and measure the potential benefits from pursuing a particular risk response - When to seek additional guidance on how to evaluate risk exposure levels, such as while evaluating exposures germane to risk tolerance statements Practitioners use both qualitative and quantitative models for calculating and communicating about exposure. Figure 5 (derived from Table I-2 of NIST SP 800-30) demonstrates the use of qualitative descriptors for likelihood and impact as well as how these might be used to determine an overall exposure value. Each risk is evaluated in light of the risk's likelihood and impact and determined during risk analysis. The thresholds for ranges of exposure can be established and published as part of the enterprise governance model and used by stakeholders to prioritize each risk in the register. Figure 5: Likelihood and Impact Matrix Derived from NIST SP 800-30 Rev.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Integrating Cybersecurity and Enterprise Risk Management (ERM)."}]}
{"id": "nist_00909", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity of Genomic Data provide? (Section 93) Loren Buhle (DNAnexus) Session 3 Cybersecurity Challenges for Genomic Data Storage: Xiaofeng Wang (Indiana University) Moderated Q&A: Jianqing Liu (University of Alabama in Huntsville) Session 4 Privacy Challenges for Genomic Data: Sumitra Muralidhar (Veterans Affairs Million Veterans Program), Natalie Ram (University of Maryland Carey School of Law) Moderated Q&A: Julie Snyder (MITRE) Session 5 Current and Future Genomic Data Use Challenges: Gail Jarvik (American Society of Human Genetics [ASHG]), Ankit Malhotra (Amazon Web Services [AWS]), Heidi Sofia (NIH National Human Genome Research Institute [NHGRI]) Moderated Q&A: Nick Cochran (HudsonAlpha) | | Segment 5: Open Lightning Round | Audience Insights: Li-San Wang (University of Pennsylvania) | | Segment 6: Next Steps | Close Out: Ron Pulivarti (NIST) | Table 3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cybersecurity of Genomic Data."}]}
{"id": "nist_00910", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Acquisition Consistency according to Cell Phone Forensic Tools_ an Overview and Analysis? Acquisition Consistency: Two consecutive acquisition produce different hashes on the following database files: \\Categories Database, \\ConfigMetabase, SchedSync.dat, DB\\_notify\\_events, DB\\_notify\\_queue, pmailFolders, pmailMsgClasses, pmailNamedProps, pmailServices, and Speed.db. (Below)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_00911", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms provide? (Section 87) e warning and continue operations or to simply discontinue operations. This warning must not be taken lightly. Ignoring the warning means that the user is accepting the risks associated with doing so. For example, if a warning indicates a compromised digital signature certificate, there is a possibility that someone other than the claimed owner of the certificate actually used the private key corresponding to the public key to sign data. Depending on the data, it may not be prudent to ignore the warning. Users should consult with their organizations to determine how to respond to this warning. A PKI consists of at least one CA with its subscribers, as shown in Figure 5. Each of the subscribers (e.g., User 1, User 2, and User 3) obtains a certificate containing their public key and other information, which is signed by their CA. All CA subscribers are provided with the public key of the CA. As a basic example of how this works, suppose that User 3 signs a document and sends the signed document to User 1, who needs to verify the contents and source of the signed document. This is accomplished as follows: 1. User 1 obtains the certificate containing the public key that corresponds to the private key used to sign the document (i.e., User 1 obtains User 3's certificate). Either User 3 supplies that certificate or the certificate is obtained from some other source (e.g., the CA). 2. User 1 verifies User 3's certificate using the CA's public key. 3. User 1 then employs the public key in User 3's certificate to verify the signature on the signed document received from User 3. If the signature is successfully verified, then User 1 knows that User 3 generated the signature, and no unauthorized modifications were made to the document after the signature was generated. <!-- image --> Other more-complicated scenarios exist when users subscribing to different CAs need to interact using CAs that have cross-certified by signing a certificate for each other.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, sso. Contains security framework guidance for authentication systems. Source: Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms."}]}
{"id": "nist_00912", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 658) lemented security program in terms of conformance to policy, determine whether there is a need to enhance policies and procedures, and evaluate the robustness of the implemented security technologies. 6.2.3.2 Inadequate Security Oversight by Management Description Inadequate oversight and commitment by management can result in a suboptimal security cyberculture throughout the organization. Optimal risk management practices begin from the top 7 tier of the organization. Without senior management oversight and ownership, it is very difficult to maintain and fund a successful cybersecurity security program. Potential Impact Lack of clear senior management ownership of a security program makes it almost impossible to enforce the provisions of the program in the event of a policy being compromised or abused. 6.2.3.3 Inadequate Continuity of Operations or Disaster Recovery Plan Description An inadequate continuity of operations/disaster recovery plan can result in lacking or no procedures in place to ensure the continuation or restoration of operations in the event of a security incident. A continuity of operations/disaster recovery plan should include roles, responsibilities, training, periodic testing and exercises, and continuity of operations/disaster recovery plan updates, as well as identification of alternative storage sites, alternative command and control centers and methods, recovery and reconstitution, as well as fail-safe responses. Potential Impact An inadequate continuity of operations or disaster recovery plan could result in longer than necessary recovery from a possible plant or operational outage. 6.2.3.4 Inadequate Risk Assessment Process Description Lack of a robust risk assessment process can result in an inaccurate risk determination. This risk determination ultimately impacts the organization\u2019s understanding of what risks it faces and the associated policies, processes, and security mitigations that are implemented.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_00913", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-1 in Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events? (Part 146) Control IP-1: --> 12. Select the Active Directory domain controller. 13. Click OK. 14. Check the box next to the selected domain controller. 15. Click Edit. 16. Enter credentials for an administrator account. 17. Click Save. 18. Click Config WMI. 19. Click OK. <!-- image --> <!-- image --> 20. Click OK when this configuration finishes. 21. Navigate to Administration &gt; System &gt; Settings &gt; Client Provisioning. 22. Set Enable Automatic Download to Enable. 23. Click Save. 24. Navigate to Administration &gt; Identity Management &gt; External Identity Sources &gt; Active Directory. 25. Click the Groups tab. 26. Click Add &gt; Select Groups from Directory. 27. Click Retrieve Groups. (This should populate the window with the groups from Active Directory.) 28. Select them all. <!-- image --> <!-- image --> 29. Click OK. (If you add more groups to Active Directory they can be imported in the same way in the future.) 30. Click the Attributes tab. 31. Click Add &gt; Select Attributes from Directory. 32. Enter a username. 33. Click Retrieve Attributes. (This will populate the window with Active Directory's available attributes, so they can be used for policy in Cisco ISE.) 34. Click OK. 35. Select any desired attributes. <!-- image --> 36. Click OK. 37. Click Save. ## 2.16.6 Policy Enforcement: Developing Policy Conditions 1. Navigate to Policy &gt; Policy Elements &gt; Conditions &gt; Posture. 2. Expand the Posture section. This will reveal a list of categories for conditions. (Note: These conditions allow you to select or define requirements that endpoints should meet. In typical enterprises, these conditions can be used as requirements to gain network access-however, this strongly depends on the capabilities of your network device.) 3. As an example, we will require that Cisco AMP be installed on all Windows devices. If you are using a different anti-malware software, locate that instead. Click Anti-Malware Condition. <!-- image --> 4. Click Add. 5. Enter a name. 6.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_00914", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure say about 5.2.3. Data Security Category? (Part 19) According to Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure, 5.2.3. Data Security Category: | This may include metering data collected about energy consumed, information used to manage loads and balance power, and local breaker/switchgear control commands. | ISA/IEC 62443-2- 1:D4E1 ORG 2.2, DATA 1.2, USER 1.16 ISA/IEC 62443-3- 3:2013 SR 3.1, SR 3.3, SR 3.4, SR 3.8 | | DS-7: The development and testing environment(s) are separate from the production environment. | Ecosystem: Separating development and testing environments from production environments is considered a best practice. Exceptions, such as early release (e.g., beta versions), can be managed closely while trying to keep as much separation as possible between development and production.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure."}]}
{"id": "nist_00915", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974 say about CURRENT LEGISLATIVE PROPOSALS IN CONGRESS? (Part 3) According to Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974, CURRENT LEGISLATIVE PROPOSALS IN CONGRESS: ned that the worst enemy of privacy is not the computer -its worst enemy is apathy and ignorance. I am pleased that the President addressed himself to privacy in his recent State of the Union Address. Just a few days ago, he announced the formation of a commission on the issue of Privacy and Data Banks in our country. Suffice to say, it does us little good to attack the computer -it is only an instrument of man. \\^Tiat must be attacked is the computer mentality-the kind of faceless bureaucracy in and out of Governxnent that seeks to make the computer a supreme being. The potential of privacy invasion is always present in a sophisticated computer operation. Remarkably, the misuse of information held about individuals in computer systems has been held to a minimum. But the potential for misuse is still there, and certainly data surveillance has grown to very menacing proportions due to the technological advances which alter such information Given multiple use and consolidation through automated systems. Substantial increases in demand for personal reports by Government Agencies, Private Systems, and Social Science Researchers have intensified the severity of the problem. As you know, it is not enough for us to discuss the technology of the computer and speak of privacy in an abstract fashion. We must resolve, at this Conference, and in every other private and public forum to do what is necessary to protect our constitutional right to privacy. Let us make no mistake about it. the computer already knows more about most of us than we know about ourselves. The amount of data held in computer systems is enormous. Think about it for a moment. The list includes tax returns, census responses, social security data, military records, security files, finger prints, FHA and VA mortgage guarantees, credit records, health data, and social research involving individuals. Such examples are barely the tip of the iceberg.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974."}]}
{"id": "nist_00916", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Section 38) h, compromise, or otherwise adversely impact a system. Social engineering includes phishing, pretexting, impersonation, baiting, quid pro quo, threadjacking, social media exploitation, and tailgating. Social mining is an attempt to gather information about the organization that may be used to support future attacks. Security literacy training includes how to communicate employee and management concerns regarding potential indicators of insider threat and potential and actual instances of social engineering and data mining through appropriate organizational channels in accordance with established policies and procedures. Source Controls: AT-02, AT-02(02), AT-02(03) Supporting Publications: SP 800-50 [32], SP 800-160-2 [10] - a. Provide role-based security training to organizational personnel: 1. Before authorizing access to the system or CUI, before performing assigned duties, and [ Assignment: organization-defined frequency ] thereafter 2. When required by system changes or following [ Assignment: organizationdefined events ]. - b. Update role-based training content [ Assignment: organization-defined frequency ] and following [ Assignment: organization-defined events ]. Organizations determine the content and frequency of security training based on the assigned duties, roles, and responsibilities of individuals and the security requirements of the systems to which personnel have authorized access. In addition, organizations provide system developers, enterprise architects, security architects, software developers, systems integrators, acquisition/procurement officials, system and network administrators, personnel conducting configuration management and auditing activities, personnel performing independent verification and validation, security assessors, and personnel with access to system-level software with securityrelated technical training specifically tailored for their assigned duties.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_00917", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Requirements for Cryptographic Accordions say about Publication History? According to Requirements for Cryptographic Accordions, Publication History: Approved by the NIST Editorial Review Board on 2025-04-02", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Requirements for Cryptographic Accordions."}]}
{"id": "nist_00918", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI provide? (Section 133) raft, Inc. VR204801 C Compiler: SCO UNIX* Development System Release 3.2v4.2 APTL: 100342 Mindcraft, Inc. 151-2SEQ001 Issued: 04/12/94 Type: Native Product Supplier: Sequent Computer Systems Inc. Product: DYNIX/ptx Version 4.0.0 PCD: DYNIX/ptx POSIX.1 Conformance Specification Part Number 1003-49622-04 GTI - Supported by Product MFS - Supported by Product MC - Supported by Product AP - Supported by Product Computer Hardware Supplier: Sequent Computer Systems Inc. Computer Hardware Product: Sequent Symmetry Systems SE20 C Compiler: ptx/C (Version 4.0.0) APTL: 100342 Mindcraft, Inc. 151-2SEQ002 Issued: 04/12/94 Type: Native Product Supplier: Sequent Computer Systems Inc. Product: DYNIX/ptx Version 2.1.1 PCD: DYNIX/ptx POSIX.1 Conformance Specification Part Number 1 003-49622-03a GTI - Supported by Product MFS - Supported by Product MC - Supported by Product AP - Supported by Product Computer Hardware Supplier: Sequent Computer Systems Inc. Computer Hardware Product: Sequent Symmetry Systems SE60 C Compiler: ptx/C (Version 2.1.1) APTL: 100342 Mindcraft, Inc. 151-2SGI001 Issued: 03/07/95 Type: Native Product Supplier: Silicon Graphics, Inc. Product: IRIX 5.3 with patches 278, 279, and 280 PCD: IRIX 5.3 POSIX.1 Conformance Document GTI - Supported by Product MFS - Supported by Product MC - Not provided by product AP - Supported by Product Computer Hardware Supplier: Silicon Graphics, Inc. Computer Hardware Product: Indigo 2 C Compiler: IRIX Development Option 5.3 (SC4-IDO-5.3) APTL: 100342 Mindcraft, Inc. 151-2SGI002 Issued: 03/07/95 Type: Native Product Supplier: Silicon Graphics, Inc. Product: IRIX 5.3 with patches 278, 279, and 280 PCD: IRIX 5.3 POSIX.1 Conformance Document GTI - Supported by Product MFS - Supported by Product MC - Not provided by product AP - Supported by Product Computer Hardware Supplier: Silicon Graphics, Inc.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI."}]}
{"id": "nist_00919", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Contact according to Computer Security Division 2012 Annual Report? Contact: Dr. Lily Chen (301) 975-6974 llchen@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_00920", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Building Secure Microservices-based Applications Using Service-Mesh Architecture provide? (Section 4) e 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. API gateway; Application Programming Interface (API); circuit breaker; load balancing; microservices; Service Mesh; service proxy. The 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. NOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, continuous monitoring. General security reference material without sensitive content. Source: Building Secure Microservices-based Applications Using Service-Mesh Architecture."}]}
{"id": "nist_00921", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-3 in Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders? (Part 176) Control AC-3: A few lines of Python can get the SAML response into a readable format. In this example, the value above has been saved to a file called samlresp.txt : ``` $ python Python 2.7.10 (default, Feb 7 2017, 00:08:15) [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)] on darwin ``` ``` Type \"help\", \"copyright\", \"credits\" or \"license\" for more information.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, single sign-on. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_00922", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Electronic Health Records on Mobile Devices say about puppet will install here? (Part 95) According to Securing Electronic Health Records on Mobile Devices, puppet will install here: ords on Mobile Devices 13 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P . 1 8 0 0 - 1 . NIST Cybersecurity Framework v1.1 Sector-Specific Standards & Best Practices Security Characteristics Function Category Subcategory PR.DS-3: Assets are formally managed throughout removal, transfers, and disposition PR.DS-6: Integrity checking mechanisms are used to verify software, firmware, and information integrity NIST SP80 0-53 Rev 4 CM-8, MP-6, PE-16 IEC/ISO27002 7.1.1, 7.1.2, 9.1.6, 9.2.6, 9.2.7, 10.7.1, 10.7.2, 10.7.3 20 Critical Security Controls CSC-1, CSC-2 SC-16, SI-7 10.4.1, 12.2.2, 12.2.3 CSC-3 HIPAA Security Rule [2] 45 C.F.R. \u00a7\u00a7 164.308(a)(1)(ii)(A), 164.310(a)(2)(ii), 164.310(a)(2)(iii), 164.310(a)(2)(iv), 164.310(d)(1), 164.310(d)(2) 45 C.F.R. \u00a7\u00a7 164.308(a)(1)(ii)(D), 164.312(b), 164.312(c)(1), 164.312(c)(2), 164.312(e)(2)(i) NIST SP 1800-1D: Securing Electronic Health Records on Mobile Devices 14 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P . 1 8 0 0 - 1 . NIST Cybersecurity Framework v1.1 Sector-Specific Standards & Best Practices Security Characteristics Function Category Subcategory Information Protection Processes and Procedures (PR.IP) PR.IP-1: A baseline configuration of information technology/ industrial control systems is created and maintained incorporating security principles (e.g. concept of least functionality) 20 Critical Security Controls CSC-2, CSC-3, CSC-4, CSC-7, CSC-13 HIPAA Security Rule [2] 45 C.F.R.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Securing Electronic Health Records on Mobile Devices."}]}
{"id": "nist_00923", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Minimum Security Requirements for Federal Information and Information Systems say about 10. Qualifications.? According to Minimum Security Requirements for Federal Information and Information Systems, 10. Qualifications.: The application of the security controls defined in NIST Special Publication 800-53 required by this standard represents the current state-of-the-practice safeguards and countermeasures for information systems. The security controls will be reviewed by NIST at least annually and, if necessary, revised and 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. The 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Minimum Security Requirements for Federal Information and Information Systems."}]}
{"id": "nist_00924", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PS-15413 in Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations? (Part 92) Control PS-15413: ntal guidance, see control enhancements. Departments and agencies should refer to Appendix F to implement this guidance in accordance with Executive Order 14028, Improving the Nation's Cybersecurity . ## Control Enhancement(s): - (6) LEAST PRIVILEGE | PRIVILEGED ACCESS BY NON-ORGANIZATIONAL USERS Supplemental C-SCRM Guidance: Enterprises should ensure that protections are in place to prevent non-enterprise users from having privileged access to enterprise supply chain and related supply chain information. When enterprise users include independent consultants, suppliers, developers, system integrators, external system service providers, and other ICT/OT-related service providers, relevant access requirements may need to use least privilege mechanisms to precisely define what information and/or components are accessible, for what duration, at what frequency, using what access methods, and by whom. Understanding what components are critical and non-critical can aid in understanding the level of detail that may need to be defined regarding least privilege access for non-enterprise users. - Level(s): 2, 3 ## AC-17 REMOTE ACCESS Supplemental C-SCRM Guidance: Ever more frequently, supply chains are accessed remotely. Whether for the purpose of development, maintenance, or the operation of information systems, enterprises should implement secure remote access mechanisms and allow remote access only to vetted personnel. Remote access to an enterprise's supply chain (including distributed software development environments) should be limited to the enterprise or contractor personnel and only if and as required to perform their tasks. Remote access requirements - such using a secure remote access solution, employing multi-factor authentication, limiting access to specified business hours, limit access to specific assets (not networks) based on role and from specified geographic locations - must be properly defined in agreements.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, privileged access. Contains security framework guidance for authentication systems. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_00925", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Engineering Trustworthy Secure Systems provide? (Section 10) Acronyms.................................................................................................47 | Appendix A. Acronyms.................................................................................................47 | | | Appendix B. Glossary | Appendix B. Glossary | ...................................................................................................49 | | Appendix C. Security Policy and Requirements | Appendix C. Security Policy and Requirements | ........................................................64 | | C.1. Security Policy | C.1. Security Policy | .........................................................................................................64 | | C.2. | Security Requirements | ............................................................................................65 | | C.3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_00926", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does U.S. Department of Energy Risk Assessment Methodology say about GLOSSARY? (Part 26) According to U.S. Department of Energy Risk Assessment Methodology, GLOSSARY: ls) and applications programs, and routines which protect data handled by an ADP system and its resources. SPOOFING The deliberate act of inducing a user or a resource into taking an incorrect action. STAND ALONE, SINGLE-USER SYSTEM A system that is physically and electrically isolated from all other systems, and is intended to be used by one person at a time, with no data belonging to other users remaining in the system (e.g., a personal computer with removable storage media such as a floppy disk). SYNCHRONIZED CLOCKS Mechanism that may be used to provide \"liveness\" assurance in support of authentication. SYSTEM An assembly of computer hardware, software, or firmware configured for the purpose of classifying, sorting, calculating, computing, summarizing, transmitting and receiving, storing, controlling or receiving data with a minimum of human intervention. SYSTEM HIGH SECURITY MODE The mode of operation in which the computer system and all of its connected peripheral devices and remote terminals are protected in accordance with the requirements for the highest security level of material contained in the system at that time. All personnel having access to the system have a security clearance, but not a need-to-know, for all material then contained in the system. SYSTEM INTEGRITY The state that exists when there is complete assurance that under all conditions an ADP system is based on the logical correctness and reliability of the operating system, the logical completeness of the hardware and software that implement the protection mechanisms, and data integrity. SYSTEM SECURITY OFFICER (SSO) The person (s) responsible for ensuring thatsecurity is provided for and implemented throughout the life cycle of an AIS from the beginning of the concept development phase through its design, development, operation, maintenance, and secure disposal.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: U.S. Department of Energy Risk Assessment Methodology."}]}
{"id": "nist_00927", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for Media Sanitization say about optical disk? According to Guidelines for Media Sanitization, optical disk: A plastic disk that is read using an optical laser device.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Media Sanitization."}]}
{"id": "nist_00928", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2009 Annual Report say about Securing the Domain Name System (DNS)? (Part 1) According to Computer Security Division 2009 Annual Report, Securing the Domain Name System (DNS): Securing the Domain Name System (DNS) The Domain Name System (DNS) is a global distributed system in which Internet addresses in mnemonic form such as http:// csrc.nist.gov are converted into the equivalent numeric Internet Protocol (IP) addresses such as 129.6.13.39. Certain servers throughout the world maintain the databases needed, as well as perform the translations. A DNS server that is performing a translation may communicate with other Internet DNS servers if it does not have the data needed to translate the address itself. As with other Internet-based systems, DNS is subject to several threats. To counter these threats, the Internet Engineering Task Force (IETF)-an international standards body-developed a set of specifications for securing DNS called DNS Security Extensions (DNSSEC) to provide origin authentication and data integrity for all responses from the DNS. In partnership with the Department of Homeland Security, NIST has been actively involved in promoting the deployment of DNSSEC since 2004. As part of this continuing effort, we published guidelines for DNSSEC deployment in NIST SP 800-81, Secure Domain Name System (DNS) Deployment Guide , in May 2006. This year, the first revision was begun (SP 800-81r1). The revision includes updated configuration and operational guidance based on lessons learned from early deployments. Some of these changes include: - Aligning cryptographic algorithm and key recommendations with NIST approved algorithms and key sizes; - Guidance on the use of Next Secure 3 (NSEC3) DNS Resource Record that presents authenticated denial of existence so as to minimize information leakage; and - Guidance on cryptographic algorithm rollover and DNSSEC deployment in split zones (e.g., firewall, Network Address Translation (NAT)) environments.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Computer Security Division 2009 Annual Report."}]}
{"id": "nist_00929", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Building a Cybersecurity and Privacy Learning Program say about 1.6.2. Senior Leadership? (Part 2) According to Building a Cybersecurity and Privacy Learning Program, 1.6.2. Senior Leadership: being granted access to system resources Agencies and organizations should form a Senior Leadership Committee that meets regularly with CPLP managers to discuss strategy and provide resource support. The CPLP managers will provide the Senior Leadership Committee with regular reports on the CPLP's performance throughout the year. If there is an emerging risk or new threat that needs to be addressed in the CPLP, the Senior Leadership Committee can connect the learning team with operational teams and SMEs who can provide learning content and resources. Organizations may also include employee representatives as stakeholders in the Senior Leadership Committee to ensure that they have a voice in decision-making.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Building a Cybersecurity and Privacy Learning Program."}]}
{"id": "nist_00930", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Wireless Infusion Pumps in Healthcare Delivery Organizations provide? (Section 5) ing number of infusion pumps connecting to networks, the vulnerabilities and risk factors become more critical, as they can expose the pump ecosystem to external attacks, compromises, or interference. SOLUTION The NCCoE has developed cybersecurity guidance, NIST Special Publication (SP) 1800-8: Securing Wireless Infusion Pumps, by using standards-based commercially available technologies and industry best practices to help HDOs strengthen the security of the wireless infusion pump ecosystem within healthcare facilities. This NIST cybersecurity publication provides best practices and detailed guidance on how to manage assets, protect against threats, and mitigate vulnerabilities by performing a questionnaire-based risk assessment. In addition, the security characteristics of the wireless infusion pump ecosystem are mapped to currently available cybersecurity standards and the Health Insurance Portability and Accountability Act (HIPAA) Security Rule. Based on our risk assessment findings, we apply security controls to the pump\u2019s ecosystem to create a \u201cdefense-in-depth\u201d solution for protecting infusion pumps and their surrounding systems against various risk factors. Ultimately, we show how biomedical, networking, and cybersecurity engineers and IT professionals can securely configure and deploy wireless infusion pumps to reduce cybersecurity risk. While the NCCoE used a suite of commercial products to address this challenge, this guide does not endorse these particular products, nor does it guarantee compliance with any regulatory initiatives. Your organization's information security experts should identify the products that will best integrate with your existing tools and IT system infrastructure. Your organization can adopt this solution or one that adheres to these guidelines in whole, or you can use this guide as a starting point for tailoring and implementing parts of a solution.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Wireless Infusion Pumps in Healthcare Delivery Organizations."}]}
{"id": "nist_00931", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control BA-123 in Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio? (Part 32) Control BA-123: another risk refers to an outage of the customer help desk, there may need to be a third risk in the register that considers the likelihood and impact of an outage that affects both services at once. It is also important to identify cascading risks where one primary risk event may trigger a secondary and even a tertiary event. Analysis of the likelihood and impact of these first-, second-, and third-order risks is described in Sec. 3.3. During the threat modeling process, the practitioner needs to look out for and mitigate instances of cognitive bias. Some common issues of bias include: - Overconfidence - The tendency for stakeholders to be overly optimistic about risk scenarios (e.g., unreasonably low likelihood of a threat event, overstated benefits of an opportunity, exaggerated estimation of the ability to handle a threat) - Groupthink - Rendering decisions as a group about potential threat sources and threat events in a way that discourages creativity or individual responsibility - Following trends - Blindly following the latest hype or craze without a detailed analysis of the specific threats facing the organization - Availability bias - The tendency to focus on issues (such as threats) that come readily to mind because one has heard or read about them, perhaps in ways that are not representative of the actual likelihood of a threat event occurring and resulting in adverse impact ## 3.2.3. Determination of Exploitable and Susceptible Conditions The next key input to risk identification is understanding the potential conditions that enable a threat event to occur. It is important to consider all types of vulnerabilities in all assets, including people, facilities, and information. For this document, vulnerability is simply a condition that enables a threat event to occur. It could be an unpatched software flaw, a raw material limitation, a process that leads to human error, or a physical environmental condition (like a wooden structure being flammable).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio."}]}
{"id": "nist_00932", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2008 Annual Report say about Policy Machine? (Part 1) According to Computer Security Division 2008 Annual Report, Policy Machine: Policy Machine As a major component of any operating system or application, access control mechanisms come in a wide variety of forms, each with their individual attributes, functions, methods for configuring policy, and a tight coupling to a class of policies. A natural consequence of the deployment of many heterogeneous systems is a lack of interoperability. A lack of interoperability may not be a problem for systems that can adequately operate independently of one another, but access control mechanisms require interoperability to function efficiently. Users with vastly different credentials have a need to access resources protected under different mechanisms, and resources that are protected under different mechanisms differ vastly in their sensitivity and therefore accessibility. This lack of interoperability introduces significant privilege and identity management issues. Interoperation is one problem associated with today's access control operations. Another problem pertains to policy enforcement. Since the early days of shared computing, research programs have focused on creating access control models that support specific organization and resource sensitivity requirements. Of the numerous recognized access control policies, today's operating systems (Oss) are limited to the enforcement of instances of Discretionary Access Control (DAC) and simple variations of Role-Based Access Control (RBAC) policies, and to a far lesser extent, instances of Mandatory Access Control (MAC) policies. As a consequence, there are a number of important policies (orphan policies) that lack a commercially viable OS mechanism for their enforcement. Among these orphan policies is the need to combine arbitrary policies. To fill policy voids, policies are routinely accommodated through the implementation of access control mechanisms at the application level.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, identity management, sso. Contains security framework guidance for authentication systems. Source: Computer Security Division 2008 Annual Report."}]}
{"id": "nist_00933", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.4 Objective 4 -User Compliance With External Requirements according to NIST Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls, 5.4 Objective 4 -User Compliance With External Requirements: In connection with all system related activities, users should undertake to assure compliance with all external system requirements, incuding: 1. Legal. 2. 2.. Regulatory. 3. Interagency and intraagency. 4. Internal and external auditor needs.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls."}]}
{"id": "nist_00934", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PS-15413 in Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations? (Part 303) Control PS-15413: isclosed financial information of public companies that trade on global stock markets. Upon discovery of the attack, ABC Company could face significant reputational harm due to the negative publicity. ABC Company's customers may engage in legal action against ABC Company as a result of their failure to appropriately patch known vulnerabilities in their software products. ## Mitigating Strategies ABC Company identified the following areas for improvement in order to enhance their secure software development practices and improve the confidence in their products: - Ensure that developers receive training on secure development practices and are instructed on the use of vulnerability tooling so that developed software is secure. - Ensure that reused system components - whether developed internally or open source - are evaluated as part of a standard process for known vulnerabilities (Ref. SA-15). - Maintain a system component inventory to aid in maintenance of the software product throughout its life cycle (Ref. CM-8). - Continuously monitor system components for vulnerabilities that arise, and ensure that appropriate processes are in place for expeditious remediation once a fix is available. Automate this process where possible (Ref. CA-7, RA-5). Table 13.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_00935", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Subject according to NIST Test Personal Identity Verification (PIV) Cards Version 2? Subject: CN=Test Cardholder XII, ou=Test Agency, ou=Test Department, o=U.S. Government, c=US", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_00936", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out say about INCIDENT RESPONSE TEAM? According to Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out, INCIDENT RESPONSE TEAM: - o Computer Security Act of 1987, (Pub. L 100-235) - o OMB Circular A-130, Appendix III, Security of Federal Automated Information Systems - o NIST SP 500-166, Computer Viruses and Related Threats: A Management Guide - o NIST SP 500-170, Management Guide to the Protection of Information Resources - o NIST SP, Establishing a Computer Security Incident Handling Capability, 1991 - o Organizing a Corporate Anti-Virus Effort, Alan Fedeli, 1991 - o Security Policy Handbook, P. Holbrook and J. Reynolds, 1991 - o Responding to Computer Security Incidents: Guidelines for Incident Handling, E.E, Schultz, D.S. Brown, and T.A. Longstaff, 1990", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out."}]}
{"id": "nist_00937", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain ABSTRACT according to NIST Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events According to Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events, ABSTRACT: Ransomware, destructive malware, insider threats, and even honest user mistakes present ongoing threats to organizations. Organizations' data, such as database records, system files, configurations, user files, applications, and customer data, are all potential targets of data corruption, modification, and destruction. Formulating a defense against these threats requires two things: a thorough knowledge of the assets within the enterprise, and the protection of these assets against the threat of data corruption and destruction. The NCCoE, in collaboration with members of the business community and vendors of cybersecurity solutions, has built an example solution to address these data integrity challenges. Multiple systems need to work together to identify and protect an organization's assets against the threat of corruption, modification, and destruction. This project explores methods to effectively identify assets (devices, data, and applications) that may become targets of data integrity attacks, as well as the vulnerabilities in the organization's system that facilitate these attacks. It also explores methods to protect these assets against data integrity attacks using backups, secure storage, integrity checking mechanisms, audit logs, vulnerability management, maintenance, and other potential solutions.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_00938", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2010 Annual Report provide? (Section 160) ERO\u00ad AA infrastructure includes Federal Emergency Response Officials (FEROs), State/Local/Tribal/Private Sector Emergency Response Officials (SLTP-EROs) and the FEMA Disaster Reserve Workforce (DRW). The system supports the establishment, conveyance and validation of Identity Credentials (ICs), Attribute Credentials (ATs) and Deployment Authorization Credentials (DAs). Apart from enumeration of the types of EROs and their associated author\u00ad ity domains (called major players) and types of credentials, the conceptualization of the framework for ERO-AA infrastructure includes detailed description of various component services un\u00ad der three major service classes: Credentialing Service Class, Iden\u00ad tity Verification and Attribute Validation Service Class and Trust Federation Service Class. The framework is predicated upon the use of trusted tokens capable of supporting biometric as well as secret key based identity authentication. Dr. Ramaswamy Chandramouli mouli@nist.gov Ms.Teresa Schwarzhoff teresa.schwarzhoff@nist.gov Group: Systems and Emerging Technologies Security Research Web services are currently a preferred way to develop and pro\u00ad vide complex services. This complexity arises due to the com\u00ad position 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 mis\u00ad use is reported, investigators have to navigate through a collec\u00ad tion of logs to recreate the attack. In order to facilitate that task, the report proposes creating forensics web services (FWS) that would securely maintain transactional records between other web services. These secure records can be re-linked to reproduce the transactional history by an independent agency. The report demonstrates the necessary components of a forensic frame\u00ad work for web services and its success through a case study. Dr.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, token. Contains security framework guidance for authentication systems. Source: Computer Security Division 2010 Annual Report."}]}
{"id": "nist_00939", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Purpose of the Conference according to NIST Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974 According to Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974, Purpose of the Conference: The second of two national conferences on Privacy and Security in Computer Systems was held at the National Bureau of Standards on March 4-5, 1974, to continue the dialog in search of ways to safeguard confidential information in automated systems. The first conference, held in November, 1973, featured governmental spokesmen who described the nreds and problems of Federal, state and local agencies in protecting confidential and valuable data from loss or misuse while at the same time providing free access to information concerning the public's business.' The second conference provided the opportunity for persons or organizations to offer views and proposals on how these governmental issues might be resolved. The conference was attended by 376 persons: 265 from government and 111 from the private sector. The attendees represented four congressional offices, 36 Federal agencies, 23 states, six municipalities, 33 computer companies or consulting organizations, three trade associations, and 20 professional associations, universities and public interest groups. Total registration at both conferences was 886. In his welcoming remarks. Dr. Richard W. Roberts, Director, National Bureau of Standards, observed that this broad spectrum of interest was demonstrative recognition that all groups must work together in harnessing the highly automated information systems that serve so many areas of our society. Dr. Betsy Ancker-Johnson, Assistant Secretary for Science and Technology, Department of Commerce, noted that the President's February 23, 1974, statement on the American Right to Privacy accentuated the crucial nature of the privacy issue and the urgency of purpose represented by the conference objectives.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974."}]}
{"id": "nist_00940", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IR-7864 in The Common Misuse Scoring System (CMSS)_ Metrics for Software Feature Misuse Vulnerabilities? (Part 4) Control IR-7864: roduce a severity score for each vulnerability. CMSS enables organizations to make security decisions based on a standardized quantitative assessment of their vulnerability to software feature misuse. 1 2 3 ## Table of Contents | 1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: The Common Misuse Scoring System (CMSS)_ Metrics for Software Feature Misuse Vulnerabilities."}]}
{"id": "nist_00941", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Securing Public Web Servers say about 7.5.1 SSL/TLS Capabilities? (Part 1) According to Guidelines on Securing Public Web Servers, 7.5.1 SSL/TLS Capabilities: 7.5.1 SSL/TLS Capabilities SSL/TLS provides the following capabilities to HTTP and other application layer protocols [SSL98]: - GLYPH&lt;c=31,font=/IEIOAF+Webdings&gt; Server AuthenticationSSL/TLS allows a Web client (user) to confirm a Web server's identity. SSL/TLS-enabled Web clients (browsers) can employ standard techniques of public key cryptography to check that a server's name and public key are contained in a valid certificate issued by a CA listed in the client's list of trusted CAs. This confirmation might be important if the user, for example, is sending a credit card number over the network and wants to confirm the receiving server's identity. - GLYPH&lt;c=31,font=/IEIOAF+Webdings&gt; Client AuthenticationSSL/TLS allows a Web server to confirm a user's identity using the same techniques as those used for server authentication by reversing the roles. SSL/TLS-enabled Web 49 Proper understanding of SSL and the information presented in this section requires at least a basic understanding of cryptographic algorithms, message digest functions, digital signatures, symmetric encryption algorithms, and asymmetric encryption algorithms. For an introduction to cryptography, see NIST SP 800-32, Introduction to Public Key Technology and the Federal PKI Infrastructure . For more information on transport layer security, see NIST SP 800-52, Guidelines for the Selection and Use of Transport Layer Security (TLS) Implementations . Both of these documents can be found at http://csrc.nist.gov/publications/nistpubs/. 50 SSL versions before 3.0 are insecure and should not be used. 51 http://www.ietf.org/rfc/rfc2246.txt server software can confirm that a client's certificate is valid and was issued by a CA listed in the server's list of trusted CAs. 52 This confirmation might be important if the server, for example, is a bank that is sending confidential financial information to a customer and wants to confirm the recipient's identity.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Guidelines on Securing Public Web Servers."}]}
{"id": "nist_00942", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Securing Web Transactions_ TLS Server Certificate Management? (Part 380) Control HA-1: Create a New Notification, take the following steps: 4. When finished, click Save Changes. | Email Address | Enter the email address of the person to whom the audit log notifications are to be sent. | |-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Division | In the drop-down, select the divisions whose account activity needs to be monitored. | | Notify me about | Check any of the following options: \u2022 Order Changes Alerts if any changes are made to certificate orders. \u2022 User Changes Alerts if any edits are made to any user accounts. \u2022 User Logins Alerts of all account logins. \u2022 Logins from Invalid IP Addresses Alerts if any account logins are made from invalid IP addresses. \u2022 Certificate Revocations Alerts to all certificates are revocations. | The designated individual should start receiving the selected audit log notifications. ## Notification Management Typically, notifications are not strictly required when utilizing Venafi to manage certificates, as expiring certificates are renewed automatically (or not) based on configured policy within Venafi. However, it is beneficial to configure renewal notifications within CertCentral. ## 2.3.3.4.1 Account Notifications Before sending email from an account, assign an email address to receive a copy of any message sent (e.g., approval notifications). Configure renewal notifications and add default renewal messages that include renewal notifications. <!-- image --> ## 2.3.3.4.2 Set Up Email Notification Accounts 1. In the CertCentral account's sidebar menu, click Settings &gt; Notifications. 2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_00943", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings provide? (Section 318) instability and may cause severe network performance problems. Studies of BGP have considered convergence [10, 20, 34] and possible optimizations to control and accelerate it [11, 19, 21, 23, 30, 38]. Because BGP is central to Internet functionality and is vulnerable to malicious actors, we need to secure the information that BGP distributes. We consider each component: - GLYPH&lt;15&gt; Origin authentication considers whether the originating AS really controls a claimed IP address range. - GLYPH&lt;15&gt; Path authentication considers whether a claimed path to reach some IP prefix is in fact valid. The dominant security solution, Secure BGP (SBGP) [17] focuses on the Update messages. The first step of S-BGP is to set up public key infrastructures to help establish the authenticity of the involved parties. S-BGP uses X.509 [12] public key certificates and puts BGPrelated information into certificate extensions. Speakers digitally sign the Update messages they announce to peers; with these X.509 certificates, recipients can verify the signatures to authenticate the received routes. More specifically, each speaker uses address attestations (AAs) for origin authentication, and route attestations (RAs) for path authentication. Figure 1: Sketch of the S-BGP PKIs. <!-- image --> To enable validation of attestations, S-BGP proposes two X.509 public key infrastructures. The first PKI contains certificates to authenticate the owners of portions of the IP address space . The second PKI is to authenticate BGP speakers, ASes, and the owners of ASes. Figure 1 illustrates the structures of these PKIs. Both PKIs are hierarchies rooted at ICANN [15]. ICANN issues itself selfsigned certificates and further issues certificates to the the first tier of organizations, typically Regional Internet Registries (RIRs) such as ARIN, RIPE, APNIC, and LACNIC. PSfrag replacements ASes, and BGP speakers. The AS number authentication is similar to address allocation authentication.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_00944", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2009 Annual Report provide? (Section 89) er development. NIST has initiated the development of CTSs for selected international versions of biometric data interchange formats. The associated sample data will also be generated. Research is planned on the need for the development of additional CTSs to test implementations of new biometric technical interface standards being developed. NIST will also research the adaptation of existing modules to our architecture. The detailed analysis of the base standards that are the target of our CTS development has already led to a number of technical contributions towards the development of national and international biometric standards taking place in INCITS and JTC 1/SC37 (e.g., finger minutiae and finger image standards, conformance testing methodology standards). The Biometric Consortium (BC), co-chaired by NIST and NSA, serves as a focal point for research, development, testing, evaluation, and application of biometric-based personal identification/ verification technology. The BC's primary function is to organize and host an annual conference, which enables federal government participants to engage in exchanges with national and international participants on topics such as biometric technologies for defense, homeland security, identity management, border crossing and electronic commerce. The 2009 conference, co-sponsored by NIST, NSA, DHS, DoD Biometrics Task Force, the National Institute of Justice (NIJ), GSA, the Volpe National Transportation Systems Center, and the Armed Forces Communications and Electronics Association (AFCEA), was held September 22-24. It addressed the important role that biometrics can play in the identification and verification of individuals in government and commercial applications worldwide.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: identity management, sso. Contains security framework guidance for authentication systems. Source: Computer Security Division 2009 Annual Report."}]}
{"id": "nist_00945", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for Securing Radio Frequency Identification (RFID) Systems say about 1.1 Authority? According to Guidelines for Securing Radio Frequency Identification (RFID) Systems, 1.1 Authority: The National Institute of Standards and Technology (NIST) developed this document in furtherance of its statutory responsibilities under the Federal Information Security Management Act (FISMA) of 2002, Public Law 107-347. NIST is responsible for developing standards and guidelines, including minimum requirements, for providing adequate information security for all agency operations and assets; but such standards and guidelines shall not apply to national security systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), 'Securing Agency Information Systems,' as analyzed in A-130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in A-130, Appendix III. These guidelines have been prepared for use by Federal agencies. They 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 guidance 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_00946", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Telehealth Remote Patient Monitoring Ecosystem provide? (Section 242) | \uf0a7 Ability to detect unauthorized hardware and software components. | \uf0a7 Providing details for how to establish unique identification for each IoT device associated with the system and critical system components within which it is used. \uf0a7 Providing IoT device customers with the details necessary to establish and implement unique identification for each IoT device associated with the system and critical system components within which it is used. \uf0a7 Providing IoT device customers with the details necessary to require unique identifiers for each IoT device associated with the system and critical system | 45 C.F.R. \u00a7\u00a7 164.308(a)(1)(ii)(A) 164.308(a)(4)(ii)(A) 164.308(a)(7)(ii)(E) 164.308(b) 164.310(d) 164.310(d)(2)(iii) | | ID.AM-2: Software platforms and applications within the organization are inventoried. | \uf0a7 Ability to identify software loaded on the IoT device based on IoT device identity. \uf0a7 Ability to detect unauthorized hardware and software components. | N/A | 45 C.F.R. \u00a7\u00a7 164.308(a)(1)(ii)(A) 164.308(a)(7)(ii)(E) | | ID.AM-4: External information systems are catalogued. | N/A | \uf0a7 Providing documentation detailing all the cloud services used to support the IoT device. | 45 C.F.R.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_00947", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control WE-1272 in Metrics and Methodology for Hardware Security Constructs? (Part 14) Control WE-1272: | 0 | 0 | 0 | 2 | | CWE-1191 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 5 | | CWE-1231 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 2 | | CWE-1233 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 2 | | CWE-1274 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 5 | | CWE-1260 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 4 | | CWE-1240 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 2 | | CWE-1256 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 3 | | Threat", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Metrics and Methodology for Hardware Security Constructs."}]}
{"id": "nist_00948", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2015 Annual Report provide? (Section 93) etworking. The conference continues to be a valuable forum for individuals from government, industry, and academia who are involved with information systems/ cybersecurity workforce development. Attendees gain insights regarding information security awareness, training, education, certification, and professionalization. Attendees also learn of ongoing and planned training and education programs and cybersecurity initiatives. It provides NIST the opportunity to provide assistance to departments and agencies as they work to meet their FISMA responsibilities. The FISSEA website provides links to the Conference Program, and also links to presentations (http:/ /csrc.nist. gov/fissea). The next conference will be held at NIST on March 15-16, 2016. http:/ /csrc.nist.gov/fissea Ms. Patricia Toth (301) 975-5140 Ms. Peggy Himes (301) 975-2489 peggy.himes@nist.gov patricia.toth@nist.gov Since the inception of this Advisory Board in 1987, the Information Security and Privacy Advisory Board (ISPAB) has successfully renewed its charter with proper authority every two years. The Board plays a central and unique role in providing the government with expert advice concerning information security and privacy issues that may affect federal information systems. Title III of the E-Government Act of 2002 reaffirmed the need for this Board by giving it an additional responsibility: to thoroughly review all of the proposed information technology standards and guidelines developed under Section 20 of the National Institute of Standards and Technology Act (15 U.S. Code (U.S.C.) 278g3), as amended. The ISPAB is a federal advisory committee with specific statutory objectives to identify emerging managerial, technical, administrative, and physical safeguard issues related to information security and privacy. The Board was originally created by the Computer Security Act of 1987 (P.L.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2015 Annual Report."}]}
{"id": "nist_00949", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain &lt;IssuerIdentificationNumber&gt;: according to NIST Representation of PIV Chain-of-Trust for Import and Export According to Representation of PIV Chain-of-Trust for Import and Export, &lt;IssuerIdentificationNumber&gt;:: This element is optional and if used occurs only once. The element consist of six characters for the department code, four characters for the agency code, and a five-digit number that uniquely identifies the issuing facility within the department or agency. The &lt;IssuerIdentificationNumber&gt; element is the value for Zone 2B on the back of the PIV Card. The data is provided in an xs:string format.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Representation of PIV Chain-of-Trust for Import and Export."}]}
{"id": "nist_00950", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Survey Findings according to NIST Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST According to Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST, Survey Findings: Although all of the scientists interviewed keep some form of research notebooks, their notekeeping practices and styles vary. The majority of them keep a combination of handwritten notes and electronic notes. Most scientists consider notekeeping to be solely for documenting important research progress, procedures and results. Presently, security and legal concerns are not considered a major issue, although this may change in the future. The most important requirement that was expressed for an ERN is ease of use. Information must be entered in an effortless manner and must be cost-effective in order for the ERN to be acceptable to the scientists and managers. Basically, the ERN must do everything that a pencil and paper can do, with value-added. Writing and drawing in a paper-based notebook will be replaced by an ERN system with textand image-processing capabilities, and possibly with a scanner as well. The tools for making different types of notebook entries must be provided and integrated so that it is possible to link different objects together and still allow the retrieval of a specific object if desired. Each committed entry should be signed by the author using digital signature technology. The signed entry should also be sent to an independent time-stamping server in order to obtain an official time-stamp.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST."}]}
{"id": "nist_00951", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does ANSI_NIST-ITL 1-2011 Requirements and Conformance Test Assertions provide? (Section 178) gle image. This field is mandatory if an image has been stitched, and the value shall be set to 'Y'. Otherwise, this field shall not appear in the record. Reserved for future useonly by ANSI/NIST-ITL. D 14.027-SIF Conditional <See Requirement ID: \u201cField: 14.027-Stitched Image Flag Dependent\u201d> - 14.028, 14.029 Reserved <See Requirement ID: \u201cField: Type14- CondCode>. 8.14.27, Table 67 <Table 67 lists the value constraints for DMM.> 1 O 14.030- DMM {14.030} MO ASCII(CONTROLLED, ASSISTED, OBSERVED, UNATTENDED, UNKNOWN) 8.14.28, Table 67 <Table 67 lists the value constraints for FAP.> 1 O 14.031-FAP {14.031} MO [10, 20, 30, 40, 45, 50, 60] Table 67 Reserved for future useonly by ANSI/NIST-ITL. Table 67 User Defined Fields Table 67 Reserved for future useonly by ANSI/NIST-ITL. 8.14.30, Table 67 8.14.31, Table 67 This is an optional field, listing the operations performed on the original source in order to prepare it for inclusion in a biometric record type. See Section 7.4.1. This is an optional field. See Section 7.7.1.1. - - - 14.032 to 14.199 Reserved 14.200 to 14.900- User Defined 14.901- Reserved <See Requirement ID: \u201cField: Type14- CondCode>. TRUE <See Requirement ID: \u201cField: Type14- CondCode>. O 14.902- ANN-Value <See Requirement ID: \u201cField: xx.902-ANN\u201d >. O 14.903-DUI <See Requirement ID: \u201cField: Device ID\u201d >. t-2 Value 8.14.32, This is an optional field. See Section O 14.904- <See Requirement ID: \u201cField: Make Model\u201d >. t-2 131 t-2 t-2 t-2 t-2 t-2 B B B 14.904- Make/Mode l/Serial Number Value Field: 14.905, 14.994- Reserved Field: 14.995- Associated Context Value Field: 14.996- Hash Value Field: 14.997- Source Representati on Value Field: 14.998- Geographic Sample Acquisition Location Value Field: 14.999- Image Data Valid Table 67 7.7.1.2. MMS Value Table 67 Reserved for future useonly by ANSI/NIST-ITL. - 14.905, 14.994- Reserved <See Requirement ID: \u201cField: Type14- CondCode>.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: ANSI_NIST-ITL 1-2011 Requirements and Conformance Test Assertions."}]}
{"id": "nist_00952", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DS-2 in Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)? (Part 67) Control DS-2: - Connecting to 192.168.20.117:80... connected. HTTP request sent, awaiting response... 200 OK Length: 10701 (10K) [text/html] Saving to: \u2018index.html.12\u2019 0K .......... 100% 6.05M=0.002s 2019-07-10 18:59:40 (6.05 MB/s) - \u2018index.html.12\u2019 saved [10701/10701] (approved): --2019-07-10 18:55:39-- Connecting to 192.168.20.197:80... connected. HTTP request sent, awaiting response... 200 OK NIST SP 1800-15D: Securing Small-Business and Home Internet of Things Devices 160 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Test Case Field Description Length: 10701 (10K) [text/html] Saving to: \u2018index.html.8\u2019 0K .......... 100% 2.03M=0.005s 2019-07-10 18:55:40 (2.03 MB/s) - \u2018index.html.8\u2019 saved [10701/10701] (approved): --2019-07-10 18:59:21-- Connecting to 192.168.20.183:80... connected. HTTP request sent, awaiting response... 200 OK Length: 10701 (10K) [text/html] Saving to: \u2018index.html.10\u2019 0K .......... 100% 17.6M=0.001s 2019-07-10 18:59:21 (17.6 MB/s) - \u2018index.html.10\u2019 saved [10701/10701] Procedure 5 (from laptop to pi): [mud@localhost ~]$ wget 192.168.20.222 --2019-07-10 19:03:17-- Connecting to 192.168.20.222:80... failed: Connection refused. Procedure 6 (from device): http://www.facebook.com (unapproved): --2019-07-10 19:17:39-- https://www.facebook.com/ Resolving www.facebook.com (www.facebook.com)... 31.13.71.36, 2a03:2880:f112:83:face:b00c:0:25de NIST SP 1800-15D: Securing Small-Business and Home Internet of Things Devices 161 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Test Case Field Description Connecting to www.facebook.com (www.facebook.com)|31.13.71.36|:443... failed: Connection refused. Connecting to www.facebook.com (www.facebook.com)|2a03:2880:f112:83:face:b00c:0:25de|:4 43...", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_00953", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Publication History according to NIST Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile, Publication History: Approved by the NIST Editorial Review Board on 2025-03-25 Supersedes NIST SP 800-61r2 (August 2012) https://doi.org/10.6028/NIST.SP.800-61r2", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, csf, fips. General security reference material without sensitive content. Source: Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile."}]}
{"id": "nist_00954", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Trademark Information according to NIST Guidelines for Access Control System Evaluation Metrics According to Guidelines for Access Control System Evaluation Metrics, Trademark Information: All registered trademarks or trademarks belong to their respective organizations.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Access Control System Evaluation Metrics."}]}
{"id": "nist_00955", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective say about Notes on Figure 1 Examples of Cybersecurity SDOs? According to Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective, Notes on Figure 1 Examples of Cybersecurity SDOs: The following Figure 1 illustrates some of the SDOs that have developed cybersecurity standards, in which Federal agencies have had some level of participation. This figure is not intended to be all inclusive. Federal agency participation in these SDOs is driven by each agency's mission and objectives. A brief description of these SDOs, including a few specific subgroups, is given after Figure 1. In addition, based upon history, it is anticipated that other relevant SDOs will appear in the future. Figure 1: Examples of Cybersecurity SDOs <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective."}]}
{"id": "nist_00956", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Policy Machine_ Features, Architecture, and Specification provide? (Section 93) e authority granted to every user through the previous association. Prohibitions are illustrated similarly to associations, but with a different style and orientation of connector. This prohibition denies the user from creating messages within its own inbox, slightly overriding the system-wide authority to create messages in any inbox. - \uf0a7 The association between ID u2 and In u2 allows the user to delete messages from its own inbox. - \uf0a7 To create and delete messages within the containers Out ui, Draft ui, and Trash ui, an association granting such authorization is needed between ID u2 and each of those containers. A few improvements can be made to the current policy specification. For example, a user can update a copy of a sent message residing in its outbox, which can bring about an unwanted inconsistency from what was actually sent. To avoid this situation, the policy can be revised via an obligation that prevents alterations to messages in the user's outbox, once they are written to it. The obligation presumes that draft messages are composed in the sender's drafts folder, and when ready to be sent, copied over in their entirety to newly created message objects in the sender's outbox, before being deleted from the drafts folder. The following obligation accomplishes the write-once restriction through the creation of a user prohibition: Similarly, the current policy allows a user to update messages that it has posted to another user's inbox or messages that other users have posted there. The policy can be extended slightly with an obligation to prevent any alterations to a message after it is initially written to an inbox.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Policy Machine_ Features, Architecture, and Specification."}]}
{"id": "nist_00957", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2011 Annual Report provide? (Section 49) sign Principles subgroup continues the work of identifying bottom-up problems and design considerations developed by the former Bottom-up, Vulnerability, and Cryptography and Key Management subgroups. - The High-Level Requirements subgroup addresses the procedural and technical security requirements of the Smart Grid to be addressed by stakeholders in Smart Grid security. To create the initial set of security requirements in NISTIR 7628 v1.0, this subgroup adapted industry-accepted security source documents for the Smart Grid. - The Privacy subgroup continues to investigate privacy concerns between utilities, consumers, and non-utility third parties. - The Standards subgroup assesses standards and other documents with respect to the cybersecurity and privacy requirements from NISTIR 7628. These assessments are performed on the standards contained in the SP 1108, Framework and Roadmap for Smart Grid Interoperability Standards, or in support of the Priority Action Plans (PAPs). - The Testing and Certification subgroup establishes guidance and methodologies for cybersecurity testing of Smart Grid systems, subsystems, and components. Future work includes working with the SGIP - the Committees, the Domain Expert Working Groups, and the Priority Action Plans - to integrate cybersecurity into their work efforts. Collaboration will continue with the Department of Energy and the North American Electric Reliability Corporation to produce a cybersecurity risk management process document for the electricity sector. Reviewing and updating NISTIR 7628, if needed, will occur in early 2012. Developing a virtual test environment for the National Electrical Manufacturers Association's AMI upgradeability standard and creating an assessment guide for assessing the high-level cybersecurity requirements contained in NISTIR 7628 are also slated for the next year.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Computer Security Division 2011 Annual Report."}]}
{"id": "nist_00958", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Securing Radio Frequency Identification (RFID) Systems provide? (Section 201) At this point, the tags may no longer be in the possession of the organization that issued them, but they may still store identifiers or other data that could reveal PII | | # | Federal CIO Council Control Family | Definition | RFID Considerations | |-----|------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | | | though either direct or indirect means.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, control family, security control. General security reference material without sensitive content. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_00959", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in 2016 NIST_ITL Cybersecurity Program Annual Report? (Part 72) Control HA-3: unications. ## Part n e r s h i p s External Projects. The TIG funds external projects, including a pilot program that impacted more than 6.7 million individuals in its first four years. These projects aim to catalyze the marketplace to begin developing solutions aligned with the guiding principles. The marketplace is currently transitioning from broad market issues to targeting specific gaps and market impediments as the identity ecosystem matures. The pilots develop and deploy technology, models, and frameworks that wouldn't otherwise exist in the marketplace. In FY 2016, the pilot programs made remarkable progress; the 24 projects include more than 170 partner organizations across 12 sectorsincluding the development or deployment of 14 multi-factor authentication solutions. Over the course of the fiscal year, six new pilots were launched (including five supporting state services and one driving federated identity in healthcare) (See https:/ /www.nist.gov/itl/tig/pilot-projects). Figure 27: NIST employs four primary tactics: partnerships, publications, market intelligence, and communications <!-- image --> Identity Ecosystem Framework. The privatelyled Identity Ecosystem Steering Group (IDESG) laid the groundwork for better digital identity transactions with the release of the Identity Ecosystem Framework (IDEF) in early FY 2016. The IDEF lays a foundation for the Identity Ecosystem by providing a baseline set of requirements that define how to execute transactions involving digital identity that puts users at the center by aligning with the four guiding principles, continually improving online commerce, the efficiency of digital services, and online interactions (see http:/ /www.idesg.org/News-Events/Press-Releases/ ID/74/Identity-Ecosystem-Framework-Released-CreatingUnprecedented-Rules-of-the-Road-for-Online-Identity). Strategic partners.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor. Contains security framework guidance for authentication systems. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_00960", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector say about D.9.3.1 Configuration? According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector, D.9.3.1 Configuration: - \uf0a7 Behavior Anomaly Detection: Dragos - Configured to receive packet streams from DMZ, Testbed LAN, Supervisory LAN, and Control LAN. - \uf0a7 File Integrity Checking: ForceField - PI Server is configured to use ForceField drive.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector."}]}
{"id": "nist_00961", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain ASSESSMENT OBJECTIVE according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, ASSESSMENT OBJECTIVE: Determine if: A.03.04.04.a: changes to the system are analyzed to determine potential security impacts prior to change implementation. A.03.04.04.b: the security requirements for the system continue to be satisfied after the system changes have been implemented.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_00962", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector provide? (Section 270) provide data security safeguards for medical images. The Azure solution provides data-at-rest encryption and, through a combination of access control and encryption, provides data security assurance. The NCCoE lab used several different solutions to address data-in-transit encryption. As described in Section 2.6.2, DigiCert PKI, the lab implemented SSL/TLS encryption using DigiCert-issued certificates. Communications between modalities and clinical systems are secured using HIP, as described in Section 2.7.3, Tempered Networks Identity Defined Networking (IDN). Microsoft Azure is a cloud service provider that provides storage and encryption for unstructured data in a remote location separate from the HDO environment. This project used an Azure blob storage account as a remote archive for medical images managed by the VNA. For more information on configuring Azure Storage accounts, including recommended security practices, visit Microsoft's Azure Blob Storage Documentation [13]. To proceed with the following steps, a Microsoft Storage account needs to be established. 1. From a web browser, navigate to https://portal.azure.com/. 2. Log in to the Microsoft account. 3. On the home screen, click Create a resource. 4. Type storage account into the search bar, then click Storage account. 5. On the Storage Account screen, click the Create button. A new screen will appear that requires information to be populated, found in the Basics tab. When complete, click the Next: Networking button. Populate the Basics information using the following values: <!-- image --> <!-- image --> - a. On the Subscription field, select Enterprise from the pull-down menu. - b. Navigate to the Resource Group field . Select the corresponding r esource group. If one is not available, create a new resource group. - c. Navigate to the Storage Account Name field. From the pull-down menu, select the storage account name that had previously been created. - d. Navigate to the Location field.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, pki. Contains security framework guidance for authentication systems. Source: Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector."}]}
{"id": "nist_00963", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Smart Card Technology_ New Methods for Computer Access Control say about 6.2 The NBS Biometric Smart Card Access Control System? (Part 2) According to Smart Card Technology_ New Methods for Computer Access Control, 6.2 The NBS Biometric Smart Card Access Control System: number, the identification number of the smart card, and an indication of whether the user's identity is confirmed or rejected. This access control record is encrypted using DES and sent to the host. The host decrypts the record and checks that it is not a playback of a previous record, and then grants or denies access, depending on the information in the record. Files of access control records can be maintained by the host computer as an audit trail for the system. At any time, the last user's fingerprint resident in the fingerprint verification device may be printed out upon request.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Smart Card Technology_ New Methods for Computer Access Control."}]}
{"id": "nist_00964", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls say about 3.1 Targets? (Part 2) According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls, 3.1 Targets: to modification. We also considered the distinction between analog and digital data. However, this distinction appears to exist primarily in communication links and is not relevant to \"remote sites\". - 3.1.1.3 Sensitivity : The vulnerability of the data varies with its inherent sensitivity. This inherent sensitivity is a function of quantity, context, age and degree of analysis. - o Quantity : The sensitivity of data increases with quantity along an \"S\" shaped turve, i.e., the sensitivity increases more slowly with quantity for large quantities. This is because large quantities of data start to look like noise (forest and trees effect). - o Context : The sensitivity of data varies with its context. It tends to increase along an exponential step function with the number of distinct associations such that \"employee number\" and \"salary\" taken together are significantly more sensitive than either alone and adding \"name\" increases the sensitivity by an order of magnitude. - o Interpretation : The sensitivity of data increases with the degree of analysis or interpretation such that raw data is less sensitive than organized data which is less sensitive than the conclusions which may be drawn which are less sensitive than the plans of action. - \u00b0 Age : In general, the sensitivity of data decreases with age. However, there are exceptions. - 3.1.1.4 Kind or Use: Three kinds of data were identified. They are user or application data, system or control data, such as security tables, and programs or procedures. There was considerable discussion in the group as to whether or not to treat data and programs separately or together. The majority felt that programs are substantively different from other data and that it would be misleading to treat them together. This author contended that from the perspective of vulnerabilities, programs were the same as other data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls."}]}
{"id": "nist_00965", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6 Certificate Revocation Lists according to NIST Report of the NIST Workshop on Digital Signature Certificate Management, December 10-11, 1992 According to Report of the NIST Workshop on Digital Signature Certificate Management, December 10-11, 1992, 6 Certificate Revocation Lists: The following \"hot list\" format is based on that of Internet RFC 1114, with the addition of a reason code. CertificateRevocationList :: signature issuer lastUpdate nextUpdate revokedCertificates", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the NIST Workshop on Digital Signature Certificate Management, December 10-11, 1992."}]}
{"id": "nist_00966", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is This publication is available free of charge from according to Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)? This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_00967", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-1 in Cybersecurity Framework Manufacturing Profile? (Part 68) Control AC-1: esides. Physical access controls may include, for example, lists of authorized individuals, identity credentials, escort requirements, guards, fences, turnstiles, locks, monitoring of facility access. | PE-Family, PE-8 | | | | | Moderate | | | | | PR.AC-2 | Protect power equipment, power cabling, network cabling, and network access interfaces for the manufacturing system from accidental damage, disruption, and physical tampering. Ensure availability and integrity of wireless systems, especially safety related systems. Employ redundant and physically separated power systems for critical manufacturing operations. | PE-9 (1) | | | | | High | | | | | | Control physical access to the manufacturing system in addition to the physical access for the facility.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile."}]}
{"id": "nist_00968", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to NIST_SP_800-53r5_Security_Privacy_Controls? Discussion: Permitting authorized individuals to make changes to system logging enables", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_00969", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST_SP_800-207_Zero_Trust_Architecture say about 3.3 Trust Algorithm? (Part 3) According to NIST_SP_800-207_Zero_Trust_Architecture, 3.3 Trust Algorithm: ocesses that utilize the data (i.e., those responsible for the mission). - Threat intelligence: This is an information feed or feeds about general threats and active malware operating on the internet. This could also include specific information about communication seen from the device that may be suspect (such as queries for possible malware command and control nodes). These feeds can be external services or internal scans and discoveries and can include attack signatures and mitigations. This is the only component that will most likely be under the control of a service rather than the enterprise. The weight of importance for each data source may be a proprietary algorithm or may be configured by the enterprise. These weight values can be used to reflect the importance of the data source to an enterprise. The final determination is then passed to the PA for execution. The PA's job is to configure the necessary PEPs to enable authorized communication. Depending on how the ZTA is deployed, this may involve sending authentication results and connection configuration information to gateways and agents or resource portals. PAs may also place a hold or pause on a communication session to reauthenticate and reauthorize the connection in accordance with policy requirements. The PA is also responsible for issuing the command to terminate the connection based on policy (e.g., after a time-out, when the workflow has been completed, due to a security alert).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-207_Zero_Trust_Architecture."}]}
{"id": "nist_00970", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Attribute-based Access Control for Microservices-based Applications using a Service Mesh say about 1.6 Organization of This Document? According to Attribute-based Access Control for Microservices-based Applications using a Service Mesh, 1.6 Organization of This Document: The organization of this document is as follows: - Section 2 provides an overview of a microservices-based application, its security requirements, a brief description of the overall architecture of reference platform for orchestration and resource management of microservices-based applications and the reference service mesh platform. The latter two are used as examples to illustrate the building blocks involved in the deployment recommendations. - Section 3 outlines the advantages of ABAC for the application environment and describes the functional architecture for two of the standard ABAC representations. - Section 4 discusses the building blocks of the authentication and authorization framework, the requirements and recommendations for configuration of policies that are required in the reference orchestration and resource management platform and in the reference service mesh platform for implementing the framework. The recommendations span mechanisms for supporting both end user and service level authentication and authorization policies. The minimal set of policy elements needed in authorization policies are also outlined. - Section 5 discusses some architectural features of the framework such as functionality of a reference monitor, supporting infrastructure, advantages as an ABAC implementation, and enforcement alternatives. - Section 6 provides summary and conclusions.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Attribute-based Access Control for Microservices-based Applications using a Service Mesh."}]}
{"id": "nist_00971", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Page 4, Figure 3 - Suggested Modification/Correction according to NIST A Report on the Privilege (Access) Management Workshop According to A Report on the Privilege (Access) Management Workshop, Page 4, Figure 3 - Suggested Modification/Correction: 'To answer the question, 'Where does privilege management fit in this view?' the suggested modification/correction is to include a taxonomy in place of Figure 3 to show the relationships between identity, credential, access, privilege, attribute, policy, and metadata management and access control. <!-- image --> Privilege management should be used to refer to the management of entity permissions that correlate to attributes and the applicable policies. (More info on this in the next comment.) Metadata management would include the characteristics of resources (i.e., data, files, applications) to which access is controlled. Access control would be the calculations and execution of permissions defined in privilege management.' [Editor: The proffered figure is a good representation of logical relationships, while Figure 3 in this document shows functional relationships. As an aside, the labels 'Policy Decision Point' and 'Policy Enforcement Point' should probably be 'Access Control Decision' and 'Access Control Enforcement' to be consistent with the earlier comment. In any case, the proffered figure is an excellent adjunct to those in the body of this document. The statements following 'Privilege should be used to refer to the management of entity permissions . . .' represent a departure from the view of privilege management taken in this document. As Anil Ramcharan has suggested in his comment, there is more information on this in the next comment, where we will address the issue. [Editor: The figure and caption in the body of the NISTIR that Anil Ramcharan has referred to are as follows (reproduced here for the convenience of the reader): Figure 3. Authentication Management and Privilege Management <!-- image --> -end of Editor comment.]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: A Report on the Privilege (Access) Management Workshop."}]}
{"id": "nist_00972", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Section 146) ement to relevant sub-tier contractors. Departments and agencies should refer to Appendix F to implement this guidance in accordance with Executive Order 14028, Improving the Nation's Cybersecurity . - Level(s): 2, 3 - Control Enhancement(s): - (8) ACCESS ENFORCEMENT | REVOCATION OF ACCESS AUTHORIZATIONS Supplemental C-SCRM Guidance: Prompt revocation is critical to ensure that suppliers, developers, system integrators, external system service providers, and other ICT/OT-related service providers who no longer require access or who abuse or violate their access privilege are not able to access an enterprise's system. Enterprises should include in their agreements a requirement for contractors and sub-tier contractors to immediately return access credentials (e.g., tokens, PIV or CAC cards, etc.) to the enterprise. Enterprises must also have processes in place to promptly process the revocation of access authorizations. For example, in a 'badge flipping' situation, a contract is transferred from one system integrator enterprise to another with the same personnel supporting the contract. In that situation, the enterprise should disable the existing accounts, retire the old credentials, establish new accounts, and issue completely new credentials. - Level(s): 2, 3 - (9) ACCESS ENFORCEMENT | CONTROLLED RELEASE Supplemental C-SCRM Guidance: Information about the supply chain should be controlled for release between the enterprise and third parties. Information may be exchanged between the enterprise and its suppliers, developers, system integrators, external system service providers, and other ICT/OT-related service providers. The controlled release of enterprise information protects against risks associated with disclosure.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, token, sso. Contains security framework guidance for authentication systems. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_00973", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings provide? (Section 278) with exceptions such as invalid signatures or to ensure that the signed contents is the same as previously sent (since it's within the client's control, a malicious user may change it). - Usable ID enumeration: This filter is triggered by the 'send-usable-ids' command. First, it forces the request to become a POST (even if the browser has sent it as a GET or HEAD). Kapanga then builds a body with a list of PEM-encoded ultimately trusted certificates it has. This is extremely useful because the site can know in advance which identities we can assume, inform the user which ones are acceptable or not and help the user select an appropriate one for login or registration, reducing the likelihood of frustrating failures. The webmasters we have been working with point this particular feature as the one that mostly contributes for the overall user acceptance - it makes it viable to make helpful web-based certificate enrollment/registration system almost as simple as traditional name+password+cookie methods, as shown in Figure 7. <!-- image --> Figure 6: The HTTPS Logon filterset in a client authentication scenario. In (a) the user directs the web browser to an HTTP URL containing the command for adding the site to the Encryption Domain. As Kapanga was engaged to the browser, the request is actually sent over HTTPS because the command parser filter is executed early in the filter chain. Thus, when the request reaches the HTTPS Logon filter, the site address and port is already in the Encryption Domain. In (b), the site has requested client authentication and Kapanga asks the user which certificate he/she wants to use and the passphrase of its associated private key. Unlike Internet Explorer, Kapanga doesn't show expired, revoked or altogether untrusted certificate, nor has a 'remember password' checbox to ruin the whole security of the process.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, sso. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_00974", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2013 Annual Report? (Part 30) Control HA-3: conference, ' Safeguarding Health Information: Building Assurance through HIPAA Security ,' in May 2013 at the Ronald Reagan Building 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. Over 600 in-person and virtual attendees from federal, state, and local governments, academia, HIPAA-covered entities and business associates, industry groups, and vendors heard from, and interacted with, healthcare, security, and 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: - \u0097 Updates on the OCR privacy, security, and breach notification audit program - \u0097 Patient and provider identity management, HIPAA requirements in cloud and mobile environments - \u0097 HIPAA rule changes affecting breach notification and HIPAA security - \u0097 Cybersecurity Framework for improving critical infrastructure cybersecurity - \u0097 Health IT activities at the National Cybersecurity Center of Excellence - \u0097 Methods for managing insider threat - \u0097 Tools available to manage security settings on end-user devices The keynote address was delivered by Eric Dishman, Fellow and General Manager of the Health Strategy &amp; Solutions Group at Intel. In FY 2014, NIST plans to issue a draft revision to Special Publication (SP) 800-66, An Introductory Resource Guide for Implementing the HIPAA Security Rule . As part of its continued outreach efforts, NIST also plans to co-host the seventh annual Safeguarding Health Information conference with OCR. ## Contact: Mr.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: identity management, sso. Contains security framework guidance for authentication systems. Source: Computer Security Division 2013 Annual Report."}]}
{"id": "nist_00975", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Engineering Trustworthy Secure Systems provide? (Section 308) tisfactorily progressing in consideration of project security aspects. - PM-2.3 Act to redirect projects that can be expected to progress satisfactorily with appropriate security-informed redirection. References: [4] [86] [100] - PM-3.1 Where agreements permit, act to cancel or suspend projects whose security-driven disadvantages or security-driven risks to the organization outweigh the benefits of continued investments. - PM-3.2 After completion of the agreement for the security aspects of products or services, act to close the projects. Note : Closure is accomplished in accordance with organizational security policies, procedures, and the agreement. References: [4] [86] [100] The purpose of the Human Resource Management process is to provide the organization with necessary human resources and to maintain their competencies in a manner consistent with strategic needs. Reprinted with permission from IEEE, Copyright IEEE 2015, All rights reserved. - -Define the security criteria for necessary human resources, and maintain their competencies in a manner consistent with strategic needs. - -Security-relevant skills required by projects are identified. Personnel with necessary security skills are provided to projects. NIST SP 800-160v1r1 November 2022 - -Security-relevant skills of personnel are developed, maintained, or enhanced. - -Security-relevant personnel conflicts are resolved. HR-1.1 Identify the security-relevant skills needed based on current and expected projects. HR-1.2 Identify and record the security-relevant skills of personnel. References: [4] [86] [100] [132] [109] [133] HR-2.1 Establish a plan for developing security-relevant skills. Note: Security-relevant skills include core and specialty competencies. HR-2.2 Obtain security-relevant training, education, or mentoring resources. HR-2.3 Provide planned security-relevant skills development. HR-2.4 Maintain records of security-relevant skills development.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_00976", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) provide? (Section 160) all support AES-128 in the CMAC mode as the default for Low and Moderate impact-levels and AES-256 in the CMAC mode as the default for High impact- levels, as specified in [FIPS 197] and [SP 800-38B]. | | PR:7.3 | When interoperability is required, and a symmetric block- cipher algorithm is to be used for authenticated encryption, a Federal CKMS shall support AES-128 in the GCMmode as the default for Low and Moderate impact-levels, and AES- 256 in the GCMmode as the default for High impact-levels, as specified in [FIPS 197] and [SP 800-38D]. | | PR:7.4 | When interoperability is required, and a symmetric block- cipher algorithm is to be used for key wrapping, a Federal CKMS shall support AES-128 in the GCMmode as the default for Low and Moderate impact-levels, and AES-256 in the GCMmode as the default for High impact-levels, as specified in [FIPS 197] and [SP 800-38D]. | | PR:7.5 | When interoperability is required, and a hash function is to be used for a purpose that requires collision resistance 10 , an FCKMS shall support SHA-256 as the default for Low and Moderate impact-levels, and SHA-384 as the default for High impact-levels, as specified in [FIPS 180]. | 9 As opposed to authenticated encryption, which is addressed in PR:7.3 . 10 E.g., for the generation of a digital signature. | PR:7.6 | When interoperability is required, and digital signature generation and verification is to be performed using DSA, the hash function used during signature generation and verification shall be selected as specified in PR:7.5 .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_00977", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation provide? (Section 87) | | [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/ | | [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 | | [Arbor2] | 'NETSCOUT Arbor's 14th Annual Worldwide Infrastructure Security Report' (2019). 03/SECR_005_EN-1901%E2%80%93WISR.pdf | | [ARIN1] | 'Using RPKI at ARIN to certify resources,' ARIN online. https://www.arin.net/resources/rpki/using_rpki.html#hosted | | [ARIN2] | M. Kosters, 'ARIN Provisioning in RPKI,' NANOG 67, June 2016.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation."}]}
{"id": "nist_00978", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST provide? (Section 25) n entry is signed, permissions can be automatically set to make the entry read-only for all users. However, the original author should be able to add a signed addendum to the entry if the need arises. It may also be beneficial to include singleauthor project notebooks in this database. Scientists often find it useful to share information by consulting a peer's notebook during information searches and work flow coordination. In an electronic environment, a centralized database for the ERN that permits simultaneous access over a network would be most convenient. Another important reason for storing the ERNs in a central database is that the central database management system can provide the crucial time-stamping and digital signature capabilities for the ERNs. Most scientists use a variety of software tools such as spreadsheets, statistical packages, finite element analysis packages, etc. Ideally, these should be linked to the ERN in order to integrate important data and prevent needless repetition. Since many scientists use visual browsing to search for particular notebook entries, it would be useful for the ERN to provide a similar capability. This may be done by placing a series of thumbnail sketches of consecutive entries on the screen. Using visual recognition as a search mechanism might prove to be faster in some cases than using hypertext to retrieve important data. In the previous section, the required ERN features were presented. In this section, current technologies as well as commercial products that are relevant for the design of the ERN are reviewed. The enabling technologies to support the ERN design include: - Electronic notepad and PDA technology; - Handwriting recognition technology; - Optical Character Recognition (OCR) technology; - Multimedia technology; - Object-oriented technology; - Database management technology; - Digital signature technology; - Time-stamping technology.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST."}]}
{"id": "nist_00979", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Prerequisites according to Recommendation for Block Cipher Modes of Operation_ the CCM Mode for Authentication and Confidentiality? Prerequisites: block cipher algorithm; key K ; counter generation function; formatting function; MAC length Tlen . Input : valid nonce N ; valid payload P of length Plen bits; valid associated data A ; Output : ciphertext C.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Block Cipher Modes of Operation_ the CCM Mode for Authentication and Confidentiality."}]}
{"id": "nist_00980", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Electronic Health Records on Mobile Devices say about puppet will install here? (Part 103) According to Securing Electronic Health Records on Mobile Devices, puppet will install here: ntrols T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P . 1 8 0 0 - 1 . Company Product V. Architecture Element* Use Open source Open source Fedora PKI Manager 9 2 BIND 9.9.4 3, 5 Open source Puppet Enterprise 3.7 5 Cisco Identity Services Engine 1.2 7, 15 Cisco ASAv 9.4 Open source UrBackup 1.4.8 12 Root CA cryptographically signs identity certificates to prove authenticity of users and devices Domain name system (DNS) server performs host or fully qualified domain resolution to Internet Protocol (IP) addresses Secure configuration manager for creation, continuous monitoring, and maintenance of secure server and user hosts Local and remote mobile network access control (NAC), RADIUSbased authentication, authorization, and accounting management server Enterprise-class VPN server based on both TLS and IPsec Online remote backup system used to provide disaster recovery Cisco RV220W 6.0.4 16, 17 Wi-Fi access point NIST SP 1800-1D: Securing Electronic Health Records on Mobile Devices 24 NIST Cybersecurity Framework Function Detect (DE) T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f Reference to NIST 800-53 Rev 4 Controls AC-2, AC-4, AU-12, CA-3, CA-7, CM-2, CM-3, CM-8, PE-3, PE-6, PE-20, RA-5, SC-5, SC-7, SI-3, SI-4 c h a r g e f r o m : h t t p : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P Respond (RS) AU-6, CA-2, CA-7, CP-2, PE-6, IR-4, IR-5, IR-8, SI-4 . 1 8 0 0 - 1 . Company Product V.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Securing Electronic Health Records on Mobile Devices."}]}
{"id": "nist_00981", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Control according to Trustworthy Email? Control: The information system protects against an individual (or process acting on behalf of an individual) falsely denying having performed [ Assignment: organization-defined actions to be covered by non-repudiation ].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Trustworthy Email."}]}
{"id": "nist_00982", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Notional Supply Chain Risk Management Practices for Federal Information Systems provide? (Section 46) ationships with integrators or suppliers. Note: (1) Use information as available, including information from commercial sources, U.S. government agencies, and intelligence information as appropriate. (2) Respond to such changes when appropriate, e.g., by adding additional countermeasures (such as additional practices from this document) or changing to a less risky integrator or supplier; - Integrate ICT SCRM considerations in continuous monitoring activities; and - Collect feedback on integrator or supplier responsiveness and effectiveness at mitigating risks per acquirer requests. The acquirer should use the practices in Section 4 to address supply chain assurance when acquiring replacement components or field additions/modifications/upgrades, particularly if they do not go through traditional acquisition processes that examine ICT supply chain risks. Acquirers and integrators need to be aware of the time frame within which their elements and systems are expected to become obsolete and plan for replacing and upgrading these elements and systems. Systems that have a long life cycle may require a substantial number of elements that are no longer available from the original component manufacturer or through their franchised distributors. In some cases, upgrades may not be compatible with the system (backwards compatible) or supported by the original manufacturer. Acquirers and integrators should identify and plan for when elements become obsolete. This section provides ten practices that federal department and agency acquirers (acquirers) should consider when creating the list of practices that they employ as part of their ICT SCRM strategy. Each practice is a blend of programmatic activities, validation/verification activities and requirements, as well as general and technical implementation requirements.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, continuous monitoring. General security reference material without sensitive content. Source: Notional Supply Chain Risk Management Practices for Federal Information Systems."}]}
{"id": "nist_00983", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Information Technology Security Services provide? (Section 29) 's policy meets a higher standard, will 'the service provider's' have trouble meeting this higher standard? If lower, will 'the service provider' abide by the stricter policies of the organization? 3. How does 'the service provider' address the comingling of its data with that of another organization? Are processes in place to ensure that an organization's data is protected? | 1 The organization is the unit that acquires and ultimately receives the security service from the service provider. An organizational conflict of interest (OCI) may exist when a party to an agreement has a past, present or future interest related to the work performed (or to be performed), which may diminish its capacity to provide impartial, technically sound, objective service or results in an unfair competitive advantage. Of course, it is best to avoid organizational conflicts before they arise. The Federal Acquisition Regulation (FAR) (subpart 9.5) describes two underlying principles why avoiding an OCI is important: - \u0083 Preventing the existence of conflicting roles that might bias a [service provider's] judgment - \u0083 Preventing unfair competitive advantage According to the FAR, an unfair competitive advantage exists where a [service provider] possesses proprietary information that was obtained from a Government official without proper authorization or source selection information that is relevant to the contract but is not available to all competitors, and such information would assist that [service provider] in obtaining the contract. Although the FAR applies to Federal contracts, any organization should be aware that an OCI could occur in any phase of the IT security services lifecycle and may provide an unfair competitive advantage. - \u0083 There are several methods that an organization can take to avoid, neutralize, or minimize the effect of an OCI. They can include: modify or eliminate the offending parts of the agreement, statement of work, contract, etc.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Information Technology Security Services."}]}
{"id": "nist_00984", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Guidelines for the Use of PIV Credentials in Facility Access? (Part 80) Control PD-12: aster than RSA private key operations, PCIs should consider issuing PIV Cards with ECC Card Authentication keys rather than RSA. The performance of the PIV Card is partially dependent upon the reader. The PKI-CAK authentication mechanism is usually performed over the contactless interface, with the PIV Card being powered by the reader's magnetic field, and cards will operate more slowly when they are underpowered. Improper installation of the reader may lead to the card being underpowered, and it may also create interference that makes communication between the card and the reader unreliable, which would also lead to increased transaction times. Recommendation C.2 : Make use of Qualified HSPD-12 Service Providers 22 to ensure that PACS components are properly installed and that readers are properly tested and tuned to provide optimal performance. In order to maximize performance, the PIV Card needs to be held correctly within the reader's magnetic field. So, departments and agencies should provide information to their cardholders on the proper way to present their cards to the readers. Placing an image on the reader depicting the proper orientation of the card may also be helpful. Preregistration of PIV Cards can help to speed up many of the steps in the PKI-CAK authentication mechanism. If the card's Card Authentication certificate was obtained during the preregistration process then it doesn't need to be read from the card at the time of authentication. 23 Instead, the reader can obtain an identifier from the card (e.g., by reading the initial portion of the CHUID and extracting the FASC-N, Card UUD, or Cardholder UUID) and can then use the identifier to look up the certificate in the local cache. In addition, status information for the Card Authentication certificate may be obtained from a caching status proxy rather than performing certificate validation at the time of authentication.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Guidelines for the Use of PIV Credentials in Facility Access."}]}
{"id": "nist_00985", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Digital Identity Guidelines_ Identity Proofing and Enrollment provide? (Section 126) haustive list of types of identity evidence grouped by strength. Fair Evidence Examples A.1. The qualities and features of the different types of FAIR evidence vary based on how they are implemented. CSPs must evaluate and document the evidence types that it will accept based on the requirements provided in these guidelines. Table 4.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Digital Identity Guidelines_ Identity Proofing and Enrollment."}]}
{"id": "nist_00986", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications provide? (Section 42) and 15. The Random Excursions Variant Test. This section (Section 2) consists of 15 subsections, one subsection for each test. Each subsection provides a high level description of the particular test. The corresponding subsections in Section 3 provide the technical details for each test. Section 4 provides a discussion of testing strategy and the interpretation of test results. The order of the application of the tests in the test suite is arbitrary. However, it is recommended that the Frequency test be run first, since this supplies the most basic evidence for the existence of non-randomness in a sequence, specifically, non-uniformity. If this test fails, the likelihood of other tests failing is high. (Note: The most time-consuming statistical test is the Linear Complexity test; see Sections 2.10 and 3.10). Section 5 provides a user's guide for setting up and running the tests, and a discussion on program layout. The statistical package includes source code and sample data sets. The test code was developed in ANSI C. Some inputs are assumed to be global values rather than calling parameters. A number of tests in the test suite have the standard normal and the chi-square ( \u03c7 2 ) as reference distributions. If the sequence under test is in fact non-random, the calculated test statistic will fall in extreme regions of the reference distribution. The standard normal distribution (i.e., the bell-shaped curve) is used to compare the value of the test statistic obtained from the RNG with the expected value of the statistic under the assumption of randomness. The test statistic for the standard normal distribution is of the form z = (x \u00b5 )/ \u03c3 , where x is the sample test statistic value, and \u00b5 and \u03c3 2 are the expected value and the variance of the test statistic. The \u03c7 2 distribution (i.e., a left skewed curve) is used to compare the goodness-of-fit of the observed frequencies of a sample measure to the corresponding expected frequencies of the hypothesized distribution.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications."}]}
{"id": "nist_00987", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Audit and Evaluation of Computer Security provide? (Section 125) m. process of aggregation hierarchically until all microscopic levels of control adequacy on the (lowest) line item level have been trans- lated into macroscopic parameters on higher subsystem levels. It is perfectly conceivable, even at this very preliminary stage of the investigation, that a \"standard\" scale for system security may even- tually evolve from the crude beginnings postulated here. These criti- 6-19 I I 1 I 1 1 1 1 I I \u2014 \u2014 1 1 CQ >-O< C_)o QC ZD ce: t\u2014 o 2:oo 00 00 LUOo =3: CD O O) +->c CDO cn 4-> Q. E oo OJ cn cu o cn OJ +-> (/) >. CD n3 S- CD o s- Q_ i- OJ CO 4-5 =3 o a. s- n3 OJ Ci3 X OJ o I o CD I O I I CM I O O o I\u2014 I\u2014 d: oo \u2014I o O _l Q_o cc: 00 I\u2014 h- ^ 2r 0003:0 O LU O HH t\u2014 o I\u2014 LU 00 \u2014I C_) h- <C \u2022-\" LU Q. 00 ^ S O ZD Q. s: d; o 00 s: UJ ca; I\u2014t o Q. CQ Q o H-i Q. E o cu o cn_j CD r\u2014 >- O I\u2014 C_) I\u2014 ^ CQO cC O Q::O =) \u20141 CO 00 O oo LU o cc: I t t 1^0 I 000^ i I 1010 CM CM O I\u2014 I CM CVJ CM I I\u2014 CM I 00 2: 00 q; I\u2014 LU O O 00 o q; <C u-1 I\u2014 LU cc: ^ S C3i o oo >- o 00 1\u20141 s 00 q; o LU CD O LU h- <_> I\u2014 o< ^ LU < 2: Q^ < LU C!3 o h- o q: cc cn I\u2014I Q_ LU a: cx: I T3 N CD CD > LO \u20221 13 +J -l-> \u2022r\u2014 z: +-) fO cu S- 3 CD 2: +-> o cc LU Q_ 00 o 2: OO Q. O _l 00 1\u2014 1\u2014I LU H- < q; <o [\u2014 LU 1\u2014 CC ^ Q I\u2014I 2: =) cC O <C Ll_ O CD 'q. +-> t\u2014 00 CD 2: 0 -\u00bb-> 1\u2014 0 [\u2014 E X 1\u2014 <D 1\u2014 LU CC M CC s: 1\u2014 =c 1\u2014 in > 00 CC < LU 0 00 0 u_ 00 a: LU 1\u2014 0 0 CC AT EE 0 EM <: C_) cc: LU 1\u2014 cc _J 0 Q_ 00 LU Cl_ LU >- >- 00 D_ Q 1\u2014 00 =) < U_ 00 LU CO ct: LU Z3 CC Q =3 LUQ O LU OO QCO CL. Ct: OO 00 LU 00 C_) LU OO <C eC LUo c_> LU cC 00 LU 00 cc LU ZD cc: Q 00 =3 LU LU Q O q; LU o ZD o cc: Q O Q. LU ccO Q_ H- o LU Cc: D- LU 2: LU LU a. LU CQ :r D.^ oo \u2014I 00 LU cc > LU LU D. Q CD a CD CJ > \u2022r- S- > cu S- 00 (D 00 > M- \u2022r\u2014 0 ^- cn +-> 0 cu LO fO +-> <+- ^- 0 cu 0 u cu ^ CL 0 1 Q 1\u2014 00 _l 1/1 No AT LU LU Q- CC >- zr I\u2014 f\u2014 I\u2014I C_) ei: _J LU 00 a.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Audit and Evaluation of Computer Security."}]}
{"id": "nist_00988", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Status Report on the Second Round of the SHA-3 Cryptographic Hash Algorithm Competition provide? (Section 7) ......................................................................................9 ................................................................................................................ | | | 4.3 CubeHash | 9 | | | 4.3.1 Security | 10 | | | 4.3.2 | ....................................................................................................... Performance................................................................................................ 11 | | | 4.3.3 | Discussion................................................................................................... 12 | | | 4.4 ECHO.....................................................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Second Round of the SHA-3 Cryptographic Hash Algorithm Competition."}]}
{"id": "nist_00989", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NSTIC Pilots_ Catalyzing the Identity Ecosystem say about 5.1. Acronyms? According to NSTIC Pilots_ Catalyzing the Identity Ecosystem, 5.1. Acronyms: AAAE American Association of Airport Executives AAMVA The American Association of Motor Vehicle Administrators ACT-IAC American Council for Technology - Industry Advisory Council AP Attribute provider AXN Attribute Exchange Network COI Community of interest COPPA Children's Online Privacy Protection Act COTS Commercial off the shelf CSDII The Cross Sector Digital Identity Initiative CSP Credential Service Provider DHS Department of Homeland Security DMV Department of Motor Vehicles FFO Federal funding opportunity FICAM Federal Identity and Access Management FIPS Federal information processing standards FNS Food and Nutrition Services FTC Federal Trade Commission FY Fiscal Year GP Guiding Principles GSA General Services Administration GTRI Georgia Tech Research Institute IDESG Identity Ecosystem Steering Group IDEF Identity Ecosystem Framework IdP Identity provider ITL Information Technology Laboratory KBA Knowledge-based authentication LoA Level of assurance MFA Multi-factor authentication NCRIC Northern California Regional Intelligence Center NIEF National Identity Exchange Federation NIST National Institute of Standards and Technology NSTIC National Strategy for Trusted Identities in Cyberspace NPO National Program Office OIDC OpenID Connect OMB Office of Management and Budget PDS Personal Data Store PIV Personal Identity Verification PKI Public key infrastructure PRIVO Privacy Vaults Online RNS Resilient Network Systems", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, mfa. Contains security framework guidance for authentication systems. Source: NSTIC Pilots_ Catalyzing the Identity Ecosystem."}]}
{"id": "nist_00990", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Supporting Roles according to NIST_SP_800-37r2_Risk_Management_Framework? Supporting Roles: System Owner or Common Control Provider; Information Owner or Steward; System Security Officer; System Privacy Officer; Senior Agency Information Security Officer; Senior Agency Official for Privacy.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_00991", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Identity and Access Management for Electric Utilities say about Java Application? (Part 55) According to Identity and Access Management for Electric Utilities, Java Application: Reconciliation for: Users e. Reconciliation Type: Incremental Reconciliation f. Reconciliation Triggers: AlertDbConnectorTrigger g. Select the schedule as Immediate, Once, Periodically, or Advance. For Periodically, specify the Start At, End At, and Rerun every (duration of job frequency, which should be no less than every 2 minutes). T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . NIST SP 1800-2C: Identity and Access Management for Electric Utilities 220 Figure 9-47 Guardian Reconciliation Job T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . Click Save. 10 PACS Server: RS2 Access It! Universal Server Installation The Access It! Universal RS2 Technologies PACS Server is installed on the PACS Network to help control physical access to simulated facilities, rooms, etc. RS2 Technologies cards and card readers were also included in both builds. The RS2 Technologies PACS Server is installed on a VM that is running the Windows Server 2012 R2 OS. . 10.1 Security Characteristics Cybersecurity Framework Categories: PR.AC-2: Physical access to assets is managed and protected. NIST SP 800-53 Revision 4 Security Controls: PE-2, PE-3, PE-4, PE-5, PE-6, PE-9 NIST SP 1800-2C: Identity and Access Management for Electric Utilities 221 10.2 System Environment The system for the PACS-Console Server configured by the NCCoE contains the following configuration settings and environmental constraints: \uf0a7 Windows Server 2012 R2 \uf0a7 VM with CPU Quad Core 2.199 GHz \uf0a7 VM with 8,192 MB of memory \uf0a7 virtual hard disk containing 240 GB of storage 10.3 AIUNIVERSAL Installation T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_00992", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Analysis of First Responder Mobile and Wearable Devices say about Description? According to Security Analysis of First Responder Mobile and Wearable Devices, Description: A police officer selects a device from a charging station. Although this device is different from the device the officer used yesterday, the officer proceeds to log into the device. After login, the device is automatically configured with the officer's Quality of Service, Priority, and Preemption (QPP) information, and public safety mobile applications are configured with the appropriate settings.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Analysis of First Responder Mobile and Wearable Devices."}]}
{"id": "nist_00993", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Security and Privacy in Public Cloud Computing say about Abstract? According to Guidelines on Security and Privacy in Public Cloud Computing, Abstract: Cloud computing can and does mean different things to different people. The common characteristics most interpretations share are on-demand scalability of highly available and reliable pooled computing resources, secure access to metered services from nearly anywhere, and displacement of data and services from inside to outside the organization. While aspects of these characteristics have been realized to a certain extent, cloud computing remains a work in progress. This publication provides an overview of the security and privacy challenges pertinent to public cloud computing and points out considerations organizations should take when outsourcing data, applications, and infrastructure to a public cloud environment. Keywords: Cloud Computing; Computer Security and Privacy; Information Technology Outsourcing", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Security and Privacy in Public Cloud Computing."}]}
{"id": "nist_00994", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.3 WHERE WERE THESE EVENTS TAKING PLACE? according to NIST Report_ Authentication Diary Study According to Report_ Authentication Diary Study, 4.3 WHERE WERE THESE EVENTS TAKING PLACE?: For each authentication event recorded, participants were asked to record whether they were on or off the NIST campus at the time of the event. Figure 5 shows the number of events recorded by each participant, while distinguishing the location (i.e., whether they were on- or off-campus). Figure 5: Participants' authentication events by location <!-- image --> Table 2 provides a delineation of all participants' authentication events by location (oncampus or off-campus) and type (work-related or personal). It should be noted that authentication events recorded on the NIST campus were not always work-related; likewise, not all events that were recorded off-campus were personal. Table 2: Authentication events by location and type | | Event Type | Event Type | | |----------------|--------------|--------------|-----------| | Event Location | Personal | Work-related | All Types | | NIST | 26 | 359 | 385 | | Off-campus | 63 | 80 | 143 | | All Locations | 89 | 439 | 528 | Additionally, the data show that 72.92% of the recorded authentication events took place on-campus, while 27.08% took place off-campus. This is to be expected, given that most of our participants worked on-campus during the diary day. Two participants were telecommuting at the time of the study, and one was on work-related travel.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report_ Authentication Diary Study."}]}
{"id": "nist_00995", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Labels for Open Systems_ an Invitational Workshop say about Advantages? According to Security Labels for Open Systems_ an Invitational Workshop, Advantages: - The passport can be distributively administered - The simplest form can be quickly established because it only contains ID and authentication information, requiring no lengthy and controversial negotiations on meanings of privileges. Most countries in the world agree, regardless of their politics or ideologies, on use of passports. - Use of visas allow privileges to be included in passports to simplify border decisions. - The token should be small enough to be included as a label in every PDU that directly or vicariously represents a user. - The privilege information can be locally held at destinations of service/access requests instead of at origins, simplifying administration at each domain and reducing trust negotiations among domains. - The same credentials (passport, token) can be used at convenient intervening checkpoints (security interfaces between major components) such as between a workstation application and its communications system (airport passport check), at the entrance to and exit from a network, at the entrance to a host or other network, at the application within a host or server. This reduces the amount of credential information carried by the PDUs and increases useable communication bandwidth. - The passport applies the benefits of an already-working solution that has stood the test of time in world diplomacy to distributed systems security.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Security Labels for Open Systems_ an Invitational Workshop."}]}
{"id": "nist_00996", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 1143) issemina\ue000on of security alerts and advisories]. T h i s p u b l i c a \ue000 o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h \ue003 p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P. 8 0 0 - 5 3 A r 5 CHAPTER FOUR PAGE 625 Reference produced from open data h\ue003ps://github.com/usnistgov/oscal-content T h i s p u b l i c a \ue000 o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h \ue003 p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P. 8 0 0 - 5 3 A r 5 NIST SP 800-53A, REV. 5 ASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS SI-06 SECURITY AND PRIVACY FUNCTION VERIFICATION ASSESSMENT OBJECTIVE: Determine if: SI-06_ODP[01] security func\ue000ons to be veri\ufb01ed for correct opera\ue000on are de\ufb01ned; SI-06_ODP[02] privacy func\ue000ons to be veri\ufb01ed for correct opera\ue000on are de\ufb01ned; SI-06_ODP[03] SI-06_ODP[04] SI-06_ODP[05] SI-06_ODP[06] SI-06_ODP[07] SI-06_ODP[08] SI-06a.[01] SI-06a.[02] SI-06b.[01] SI-06b.[02] SI-06c.[01] SI-06c.[02] SI-06d.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_00997", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain INTRUSION DETECTION according to NIST U.S. Department of Energy Risk Assessment Methodology According to U.S. Department of Energy Risk Assessment Methodology, INTRUSION DETECTION: - CCTV - Alarms - -Balanced magnetic switches - Motion - -Volumetric - -Infrared", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: U.S. Department of Energy Risk Assessment Methodology."}]}
{"id": "nist_00998", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Attribute Metadata_ A Proposed Schema for Evaluating Federated Attributes provide? (Section 37) hould not be confused with the concept of a Derived pedigree, which focuses on generating the attribute's value rather than verifying it. 6. Not Verified - The attribute's value has not been verified. Table 8 - Currency Metadata | Metadata Element | Description | Recommended Values | |--------------------|----------------------------------------------------------------------------------------------------------------------|----------------------| | Last Verification | The date and time when the attribute value was last verified as being true and belonging to the specified individual | No restrictions | | Last Refresh | The date and time when the attribute was last refreshed | No restrictions | | Metadata Element | Description | Recommended Values | |--------------------|--------------------------------------------------|----------------------| | Expiration Date | The date an attribute's value is no longer valid | No restrictions | RPs may not trust certain attribute values unless they have been verified within a certain time period. This is particularly true for certain values associated with attributes such as Role or Security Clearance , where the original established date of the value alone may not be sufficient for granting access to national security systems or data. Last Verification provides the most recent date and time at which the value was verified as true and belonging to the specified individual. This metadata provides only the last date that verification occurred, and does not include any information about method of verification. Last Refresh contains information on the date and time when an attribute's value was last refreshed. The age of the attribute can be derived from this attribute value.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: security clearance, national security. Contains guidance on protecting sensitive government information. Source: Attribute Metadata_ A Proposed Schema for Evaluating Federated Attributes."}]}
{"id": "nist_00999", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report) say about PAGE? (Part 2) 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), PAGE: | . | . | . . | III-17 | | III-13 | Physical/Environmental Protection-GADPS | | . | . | . | III-17 | | III-14 | Controls-GADPS | | | | | III-17 | | III-15 | Production, I/O Emergency, Backup, and Cont. Planning-GADPS | | | | | III-18 | | III-16 | Software and Maintenance-GADPS | . | . | . | . | III-18 | | III-17 | System Security Awareness and Training-GADPS | . | . | . | . | III-18 | | III-18 III-19 | Authorization and Access Controls-GADPS Audit Trail Mechanisms-GADPS | | . . | . . | . . | III-19 III-19 | | III-20 | Confidentiality Controls-GADPS | | | | | III-19 | | III-21 | Integrity Controls-GADPS | | | | | III-20 | | III-22 | User | Identification/Authorization-GADPS | . | . | . | III-20 | | III-23 | Assignment Security Responsibility-MAS | | | . | . | III-22 | | III-24 | Personnel Screening-MAS . | . | | . | .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)."}]}
{"id": "nist_01000", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6.23.1 Security Benefit according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance, 6.23.1 Security Benefit: Incident management tools enable manufacturers to minimize downtimes due to incidents and increase the efficiency and productivity of the manufacturing system. Information gained during incident handling can be used to better prepare for handling any future incident. Incident response plans enable organizations to act proactively before an incident or immediately after an incident is noticed to limit the impact from incidents.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance."}]}
{"id": "nist_01001", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Manageability is an important system property enabling several of the FIPPs according to An Introduction to Privacy Engineering and Risk Management in Federal Systems? Manageability is an important system property enabling several of the FIPPs: access and amendment; accountability; minimization; quality and integrity; and individual participation. If agencies cannot administer individuals' information with sufficient granularity, they cannot be confident that inaccurate information can be identified and corrected, obsolete information is disposed of, only necessary information is collected or disclosed, and that individuals' privacy preferences about uses of their information are implemented and maintained.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: An Introduction to Privacy Engineering and Risk Management in Federal Systems."}]}
{"id": "nist_01002", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Report on the Privilege (Access) Management Workshop say about Summary? (Part 2) According to A Report on the Privilege (Access) Management Workshop, Summary: facilitate integration of products from various vendors. Existing definitions serve the purpose of effective discourse, but there is currently no generally accepted definition of privilege management. This report uses a definition of privilege management 15 that aligns with the draft definition of privilege management made by the Identity, Credential, and Access Management (ICAM) Subcommittee of the Federal Information Security &amp; Identity Management Committee. The eXtensible Access Control Markup Language (XACML), an OASIS standard for managing access control policy, provides some of what is needed to support enterprise-level privilege management. Also needed are capabilities for creation and maintenance of policy, policy enforcement, attribute collection, maintenance, and retrieval, and definition of resource attributes. In the area of access control methods, this report concludes that a formal standardized definition of attribute-based access control (ABAC) is needed. Although there has been much socialization of the term ABAC, there are still many variations in its description. Toward the end of standardizing its meaning, a definition of ABAC was offered as a starting point. There are three access control methods that are clearly distinguishable from one another: identity-based access control (IBAC), role-based access control (RBAC), and attribute-based access control (ABAC). Although policy-based access control (PBAC) does not need to be considered a separate access control method, the ideas associated with views of it make it clear 15 Privilege management is the definition and management of attributes and policies that are used to decide whether a user's request for access to some resource should be granted. that full realization of ABAC's potential requires better attribute and policy management capabilities at the enterprise level.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, identity management, sso. Contains security framework guidance for authentication systems. Source: A Report on the Privilege (Access) Management Workshop."}]}
{"id": "nist_01003", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Subject Public Key Info according to NIST Test Personal Identity Verification (PIV) Cards Version 2? Subject Public Key Info: rsaEncryption, 2048-bit modulus, e=65537", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_01004", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations say about REFERENCES? According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, REFERENCES: Source Control: MA-05 Supporting Publications: None", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_01005", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Computer Security Log Management say about 5.2.3 Comparing System-Level and Infrastructure-Level Analysis? (Part 1) According to Guide to Computer Security Log Management, 5.2.3 Comparing System-Level and Infrastructure-Level Analysis: 5.2.3 Comparing System-Level and Infrastructure-Level Analysis Analysis is typically very similar for system-level and infrastructure administrators. The main difference is that for infrastructure administrators, log analysis is often a primary responsibility, whereas for systemlevel administrators it is often a secondary responsibility, particularly if the infrastructure administrators are reviewing the most important log entries from systems. In such an arrangement, infrastructure administrators typically perform log analysis on an ongoing basis each day, and system-level administrators perform periodic reviews (e.g., daily, weekly) commensurate with the criticality of each system and its information. Also, infrastructure administrators might have access to more sophisticated tools than system-level administrators do because it is cost-prohibitive to have them available for all systems. Regardless of how much analysis is performed at the infrastructure level, system-level administrators usually need to perform analysis for the following types of entries: - GLYPH&lt;c=31,font=/APONEK+Webdings&gt; Entries that are of interest or importance at the system level but are not forwarded to the infrastructure because of their relative priority - GLYPH&lt;c=31,font=/APONEK+Webdings&gt; Entries for log sources that cannot automatically participate in the infrastructure (e.g., unusual proprietary formats, standalone systems, legacy systems, appliances) - GLYPH&lt;c=31,font=/APONEK+Webdings&gt; Entries that cannot be understood without context that is only available at the system level. System-level administrators can usually perform their reviews and analysis using a variety of tools and techniques. On some systems, particularly those with many log sources, it is effective to establish a local log infrastructure and store the data from all of the system's log sources there.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Computer Security Log Management."}]}
{"id": "nist_01006", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Electronic Health Records on Mobile Devices provide? (Section 98) thentication No internal or external identity source is required for the EAP-TLS certificate-based authentication method because the identity is validated based on the trusted certificate in the PKI. However, you must set up the Certificate Authentication Profile in the ISE as the external identity source. Instead of authenticating via the traditional username and password, Cisco ISE compares a certificate received from a client with one in the server to verify the authenticity of a user or device. Note that although internal or external identity sources are not needed for TLS authentication, internal or external identity sources can be added and used for authorization of a policy condition, if desired. To create a Certificate Authentication Profile: 1. Use the Administration Portal to navigate to the path Administration > Identity Management > External Identity Sources > Certificate Authentication Profile and click Add. NIST SP 1800-1C: Securing Electronic Health Records on Mobile Devices 27 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 1 . . 2. Fill out the form with proper parameters. Be sure to select the Subject Name as the Principal Username X509 attribute because it is the field that will be used to validate the authenticity of the client. 7.3.5 Set Authentication Protocols Cisco ISE uses authentication protocols to communicate with external identity sources. Cisco ISE supports many authentication protocols, such as the Password Authentication Protocol, Protected Extensible Authentication Protocol, and the EAP-TLS. For this build, we used the EAP-TLS protocol for user and machine authentication. To specify the allowed protocols services in Cisco ISE: 1. From the Administration Portal, navigate to the path Policy > Policy Elements > Results > Authentication > Allowed Protocols > Add. 2.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, identity management. Contains security framework guidance for authentication systems. Source: Securing Electronic Health Records on Mobile Devices."}]}
{"id": "nist_01007", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Developing Security Plans for Federal Information Systems say about COMMON TERMS AND DEFINITIONS? (Part 5) According to Guide for Developing Security Plans for Federal Information Systems, COMMON TERMS AND DEFINITIONS: commended controls in the low, moderate, or high baselines described in NIST SP 800-53, that provide equivalent or comparable protection for an information system. | | Confidentiality [44 U.S.C., Sec. 3542] | Preserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information. | 32 | Configuration Control [CNSS Inst. 4009] | Process for controlling modifications to hardware, firmware, software, and documentation to ensure that the information system is protected against improper modifications before, during, and after system implementation. | |-----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Countermeasures [CNSS Inst. 4009] | Actions, devices, procedures, techniques, or other measures that reduce the vulnerability of an information system. Synonymous with security controls and safeguards. | | Executive Agency [41 U.S.C., Sec. 403] | An executive department specified in 5 U.S.C., Sec. 101; a military department specified in 5 U.S.C., Sec. 102; an independent establishment as defined in 5 U.S.C., Sec. 104(1); and a wholly owned Government corporation fully subject to the provisions of 31 U.S.C., Chapter 91. | | Federal Enterprise Architecture [FEA Program Management | A business-based framework for government-wide improvement developed by the Office of Management and Budget that is intended to facilitate efforts to transform the federal government to one that is citizen-centered, results-oriented, and market-based. | | Federal Information System [40 U.S.C., Sec.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Guide for Developing Security Plans for Federal Information Systems."}]}
{"id": "nist_01008", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches say about 5.3.1 User Login with Multifactor Authentication? (Part 1) According to Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches, 5.3.1 User Login with Multifactor Authentication: 5.3.1 User Login with Multifactor Authentication Phishing-resistant multifactor authentication is a security best practice. The architecture recommends the use of a password, pin (personal identification number) or biometric with an asymmetric cryptographic key for authentication. However, it is common practice for organizations to offer a variety of MFA solutions. This can include user-owned mobile devices, which may impact privacy risk [17]. Figure 5-1 Multifactor Authentication Data Flow Diagram <!-- image --> Table 5-8 User Login with Multifactor Authentication Data Actions | Data Type | Data Action | Privacy Impact | |---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Username | Username is stored by the user workstation and transferred across the authentication process to help identify the trans- action. | Usernames potentially contain inferable PII such as user's first and last names. | | Client IP Ad- dress | The client IP (Internet Protocol) address is stored by the user workstation, and transferred as part of communica- tions where it is an endpoint.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, mfa. Contains security framework guidance for authentication systems. Source: Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches."}]}
{"id": "nist_01009", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N say about &lt;Policy PolicyId = 'Policy 1' rule-combining-algorithm='permit-overrides'&gt;? (Part 1) According to A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N, &lt;Policy PolicyId = 'Policy 1' rule-combining-algorithm='permit-overrides'&gt;: &lt;Policy PolicyId = 'Policy 1' rule-combining-algorithm='permit-overrides'&gt; ``` // Doctor Access to Medical Records // <Target> /* :Attribute-Category :Attribute ID :Attribute Value */ :access-subject :Role :doctor :access-subject :Role :intern :resource :Resource-id :medical-records :action :Action-id :read :action :Action-id :write </Target> <Rule RuleId = 'Rule 1' Effect='Deny'> <Condition> ``` ``` Function: string-not-equal ``` ``` /* :Attribute-Category :Attribute ID */ :access-subject :WardAssignment :resource :WardLocation </Condition> </Rule> <Rule RuleId = 'Rule 2' Effect='Deny'> <Condition> Function: and Function: string-equal /* :Attribute-Category :Attribute ID :Attribute Value */ :access-subject :Role :intern Function: string-equal /* :Attribute-Category : Attribute ID :Attribute Value */ :action :Action-id :write </Condition> </Rule> <Rule RuleId = 'Rule 3' Effect='Permit'> <Condition> Function: and Function: string-equal /* :Attribute-Category :Attribute ID :Attribute Value */ :access-subject :Role :doctor Function: string-equal /* :Attribute-Category :Attribute ID :Attribute Value */ :resource :PatientStatus :critical </Condition> </Rule> </Policy> ``` Together policies (PolicySets and Policies) and attribute assignments define the authorization state. Table 1 defines the authorization state for Policy 1 by specifying attribute names and values.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N."}]}
{"id": "nist_01010", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Section 83) R1: Allow incident handlers to manually select and perform containment actions instead of or in addition to automated | |---------------|-------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | RS.MI-02 | Incidents are eradicated | High | containment measures.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: csf, fips, security control. General security reference material without sensitive content. Source: Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile."}]}
{"id": "nist_01011", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PS-15413 in Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations? (Part 173) Control PS-15413: prise's information sharing policy. The C-SCRM PMO can help identify C-SCRM stakeholders to include in threat information sharing, as well as potential sources of information for supply chain threats. Level(s): 1, 2 ## PM-17 PROTECTING CONTROLLED UNCLASSIFIED INFORMATION ON EXTERNAL SYSTEMS Supplemental C-SCRM Guidance: The policy and procedures for controlled unclassified information (CUI) on external systems should include protecting relevant supply chain information. Conversely, it should include protecting agency information that resides in external systems because such external systems are part of the agency supply chain. Level(s): 2 ## PM-18 PRIVACY PROGRAM PLAN Supplemental C-SCRM Guidance: The privacy program plan should include C-SCRM. Enterprises should require their prime contractors to implement this control and flow down this requirement to relevant sub-tier contractors. Level(s): 1, 2 ## PM-19 PRIVACY PROGRAM LEADERSHIP ROLE Supplemental C-SCRM Guidance: The privacy program leadership role should be included as a stakeholder in applicable C-SCRM initiatives and activities. Level(s): 1 ## PM-20 DISSEMINATION OF PRIVACY PROGRAM INFORMATION Supplemental C-SCRM Guidance: The dissemination of privacy program information should be protected from cybersecurity risks throughout the supply chain. Level(s): 1, 2 ## PM-21 ACCOUNTING OF DISCLOSURES Supplemental C-SCRM Guidance: An accounting of disclosures should be protected from cybersecurity risks throughout the supply chain. Level(s): 1, 2 ## PM-22 PERSONALLY IDENTIFIABLE INFORMATION QUALITY MANAGEMENT Supplemental C-SCRM Guidance: Personally identifiable information (PII) quality management should take into account and manage cybersecurity risks related to PII throughout the supply chain.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_01012", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Cybersecurity Framework Version 1.1 Manufacturing Profile? (Part 57) Control AM-1: to each verified user, device, and process interacting with the manufacturing systems. Ensure credentials are authenticated and the unique identifiers are captured when performing system interactions. | IA-5 | | PROTECT | Identity Management, Authentication and Access Control (PR.AC) | PR.AC-7 | Low Impact | | | PROTECT | Identity Management, Authentication and Access Control (PR.AC) | PR.AC-7 | Perform a risk assessment on manufacturing user transactions to document and implement the authentication mechanisms required (e.g. single- or multi-factor) for each transaction.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, identity management. Contains security framework guidance for authentication systems. Source: Cybersecurity Framework Version 1.1 Manufacturing Profile."}]}
{"id": "nist_01013", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Gema Howell according to Guidelines for Managing the Security of Mobile Devices in the Enterprise? Gema Howell: 0000-0002-0428-5045 Murugiah Souppaya: 0000-0002-8055-8527", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Managing the Security of Mobile Devices in the Enterprise."}]}
{"id": "nist_01014", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to NIST_SP_800-53r5_Security_Privacy_Controls? Discussion: Hardware integrity verification allows organizations to detect unauthorized", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01015", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2005 Annual Report say about e-AUTHENTICATION? (Part 1) According to Computer Security Division 2005 Annual Report, e-AUTHENTICATION: e-AUTHENTICATION T he Office of Management and Budget (OMB) has identified the remote identification of users, or e-authentication, as a crosscutting impediment to the provision of Internetbased government services. To fully realize the benefits of electronic government, government agencies require e-authentication policies and corresponding technical guidance tailored to the protection of government systems and data. This project establishes a policy structure for eauthentication within the U.S. government, promoting consistent implementation of eauthentication across Federal agencies. This consistency will in turn help to enhance government efficiency by securing electronic processes needed to conduct more transactions through egovernment applications. OMB released memorandum M-04-04, EAuthentication Guidance for Federal Agencies , in December 2003. This OMB policy <!-- image --> memorandum defined four levels of authentication - Levels 1 to 4 - in terms of the assurance that an asserted identity is valid. The OMB guidance requires agencies to perform a risk assessment to determine the appropriate authentication level for an application based on the likely consequences of an authentication error. This means a system using Level 4 authentication - a system that allows a user access to more sensitive, personal information for example - has a much higher assurance that a user's identity is what it is claimed it to be. After completing a risk assessment and mapping the identified risks to the required assurance level, OMB guidance directs agencies to identify and implement appropriate authentication mechanisms based on NIST technical guidance. In 2004, our e-authentication technical guidance was published as SP 800-63, Recommendation for Electronic Authentication .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Computer Security Division 2005 Annual Report."}]}
{"id": "nist_01016", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AU-8 in Guidelines for Smart Grid Cybersecurity? Control AU-8: Time Stamps 2.16.8 Time Stamps CIP 007-3a (R5.1.2, R6.3) SG.AU-9 Protection of Audit Information", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01017", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Report on Lightweight Cryptography provide? (Section 39) oe, C., PRESENT: An Ultra-Lightweight Block Cipher . Proc. 9th International Workshop on Cryptographic Hardware and Embedded Systems (CHES 2007), Vienna, Austria, September 10-13, 2007, LNCS 4727, pp. 450-466, - [10] Borghoff, J., Canteaut, A., G\u00fcneysu, T., Kavun, E.B., Knezevic, M., Knudsen, L.R., Leander, G., Nikov, V., Paar, C., Rechberger, C., Rombouts, P., Thomsen, S.S., and Yal\u00e7\u0131n, T., PRINCE - A Low-Latency Block Cipher for Pervasive Computing Applications . Proc. 18th International Conference on the Theory and Application of Cryptology and Information Security (ASIACRYPT 2012), Beijing, China, December 2-6, 2012, LNCS 7658, pp. 208-225, - [11] Chen, L., Recommendation for Key Derivation through Extraction-then-Expansion , NIST Special Publication (SP) 800-56C, National Institute of Standards and Technology, Gaithersburg, Maryland, November 2011, https://doi.org/10.6028/NIST.SP.800-56C - [12] Chen, L., Recommendation for Key Derivation Using Pseudorandom Functions (Revised) , NIST Special Publication (SP) 800-108, National Institute of Standards and Technology, Gaithersburg, Maryland, October 2009, https://doi.org/10.6028/NIST.SP.800-108 - [13] Cryptographic Research and Evaluation Committees, http://www.cryptrec.go.jp/english/ [accessed August 11, 2016] - [14] Cryptographic Research and Evaluation Committees, CRYPTREC Report 2014 , Report of the Cryptographic Technology Evaluation Committee, 296 pages, March 2015, - [15] Dang, Q., Recommendation for Existing Application-Specific Key Derivation Functions , NIST Special Publication (SP) 800-135 Revision 1, National Institute of Standards and Technology, Gaithersburg, Maryland, December 2011, - [16] De Canni\u00e8re, C., and Preneel, B., Trivium : 'New Stream Cipher Designs - The eSTREAM Finalists' (Springer, 2008), LNCS 4986, pp.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Report on Lightweight Cryptography."}]}
{"id": "nist_01018", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings? (Part 99) Control PD-12: , D. Engert, I. Foster, C. Kesselman, S. Tuecke, J. Volmer, an d V. Welch, 'A National-Scale Authentication Infrastructure,' IEEE Computer , 33(12):60 66, December 2000. Doster, W., M. Watts, and D. Hyde, 'The KX.509 Protocol,' U niversity of Michigan, Ann Arbor, MI, 2001 (. citi.umich.edu/techreports/reports/citi-tr-01 2.pdf). Foster, I., and C. Kesselman, 'Globus: A Metacom puting Infrastructure Toolkit.' Intl J. Supercomputer Applications , 11(2):115128, 1997. Heimdal Kerberos Implementation (http:// www.pdc.kth.se/heimdal/), October 5, 2006. Komar, B., 'Microsoft Windows Server 2003 PKI and Certificate Security,' Microsoft PKI Team, Microsoft Press, Redmond, WA, 2004. Microsoft Corporation, '2821A: Design ing and Managing a Micros oft Windows Public Key Infrastructure,' Microsoft Official Curriculum 2821A, Redmond, WA, 2003. Neuman, B.C., and T. Ts'o, 'Kerberos: An Authentication Service for Computer Networks,' IEEE Communications , 32(9):33-38, September 1994. Open Smart Card Project ( . opensc-project.org/), October 5, 2006. RSA Laboratories, PKCS #11 v2.20: Cryptographic Token Interface Standar d , Bedford, MA, June 2004. Sun Documentation (http://docs.sun.com/, http://docs.sun.com/app/do cs/prod/entsys.05 q4#hic). Sun Java Enterprise Server 2005Q4, (.sun.com/software/javaenterpris esystem/index.xml). U.S. Department of Homeland Security, Homeland Security Presidential Directive (HSPD-12): Policy for a Common Identification Standard for Federal Employees and Contractors (. whitehouse.gov/news/releases/2004/08/2004 0827-8.html), August 27, 2004. Zhu, L., and B. Tung, RFC 4556 Public Key Cryptography for Initial Authent ication in Kerberos (PKINIT) , The Internet Society, June 2006. ## 6th Annual PKI R&amp;D Workshop - Proceedings 1 Microsoft offers both Standard Certificate Services and Enterprise Certificate Services.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, token. Contains security framework guidance for authentication systems. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_01019", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation provide? (Section 265) 0 - Configure the RUT with the VCs by using the following file: - Verify that the RUT received all VRPs in the RPKI database coming from Cache s 1 and 2. - The RUT receives Update 10.100.0.0/16 65510. - Verify that the RUT received the update from Step 6 and validated it as valid . - The RUT receives Update 10.100.0.0/16 65511. - Verify that the RUT received the update from Step 8 and validated it as invalid . - Shut down Cache 1. - Verify that the validation state of both updates did not change. <!-- image --> Each of the expected results in Steps 1, 4, 6, 8, and 10 above will be verified. Results were as expected. The vendor implementations act differently, mainly controlled by their configurations. This means that one implementation identified the loss of the cache faster than the other. We determined that the router that kept data longer cleared stale data after a configured time span between one minute and one hour. Test SIDR Requirements CR-6.6.1 when working with IPv4/6 addresses. Show that the RUT receives and installs VRPs of two RPKI caches with a slightly different view on the RPKI into the RPKI database properly. Then, Cache 1 disappears. The testbed is configured with the topology, IP addressing scheme, and ASNs as depicted in the Testbed Architecture in Figure E-1 and Figure E-2. The RUT's cache is empty, and RPKI validator/ Caches 1 and 2 are empty. <!-- image --> | IPv4 or IPv6? | Both | Both | |-----------------|--------|--------| | Procedure | Verify | | - Connect the RUT to RPKI Cache 1 and receive three ROAs: - 10.100.0.0/16 16 65510 - 10.100.0.0/16 20 65510 - FD00::10.100.0.0/64 64 65510 - Connect the RUT to RPKI Cache 2 and receive three ROAs: - 10.100.0.0/16 16 65511 - 10.100.0.0/16 20 65511 - FD00::10.100.0.0/64 64 65511 - Configure the RUT with the VCs by using the following file: - Verify that the RUT received all VRPs in the RPKI database coming from Caches 1 and 2. - The RUT receives Update 10.100.0.0/16 65510.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_01020", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities? (Part 21) Control ES-1: tablishing an event schedule; and documenting the TT&amp;E event methodology. Section 3 briefly discusses the role of training in a TT&amp;E program and how training is related to exercises and tests. Section 4 contains information on determining the need for tabletop exercises, and designing, developing, conducting, and evaluating an exercise event. This section describes the design phase in detail, including determining the topics and scope; identifying the objectives; identifying participants and training staff; and coordinating logistics. Sections 5 and 6 contain similar information for functional exercises and tests, respectively. This document also contains several appendices. Appendices A, B, and C contain samples of the documentation associated with tabletop exercises, functional exercises, and tests, respectively. Appendix D contains a glossary, and Appendix E contains an acronym list. Appendix F identifies print and online resources that may be helpful in scoping, planning, documenting, conducting, and evaluating TT&amp;E events. Appendix G contains an index for the publication. ## 2. Establishing a Test, Training, and Exercise Program An organization's IT plans need to be maintained to sustain the organization's ability to prepare for, respond to, manage, and recover from disasters affecting its mission. 2 Common types of IT plans used for this purpose are as follows: - GLYPH&lt;c=31,font=/KKMIHL+Webdings&gt; Contingency plan: Recovering and reconstituting IT systems. 3 Contingency plans include continuity of operations plans, business continuity plans, and disaster recovery plans. - GLYPH&lt;c=31,font=/KKMIHL+Webdings&gt; Incident response plan: Reporting and managing computer security incidents. 4 The following are the major types of events used to maintain these plans: - GLYPH&lt;c=31,font=/KKMIHL+Webdings&gt; Tests.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities."}]}
{"id": "nist_01021", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Small Business Information Security_ The Fundamentals say about 1.2 Organization of this Publication? According to Small Business Information Security_ The Fundamentals, 1.2 Organization of this Publication: The rest of this publication is organized as follows: - Section 2 describes how an information security program can be implemented. - Section 3 discusses those key actions small businesses can take to develop or improve their information security and cybersecurity. - Section 4 identifies several key practices directed towards users which you can implement immediately and which will protect your system and information. - Appendix A provides a glossary of key terms and acronyms used in this publication. - Appendix B contains sources referenced throughout this publication. - Appendix C contains a description of the NIST Framework for Improving Critical Infrastructure Cybersecurity [CSF14] . - Appendix D provides worksheets useful in conducting a risk analysis. - Appendix E contains example information security policy and procedure statements.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: csf, fips, security control. General security reference material without sensitive content. Source: Small Business Information Security_ The Fundamentals."}]}
{"id": "nist_01022", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Report of the Workshop on Cryptography in Support of Computer Security provide? (Section 11) tion about its underlying structure. Tomorrow, we will break up into two working groups in order to explore in some detail two important areas of interest. The mathematics working group, headed by Dr. Howard Campaigne, will deal with the strictly mathematical aspects of the algorithm, especially from a cryptanalyt ic point of view. The applications working group, headed by Dr. Joseph Eachus, will deal with the very practical areas of key generation, usage, and distribution that are so important in the day-to-day use of an encryption scheme. Following Professor Bigelow's introduction, Dr. Ruth Davis, Director of the Institute for Computer Sciences and Technology, welcomed the participants, thanked them for their participation and outlined briefly the history of the NBS involvement with the Data Encryption Standard, the purpose of the standard and the anticipated contribution of the workshop DAVIS: It has long been recognized that a publicly available encryption technique was needed to protect data as it is stored in a computer or transmitted from one computer to another. To this end NBS has been working on a data encryption standard since 1972. The purpose of the standard is to provide a uniform technique for all Federal agencies to use. It is not intended to be universally applied wherever data is stored or transmitted within the United States. In selecting a candidate for a standard, NBS twice solicited in the Federal Register and selected the algorithm that best satisfied the requirements of a standard from among those submitted. In establishing a standard, the encryption algorithm is not left in vacuo. It will be embedded in a framework of guidelines that recommend procedures and environments in which the algorithm is used as only one part of an overall security system. We are now working on developing such guidelines.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Workshop on Cryptography in Support of Computer Security."}]}
{"id": "nist_01023", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does PIV Data Model Test Guidelines say about ibute OID = 2.16.840.1.101.3.6.6). AS07.04.09: The FASC-N shall be populated in the subjectAltName extension using the pivFASC-N attr? According to PIV Data Model Test Guidelines, ibute OID = 2.16.840.1.101.3.6.6). AS07.04.09: The FASC-N shall be populated in the subjectAltName extension using the pivFASC-N attr: VE07.04.09.01: The vendor shall specify in its documentation the inclusion of the FASC-N in the subjectAltName extension as part of the card authentication certificate profile. TE07.04.09.01: The tester shall validate the presence of the FASC-N in the subjectAltName extension in the card authentication certificate issued by the vendor.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_01024", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.1 Acceptance of the Second-Round Candidates according to NIST Status Report on the Second Round of the NIST Post-Quantum Cryptography Standardization Process According to Status Report on the Second Round of the NIST Post-Quantum Cryptography Standardization Process, 2.1 Acceptance of the Second-Round Candidates: NIST selected 26 candidate algorithms for the second round. Of the 26 candidates, 17 were keyestablishment mechanisms (KEMs) or public-key encryption schemes, while nine were digital signatures. Submission teams were allowed to make minor modifications and re-submit their packages, which had to meet the same requirements as the original submissions. Four of the candidates were mergers of first-round algorithms: LEDAcrypt (merged from LEDAkem and LEDApkc), NTRU (merged from NTRUEncrypt and NTRU-HRSS-KEM), ROLLO (merged from LAKE, LOCKER, and Ouroboros-R), and Round5 (merged from Hila5 and Round2). The complete updated specifications were posted on www.nist.gov/pqcrypto on April 10, 2019, for public review. Table 2: Second-Round Candidates | BIKE | LEDAcrypt | Rainbow | |--------------------|-------------|-------------| | Classic McEliece | LUOV | ROLLO | | CRYSTALS-DILITHIUM | MQDSS | Round5 | | CRYSTALS-KYBER | NewHope | RQC | | FALCON | NTRU | SABER | | FrodoKEM | NTRU Prime | SIKE | | GeMSS | NTS-KEM | SPHINCS+ | | HQC | Picnic | Three Bears | | LAC | qTESLA | |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Second Round of the NIST Post-Quantum Cryptography Standardization Process."}]}
{"id": "nist_01025", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.2.4 Installing AssetCentral according to NIST IT Asset Management According to IT Asset Management, 4.2.4 Installing AssetCentral: AssetCentral is installed on a hardened CentOS7 Linux system. AssetCentral requires PHP, Web Server (Apache) and MySQL database to be installed. Table 4-1 Recommended Versions for AssetCentral - Tier 3 | Vendor | Product | Version | |----------|-------------------------|---------------------------------| | RedHat | Enterprise Linux Server | Release 6.4 (Santiago) (x86_64) | | Apache | Web Server | httpd-2.2.15-26.el6.x86_64 | | mysql | Server | 5.1.6.6 | | php | | 5.3.3 or higher |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IT Asset Management."}]}
{"id": "nist_01026", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Section 102) | A system that does not meet the criteria for a federal system. | | network | A system implemented with a collection of interconnected components. Such components may include routers, hubs, cabling, telecommunications controllers, key distribution centers, and technical control devices. | | network access | Access to a system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, Internet). | | on behalf of (an agency) [32 CFR 2002] | A situation that occurs when: (i) a non-executive branch entity uses or operates an information system or maintains or collects information for the purpose of processing, storing, or transmitting federal information; and (ii) those activities are not incidental to providing a service or product to the Government. | | operational technology | The hardware, software, and firmware components of a system used to detect or cause changes in physical processes through the direct control and monitoring of physical devices. | | organization [FIPS 200, Adapted] | An entity of any size, complexity, or positioning within an organizational structure. | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | penetration-resistant architecture | An architecture that uses technology and procedures to limit the opportunities for an adversary to compromise an organizational system and to achieve a persistent presence in the system.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_01027", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Considerations for Remote Electronic UOCAVA Voting say about 5.4.6 Formal Verification of Software? According to Security Considerations for Remote Electronic UOCAVA Voting, 5.4.6 Formal Verification of Software: Formal verification of software involves providing mathematical proofs of the correctness of a given piece of software. In order to do formal verification, it must be possible to very precisely describe correct behavior in an algorithm. For this reason, formal verification is very hard to do for large software systems since it is difficult to precisely capture the behavior of a complex system. However formal verification is sometimes done for smaller pieces of a larger software system, such as the software implementing a cryptographic algorithm or protocol. Formal verification of software is very expensive, and is only done in extraordinary applications. For example, the INTEGRITY-178B real-time operating system, one of only two formallyverified operating systems, is used in military and commercial avionics. Formal verification of system designs, while still uncommon, is required at Evaluation Assurance Levels 5, 6 and 7 of a Common Criteria security evaluation [25]. Again, these often involve verifying only a small piece of software within a larger system. Because of its considerable cost, formal verification of software or designs is likely not well-suited to mitigating risks of software defects or vulnerabilities in remote electronic voting systems.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Remote Electronic UOCAVA Voting."}]}
{"id": "nist_01028", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PS-201 in Trustworthy Email? (Part 112) Control PS-201: ocol. It is further recommended that the connection between the client and MSA be secured using TLS [RFC5246] [RFC8314], associated with the full range of protective measures described in Section 5.2. ## 7.3.2 Receiving via IMAP Email message receiving, and management occurs between a client and a server using the Internet Message Access Protocol (IMAP) protocol [RFC3501] over port 143 and 993. A client may be located anywhere on the Internet, establish a transport connection with the server, authenticate itself, and manipulate the remote mailbox with a variety of commands. Depending on the server implementation, it is feasible to have access to the same mailbox from multiple clients. IMAP has operations for creating, deleting and renaming mailboxes; checking for new messages; permanently removing messages; parsing; searching; and selective fetching of message attributes, texts and parts thereof. It is equivalent to the local control of a mailbox and its folders. Establishing a connection with the server over TCP and authenticating to a mailbox with a username and password sent without encryption is not recommended. IMAP clients should connect to servers using TLS [RFC5246] [RFC8314], which should be associated with the full range of applicable protective measures described in Section 5.2. ## 7.3.3 Receiving via POP3 Before IMAP [RFC3501] was invented, the Post O ffice Protocol (POP , now POP version 3 or POP3) had been created as a mechanism for remote users to connect to mailbox, download mail, an d delete it off the server . It was expected at the time that access be from a single, dedicated user, with no conflicts . Provision for encrypted transport was not made. \ufffde protocol went through an evolutionary cycle of upgrade s, and the current instance, POP3 [RFC5034] is aligned with the Simple Authentication Security Layer (SASL) [RFC4422] and optionally operated over a secure encrypted transport layer, TLS [RFC5246].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Trustworthy Email."}]}
{"id": "nist_01029", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Card Technology Developments and Gap Analysis Interagency Report say about Transcript Excerpts:? (Part 3) According to Card Technology Developments and Gap Analysis Interagency Report, Transcript Excerpts:: one barrier. Security: The multi-application is in my opinion the most important. And that's actually part of the migration strategy, the fact that you can have multiple applications on the same card. Interoperability and Further Growth: So in multi-application, the way I like to describe it, is if you took 16, 32, whatever the capacity chip is, separate cards and glued them all together in one card, in effect it is 16 different cards. Each card has its own security keys. And in a sense, it's almost like a firewall. One application can't get to the other application. So conceptually, it's just 15 cards all glued together in one convenient form factor. And here I'm showing that in each of the different application slots, you can put different applications. Access control and logical access are the two most mainstream. And interestingly enough, this actually solves an interesting problem. This is because the physical security director of an installation never trusts the IT guy because they're sort of like rivals. And the IT guy doesn't trust the other guy. So in the older models, they actually used separate cards. But now because each one has its own keys and can maintain its own application, they can both play in the same sandbox together. Everyone can carry the same card. Yet, the IT guy can control access to the computers. And the physical access guy can control access to the building. Multiple Applications: One particular thing that I think is real important when you get to multiple applications is access control is typically the application. That controls the card. What I mean by that is that's typically where the card gets issued from. And if you have a vendor that doesn't tell you or won't disclose to you the keys, the unused applications, that in effect becomes a proprietary card. And you can't use the card for other applications. So that's a real important thing when selecting access control.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Card Technology Developments and Gap Analysis Interagency Report."}]}
{"id": "nist_01030", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2013 Annual Report provide? (Section 111) mponents for conformance to specifications in FIPS 201 and its companion documents. The two PIV components that come under the scope of NPIVP are PIV Smart Card Application and PIV Middleware. All of the tests under NPIVP are handled by third-party laboratories that are accredited as Cryptographic and Security Testing (CST) Laboratories by the NIST NVLAP and are called accredited NPIVP test facilities. As of September 2013, there were nine such facilities. In prior years, CSD published SP 800-85A, PIV Card Application and Middleware Interface Test Guidelines , to facilitate development of PIV Smart Card Application and PIV Middleware that conform to interface specifications in SP 800-73, Interfaces for Personal Identity Verification . CSD also developed an integrated toolkit called 'PIV Interface Test Runner' for conducting tests on both PIV Card Application and PIV Middleware products, and provided the toolkit to accredited NPIVP test facilities. NPIVP validation utilized the following versions and documents throughout FY 2013: - \u0097 SP 800-73-3, Interfaces for Personal Identity Verification - \u0097 SP 800-85A-2, PIV Card Application and Middleware Interface Test Guidelines In FY 2013, two new PIV card application products were validated for conformance to SP 800-73-3 and received certificates, bringing the total number of NPIVP validated PIV Card application products to 36. Three PIV Middleware products were validated for conformance to SP 800-73-3 and received certificates, for a total number of 20 NPIVP-validated PIV Middleware products. In addition, NPIVP is closely involved in ensuring that all changes in PIV companion documents, such as SP 80073-3, SP 800-76-2, and SP 800-78-3, are fully reflected in the conformance test document SP 800-85A-2 as well as subsequently in the PIV Test Runner toolkit consequent on the expected publication of FIPS 201-2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2013 Annual Report."}]}
{"id": "nist_01031", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IA-2 in Security and Privacy Controls for Information Systems and Organizations? (Part 8) Control IA-2: d/or requested action. For example, a user authenticates via a notebook computer to a remote server to which the user desires access and requests some action of the server via that communication path. Subsequently, the server contacts the user via the user\u2019s cell phone to verify that the requested action originated from the user. The user may confirm the intended action to an individual on the telephone or provide an authentication code via the telephone. Out-of-band authentication can be used to mitigate actual or suspected \u201cman-in the-middle\u201d attacks. The conditions or criteria for activation include suspicious activities, new threat indicators, elevated threat levels, or the impact or classification level of information in requested transactions. Related Controls: IA-10, IA-11, SC-37. References: [FIPS 140-3], [FIPS 201-2], [FIPS 202], [SP 800-63-3], [SP 800-73-4], [SP 800-76-2], [SP 800-78-4], [SP 800-79-2], [SP 800-156], [SP 800-166], [IR 7539], [IR 7676], [IR 7817], [IR 7849], [IR 7870], [IR 7874], [IR 7966].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01032", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-256 in Guide to Bluetooth Security? (Part 23) Control HA-256: ic strength. 20 A published theoretical known-plaintext attack can recover the encryption key in 2 38 computations, compared with a brute force attack, which would require testing 2 128 possible keys. If communications require FIPS-approved cryptographic protection (e.g., to protect sensitive information transmitted by Federal agencies), this protection can be achieved by layering applicationlevel FIPS-approved encryption over the native Bluetooth encryption. ## 3.1.3.2 AES-CCM Encryption Algorithm As shown in Figure 3-8, the encryption key provided to the encryption algorithm is produced using the h3 function. The h3 function produces stream cipher keys based on the 128-bit link key, which is a secret that is held in the Bluetooth devices; the unique 48-bit Bluetooth device address of the master; the unique 48-bit Bluetooth device address of the slave; a fixed key ID 'btak'; and the 96-bit ACO value. The ACO is produced during the authentication procedure, as shown in Figure 3-6. The encryption key is shortened by taking the 128 most significant bits of the original encryption key. The Bluetooth AES-CCM encryption procedure is based on Request for Comment (RFC) 3610, Advanced Encryption Standard - Counter with Cipher Block Chaining-Message Authentication Code . The AES-CCM encryption function takes the following as inputs: the encryption key, the encryption 20 Y. Lu, W. Meier, and S. Vaudenay. 'The Conditional Correlation Attack: A Practical Attack on Bluetooth Encryption.' nonce, and the payload bits. The nonce format is of two types: the payload counter format which is used for Asynchronous Connection-Less (ACL) packets, and the clock format (which also includes an 11-bit day counter) which is used for enhanced Synchronous Connection Oriented (eSCO) packets. When AES-CCM encryption is enabled, ACL packets include a 4-octet Message Integrity Check (MIC). eSCO packets do not include a MIC. Figure 3-8.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Bluetooth Security."}]}
{"id": "nist_01033", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Zero Trust Architecture provide? (Section 69) ado en la ausencia de confianza impl\u00edcita basada en la ubicaci\u00f3n de la red significa que los agresores necesitan comprometer una cuenta o un dispositivo existente para conseguir entrar en una empresa. Una ZTA bien desarrollada e implementada deber\u00eda impedir que una cuenta o activo comprometido acceda a otros recursos fuera de su \u00e1mbito o patrones de acceso normales. En consecuencia, las cuentas con pol\u00edticas de acceso a los recursos ser\u00edan los objetivos principales de los agresores. Los atacantes pueden utilizar el Phishing, la Ingenier\u00eda Social o una combinaci\u00f3n de ataques para obtener las credenciales de cuentas con valor, y el significado de valor ser\u00e1 diferente en funci\u00f3n de la motivaci\u00f3n. Por ejemplo, las cuentas de administrador de la empresa pueden ser valiosas, pero los interesados en obtener beneficios econ\u00f3micos considerar\u00e1n que aquellas cuentas que tienen acceso a los recursos financieros o de pago tienen el mismo valor que las mencionadas anteriormente. La implementaci\u00f3n de un MFA para las solicitudes de acceso puede reducir el riesgo de p\u00e9rdida de informaci\u00f3n de una cuenta afectada. Sin embargo, un atacante con credenciales v\u00e1lidas (o un usuario malintencionado) podr\u00eda acceder a los recursos de una cuenta para la que se le hubiese concedido el acceso. Por ejemplo, un agresor o un colaborador afectado que tuviese las credenciales y el acceso al activo propiedad de la empresa de un empleado v\u00e1lido de recursos humanos podr\u00eda acceder a su base de datos. La ZTA reduce el riesgo y evita que cualquier cuenta o activo comprometido se desplace lateralmente por la red. Si las credenciales afectadas no est\u00e1n autorizadas para acceder a un recurso concreto, se les denegar\u00e1 el acceso. Adem\u00e1s, es m\u00e1s probable que un algoritmo de confianza contextual (v\u00e9ase la secci\u00f3n 3.3.1) detecte y responda r\u00e1pidamente a este ataque que cuando se produce en una red heredada basada en el per\u00edmetro.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Zero Trust Architecture."}]}
{"id": "nist_01034", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Author ORCID iDs according to NIST Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, Author ORCID iDs: Ron Ross: 0000-0002-1099-9757 Victoria Pillitteri: 0000-0002-7446-7506", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_01035", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2003 Annual Report say about MULTI-CARD TECHNOLOGY? (Part 3) According to Computer Security Division 2003 Annual Report, MULTI-CARD TECHNOLOGY: tions across organizations, and interoperability. These issues have been examined for evidence of gaps in existing standards and other factors that hamper government-wide application integration. The findings from the initial efforts and suggested priorities for follow-on activities are being developed into NIST Interagency Report 7056, Card Technology Developments and Gap Analysis Interagency Report, which should be available in the first part of 2004. Contact: Mr. Curt Barker (301) 975-8443 wbarker@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2003 Annual Report."}]}
{"id": "nist_01036", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Length according to Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)? Length: unspecified [text/html]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_01037", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report_ Authentication Diary Study say about 5.2.3.3 Authentication Element Entry Effort? (Part 1) According to Report_ Authentication Diary Study, 5.2.3.3 Authentication Element Entry Effort: 5.2.3.3 Authentication Element Entry Effort The factor pertaining to the effort required to submit authentication information was informed by adding an assigned 'effort value' for each element reported being used during an authentication event. The effort factor added to the overall calculated distribution measure is always a negative value, reflecting the negative effect on the participant's primary task. As shown in Table 14, the value -0.5 is assigned if the user had the element memorized or had to look it up (e.g., on a handwritten note), and -0.1 if the element was contained in a mechanism such as a Web browser or PIV card. Note the relatively small value assigned to the Minor impact category reflects the relatively lower cognitive impact on the user. Table 14: Effort values for different types of authentication elements | Authentication element status | Impact | Value | |-------------------------------------------------------------------------------------------------------------------|----------|---------| | Memorized or remembered | Major | -0.5 | | Look up by user (e.g., RSA token, file, paper) | Major | -0.5 | | 'Something you have,' 'something you are' or contained in mechanism (e.g., PIV card, fingerprint, browser-stored) | Minor | -0.1 | Most authentications required a combination of different types of elements or information, and some required multiple elements of the same type.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Report_ Authentication Diary Study."}]}
{"id": "nist_01038", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities provide? (Section 69) lity Impact metrics are each set to 'Complete' to indicate the increased level of access. The Collateral Damage Potential is set to 'Low' because exploitation would cause only slight damage and loss. In the example environment, the need for availability for the targets is low as compared to preserving their confidentiality and integrity, so the Availability Requirement is set to 'Low' and the Confidentiality and Integrity Requirements are set to 'Medium.' The environmental vector would be LVP:L/PTV:L/LRL:L/EC:C/EI:C/EA:C/CDP:L/CR:M/IR:M/AR:L. The environmental exploitability subscore is 1.6 and the impact subscore is 10.0, for an exploitability score of 6.1. CCSS is based on CVSS and CMSS, so there are many similarities among the three specifications. However, there are some important differences as well. This section provides a brief discussion of the major differences between the specifications. Individuals interested in more details on the differences are encouraged to compare the specifications side-by-side. The specifications have similar structures, making such comparisons easy. 15 For the base metrics, all three specifications use the same six metrics and the same equations for calculating scores. The descriptions for each metric have been adjusted to fit the characteristics of the category of vulnerabilities that they cover. The most notable difference is that CCSS also measures the type of exploitation: active or passive. Active exploitation refers to an attacker performing actions to take advantage of a vulnerability, while passive exploitation refers to vulnerabilities that prevent authorized actions from occurring, such as a configuration setting that prevents audit log records from being generated for security events. The Exploitability base metrics in CCSS are defined differently for active and passive exploitation because of the differences in the ease of exploitation.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities."}]}
{"id": "nist_01039", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guidelines for Securing Radio Frequency Identification (RFID) Systems? (Part 277) Control ES-1: UHF, which can offer operating ranges of several meters. The UHF specification defines a tag that operates at 860 MHz - 960 MHz and has an EPC identifier, an error detection code, and a kill command. The EPC shall be a valid EPC that contains four subfields: a header, an EPC manager ID, an object class, and a serial number. The error detection is performed using a 16-bit CRC. The kill password is 8 bits. 95 The EPCglobal Class-1 Generation-2 standard is the only specification that became a standard ratified by EPCglobal. 96 The previous Class-0 and Class-1 Generation-1 tags are expected to be phased out and replaced by Class-1 Generation-2 tags. It describes tags with five major features: an EPC, a tag identifier (TID), a kill command, an optional password-protected access control, and an optional user memory. The tag identifier is used to identify the design and features of the individual tag. This is necessary since tags may have optional or custom commands and features. CRCs are used in some communications and for the EPC. There is a 32-bit kill password and a 32-bit access password. The standard also implements a lock command which can temporarily or permanently make an area of memory write-protected or readand-write protected. 97 EPCglobal Class-1 Generation-2 tags also use a cover-coding method to obscure information that is sent from a reader to a tag. Cover-coding is explained in Section 5.3.2.1. ## A.3 Security Mechanisms in RFID Standards Table A-2 provides an overview of the security mechanisms offered by several RFID standards. 94 Auto-ID Center, \"Technical Report, 13.56 MHz ISM Band Class 1 Radio Frequency Identification Tag Interface Specification: Candidate Recommendation, Version 1.0.0,\" February 1, 2003, ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_01040", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Domain Name System-Based Electronic Mail Security provide? (Section 250) d terminate voluntarily after processing a limited number of requests. To conserve system resources, most server programs terminate when they become idle. Client programs run outside the Postfix core. They interact with Postfix server programs through mail delivery instructions in the user's ~/.forward file, and through small 'gate' programs to submit mail or to request queue status information. As an SMTP server, Postfix implements a first layer of defense against spambots and malware. Administrators can combine Postfix with other software that provides spam/virus filtering (e.g., Amavisd-new), message-store access (e.g., Dovecot), or complex SMTP-level access-policies (e.g., postfwd, policyd-weight or greylisting). Features include: - \uf0a7 standards-compliant support for SMTPUTF8, SMTP, LMTP, STARTTLS encryption including DANE protocol support and 'perfect' forward secrecy, SASL authentication, MIME encapsulation and transformation, DSN delivery status notifications, IPv4, and IPv6 - \uf0a7 configurable SMTP-level access policy that automatically adapts to overload - \uf0a7 virtual domains with distinct address-namespaces - \uf0a7 UNIX-system interfaces for command-line submission, for delivery to command, and for direct delivery to message stores in mbox and maildir format - \uf0a7 light-weight content inspection based on regular expressions - \uf0a7 database lookup mechanisms including Berkeley DB, CDB, OpenLDAP LMDB, Memcached, LDAP and multiple SQL database implementations - \uf0a7 a scheduler that implements parallel deliveries, with configurable concurrency and back-off strategies - \uf0a7 a scalable zombie blocker that reduces SMTP server load due to botnet spam Postfix extensions use the SMTP or Milter (Sendmail mail filter) protocols which both give full control over the message envelope and content, or a simple text-based protocol that enables complex SMTPlevel access control policies.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_01041", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Status Report on the Second Round of the SHA-3 Cryptographic Hash Algorithm Competition say about Security? According to Status Report on the Second Round of the SHA-3 Cryptographic Hash Algorithm Competition, Security: FRN-Nov07 lists the major security-evaluation factors as: - (i) applications of the hash functions 1 ; - (ii) specific requirements when hash functions are used to support HMAC, Pseudo Random Functions (PRFs), or Randomized Hashing; - (iii) additional security requirements of hash functions; - (iv) evaluations relating to attack resistance; and - (v) other consideration factors. For its security evaluations, NIST studied the large amount of feedback received from the cryptographic community via e-mail discussions in the official mailing list ( hash-forum@nist.gov ), and the SHA-3 Zoo web page [22], as well as the security arguments presented by the designers. NIST researchers also conducted their own internal cryptanalysis of the candidates.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Second Round of the SHA-3 Cryptographic Hash Algorithm Competition."}]}
{"id": "nist_01042", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TG-005 in Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)? (Part 24) Control TG-005: t in time be enforced by the system. They suggested that the distinction might be based in part upon Clark and Wilson's view of what was practical and that it might discourage attempts at enforcement. The group felt that while certification is both indicated and necessary, that its use should not be mandated where enforcement might also be an equally appropriate choice. Certification was seen as one tool among others, and not to be automatically preferred. (A subsequent discussion suggested that perhaps the distinction was between those rules that were application specific (C) and those that were specific only to the system (E)). ## GRANULARITY The working group concluded that granularity of TPs and CDIs was ultimately an application issue. While it is difficult to conclude exactly what granularity is required except in the context of a particular application, the group identified useful guidance. ## single Function The group concluded that TPs should be limited to a single well-defined function or be composed only of like or related functions. While too many small particles may be messy and administratively burdensome, in computer systems, it is far easier to group things than it is to divide them. Another test that was agreed to was that a manager should never be forced to grant privilege A simply for the purpose of conferring B. A and B should be separate units. In that case, sets A-B could be formed as could A-A and B-B. On the other hand if AB was the smallest named unit, that would fail the test. ## Separation of Duties The group took note of the generally accepted standards of good business practice for separation of duties (see position paper by W. H. Murray, attached) . These practices require that at a minimum managers must be able to separate the following: * origination from approval - * - creation from maintenance * procedure from data * assets from records ## Obvious Intent The TP should be small enough that it is obvious in its intent.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)."}]}
{"id": "nist_01043", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Status Report on the Second Round of the NIST Post-Quantum Cryptography Standardization Process provide? (Section 58) cryptanalysis. This is particularly true for digital signature schemes where the best schemes that are not based on structured lattices have a substantial performance penalty for general-purpose use. For the eight alternate candidate algorithms advancing to the third round, NIST notes that these algorithms still may potentially be standardized; although that most likely will not occur at the end of the third round. NIST expects to have a fourth round of evaluation for some of the candidates on this track. If new results emerge during the third round which undermine NIST's confidence in some of the finalists, NIST may extend the timeline, or make changes to the process. If NIST has less serious concerns specific to a particular finalist and sees the need to continue evaluating it, NIST may instead defer the decision about standardization for the affected finalist until the fourth round. The third round is expected to last 12-18 months. Submission modifications should be submitted to NIST by October 1, 2020, in a complete submission package as defined in [33]. It would be helpful if submission teams provided NIST with a summary of their expected changes by August 10, 2020. As a general guideline, NIST expects that any modifications to the seven finalists should be relatively minor while allowing more latitude to the eight additional candidate algorithms. Note, however, that larger changes may signal that an algorithm is not mature enough for standardization at this time. More detailed instructions will be provided. The efforts of the cryptographic community have been invaluable in analyzing and implementing schemes throughout this process. NIST hopes that with only seven finalists and eight alternate candidates, the public review period will include more work on side-channel resistant implementations, performance data in internet protocols, and performance data for hardware implementations in addition to more rigorous cryptanalytical study.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Second Round of the NIST Post-Quantum Cryptography Standardization Process."}]}
{"id": "nist_01044", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT) say about Data Processing? According to Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT), Data Processing: A data processing capability provides the ability to transform data based on an algorithm. The transformation may be very simple, with a single input variable and a single output, or it may be complex with multiple inputs and outputs. Control algorithms are an important type of processing that take the output of sensor(s) and actuator(s) or pre-processor(s) and provide an output that can be fed into an actuator or post-processor. These control algorithms often are used within negative feedback loops, but not always. A proportional-integral-derivative (PID) 3 controller (widely used in industrial control systems) is an example of such a control algorithm. Another example is an algorithm which models the human insulin response in a real-time system that manages the function of an artificial pancreas. Additional examples of data processing include: data aggregation capability, predictive analysis, and binary (Yes/No) analysis.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_01045", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Privacy Controls for Information Systems and Organizations provide? (Section 350) s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ time synchronous one-time tokens, and number of allowed rejections during the verification stage of biometric authentication). Actions can be taken to safeguard individual authenticators, including maintaining possession of authenticators, not sharing authenticators with others, and immediately reporting lost, stolen, or compromised authenticators. Authenticator management includes issuing and revoking authenticators for temporary access when no longer needed. Related Controls: AC-3, AC-6, CM-6, IA-2, IA-4, IA-7, IA-8, IA-9, MA-4, PE-2, PL-4, SC-12, SC-13.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01046", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Secure Web Services? (Part 34) Control ES-1: taken from NIST IR 7298, Glossary of Key Information Security Terms and NIST SP 800-100, Information Security Handbook: A Guide for Managers, available at http://csrc.nist.gov/publications/nistpubs/. More information on these concepts can be found in Computer Security: Art and Science by Matt Bishop. - Confidentiality. Preserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information - Privacy. Restricting access to subscriber or relying party information in accordance with Federal law and organization policy ## 2.3 Web Services Security Dimensions The Web services security dimensions have been defined as: secure messaging, resource protection, negotiation of contracts, trust management, and security properties 12 . These dimensions encompass the elements of security (discussed in Section 2.2) in a Web services environment. Each dimension is essential to the development of secure applications using Web services, but each dimension affects a different layer of the Web service. This section describes each security dimension and provides an overview of what technologies are available, what is on the horizon, and what remains to be done. ## 2.3.1 Secure Messaging Web services rely on the Internet for communication. Because SOAP was not designed with security in mind, 13 SOAP messages can be viewed or modified by attackers as the messages traverse the Internet. There are several options available for securing Web service messages: - HTTP over SSL/TLS (HTTPS). Because SOAP messages are transmitted using HTTP, it is trivial to modify a Web service to support HTTPS. - XML Encryption and XML Signature. These XML security standards developed by W3C allow XML content to be signed and encrypted.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Guide to Secure Web Services."}]}
{"id": "nist_01047", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Engineering Trustworthy Secure Systems say about SIGNIFICANCE OF LOSS - AN EXAMPLE? (Part 3) According to Engineering Trustworthy Secure Systems, SIGNIFICANCE OF LOSS - AN EXAMPLE: kely or probable to happen?' 39 Addressing loss occurs through the protective measures that enforce constraints to ensure that only authorized and intended behaviors and outcomes of the system occur. These include: - Protective measures that are provided by the machine portion of the system (i.e., the system architecture and design, the use of engineered features and devices within the architecture and design) - Protective measures that are provided by the human in the system (i.e., personnel, practices, procedures, the use of tools to support the human as a system element, and the human role in designing and building the machine part of the system) - Protective measures that are provided by the physical environment (i.e., controlled access areas, facility access points, physical monitoring, environmental controls, fire suppression) The terminology used to describe means and methods includes mechanisms, configurations, controls, safeguards, countermeasures, features, techniques, overrides, practices, procedures, processes, and inhibits. These may be applied in accordance with governing policies, regulations, laws, practices, standards, and techniques.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_01048", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices provide? (Section 481) Promotion Board [Potato Research and Promotion Act, Public Law 91-670, Title III, Sec. 310, Jan. 11, 1971, 84 Stat. 2044; amended by Public Law 101- 624, Title XIX, Sec. 1942, Nov. 28, 1990, 104 Stat. 3867] | Table 6: Legal Information Disclosure Prohibitions | Subject/Title of Provision | United States Code Citation | Agency/Activity [Reference] | |----------------------------------------------------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Authorization for Disclosure and Use of Intercepted Wire, Oral, or Electronic Communications | 18 U.S.C., Part I, Chapter 119, Section 2517(6) | Law Enforcement [Omnibus Crime Control and Safe Streets Act of 1968, Public Law 90- 351, Title III, Sec.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_01049", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? (Part 80) Control HA-1: Principle of Least Authority (POLA). The design picture of XPOLA is shown in Figure 3. The capability manager (Capman) is the platform for resource providers to collaborate with their users. Through this platform, the resource users send requests to the providers for access rights; the provider processes the requests and creates the corresponding capability tokens. The capability manager stores the capability tokens and supports the providers with the functionalities for manipulating the capabilities: capability generation, destruction, update, renewal, request processing, and optionally pushing the capabilities to the users. ## 4th Annual PKI R&amp;D Workshop -- Proceedings The registry service provides registration and discovery of the available Web service instances. It keeps the information of all the registered service instances. Every time a new service is instantiated, it is supposed to register itself by sending a Web Services Definition Language (WSDL) document to the registry. A WSDL document contains the detailed information needed to interact with the service instance. If the capability of a specific resource for a specific user exists in the capability manager's storage, the user can fetch the capability from the manager directly and stores it in her local token agent. The token agent is an ssh-agent-like client for interacting with the capability manager and caching the retrieved capability tokens. Figure 3 The Big Picture <!-- image --> The Community Informative Authority (CIA) is an optional trusted authentication service for identity verification in the community. It establishes trust relationships, either mutual or unilateral as required, between the users and providers. Note that CIA service does not make any authorization decisions for the providers.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_01050", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Accuracy, Integrity, and Security in Computerized Vote-Tallying provide? (Section 129) Elkins' complaints, it was reported that Attorney General Jim Mattox and Secretary of State Myra McDaniel began investigations into voting discrepancies. According to the Dallas Morning News of Sept. 23, 1986, \"the probe centers on allegations that computerized voting equipment and computer programs used to tabulate state and local elections may have been tampered with to bring about \"preprogrammed' results.\" [53] In that same newspaper article, Ms. Elkins was quoted as saying that \"the allegation is that the computer used to count the votes was given new instructions after it calculated that Max Goldblatt was leading Starke Taylor by 400 votes.\" Ms. Elkins has noted that the Dallas County computer had encountered difficulties shortly after 8 p.m. on election night, and that the candidate who was leading at 8 p.m., prior to the computer difficulties, was not leading when the computer reported again. Ms. Conny McCormack, Dallas County Elections Administrator, admitted that the documentation for the April 6, 1985 election could appear contradictory. Her explanation was that the difficulty concerned the treatment of \"split precincts,\" that is, those precincts bisected by the Dallas city boundary. There were 11 such split precincts. The value of 78,398 for ballots cast was produced by assuming zero ballots cast from these split precincts. The value of 80,208 for ballots cast was produced by adding the total ballots from the split precincts, including ballots cast outside of the city. The final value of 79,783 for ballots cast included only those ballots cast within the city of Dallas. Ms. McCormack contended that the recount generally confirmed the correctness of the originally reported outcome. [54] Ms. McCormack's explanation of the problem of reporting split precincts was supported by the vendor of the vote-tallying system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Accuracy, Integrity, and Security in Computerized Vote-Tallying."}]}
{"id": "nist_01051", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2 provide? (Section 20) e, and development. - \uf0b7 Section 4 defines SCAP content processing requirements and recommendations. - \uf0b7 Section 5 provides additional content requirements and recommendations for particular use cases. - \uf0b7 Appendix A gives an overview of major security considerations for SCAP implementation. - \uf0b7 Appendix B contains an acronym and abbreviation list. - \uf0b7 Appendix C contains a glossary of selected terms used in the document. - \uf0b7 Appendix D lists references and other resources related to SCAP 1.2. - \uf0b7 Appendix E provides a change log that documents significant changes to major drafts of this specification. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in Request for Comment (RFC) 2119 [RFC2119]. When these words appear in regular case, such as 'should' or 'may', they are not intended to be interpreted as RFC 2119 key words. When a single term within a sentence is italicized, this indicates that the term is being defined. These terms and their definitions also appear in Appendix C. Some of the requirements and conventions used in this document reference Extensible Markup Language (XML) content [XMLS]. These references come in two forms, inline and indented. An example of an inline reference is: a &lt;cpe2\\_dict:cpe-item&gt; may contain &lt;cpe2\\_dict:check &gt; elements that reference OVAL Definitions. In this example the notation &lt;cpe2\\_dict:cpe-item&gt; can be replaced by the more verbose equivalent 'the XML element whose qualified name is cpe2\\_dict:cpe-item '. An example of an indented reference is: References to OVAL Definitions are expressed using the following format: ``` <cpe2_dict:check system= \"http://oval.mitre.org/XMLSchema/oval-definitions-5\" href= \" Oval_URL \" >[ Oval_inventory_definition_id ] ``` 7 http://csrc.nist.gov/publications/PubsSPs.html#800-117 &lt;/cpe2\\_dict:check&gt; .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2."}]}
{"id": "nist_01052", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identity and Access Management for Electric Utilities provide? (Section 18) ics Evaluation Assumptions and Limitations ............................. 59 5.9.3 Example Solution Analysis .......................................................................................... 60 5.9.4 Security Characteristics Addressed ............................................................................ 62 5.9.5 Assessment of Reference Architecture ...................................................................... 64 5.9.6 Security Recommendations ........................................................................................ 69 5.9.7 Security Characteristics Evaluation Summary ............................................................ 71 NIST SP 1800-2B: Identity and Access Management for Electric Utilities vii T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . NIST SP 1800-2B: Identity and Access Management for Electric Utilities viii T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . List of Figures Figure 5-1 IdAM Capabilities ............................................................................................................. 21 Figure 5-2 IdAM Example Solution .................................................................................................... 23 Figure 5-3 Notional PACS Architecture .............................................................................................. 26 Figure 5-4 Notional OT Silo Architecture ........................................................................................... 27 Figure 5-5 Notional IT Silo Architecture .............................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_01053", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1.2 Report Structure according to NIST Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research According to Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research, 1.2 Report Structure: The remainder of this report is organized into the following sections and appendices: - Section 2 provides a summary of the business opportunities for using DPCs with modern mobile client devices. - Section 3 describes usage scenarios for issuing PIV credentials and associated DPCs. - Section 4 explains the application of Microsoft and Intercede technologies in accordance with NIST SP 800-157 to support the organization-provisioned PIV credentials usage scenario. - The following sections discuss DPC-related activities: - o Section 5: Initial issuance - o Section 6: Maintenance - o Section 7: Termination - o Section 8: Usage - Section 9 briefly looks at next steps for research in the area of DPCs. - Appendix A provides mappings between the DPC requirements from this report and requirements from other federal government standards and guidelines. - Appendix B- defines acronyms and abbreviations used in the report. - Appendix C- provides a bibliography for the report. 1 http://dx.doi.org/10.6028/NIST.SP.800-157 2 http://dx.doi.org/10.6028/NIST.FIPS.201-2 3 http://dx.doi.org/10.6028/NIST.SP.800-63-2", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research."}]}
{"id": "nist_01054", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events say about Appendix D Functional Evaluation? According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events, Appendix D Functional Evaluation: A functional evaluation of the data integrity (DI) example implementation, as constructed in our laboratory, was conducted to verify that it meets its objective of detecting and responding to DI events. Furthermore, this project aims to analyze the events to aid recovery and protection of the enterprise against future attacks. The evaluation verified that the example implementation could perform the following functions: - Detect malicious network activity, malicious mobile code, malicious code execution, and unauthorized user behavior. - Contain and analyze these types of incidents. - Mitigate the impact of these incidents as they occur. - Report relevant details for use in mitigation and protection against future events. Section D.1 describes the format and components of the functional test cases. Each functional test case is designed to assess the capability of the example implementation to perform the functions listed above and detailed in Section D.1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events."}]}
{"id": "nist_01055", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in 2016 NIST_ITL Cybersecurity Program Annual Report? (Part 146) Control HA-3: ic Safety Mobile Authentication . (July 2016) (see http:/ /nvlpubs.nist.gov/nistpubs/ir/2016/NIST. IR.8080.pdf) - NISTIR 8150, Government Data De-Identification Stakeholder's Meeting, Meeting Report . (September 2016) (see http:/ /nvlpubs.nist.gov/nistpubs/ir/2016/ NIST.IR.8150.pdf) - Choong, Y. Y., &amp; Greene, K. K. (2016, September). What's a Special Character Anyway? Effects of Ambiguous Terminology in Password Rules . Published in the Proceedings of the Human Factors and Ergonomics Society Annual Meeting (Vol. 60, No. 1, pp. 760-764). Sage CA: Los Angeles, CA: SAGE Publications. - Theofanos, M., Garfinkel, S. and Choong, Y.Y., (2016). Secure and Usable Enterprise Authentication: Lessons from the Field . IEEE Security &amp; Privacy , 14 (5), pp.14-21. - Greene, K.K., and Choong, Y.Y. ' Must I, Can I? I Don't Understand Your Ambiguous Password Rules. ' This article was accepted on 09/12/2016 and will appear in Issue 1 of the 2017 Volume of Journal of Information and Computer Security. - Stanton, B., Theofanos, M., Spickard Prettyman, S., Furman, S., ' Security Fatigue ', IT Professional , Vol. 18, Issue 5, pp. 26-32, Sept.-Oct. 2016, doi:10.1109/ MITP.2016.84 - Stanton, B., Theofanos, M., Spickard Prettyman, S., Furman, S. (2016). The Power of Qualitative Methods: Aha Moments in Exploring Cybersecurity and Trust . User Experience Magazine, 16(5). Retrieved from http:/ /uxpamagazine.org/thepower-of-qualitative-methods/ - Steves, M., Theofanos, M., (2016) ' What's in your policy? Do your users know?' National Institute of Standards and Technology Interagency Report (NISTIR) that was submitted to IEEE Security and Privacy. - Garfinkle, S., Theofanos, M. and Choong,Y.Y., ' Secure and Usable Enterprise Authentication: Lessons from the Field ,' to appear in IEEE Security &amp; Privacy, September/October 2016, a special issue on usable security.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01056", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide: according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance, Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide:: Volume 1 - General Implementation Guidance Keith Stouffer Timothy Zimmerman CheeYee Tang Jeffrey Cichonski Michael Pease Neeraj Shah Wesley Downard This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8183A-1 <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance."}]}
{"id": "nist_01057", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases say about F.2.1 IBM ROP and COP/JOP Attack Defenses? According to Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases, F.2.1 IBM ROP and COP/JOP Attack Defenses: The POWER platform added four instructions (hashst, hashchk, hashstp, hashchkp) to handle ROP in the Power ISA 3.1B starting in the Power10 processor.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases."}]}
{"id": "nist_01058", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography say about 6. Key Agreement Schemes? (Part 3) According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography, 6. Key Agreement Schemes: schemes may be further classified by whether they use finite field cryptography (FFC) or elliptic curve cryptography (ECC). A scheme may use either Diffie-Hellman or MQV primitives (see Section 5.7). Thus, for example, notation C(2e, 2s, FFC DH) completely classifies the dhHybrid1 scheme of Section 6.1.1.1 as a scheme with two ephemeral keys and two static keys that uses finite field cryptography and a Diffie-Hellman primitive (see Table 8). The names of these schemes are taken from ANS X9.42 and ANS X9.63. Table 8: Key-agreement schemes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}]}
{"id": "nist_01059", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide for Security-Focused Configuration Management of Information Systems? (Part 108) Control ES-1: ation for Key Management, Part 3: Application-Specific Key Management Guidance. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-57 Part 3, Rev. 1. https://doi.org/10.6028/NIST.SP.800-57pt3r1 | | [SP 800-58] | Kuhn R, Walsh TJ, Fries S (2005) Security Considerations for Voice Over IP Systems. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-58. https://doi.org/10.6028/NIST.SP.800-58 | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | [SP 800-63B] | Grassi PA, Newton EM, Perlner RA, Regenscheid AR, Fenton JL, Burr WE, Richer JP, Lefkovitz NB, Danker JM, Choong Y-Y, Greene KK, Theofanos MF (2017) Digital Identity Guidelines: Authentication and Lifecycle Management. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800- 63B, Includes updates as of December 1, 2017. https://doi.org/10.6028/NIST.SP.800-63B | |----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [SP 800-70] | Quinn SD, Souppaya MP, Cook MR, Scarfone KA (2018) National Checklist Program for IT Products: Guidelines for Checklist Users and Developers.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_01060", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Managing Information Security Risk_ Organization, Mission, and Information System View say about 2.7 ORGANIZATIONAL CULTURE? (Part 3) According to Managing Information Security Risk_ Organization, Mission, and Information System View, 2.7 ORGANIZATIONAL CULTURE: tions and services solely for their use. These organizations may be reluctant to use externally-provided software applications and services and this reluctance may result in lower risk being incurred. Other organizations may, on the other hand, seek to maximize advantages achieved by modern net-centric architectures (e.g., service-oriented architectures, cloud computing), where hardware, software, and services are typically provided by external organizations. Since organizations typically do not have direct control over assessment, auditing, and oversight activities of external providers, a greater risk might be incurred. In addition to the cultural impacts on organizational risk management perspectives, there can also be cultural issues between organizations. Where two or more organizations are operating together toward a common purpose, there is a possibility that cultural differences in each of the respective organizations may result in different risk management strategies, propensity to incur risk, and \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ willingness to accept risk. 58 For example, assume two organizations are working together to create a common security service intended to address the advanced persistent threat. The culture of one of the organizations may result in a focus on preventing unauthorized disclosure of information, while the nature of the other organization may result in an emphasis on mission continuity. The differences in focus and emphasis resulting from organizational culture can generate different priorities and expectations regarding what security services to procure, because the organizations perceive the nature of the threat differently.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Managing Information Security Risk_ Organization, Mission, and Information System View."}]}
{"id": "nist_01061", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SC-7 in NIST_SP_800-53r5_Security_Privacy_Controls? (Part 15) Control SC-7: on: A direct connection is a dedicated physical or virtual connection between two or more systems. Organizations typically do not have complete control over external networks, including the Internet. Boundary protection devices (e.g., firewalls, gateways, and routers) mediate communications and information flows between unclassified national security systems and external networks. Related Controls: None. (26) BOUNDARY PROTECTION | CLASSIFIED NATIONAL SECURITY SYSTEM CONNECTIONS Prohibit the direct connection of a classified national security system to an external network without the use of [Assignment: organization-defined boundary protection device]. Discussion: A direct connection is a dedicated physical or virtual connection between two or more systems. Organizations typically do not have complete control over external networks, CHAPTER THREE PAGE 303 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ including the Internet. Boundary protection devices (e.g., firewalls, gateways, and routers) mediate communications and information flows between classified national security systems and external networks. In addition, approved boundary protection devices (typically managed interface or cross-domain systems) provide information flow enforcement from systems to external networks. Related Controls: None.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, national security. Contains guidance on protecting sensitive government information. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01062", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Keywords according to NIST Guide to Bluetooth Security According to Guide to Bluetooth Security, Keywords: Bluetooth; information security; network security; wireless networking; wireless personal area networks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Bluetooth Security."}]}
{"id": "nist_01063", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-8(3) in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Control CM-8(3): Data Encoding (T1132) Inspect and Analyze Network Traffic (CM2002) Monitoring and Damage Assessment Detect", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_01064", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.2.1 Determine the Topics according to NIST Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities According to Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities, 4.2.1 Determine the Topics: The design team should determine the exercise topic based on the focus of the plan being exercised. General topics can include contingency planning and incident response; specific topics range from sustaining essential functions to managing and reporting IT security incidents. For example, disaster recovery plan exercise discussion topics would likely include the roles and responsibilities of personnel with regard to the processes and procedures associated with restoring an organization's information systems. Incident response plan exercise discussion topics would likely include processes and procedures for managing and reporting IT security incidents.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities."}]}
{"id": "nist_01065", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Platform Firmware Resiliency Guidelines provide? (Section 24) ................................................................................ C-References .......................................................................................................... | | | Appendix | Appendix | Appendix | 37 | | List of Figures | List of Figures | List of Figures | List of Figures | | Figure 1: High-Level System Architecture....................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Platform Firmware Resiliency Guidelines."}]}
{"id": "nist_01066", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2017 NIST_ITL Cybersecurity Program Annual Report say about 30th Annual FISSEA Conference? According to 2017 NIST_ITL Cybersecurity Program Annual Report, 30th Annual FISSEA Conference: March 14-15 CANCELLED due to inclement weather https:/ /www.nist.gov/news-events/ events/2017/03/30th-annual-fissea-conference", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01067", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Cybersecurity according to NIST Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective According to Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective, Cybersecurity: - Federal Information Security Modernization Act of 2014 (Public Law 113-283) - Cybersecurity Enhancement Act of 2014 (Public Law No: 113-274) - Improving Critical Infrastructure Cybersecurity (Executive Order, February 12, 2013) - National Cybersecurity Center of Excellence (Public Law 112-55, Consolidated and Further Continuing Appropriations Act of 2012) - National Initiative For Cybersecurity Education (NICE) - Section 5131 of the Information Technology Management Reform Act of 1996 (Public Law 104-106) [supersedes Computer Security Act of 1987 (Public Law 100-235)] - Federal Information Security Management Act (FISMA) of 2002 (Title III of the EGovernment Act Federal Information Security Management Act of 2002 (Public Law 107-347)) - Cybersecurity Research and Development Act of 2002 (Public Law 107-305) - National Strategy to Secure Cyberspace (February 2003) - Homeland Security Presidential Directive #12: Policy for a Common Identification Standard for Federal Employees and Contractors (August 27, 2004) - Conference Report on House Resolution 5441, Department of Homeland Security Appropriations Act, 2007: Title V - General Provisions (WHTI [Western Hemisphere Travel Initiative] Certification effort) - OMB Circular A-130 Management of Federal Information Resources (February 8, 1996) - OMB M-04-04 E-Authentication Guidance for Federal Agencies (December 16, 2003) - OMB Directive 05-24 Implementation of Homeland Security Presidential Directive (HSPD) 12 - Policy for a Common Identification Standard for Federal Employees and Contractors (August 5, 2005) - OMB Memorandum M-08-05, Implementation of Trusted Internet Connections (November 20, 2007) - OMB M-08-23 Securing the Federal Government's Domain Name System Infrastructure (August 22, 2008) - National Security Presidential Directive 54 / Homeland Security Presidential Directive 23 (NSPD-54/HSPD-23): Comprehensive National Cybersecurity Initiative (January 2008)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective."}]}
{"id": "nist_01068", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series say about 10. Implementation Considerations? (Part 3) According to Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series, 10. Implementation Considerations: e decryption-verification process is returned in constant time. Another unrelated note appears in NIST SP 800-38D, which mentions side-channel information from internal error logs. 10 Andreeva et al. [4] point out that achieving the highest level of security in the RUP setting requires the encode-then-encipher approach mentioned in Section 9 as 'pad-then-encipher.' Likewise, it is assumed for the CCM and GCM modes that the nonce is not reused and that the length of the tag is sufficiently long. Otherwise: - Reuse of the nonce in the CCM or GCM mode results in a reuse of the counter blocks for the underlying CTR mode. This leads to the devastating confidentiality attack described in Section 4.1: with knowledge of certain plaintext blocks, the adversary can use the ciphertext to derive all other plaintext blocks at locations where the counter is reused using a simple XOR operation. - If the tag is not sufficiently long, a guessing attack can be mounted, as explained in Section 5. The adversary can choose tags randomly and independent of the ciphertext and, when successful, use the fact that the underlying CTR allows an adversary to make arbitrary changes to the plaintext by flipping the corresponding bits in the ciphertext (as explained in Section 4). In the case of GCM, even more devastating attacks exist in the aforementioned settings. The adversary can recover the authentication key when short tags are used (as shown by Ferguson [35]) or when the nonce is reused (as shown by Joux [45]). In NIST IR 8319 [55], the single-key setting assumed that the key is drawn uniformly at random and is therefore unknown to the adversary. An adversary may nevertheless know the key if it is generated with an insecure or improperly implemented random bit generator (RBG) or when the protocol uses HMAC with an insecure hash function, such as MD5 or SHA-1, due to the Sloth attack [17] (CVE-2015-7575 [65]).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: cve-, adversary. Contains technical security guidance that could inform defensive posture. Source: Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series."}]}
{"id": "nist_01069", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 857) tent T h i s p u b l i c a \ue000 o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h \ue003 p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P. 8 0 0 - 5 3 A r 5 NIST SP 800-53A, REV. 5 ASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS SA-08(12) SECURITY AND PRIVACY ENGINEERING PRINCIPLES | HIERARCHICAL PROTECTION ASSESSMENT OBJECTIVE: Determine if: SA-08(12)_ODP systems or system components that implement the security design principle of hierarchical protec\ue000on are de\ufb01ned; SA-08(12) <SA-08(12)_ODP systems or system components> implement the security design principle of hierarchical protec\ue000on. POTENTIAL ASSESSMENT METHODS AND OBJECTS: SA-08(12)-Examine [SELECT FROM: System and services acquisi\ue000on policy; procedures addressing the security design principle of hierarchical protec\ue000on used in the speci\ufb01ca\ue000on, design, development, implementa\ue000on, and modi\ufb01ca\ue000on of the system; system design documenta\ue000on; security and privacy requirements and speci\ufb01ca\ue000ons for the system; system security and privacy architecture; system security plan; other relevant documents or records]. SA-08(12)-Interview [SELECT FROM: Organiza\ue000onal personnel with the responsibility for determining SA-08(12)-Test system security and privacy requirements; organiza\ue000onal personnel with system speci\ufb01ca\ue000on, design, development, implementa\ue000on, and modi\ufb01ca\ue000on responsibili\ue000es; system developers; organiza\ue000onal personnel with informa\ue000on security responsibili\ue000es]. [SELECT FROM: Organiza\ue000onal processes for applying the security design principle of hierarchical protec\ue000on in system speci\ufb01ca\ue000on, design, development, implementa\ue000on, and modi\ufb01ca\ue000on; mechanisms suppor\ue000ng the applica\ue000on of the security design principle of hierarchical protec\ue000on in system speci\ufb01ca\ue000on, design, development, implementa\ue000on, and modi\ufb01ca\ue000on].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01070", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security in ISDN provide? (Section 12) nted. Similar issues attend many financial, medical and criminal justice records. The confidentiality and use of records are now the subject of legislation and will receive more legislative attention. Today individuals are increasingly mobile, often moving to pursue their careers. The use of cash for large transactions, or simply to rent a car or buy an airline ticket, is considered unusual at best and possibly a sign of criminal activity. On the basis of the possession of plastic credit cards merchants broadly extend credit to complete strangers with no authentication of personal identity. A large catalog industry now takes orders primarily over the telephone, shipping merchandise, often within 24 hours, on the basis of a credit card number given over the telephone. A good credit rating and possession of credit cards are necessities of modem everyday life. The public network is the main carrier by which these sensitive records are gathered and accessed. It must support users with a great variety of security policies. The problem is compounded by the successive chain of domains which is involved. By itself, ISDN cannot solve the crossdomain interworking, a problem which is general to all communications systems, but it must support some of the basic mechanisms required to provide secure interworicing between domains. The problem is central to the fabric of modem society, and is as much a social policy issue as a security issue. In the United States, the National Security Agency (NSA) is charged by law with protecting classified data. The security resources and expertise of NSA are unrivaled. The National Institute of Standards and Technology (NIST) has responsibilities for the security of unclassified information.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, national security. Contains guidance on protecting sensitive government information. Source: Security in ISDN."}]}
{"id": "nist_01071", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Study of Federal Agency Needs for Information Technology Security say about network security? According to A Study of Federal Agency Needs for Information Technology Security, network security: Governmentwide mandatory minimum requirements policy, carrying the force of law, and requiring centralized management and oversight within each agency Guide to network safeguards and when to use them NIST publications need to be updated to place more emphasis on \"interconnected network systems\"", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of Federal Agency Needs for Information Technology Security."}]}
{"id": "nist_01072", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Key Management Documents say about 7.5.5. add-info? According to Secure Data Network Systems (SDNS) Key Management Documents, 7.5.5. add-info: In addition to the negotiation of options, the Ssrq and Ssrs exchange may provide the communicating entities with some additional information. This information is optional and its use by the recipient is a local matter. Some of the information may be signed by the KMS or an authorized directory service. The following sections describe some of the possible information which may appear in the Ssrq and Ssrs exchanges. Note - see SDN.906, SDNS Traffic Key Attribute Negotiation, for further information.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_01073", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does BIOS Protection Guidelines provide? (Section 39) /resources/pc\\_client\\_work\\_group\\_specific\\_imple mentation\\_specification\\_for\\_conventional\\_bios\\_specification\\_version\\_12 - [UEFI] UEFI Specification Version 2.3 . Unified EFI Forum. May 2009. - F. Wecherowski. 'A Real SMM Rootkit: Reversing and Hooking BIOS SMI Handlers.' - [Wech09] Phrack . Issue 66. 6 November 2009. - [WoTe09] R. Wojtczuk and A. Tereshkin. 'Attacking Intel BIOS.' Black Hat USA . Las Vegas, NV. 30 July 2009. ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: BIOS Protection Guidelines."}]}
{"id": "nist_01074", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings say about 4.3 Simulation? (Part 1) According to 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings, 4.3 Simulation: 4.3 Simulation Weuse discrete-event simulation to understand the performance of BGP origin and path authentication schemes in a large-scale environment. As with our earlier work, our experiments uses SSFNet [5, 28], a discrete-event simulator that provides a comprehensive model of basic BGP operations [31]. Our earlier work added hooks for variants of processing models of BGP security schemes [27]. Throughout this study, we evaluate security schemes in the same network topology and same BGP activity settings. We use a 110-AS topology, with one operating BGP speaker per AS. For modeling simplicity, each BGP speaker announces two prefixes. In our model, each AS also possesses virtual BGP speakers that don't actually run a simulated BGP protocol. We use the number of such BGP speakers to represent the size of an AS; its size affects the time it takes for one Update message to be propagated through an AS. We use the public data provided by RouteViews project [33] to generate a graph of AS connectivity of the Internet, then reduce the size to 110 ASes using a collapsing procedure. This reduced graph still preserves certain macroscopic properties [6] seen on the entire Internet. Moreover, we incorporate our estimation of route filtering policies into the topology using a method, similar to the one proposed in [7]. During normal BGP activities, we let one BGP speaker crash and reboot. We evaluate the performance of the entire system during router rebooting process. The work- load on BGP speakers could be much higher than normal BGP activities, since the rebooting BGP speaker receives routing table dumps in a short period of time from each its peers, via a large amount of route announcements. To maximize the e GLYPH&lt;11&gt; ects, we let the rebooting BGP speaker to be the one with the most peers. Besides the common settings, we also have specific parameters for each of the security schemes.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_01075", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is lunash according to Securing Web Transactions_ TLS Server Certificate Management? lunash: &gt; net dns add searchdomain int-nccoe.org", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_01076", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Framework for Designing Cryptographic Key Management Systems say about 2.1 Rationale for Cryptographic Key Management? (Part 1) According to A Framework for Designing Cryptographic Key Management Systems, 2.1 Rationale for Cryptographic Key Management: 2.1 Rationale for Cryptographic Key Management Today's information systems and the information that they contain are considered to be critical assets that require protection. The information used by government and business is often contained in computer systems consisting of groups of interconnected computers that make use of shared networks, e.g., the Internet. Since the Internet is shared by diverse and often competing organizations and individuals, information systems should protect themselves and the information that they contain from unauthorized disclosure, modification, and use. In addition, denial of service to legitimate users could be considered a significant threat in many service and time-critical application systems and the CKMS used to protect them. Additional security requirements can be derived from the organizational goals for protecting personal privacy, including anonymity, unlinkability, and unobservability of CKMS-supported communications. The information SP 800-130 August 2013 used by these systems requires protection when it is at rest, when it is being processed within a protected facility, and also when it is transported from one location to another. Cryptography is often used to protect information from unauthorized disclosure, to detect unauthorized modification, and to authenticate the identities of system entities (e.g., individuals, organizations, devices or processes). Cryptography is particularly useful when data transmission or entity authentication occurs over communications networks for which physical means of protection (i.e., physical security techniques) are often costprohibitive or even impossible to implement. Thus, cryptography is widely used when business is conducted or when sensitive information is transmitted over the Internet.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_01077", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-1 in Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers? (Part 21) Control CM-1: d authentication capabilities, assesses information about the purchase and the returning purchaser \u02bc s profile, and determines if MFA is required from the purchaser to complete shopping-cart checkout. These policies and processes are accomplished by Magento and StrongKey CryptoEngine (SKCE) Version 2.0 Open Source FIDO U2F server interaction [26]. | ID.RA-4, ID.RA- 5 | | Risk Engine | RSA Adaptive Authentication (Cloud) Version 13.1 [27] | Uses data science to provide transaction analysis and response, prompting the returning purchaser to use U2F when the organization's risk threshold is exceeded during a transaction, providing a low-friction experience for the consumer to reduce fraud while minimizing the interruptions and denials that a consumer may encounter. | ID.RA-4, ID.RA- 5 | | MFA Mechanism | SKCE Version 2.0 Open Source FIDO U2F server [26] and TokenOne cloud- based Authentication Version 2.8.5 [28] | Provides a server-based enhanced- authentication capability as required by the risk assessment module (magfido) or for the e-commerce platform administrator (TokenOne).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, mfa, token. Contains security framework guidance for authentication systems. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_01078", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-7 in Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance? (Part 60) Control CM-7: .IP) | PR.IP-5 | Low Define, implement, and enforce policy and regulations regarding emergency and safety systems, fire protection systems, and environment controls for the manufacturing system. Fire suppression mechanisms should take the manufacturing environment into account (e.g., water sprinkler systems could be hazardous in specific environments). | These Subcategory requirements can be met by developing policies and procedures in the Fire and Safety Regulations section of the Cybersecurity Program document. | | PROTECT | Information Protection Processes and Procedures (PR.IP) | PR.IP-6 | Low Ensure that manufacturing system data is destroyed according to policy. | These Subcategory requirements can be met by implementing solutions that provide the Systems Development Lifecycle Management and Media Sanitization technical capabilities Potential solutions for meeting these Subcategory requirements include: Open- AudIT, LANSweeper, Spiceworks, OCSinventory-ng, AlienVault OSSIM, MS Excel (Manual), media sanitization tools. Solutions that were implemented in use cases: Open-AudIT DBAN | | PROTECT | Information Protection Processes and Procedures (PR.IP) | PR.IP-7 | Low Incorporate improvements derived from the monitoring, measurements, assessments, and lessons learned into protection process revisions. Ensure that the security plan for the manufacturing system facilitates the review, testing, and continual improvement of the security protection processes. | These Subcategory requirements can be met by developing policies and procedures in the Periodic Reevaluation of the Program section of the Cybersecurity Program document. | | PROTECT | Information Protection Processes and Procedures (PR.IP) | PR.IP-8 | Low Collaborate and share information about manufacturing system related security incidents and mitigation measures with designated sharing partners. Employ automated mechanisms where feasible to assist in information collaboration.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance."}]}
{"id": "nist_01079", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms say about 3.2.1 Block Cipher Algorithms? According to Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms, 3.2.1 Block Cipher Algorithms: A block cipher algorithm is used with a single key in an approved mode of operation to both apply cryptographic protection (e.g., encrypt) and to subsequently process the protected information (e.g., decrypt). Several block cipher algorithms have been approved by NIST as cryptographic primitives, some of which are no longer approved for applying cryptographic protection. However, they may still be needed for processing information that was previously protected (e.g., they may be needed for decrypting previously encrypted information). The block cipher algorithms are discussed in Sections 3.2.1.1 through 3.2.1.4. A pproved modes of operation are discussed in Section 3.2.1.5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms."}]}
{"id": "nist_01080", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Random Number Generation Using Deterministic Random Bit Generators say about Information retained within the DRBG mechanism boundary after generation:? According to Recommendation for Random Number Generation Using Deterministic Random Bit Generators, Information retained within the DRBG mechanism boundary after generation:: Replaced internal state values (i.e., the new working\\_state ).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Number Generation Using Deterministic Random Bit Generators."}]}
{"id": "nist_01081", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2 Authority according to NIST Recommendation for Existing Application-Specific Key Derivation Functions According to Recommendation for Existing Application-Specific Key Derivation Functions, 2 Authority: This publication has been developed by the National Institute of Standards and Technology (NIST) in furtherance of its statutory responsibilities under the Federal Information Security Management Act (FISMA) of 2002, Public Law 107-347. NIST is responsible for developing standards and guidelines, including minimum requirements, for providing adequate information security for all agency operations and assets, but such standards and guidelines shall not apply to national security systems. This Recommendation has been prepared for use by federal agencies. It may be used by non-governmental organizations on a voluntary basis and is not subject to copyright. (Attribution would be appreciated by NIST.) Nothing in this document should be taken to contradict standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. Conformance 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: Recommendation for Existing Application-Specific Key Derivation Functions."}]}
{"id": "nist_01082", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? (Part 209) Control HA-1: al signatures and encryption, respectively. PKCS 12 permits both software and hardware implementations. Hardware implementations offer physical security in tamper-resistant tokens such as smart cards. [1] ## FEDERAL PKI POLICY AUTHORITY The Federal PKI Policy Authority (FPKI-PA), under the auspices of the Federal Identity and Credentialing Committee (FICC), is responsible for the policies of the various Federal PKI implementations; the Federal PKI Bridge CA (FBCA), the Common Policy Framework CA (CPFCA), the eGovernance CA (eGOVCA) and the Citizen and Commercial Class CA (C4A). This paper will only discuss the relevancy of the FBCA and its concomitant Certificate Policy to the use of PKCS 12. The Federal Government is required to use cryptographic modules that have been accredited as meeting the NIST Federal Information Processing Standard 140 level 2 (FIPS 140-2) accrediting process [3]. Additionally any entities PKI that want to cross-certify with the FBCA must follow US Government PKI Cross-Certification Methodology and Criteria. [4]. Once an entity PKI has completed this process, they are required to sign a Memorandum of Agreement (MOA) with the FPKI-PA, which lays out the rights and responsibilities of both parties. One of the items in every MOA is the requirement that the entity PKI cross-certifying with the FBCA shall maintain compliance with the requirements in the MOA and shall notify the FPKI-PA if any material changes occur. ## ISSUES WITH THE USE OF PKCS-12 The FBCA Certificate Policy [5] is silent on the use of PKCS 12, so that its use does not apparently violate any of the requirements in the MOA. However, as we will discuss later, there are issues associated with private key protection and activation, which are application specific that must be addressed.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, token, sso. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_01083", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.5.8.1 Introduction of a New DKIM Key according to NIST Trustworthy Email According to Trustworthy Email, 4.5.8.1 Introduction of a New DKIM Key: When initially deploying DKIM for enterprise email, or a new email service to support an organization, an administrator should insure that the corresponding public key is available for validation. \ufffdus, the DNS entry with the DKIM public portion should be published in the sender's domain before the sending MTA begins using the private portion to generate signatures. \ufffde order should be: 1. Generate a DKIM key pair and determine the selector that will be used by the MTA(s). 2. Generate and publish the DKIM TXT RR in the sending domain's DNS. 3. Ensure that the DKIM TXT RR is returned in queries. 4. Configur e the sending MTA(s) to use the private portion. 5. Begin using the DKIM key pair with email.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Trustworthy Email."}]}
{"id": "nist_01084", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessment of Access Control Systems say about 4.2 Access Rules? (Part 1) According to Assessment of Access Control Systems, 4.2 Access Rules: 4.2 Access Rules As mentioned in Section 3.5, RuBAC can be established by any attributes of a system related to the users such as domain, host, protocol, network, or IP address. For example, a user wants to access an object in another network on the other side of a router. The router employs RuBAC with the rule composed by the network addresses, domain, and protocol to decide whether or not the user can be granted access. So, if an employee changes his or her role within the organization, the existing authentication credentials remain in effect and do not need to be re configured. Using rules in conjunction with roles adds greater flexibility because rules can be applied to people as well as devices. When applying RuBAC in a distributed system for access control, it is important to decide which attributes of the system to use for the rule constraints, so that there will not be conflicts in rule setting that lead to privileges leaking. Therefore, rule-based algorithms need to be devised. For example, suppose that two of the primary types of software users are product engineers and quality engineers. Both groups usually have access to the same data, but they have different roles to perform in relation to the data and the application's function. In addition, individuals within each group have different job responsibilities that may be identified using several types of attributes such as weapon programs and manufacturing areas. To avoid confusion, applicationspecific position codes and access profile rules are maintained for each user. When storing the data object, the data owner identifies attributes that describe the document's content and purpose. At the time of application execution, the user position codes and user's profiles are matched with document attributes to determine the user's access right.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Assessment of Access Control Systems."}]}
{"id": "nist_01085", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Policy Machine_ Features, Architecture, and Specification say about 3.5 Obligations? (Part 1) According to Policy Machine_ Features, Architecture, and Specification, 3.5 Obligations: 3.5 Obligations Obligations represent potential changes to the authorization state of the policy. They are used when one or more administrative actions need to be carried out under a specific, known set of circumstances. Events are the means by which obligations are triggered. An event occurs each time a requested access executes successfully. Information related to the event is called the event context and is used by the PM to process obligations. The process identifier, identifier of the associated user, access operation, and sequence of arguments of the triggering event are mandatory and always returned as part of the event context. Other information conveyed via the event context varies based on the type of event that occurred and may include items such as the containing attributes of targeted policy elements (e.g., those pertaining to an object that was deleted), or the types of certain arguments used in an access request (e.g., for a resource access, the type of object (file, message, etc.) accessed. The two main components needed to define an obligation are an event pattern and a response. The pattern and response elements each denote a sentence in a grammar that respectively expresses the triggering conditions of an event pattern and the administrative actions of the response. The event pattern and response each represents sentences that must conform to a formal language over their respective alphabet. That is, the syntax of the sequence of symbols for each item must be well formed according to its respective grammar. The obligation relation, OBLIG, is defined as a ternary relation from U to PATTERN to RESPONSE. For each tuple (u, pattern, response) of the obligation relation, u represents the user that established the pattern and response, and under whose authorization the response is carried out.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Policy Machine_ Features, Architecture, and Specification."}]}
{"id": "nist_01086", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)? (Part 9) Control PD-12: sks and sub-tasks. ## 2. PREPARATION FOR ASSESSMENT AND AUTHORIZATION This chapter presents the fundamentals of an authorization of a PIV Card Issuer (PCI) and a Derived PIV Credential Issuer (DPCI). It includes: (i) definitions of an issuer and issuing facility; (ii) outsourcing issuer services or functions; (iii) the differences between an assessment and authorization; (iv) authorization boundaries of an issuer; (v) roles and responsibilities; (vi) the relationship between authorization under [SP 800-37-1] and SP 800-79-2; (vii) preparing for the assessment; (viii) types of authorization decisions; (xi) use of risk in the authorization decision; and (x) the contents of the authorization package. ## 2.1 Issuer At the highest level, an issuer provides a full set of functions required to produce, issue, and maintain PIV Cards or Derived PIV Credentials for an organization. A PCI or DPCI is considered operational if all relevant roles and responsibilities have been defined and appointed; suitable policies and compliant procedures have been implemented for all relevant PIV processes, 5 including sponsorship, identity proofing/registration, adjudication, card/token production, activation/issuance, and maintenance; and information system components that are utilized for performing the above-mentioned functions (processes) have been assessed and shown to meet all technical and operational requirements prescribed in FIPS 201-2 and related documents. In order to comply with Homeland Security Presidential Directive 12 ([HSPD-12]), an organization must first establish an issuer, to issue PIV Cards or Derived PIV Credentials, which conforms to and satisfies the requirements of FIPS 201-2 and related documents. The issuer must then be authorized (i.e., using the guidelines specified in this document). An organization has certain flexibility in implementing its issuance functions.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, token. Contains security framework guidance for authentication systems. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_01087", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control UI-64 in Guidelines for the Secure Deployment of IPv6? (Part 267) Control UI-64: orts used by other customers. This may be more difficult to 59 See the current version of the IETF Internet Draft, Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion , Work in Progress . detect and to mitigate without a complete system for authentication by port number, which would represent a huge security requirement. For a description of an analogous attack, see the Java-based attack described by Martin et al. 60 Some attack mitigation strategies block an IPv4 address (temporarily or permanently) after detecting an improper use. Thus, the carrier-grade NAT needs to protect other customers using the same address by making sure that a single user of a shared address cannot trigger such a response. Finally, a carrier-grade NAT needs to enforce ingress filtering of IPv6 traffic to prevent IPv6 spoofing. ## 6.6 Translation Translation consists of transforming IPv4 or IPv6 packets into the other protocol so they can be routed or transmitted across a network. Network Address Translation-Protocol Translation (NAT-PT) allows IPv6 and IPv4 devices to communicate via an intermediate translation device. Transport Relay Translator (TRT) is another mechanism to allow IPv6 hosts to communicate with IPv4 hosts through an intermediary. Translation mechanisms (IPv4 to IPv6 and IPv6 to IPv4) introduce new methods to construct networks and systems and thus enlarge the set of possible attacks against those networks and systems. Protocol translation is not recommended as a strategic approach to transitioning from IPv4 to IPv6 for a variety of reasons. Translating IPv6 into IPv4 effectively negates most of the compelling reasons for transitioning to IPv6 in the first place. Hierarchical routing, expanded address space, streamlined packet headers, and IPv6 mobility are all lost when translating IPv6 into IPv4. Translation does not solve the IPv4 address space exhaustion problem.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_01088", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings say about 4th Annual PKI R&amp;D Workshop -- Proceedings? According to 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings, 4th Annual PKI R&amp;D Workshop -- Proceedings: Secure Electronic Signature Regulations, draft, Canada Gazette Part I, 2004. Available at I/2004/20040508/html/regle6e.html account a business may have. 2 The Australian Business Number (ABN) is a unique 11 digit identifier issued by the Australian Tax Office (ATO) to all entities registered in the Australian Business Register. It is used when dealing with the ATO, other government agencies, and when supplying goods and services to other businesses. usertype=BC 3 Here we distinguish between registration - the process of obtaining an epass from epass Canada - and enrolment - the action of signing up or applying for a Government of Canada service.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_01089", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identity and Access Management for Electric Utilities provide? (Section 211) b l l i i c c a a t t i i o o n n i i s s a a v v a a i i l l l l a a b b e e f f r r e e e e o o f f c c h h a a r r g g e e f f r r o o m m : : h h t t t t p p : : / / / / d d o o i i . . . . o o r r g g / / 1 1 0 0 6 6 0 0 2 2 8 8 / / N N I I S S T T . . S S P P 1 1 8 8 0 0 0 0 - - 2 2 . . . . ip dhcp snooping dot1x system-auth-control ! diagnostic bootup level minimal spanning-tree mode pvst spanning-tree extend system-id ! redundancy mode sso ! ! ip ssh version 2 ! class-map match-any non-client-nrt-class match non-client-nrt ! policy-map port_child_policy class non-client-nrt-class bandwidth remaining ratio 10 snmp trap mac-notification change added spanning-tree portfast ! ip access-list extended ACL-DEFAULT remark Allow DHCP permit udp any eq bootpc any eq bootps remark Allow DNS permit udp any any eq domain permit icmp any any permit tcp any host 172.16.4.77 eq 8443 permit tcp any host 172.16.4.77 eq 443 permit tcp any host 172.16.4.77 eq www permit tcp any host 172.16.4.77 eq 8905 permit tcp any host 172.16.4.77 eq 8909 permit udp any host 172.16.4.77 eq 8905 permit udp any host 172.16.4.77 eq 8909 deny ip any any ip access-list extended ACL-WEBAUTH-REDIRECT permit tcp any any eq www permit tcp any any eq 443 deny ip any any ! NIST SP 1800-2C: Identity and Access Management for Electric Utilities 43 T T h h i i s s p p u u b b l l i i c c a a t t i i o o n n i i s s a a v v a a i i l l l l a a b b e e f f r r e e e e o o f f c c h h a a r r g g e e f f r r o o m m : : h h t t t t p p : : / / / / d d o o i i . . . . o o r r g g / / 1 1 0 0 6 6 0 0 2 2 8 8 / / N N I I S S T T . . S S P P 1 1 8 8 0 0 0 0 - - 2 2 . . . . logging origin-id ip logging source-interface GigabitEthernet1/0/48 !", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_01090", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI) say about APPENDIX C: ISSUER READINESS REVIEW CHECKLIST? (Part 3) According to Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI), APPENDIX C: ISSUER READINESS REVIEW CHECKLIST: orization to operate in accordance with [SP 800-37-1]. | Make sure that the information systems utilized by the issuer have been assessed and authorization to operate in accordance with [SP 800-37-1]. | | | | Ensure that the following documentation has been developed and can be made available to the assessment team: | Ensure that the following documentation has been developed and can be made available to the assessment team: | | | | (i) | Operations plan | | | | (iii) | authorization decisions for the issuer Letters of appointment (if any) | | | | (iv) | Service Level Agreements (SLA) and Memorandums of Understanding (MOU) between the organization and the service provider(s).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_01091", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) provide? (Section 101) ted process. - u) Trusted association protections: The following may need to be provided for each trusted association protection: - i. The mechanism used for integrity protection, and - ii. The mechanism used for source authentication. - v) Date-Times: - i. The generation date, - ii. The association date, - iii. The activation date, - iv. The future activation date, - v. The renewal date, - vi. The future renewal data, - vii. The date of the last rekey, - viii. The future rekey date, - ix. The date of the last usage of the key, - x. The deactivation date, - xi. The future deactivation date, - xii. The expiration date, - xiii. The revocation date, - xiv. The compromise date, - xv. The destruction date, and - xvi. The future destruction date. - w) Revocation Reason. These metadata elements specify a key's important characteristics, its acceptable uses, and other information that is related to the key. This information is used by an FCKMS when managing and protecting the key. Metadata elements relevant to the management and use of a key should be correctly associated with a key and used whenever a key is stored, retrieved, loaded into a cryptographic module, used to protect data (e.g., other keys), exchanged with peer entities authorized to use the key, and when assuring that a key is correctly protected. FR:6.2 For each key type used in the system, the CKMS design shall specify all metadata elements selected for a trusted association, the circumstances under which the metadata elements are created and associated with the key, and the method of association (i.e., cryptographic mechanism or trusted process). FR:6.3 For each cryptographic mechanism used in the Key Protections metadata element (item s above), the CKMS design shall specify the following: - i. The cryptographic algorithm: See item g) above. - ii. The parameters for the key: See item i) above. - iii. The key identifier: See item b) above. - iv.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_01092", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services say about 4.3.2. Security Continuous Monitoring Category? (Part 5) According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services, 4.3.2. Security Continuous Monitoring Category: | and minimum detectable limits. Analysis of the correlation engines may be able to determine if some faults can remain undetected. These findings can be used in the risk management procedures. Consider providing a loopback reference timing signal to continuously monitor for changes in the total network and signal propagation delay. Within a specified time, alert dependent users and applications when monitoring is unavailable or when PNT data or service is unavailable. Software and hardware can be integrated into the PNT system and critical infrastructure components to detect and mitigate GNSS jamming and spoofing events and preserve PNT data availability, continuity, and integrity. Physical access to PNT devices and components is actively monitored to detect potential breaches in security. Actively monitor | DHS GPS CI ICAO 9849 5.3.7 Kaplan 10 | | CM-3: Personnel activity is monitored | the physical environment to include the RF environment. PNT devices and equipment may be in remote locations. Positively identify people who access areas that contain PNT devices. Where feasible, implement the use of access controls that are specific to personnel, such as swipe cards and personal identification numbers (PINs). Monitor personnel actions for unauthorized activity on or using PNT systems or data. The scope of the monitoring can include elements such as login attributes (e.g., time, physical location, | NIST SP 800-53 Rev. 5 CA-7, PE-6, PE-20 NIST SP 800-53 Rev.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_01093", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges provide? (Section 45) ing for your organization and contractors (nonfederal individuals) supporting your organization unless explicitly categorized as one or the other (i.e., 'federal employees' or 'contractor employees'). The term security will be used as a shorthand for 'cybersecurity' or 'information security.' Reference to physical security or personnel security is different and will be labeled as such. Role-based training activities provide security and privacy information to organizational employees who have significant security responsibilities. This type of training is not to be confused with security or privacy awareness activities that involve security/privacy information targeted at the general workforce within the organization. - Training on specific tools required for employees to perform security-related job duties - Training for employees who have privileged access to applications or systems - Training for oversight roles such as information systems security officer (ISSO), information systems security manager (ISSM), or auditors - Training for employees who manage access and authorizations to applications and systems - Training on organizational policies and procedures related to security and privacy configurations, settings, controls, etc. - Cybersecurity for employees in leadership positions, such as 'Cybersecurity for Executives,' Cybersecurity for System Owners,' or 'Becoming A Chief Information System Officer' - General-user annual security or privacy awareness training - Leadership or management training not related to security - Coding/software development classes - Organizational orientation and onboarding briefings - Training on tools not having a security purpose As a reminder, in order to maintain anonymity, when responding to open-ended questions, please do not include any information that might identify you or your organization. However, should you accidentally include such information, the researchers will redact it from the research record. 3.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso, privileged access. Contains security framework guidance for authentication systems. Source: Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges."}]}
{"id": "nist_01094", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2007 Annual Report provide? (Section 58) SC X 'key wrapping' standard that includes versions of the AESKW algorithm for use with AES and Triple DES. | Contacts: Ms. Shu-jen Chang (Hash functions) (301) 975-2940 shu-jen.chang@nist.gov | Dr. Morris Dworkin (301) 975-2354 morris.dworkin@nist.gov | |--------------------------------------------------------------------------------------|-------------------------------------------------------------| The requirements for key management continue to expand as new types of devices and connectivity mechanisms become available (e.g., laptops, broadband access, Blackberries). We continue to address the needs of the federal government by defining the basic principles required for key management, including key establishment, wireless applications, and the Public Key Infrastructure (PKI). Modifications were made to SP 800-57, Recommendation for Key Management-Part 1: General , which included an indication of the appropriate hash functions to be used for additional applications, depending on the security strength. Parts 1 and 2 provide general guidance and best practices for the management of cryptographic keying material. Part 3 of SP 800-57 on application-specific guidance is under development and is expected to be available for initial public comment in 2008. Part 3 is intended to address the key management issues associated with currently available cryptographic mechanisms. Key management efforts have included the completion of SP 800-56A, Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography , and the commencement of a related document, SP 800-56B, Recommendation for Pair-Wise Key Establishment Schemes Using Integer Factorization Cryptography (e.g., RSA). As they become a more convenient way to access the Internet, wireless technologies are being more widely adopted by government agencies.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, key management, sso. Contains security framework guidance for authentication systems. Source: Computer Security Division 2007 Annual Report."}]}
{"id": "nist_01095", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i? (Part 157) Control ES-1: et-drafts/draft-zorn-radiuskeywrap-xx.txt). AES Key Wrap is specified in RFC 3394, Advanced Encryption Standard (AES) Key Wrap Algorithm , available at Figure 6-4. Standard IEEE 802.11 RSN Authentication Infrastructure <!-- image --> ## 6.3.3 Attacks on the Authentication Server Operating system security was not a major concern for pre-RSN WLANs because of the limited functionality of most APs. In an RSN, the core STA authentication function is performed on a separate authentication server, which typically runs on a sophisticated operating system such as UNIX, Linux, or Windows. A breach of the operating system or an application or service with operating system privileges could lead to a complete compromise of RSN security. Accordingly, WLAN security should include hardening of the servers that support the authentication process. 90 ## 6.4 EAP Multiplexing Model and Related Support Requirements This section provides additional information on the conceptual architecture of EAP for readers seeking a better understanding of how EAP works and how it interacts with other protocols. Readers who do not need this information should skip this section and proceed to Section 6.5. RFC 3748 provides a framework for EAP using a four-layer conceptual model described in Table 6-5. It is called the EAP multiplexing model because it describes how EAP can handle multiple EAP methods in the same EAP implementation. Table 6-5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i."}]}
{"id": "nist_01096", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007 provide? (Section 62) m Field size per occurrence and Minimum Occur count values for each record type. The length of the data shall be greater than or equal to the field's min size per occurrence times the min Occur count. | 1 | M | LengthMin::13.024 | Length(13.024) GTE MinSize(13.024) * MinOccurrences(13.024) | | | | | | Length_Minimum_ Tagged_Field | 9.1 (Table 8), 15.1 (Table 17), 18.1 (Table 31), 19.1 (Table 33), 22.1 (Table 37) | This requirement is inferred from the Tables describing the Minimum Field size per occurrence and Minimum Occur count values for each record type. The length of the data shall be greater than or equal to the field's min size per occurrence times the min Occur count. | 1 | M | LengthMin::13.999 | Length(13.999) GTE MinSize(13.999) * MinOccurrences(13.9999) | | | | | | Length_Minimum_ Tagged_Field | 9.1 (Table 8), 15.1 (Table 17), 18.1 (Table 31), 19.1 (Table 33), 22.1 (Table 37) | This requirement is inferred from the Tables describing the Minimum Field size per occurrence and Minimum Occur count values for each record type. The length of the data shall be greater than or equal to the field's min size per occurrence times the min Occur count.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007."}]}
{"id": "nist_01097", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Securing Radio Frequency Identification (RFID) Systems provide? (Section 24) antial productivity gains and efficiencies. These organizations and individuals include hospitals and patients, retailers and customers, and manufacturers and distributors throughout the supply chain. This document provides an overview of RFID technology, the associated security and privacy risks, and recommended practices that will enable organizations to realize productivity improvements while safeguarding sensitive information and protecting the privacy of individuals. While RFID security is a rapidly evolving field with a number of promising innovations expected in the coming years, these guidelines focus on controls that are commercially available today. RFID is a form of automatic identification and data capture (AIDC) technology that uses electric or magnetic fields at radio frequencies to transmit information. An RFID system can be used to identify many types of objects, such as manufactured goods, animals, and people. Each object that needs to be identified has a small object known as an RFID tag affixed to it or embedded within it. The tag has a unique identifier and may optionally hold additional information about the object. Devices known as RFID readers wirelessly communicate with the tags to identify the item connected to each tag and possibly read or update additional information stored on the tag. This communication can occur without optical line of sight and over greater distances than other AIDC technologies. RFID technologies support a wide range of applications-everything from asset management and tracking to access control and automated payment. Every RFID system includes a radio frequency (RF) subsystem, which is composed of tags and readers. In many RFID systems, the RF subsystem is supported by an enterprise subsystem that is composed of middleware, analytic systems, and networking services. RFID systems that share information across organizational boundaries, such as supply chain applications, also have an inter-enterprise subsystem.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_01098", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)? (Part 17) Control PD-12: as been established and the processes are in compliance with FIPS 201-2. This document identifies roles and responsibilities of key personnel involved in the assessment and authorization of an issuer. 10 Recognizing that organizations have widely varying missions and structures, there may be some differences in naming conventions for authorization-related roles and in how the associated responsibilities are allocated among personnel (e.g. one individual may perform multiple roles in certain circumstances). ## 2.6.1 Senior Authorizing Official (SAO) The Senior Authorizing Official (see Figure 2) of an organization is responsible for all operations. The SAO has budgetary control, provides oversight, develops policy, and has authority over all functions and services provided by the issuer. ## 2.6.2 Designated Authorizing Official (DAO) The Designated Authorizing Official has the authority within an organization to review all assessments of an issuer and its facilities, and to provide an authorization decision as required by [HSPD-12]. Through authorization, the DAO accepts responsibility for the operation of the issuer at an acceptable level of risk to the organization. The SAO may also fulfill the role of the DAO. The DAO shall not assume the role of the OIMO. ## 2.6.3 Organization Identity Management Official (OIMO) The Organization Identity Management Official is responsible for implementing policies of the organization, assuring that all PIV processes of the issuer are being performed reliably, and providing guidance and assistance to the issuing facilities. The OIMO implements and manages the operations plan; ensures that all roles are filled with capable, trustworthy, knowledgeable, and trained staff; makes certain that all services, equipment, and processes meet FIPS 201-2 requirements; monitors and coordinates activities with Issuing Facility Manager(s); and supports the authorization process.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, identity management, sso. Contains security framework guidance for authentication systems. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_01099", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance) provide? (Section 192) Reset the security status of the '96' key reference by sending the VERIFY command with - P2, key reference value is set to '96' - P1 parameter is 'FF' and both Lc and the data field are absent 4. Send VERIFY card command with - P2, key reference value is set to '97' - Data field of the command will contain a value that matches the Secondary Finger OCC value 5. Send GET DATA command with - Data field of the command containing the tag of the Printed Information data object 6. Reset the security status of the '97' key reference by sending the VERIFY command with - P2, key reference value is set to '97' - P1 parameter is 'FF' and both Lc and the data field are absent 7. Send GET DATA command with - Data field of the command containing the tag of the Printed Information data object 8. Send VERIFY card command with - P2, key reference value is set to '96' - Data field of the command will contain a random fingerprint value. The fingerprint is truncated so that the total length is less than 3 bytes times the minimum number of minutia specified in the BIT Group Template for key reference '96' 9. Send VERIFY card command with - P2, key reference value is set to '96' - Data field of the command will contain a random fingerprint value. The fingerprint is padded so that the total length is more than 3 bytes times the maximum number of minutia specified in the BIT Group Template for key reference '96' 10. Send VERIFY card command repeatedly until after the issuer specified maximum number of OCC tries is exceeded with - P2, key reference value is set to '96' - Data field of the command will contain an arbitrary, but correctly formatted, value that does not match the Primary Finger OCC value obtained from the vendor 11. Repeat steps 8-10 with key reference '97'. 1. The command returns the application property template with the status word '90 00' at the end. 2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)."}]}
{"id": "nist_01100", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security in ISDN say about 7.2 Standard Security Mechanisms Required for ISDN? According to Security in ISDN, 7.2 Standard Security Mechanisms Required for ISDN: A number of security mechanisms standards are needed for ISDN but need not be specific to ISDN. The OSI standards developed to provide the security mechanisms defined in IS 7498/2 should be utilized to the maximum extent possible. Specific security mechanisms are the subject of standards development efforts of the new JTC1/SC27. The following sections provide a brief overview of these security mechanisms.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security in ISDN."}]}
{"id": "nist_01101", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4. Conformance according to NIST Common Platform Enumeration_ Applicability Language Specification Version 2.3 According to Common Platform Enumeration_ Applicability Language Specification Version 2.3, 4. Conformance: Products and organizations may want to claim conformance with this specification for a variety of reasons. For example, vulnerability researchers may want to assert that they provide vulnerability applicability statements in the form of CPE Applicability Language statements. In relation to this, implementers may want to assert that their products have the ability to process applicability statements written using the CPE Applicability Language. This section provides the high-level requirements that a product or organization must meet if they are seeking conformance with this specification. The majority of the requirements listed in this section reference other sections in this document that fully define the high-level requirement.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Platform Enumeration_ Applicability Language Specification Version 2.3."}]}
{"id": "nist_01102", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain User-Controlled Identity Wallet : according to NIST A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems According to A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems, User-Controlled Identity Wallet :: A user-controlled identity wallet is an application that primarily allows a user to hold identifiers and credentials by storing the corresponding private keys. It also serves as an interface for entities to interact with one another. For example, the subjects can receive and approve credentials from the issuers and disclose presentations to relying parties. Actions can be initiated automatically through application programming interfaces (APIs) that may be triggered by a user through scanning QR codes. In certain systems, a user can fully originate identifiers offline, on their own, and directly in their identity wallet (see Section 4.4.1 on Identifier Architectures ). Identity wallets may take various forms, such as dedicated hardware wallets, mobile applications, or even paper wallets (private keys are simply printed out and kept in a safe location). They may also come natively in a browser, an operating system, or as extensions. Wallets that are proposed 'as a service' by a third-party holder that controls a user's private keys are called custodial wallets . In addition, identity wallets can act as control centers since entities can receive and decide whether to approve requests for verifiable information, thereby giving their consent to perform some action. They may also serve as gateways for accessing and using applications and services. See Section 6.4 on Ecosystem Convergence for more insight about interoperability and cryptographic schemes used to secure custodial wallets.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems."}]}
{"id": "nist_01103", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Annual Report 2018_ NIST_ITL Cybersecurity Program provide? (Section 2) o copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-206 Natl. Inst. Stand. Technol. Spec. Publ. 800-206, 31 pages (January 2020) CODEN: NSPUE2 This publication is available free of charge from: https:/ /doi.org/10.6028/NIST.SP.800-206 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. Any 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. All names are trademarks or registered trademarks of their respective owners.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Annual Report 2018_ NIST_ITL Cybersecurity Program."}]}
{"id": "nist_01104", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.3.1 CONFIGURATION MANAGEMENT POLICY AND PROCEDURES according to NIST Guide for Security-Focused Configuration Management of Information Systems According to Guide for Security-Focused Configuration Management of Information Systems, 2.3.1 CONFIGURATION MANAGEMENT POLICY AND PROCEDURES: The development of documented SecCM policy communicates senior management's expectations for SecCM to members of the organization through specific, measurable, and confirmable objectives. It is a top-down approach which defines what is required and what is not permitted with respect to using SecCM to manage and control information resources. While policy defines the objectives for what must be done, procedures describe how the policy objectives are met through specific actions and results. SecCM procedures are developed to describe the methodology and tasks for each activity that supports implementation of the SecCM policy. Documenting configuration management policy and procedures is performed during the Planning phase and supports the implementation of NIST [SP 800-53] control CM-1 Configuration Management Policy and Procedures .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_01105", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings say about Access Manager? According to 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings, Access Manager: The Access Manager is the central authentication and authorization mechanism used by other web services and resources. All requests for authentication, authoriz ation, and session state flow through this service. As shown in Figure 6, the Access Manager is the key component - bringing together disparate web services and resources.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, pki. Contains security framework guidance for authentication systems. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_01106", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Random Bit Generator (RBG) Constructions say about 2.1. RBG Security? (Part 1) According to Recommendation for Random Bit Generator (RBG) Constructions, 2.1. RBG Security: 2.1. RBG Security Ideal randomness sources generate identically distributed and independent uniform random bits that provide full-entropy outputs (i.e., one bit of entropy per output bit). Real-world RBGs are designed with a security goal of indistinguishability from the output of an ideal randomness source. That is, given some limits on an adversary's data and computing power, it is expected that no adversary can reliably distinguish between RBG outputs and outputs from an ideal randomness source. Consider an adversary that can perform 2 w computations (typically, these are guesses of the RBG's internal state) and is given an output sequence from either an RBG with a security strength of s bits (where s \u2265 w ) or an ideal randomness source. It is expected that an adversary has no better probability of determining which source was used for its random bits than <!-- formula-not-decoded --> where \u03b5 is negligible. In this recommendation, the size of the RBG output is limited to 2 64 output bits and \u03b5 \u2264 2 -32 . NIST Internal Report (IR) 8427 [NISTIR\\_8427] provides a justification for the selection of \u03b5 . An RBG that has been designed to support a security strength of s bits is suitable for any application with a targeted security strength that does not exceed s . An RBG that is compliant with this recommendation can support requests for output with a security strength of 128, 192, or 256 bits, except for an RBG3 construction (as described in Sec. 6), which can provide fullentropy output. 2 A bitstring with full entropy 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. They may be truncated to any length such that the amount of entropy in the truncated bitstring is equal to its length.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Bit Generator (RBG) Constructions."}]}
{"id": "nist_01107", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography? (Part 142) Control HA-3: tifier employed for that purpose. In particular, when an identifier is used to label party V during the key-agreement process, that identifier has a trusted association to party V's static public key. (In other words, whenever both the identifier and static public key of one participant are employed in the keyagreement process, they are associated in a manner that is trusted by the other participant.) When an identifier is used to label party U during the key-agreement process, it has been selected/assigned in accordance with the requirements of the protocol relying upon the use of the key-agreement scheme. The following is an assumption for using the derived keying material for purposes beyond the C(1e,1s) scheme itself. Party U has obtained assurance that party V is (or was) in possession of the appropriate static private key, as specified in Section 5.6.2.2.3. ## 6.2.2.1 dhOneFlow, C(1e, 1s, FFC DH) Scheme This section describes the dhOneFlow scheme. Assurance of secure key establishment using this scheme can only be obtained when the assumptions in Section 6.2.2 are true. In particular, it is assumed that party U has obtained the static public key yV of party V. In this scheme, each party has different actions, which are presented separately below. However, note that parties U and V must use identical orderings of the bit strings that are input to the key-derivation method. Party U shall execute the following actions to a) establish a shared secret value Z with party V, and b) derive secret keying material from Z . Actions: Party U generates a shared secret and derives secret keying material as follows: 1. Generate an ephemeral key pair ( rU, tU ) from the domain parameters D as specified in Section 5.6.1.1. Send the public key tU to party V. 2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}]}
{"id": "nist_01108", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain ADVERSARY EFFECTS according to NIST Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171, ADVERSARY EFFECTS: See [SP 800-160-2]: [ Preclude (Preempt); Expose (Detect)]. - 3.11.7e Develop a plan for managing supply chain risks associated with organizational systems and system components; update the plan [ Assignment: organization-defined frequency ].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_01109", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-11 in Guidelines for Smart Grid Cybersecurity? (Part 58) Control SI-11: Supreme Court concluded that the Maine PUC had resolved the privacy, trespass, and Fourth Amendment claims against the utility, but did not state exactly how the Maine PUC concluded that was the case. Finally, the Maine Supreme Court also affirmed that the plaintiffs\u2019 constitutional Fourth and Fifth Amendment claims brought against the Maine PUC were properly dismissed as without merit. Therefore, the Maine Supreme Court invalidated the portion of the Maine PUC\u2019s decision regarding health and safety, remanding it back to the Maine PUC for further proceedings to resolve that issue, and otherwise affirmed the rest of its decision. 5.3.2.5 Contractual Approaches and Issues Related to Consumer Agreements Opt-Out Provisions In response to both potential privacy and health concerns, some state legislatures and regulatory commissions have required that the customer be given the option to opt-out of smart meter implementation as part of a contract for service with a utility, or to have an installed smart meter 40 United States v. Jones, 565 US ___, 132 S.Ct. 945 (2012), p. 3 (Justice Sotomayor\u2019s concurring opinion p.5). 41 Golden Valley, 8922. 42 Golden Valley, 8922. 19 removed.43 Additionally, some utilities have voluntarily offered this option for their customers.44 The Friedman case discussed above reviewed the procedural grounds for a Maine PUC decision regarding proposed opt-out provisions. 5.3.3 Applicability of Existing Data Protection Laws and Regulations to the Smart Grid Personally identifiable information (PII) has no single, authoritative, legal definition. Fair Information Practice Principles (FIPPs) provide the most generally accepted, rather than legal, definition. However, as noted in above, there are a number of laws and regulations, each of which protects different specific types of information.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01110", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways provide? (Section 111) Such identification is not intended to imply special status or relationship with NIST or recommendation or endorsement by NIST or NCCoE; neither is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose. While NIST and the NCCoE address goals of improving management of cybersecurity and privacy risk through outreach and application of standards and best practices, it is the stakeholder's responsibility to fully perform a risk assessment to include the current threat, vulnerabilities, likelihood of a compromise, and the impact should the threat be realized before adopting cybersecurity measures such as this recommendation. National Institute of Standards and Technology Special Publication 1800-31C, Natl. Inst. Stand. Technol. Spec. Publ. 1800-31C, 128 pages, (April 2022), CODEN: NSPUE2 As a private-public partnership, we are always seeking feedback on our practice guides. We are particularly interested in seeing how businesses apply NCCoE reference designs in the real world. If you have implemented the reference design, or have questions about applying it in your environment, please email us at cyberhygiene@nist.gov. All comments are subject to release under the Freedom of Information Act. National Cybersecurity Center of Excellence 100 Bureau Drive Mailstop 2002 National Institute of Standards and Technology Gaithersburg, MD 20899 Email: nccoe@nist.gov The National Cybersecurity Center of Excellence (NCCoE), a part of the National Institute of Standards and Technology (NIST), is a collaborative hub where industry organizations, government agencies, and academic institutions work together to address businesses' most pressing cybersecurity issues. This public-private partnership enables the creation of practical cybersecurity solutions for specific industries, as well as for broad, cross-sector technology challenges.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_01111", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-1 in Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers? (Part 79) Control CM-1: provided to assist implementation. ## B.1 Availability of Skills An organization has a workforce able to implement the multifactor authentication (MFA) capabilities described in this practice guide. Work roles in the National Initiative for Cybersecurity Education (NICE) Cybersecurity Workforce Framework [18] are identified in Appendix A to assist organizations to see which work roles perform the tasks necessary to implement the capabilities contained in this practice guide. A NICE Framework work role is composed of specific knowledge, skills, and abilities required to perform tasks in that work role. ## B.2 Uniqueness of Lab Environment The example implementations were developed in a lab environment. They do not reflect the complexity of a production environment, and production deployment processes were not used. Before production deployment, it should be confirmed that the example implementation capabilities meet the organization's architecture, reliability, and scalability requirements. ## B.3 MFA Decreases Account Takeover Opportunities Using customer identification (ID) and password alone for authentication provides increased opportunities for account takeover, compared with the additional use of MFA. ## B.4 Web Browser and Returning Purchaser Accounts A web browser, not a mobile application, was used to make the purchase from the electronic commerce (e-commerce) platform's website. A returning purchaser had an account with the online retailer. ## B.5 Support of MFA Devices The purchaser expects the retailer to be committed to the continued use and support of Universal Second Factor (U2F) because the returning purchaser has invested time and/or expense in obtaining the authenticator device.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, mfa. Contains security framework guidance for authentication systems. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_01112", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security of SQL-Based Implementations of Product Data Exchange Using STEP provide? (Section 15) write up'. A user may read an object with a lower level; an object will be written with the highest level of any objects involved. For example, a user with SECRET clearance can read SENSITIVE objects. If that user uses a SECRET object and a SENSITIVE object as input, the output of the process will be labeled as SECRET. SQL can be used when a MAC policy is required, but not every SQL processor is suited to the task. SQL has no built in feature for handling labels, however nothing in the standard prevents an implementation from using and main- ^SQL does not require audit trail generation. This must be added as a value-added enhancement to the SQL processor. taining this information. First, an appropriate MAC implementation of SQL for the target OS is required. If the target OS is a MAC system, the Trusted Computing Base (TCB) subset architecture and Trusted Subject architecture can be used. If the target OS is not a MAC system, the integrity lock architecture is requiredfi. Add-on tools for detection and elimination of inference and aggregation are required. Authentication and auditing requirements are identical to those for role-based systems. The Clark-Wilson framework[CW89], the most complete model for integrity, specifies an access control policy which depends upon the user's identity, the program to be executed, and the set of data files that will be accessed. The critical programs are called trusted 'processes., or TPs, and the data files are known as constrained data items, or CDIs. Few systems support such complex access control decisions. The complexity of the access control decision closes the confidentiality loophole associated with the DAC policies. With DAC policies, user A may disclose information intended solely for user B. User B can then copy that information and make it available to anyone. In the Clark-Wilson framework it is possible to permit users to access an object, without allowing them to copy it.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, sso. Contains security framework guidance for authentication systems. Source: Security of SQL-Based Implementations of Product Data Exchange Using STEP."}]}
{"id": "nist_01113", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-1 in Cybersecurity Framework Manufacturing Profile? (Part 12) Control AC-1: lities or services that were impaired due to a cybersecurity event. The activities in the Recover Function support 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. The Manufacturing Profile for the Cybersecurity Framework presents detailed implementation language for the cybersecurity standards expressed in the Framework categories and subcategories. The Profile is intended to support cybersecurity outcomes based on business needs that the manufacturer has selected from the Framework Categories and Subcategories [2]. The Profile can be characterized as the alignment of standards, guidelines, and practices to the Framework Core in a practical implementation scenario. ## 4. Manufacturing Profile Development Approach The manufacturing profile was developed to be an actionable approach for implementing cybersecurity controls into a manufacturing system and its environment. The specific statements in the subcategories in Section 7 are derived from the security controls of the NIST SP 800-53 Rev.4 [4], and are customized to the manufacturing domain using relevant informative references. The general informative references of ISA/IEC 62443 [5] from the Framework are also listed in the References column. COBIT 5 is sourced for subcategories that have no corresponding 800-53 references. Additional input came from NIST SP 800-82, Rev. 2, both in section 6.2 (Guidance on the Application of Security Controls to ICS) and in Appendix G (ICS Overlay) [3]. For informative references to an entire control family, or set of controls (such as subcategory ID.GV-1's informative reference to all 'policy and procedures' controls), the approach took a holistic view of the controls comprising the family/set. Section 7 provides the customized CSF subcategory language developed using informative references relevant to the manufacturing domain.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, csf. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile."}]}
{"id": "nist_01114", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.8 Security Standards for Multi-Vendor Systems according to NIST Assessing Federal and Commercial Information Security Needs According to Assessing Federal and Commercial Information Security Needs, 4.8 Security Standards for Multi-Vendor Systems: Those interviewed felt that security standards that allow comprehensive implementation of security across a multi-vendor environment have failed to emerge. The possible standards would provide for: - o interfacing many systems, both present and future; - o a single user view of security services across a wide range of operating systems; and - o security features inter-operating with other security services on both local and remote machines, without the need to train users in new security products. The need to implement security should not limit an organization in choosing the best solution and integrating it into their existing system. Security technology must support users working effectively together. I !", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Assessing Federal and Commercial Information Security Needs."}]}
{"id": "nist_01115", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Technical Groups to Pt ovide Support according to NIST Proceedings of the Workshop of the Federal Criteria for Information Technology Security According to Proceedings of the Workshop of the Federal Criteria for Information Technology Security, Technical Groups to Pt ovide Support: The EB may establish and utilize special Technical Groups (TGs), as needed, to help develop q)ecific technical areas of the CC. These TGs will operate under the direction of the EB for the time needed to perform their assigned tasks. They will be staffed in a iqiresentative way, in a pattern like that of the EB.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Proceedings of the Workshop of the Federal Criteria for Information Technology Security."}]}
{"id": "nist_01116", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Usability of PIV Smartcards for Logical Access say about 5.2.4 Laptop Readers? According to Usability of PIV Smartcards for Logical Access, 5.2.4 Laptop Readers: Laptops with built-in readers, like the one in Figure 2 (right), appeared to be relatively problem-free. This was true for systems that were used off-site for telework or travel as well as for systems that were docked while on-site.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Usability of PIV Smartcards for Logical Access."}]}
{"id": "nist_01117", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Process: according to NIST Recommendation for Random Number Generation Using Deterministic Random Bit Generators According to Recommendation for Random Number Generation Using Deterministic Random Bit Generators, Process:: 1. If ( reseed\\_counter &gt; 100 000), then Return ('Reseed required', Null , V , Key , reseed\\_counter ). 2. If ( additional\\_input \u2260 Null ), then 3. 2.1 additional\\_input = Block\\_Cipher\\_df ( additional\\_input , 256). 4. 2.2 ( Key , V ) = CTR\\_DRBG\\_Update ( additional\\_input , Key , V ). Else additional\\_input = 0 256 . 3. temp = Null . 4. While ( len ( temp ) &lt; requested\\_number\\_of\\_bits ) do: 3. 4.1 V = ( V + 1) mod 2 128 . 4. 4.2 output\\_block = AES\\_ECB\\_Encrypt ( Key , V ). 5. 4.3 temp = temp || output\\_block . 5. returned\\_bits = leftmost ( temp , requested\\_number\\_of\\_bits ) 6. ( Key , V ) = CTR\\_DRBG\\_Update ( additional\\_input , Key , V ) 7. reseed\\_counter = reseed\\_counter + 1. 8. Return ('Success', returned\\_bits , V , Key , reseed\\_counter ).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Number Generation Using Deterministic Random Bit Generators."}]}
{"id": "nist_01118", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure provide? (Section 289) NIST IR 8473 October 2023 October 2023 Radio Frequency Respond Software Bill of Material Software Development Lifecycle Supervisory Control and Data Acquisition Supply Chain Risk Management Secure Digital Service Level Agreement Tactics, Techniques, and Procedures Tabletop Exercise Vehicle-To-Grid Extreme Fast Charging", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure."}]}
{"id": "nist_01119", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Description according to NIST Security Analysis of First Responder Mobile and Wearable Devices According to Security Analysis of First Responder Mobile and Wearable Devices, Description: A firefighter is responding to an emergency and utilizing their fully functional Public Safety Broadband Network (PSBN) device. Without warning, the PSBN device ceases to function, and the firefighter is unable to determine the cause of the malfunction or put the device in an operational state. To continue their duties, the firefighter uses their personal mobile device to conduct needed tasks, including downloading and logging into public safety applications.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Analysis of First Responder Mobile and Wearable Devices."}]}
{"id": "nist_01120", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Managing the Security of Information Exchanges say about 3.4 Discontinuing the Information Exchange? According to Managing the Security of Information Exchanges, 3.4 Discontinuing the Information Exchange: This section describes the process for discontinuing the information exchange, as shown in Figure 6. To the greatest extent possible, the information exchange is discontinued in a methodical manner to avoid system disruptions. Figure 6: Information Exchange Discontinue Phase <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Managing the Security of Information Exchanges."}]}
{"id": "nist_01121", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Automated Information System Security Accreditation Guidelines provide? (Section 2) s 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. 30 November 1989 | SECTION | SECTION | SECTION | PAGE | |------------------------------------------|------------------------------------------|---------------------------------------------------------|------------------| | PURPOSE | PURPOSE | PURPOSE | 1 | | DEFINITION | DEFINITION | DEFINITION | 1 | | RESPONSIBILITY | RESPONSIBILITY | RESPONSIBILITY | 1 | | THE REQUIREMENT | THE REQUIREMENT | THE REQUIREMENT | 2 | | DPI AND DPA IDENTIFICATION | DPI AND DPA IDENTIFICATION | DPI AND DPA IDENTIFICATION | 2 | | SCHEDULE | SCHEDULE | SCHEDULE | 5 | | | 1. | PROPOSED DATES | 5 | | | 2. | ACTUAL COMPLETION DATES | 6 | | | 3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Automated Information System Security Accreditation Guidelines."}]}
{"id": "nist_01122", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Criticality Analysis Process Model_ Prioritizing Systems and Components say about 3.1 Process A - Define Criticality Analysis Procedure? (Part 4) According to Criticality Analysis Process Model_ Prioritizing Systems and Components, 3.1 Process A - Define Criticality Analysis Procedure: ent, or criticality analysis experience; individuals who developed the criticality analysis model being tailored. Informed: Individuals responsible for conducting any part of the criticality analysis. | | Related processes outside of criticality analysis | [NIST SP 800-39] - (3.1) Framing Risk [NIST SP 800-160] - (3.3.1) Project Planning Process [NIST SP 800-161] - (2.2.1) Frame |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Criticality Analysis Process Model_ Prioritizing Systems and Components."}]}
{"id": "nist_01123", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does An Introduction to Information Security say about https://doi.org/10.6028/NIST.FIPS.199? (Part 6) According to An Introduction to Information Security, https://doi.org/10.6028/NIST.FIPS.199 /10.6028/NIST.SP.800-147 | | [SP800-152] | NIST Special Publication (SP) 800-152, A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) , National Institute of Standards and Technology, Gaithersburg, Maryland, October 2015, 147pp. https://doi.org/10.6028/NIST.SP.800-152 | | [SP800-155] | NIST Special Publication (SP) 800-155 (DRAFT), BIOS Integrity Measurement Guidelines , National Institute of Standards and Technology, Gaithersburg, Maryland, December 2011, 47pp. 155_Dec2011.pdf | | [SP800-160] | NIST Special Publication (SP) 800-160, Systems Security Engineering: Considerations for a Multidisciplinary Approach in the Engineering of Trustworthy Secure Systems , National Institute of Standards and Technology, Gaithersburg, Maryland, May 2016, 307pp. | | [SP800-161] | NIST Special Publication (SP) 800-161, Supply Chain Risk Management Practices for Federal Information Systems and Organizations , National Institute of Standards and Technology, Gaithersburg, Maryland, April 2015, 282pp. | | [SP800-162] | NIST Special Publication (SP) 800-162, Guide to Attribute Based Access Control (ABAC) Definition and Considerations, National Institute of Standards and Technology, Gaithersburg, Maryland, January 2014, 46pp.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, key management. Contains security framework guidance for authentication systems. Source: An Introduction to Information Security."}]}
{"id": "nist_01124", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach say about 4.6.3 Audit Survey? (Part 2) According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach, 4.6.3 Audit Survey: the risk to an acceptable level. The auditor's opinion is based on this assessment. The Validation, Verification, and Testing Plan provides the standards against which implementation will be measured. This plan defines the test conditions that will validate controls. This document will indicate how the project team plans to implement the controls. Assuming that the auditor has reviewed these documents, the two define precisely how the controls should be implemented, and thus provide the guideHnes for conducting the programming review. Training is an essential aspect of tlie proper performance of the operational MS. The auditor's concern in training is that the controls will be properly exercised. Thus, the analysis of the previously discussed two documents provides the background the auditor needs for evaluating training in the use of internal controls and security controls. 4.6.3.2 Review Programming and Training Phase Plans - Project teams which have firm implementation dates for AISs may need to make implementation compromises in order to meet those dates. If the project is late going into the Programming and Training Phase, the auditor could expect many of those compromises to occur. Two areas frequently compromised are implementation of internal and security controls (including documentation), and development of training programs. The elimination or curtailment of either or both of these areas may not directly impact the functional correctness of system outputs. In other words, the system may be able to produce the desired reports yet not in a controlled manner, or in an environment in which the users are trained. It is the intent of many project teams to install these areas after implementation. The auditor wants to ensure that the Project Plan is sufficient to guarantee that controls and training are adequately implemented. The plan should indicate who is responsible for these areas, and how they are to be implemented through specific documents.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach."}]}
{"id": "nist_01125", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Privacy Controls for Information Systems and Organizations provide? (Section 336) s: something you know (e.g., a personal identification number [PIN]), something you have (e.g., a physical authenticator such as a cryptographic private key), or something you are (e.g., a biometric). Multi-factor authentication solutions that feature physical authenticators include hardware authenticators that provide time-based or challenge-response outputs and smart cards such as the U.S. Government Personal Identity Verification (PIV) card or the Department of Defense (DoD) Common Access Card (CAC). In addition to authenticating users at the system level (i.e., at logon), organizations may employ authentication mechanisms at the application level, at their discretion, to provide increased security. Regardless of the type of access (i.e., local, network, remote), privileged accounts are authenticated using multi-factor options appropriate for the level of risk. Organizations can add additional security measures, such as additional or more rigorous authentication mechanisms, for specific types of access. Related Controls: AC-5, AC-6. (2) IDENTIFICATION AND AUTHENTICATION (ORGANIZATIONAL USERS) | MULTI-FACTOR AUTHENTICATION TO NON-PRIVILEGED ACCOUNTS CHAPTER THREE PAGE 132 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ Implement multi-factor authentication for access to non-privileged accounts. Discussion: Multi-factor authentication requires the use of two or more different factors to achieve authentication.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor. Contains security framework guidance for authentication systems. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01126", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3 say about 3.1.2 NIELSEN HOMESCAN: PROJECT APOLLO? (Part 2) According to NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3, 3.1.2 NIELSEN HOMESCAN: PROJECT APOLLO: Privacy Issues/Practices: - Privacy: There was a considerable amount of PII data. Survey participants are compensated in exchange for giving up segmentation data, demographics, and other information. - Security: There was traditional access security with group policy, implemented at the field level using the database engine, component-level application security, and physical access controls. - There were audit methods in place, but were only available to in-house staff. Opt-out data scrubbing was minimal.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3."}]}
{"id": "nist_01127", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1.1 Purpose and Scope according to NIST Guide to Malware Incident Prevention and Handling for Desktops and Laptops According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops, 1.1 Purpose and Scope: This publication is intended to help a wide variety of organizations understand the threats posed by malware and mitigate the risks associated with malware incidents. In addition to providing background information on the major categories of malware, it provides practical, real-world guidance on preventing malware incidents and responding to malware incidents in an effective, efficient manner. The information presented in this publication is intended to be used as data points entered into a much larger risk management process. See the latest version of NIST SP 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems for information on the basics of risk management. 1 This publication is based on the assumption that the organization already has a general incident response program and capability in place. See the latest version of NIST SP 800-61, Computer Security Incident Handling Guide for more information on general incident response. 2 NIST SP 800-61 serves as the foundation for this publication.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, incident response. Contains technical security guidance that could inform defensive posture. Source: Guide to Malware Incident Prevention and Handling for Desktops and Laptops."}]}
{"id": "nist_01128", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security in ISDN provide? (Section 87) pecial, secure ISDN networks, with secure switches, and secure trunks between switches, may be practical for special applications, but would not be practical in the context of the public ISDN network. However, the encryption need not stop at tlie netwoiic switch. TE-to-TE encryption, as illustrated in figure 23 is transparent to the network, and could be used between any two suitably equipped terminals, provided a 64 kbps unrestricted digital channel is available between them. A companion packet application protocol, possibly using the D channel during call set-up, is necessary for key management and authentication, to initialize the secure link. Symmetry would indicate that if there might be an ISPIB protocol, atop the B channel, then there might also be a similar ISPID protocol. Such a protocol does not appear to be practical, however, because it would confound the contention mechanism used to share the D channel on a passive bus. If complete B channel traffic flow confidentiality is required, this can be provided by the combination of the ISP2D and the ISPIB protocols. Finally, ISPO encryption at the bottom of the Physical layer is also possible, as illustrated in figure 24. In this case both B channels, the D channels and the associated framing, balance and control bits would all be encrypted in one 192 kbps stream. Encryption at this layer could not be end-to-end since the encrypted signal could not cross the NTl. In effect, the cryptographic device would be inserted in the NTl device and in front of the line card (see figs. 19 and 20) in the local office switch. This would have the advantage of denying an intruder between the NTl and the switch any traffic fiow information. It would be practical on a limited scale and would completely protect a user's confidentiality where it is most vulnerable, on his line between his premises and the telephone local office.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: Security in ISDN."}]}
{"id": "nist_01129", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Considerations for Voice Over IP Systems provide? (Section 16) their information, system operations, and continuity of essential operations when deploying VOIP systems. An especially challenging security environment is created when new technologies are deployed. Risks often are not fully understood, administrators are not yet experienced with the new technology, and security controls and policies must be updated. Therefore, agencies should carefully consider such issues as their level of knowledge and training in the technology, the maturity and quality of their security practices, controls, policies, and architectures, and their understanding of the associated security risks. These issues should be considered for all systems but are especially important with VOIP deployment for essential operations, such as systems designated \"high\" under FIPS 199, Standards for Security Categorization of Federal Information and Information Systems [2]. VOIP can provide more flexible service at lower cost, but there are significant tradeoffs that must be considered. VOIP systems can be expected to be more \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ vulnerable than conventional telephone systems, in part because they are tied in to the data network, resulting in additional security weaknesses and avenues of attack (see Appendix A for more detailed discussion of vulnerabilities of VOIP and their relation to data network vulnerabilities). Confidentiality and privacy may be at greater risk in VOIP systems unless strong controls are implemented and maintained. An additional concern is the relative instability of VOIP technology compared with established telephony systems. Today, VOIP systems are still maturing and dominant standards have not emerged. This instability is compounded by VOIP's reliance on packet networks as a transport medium. The public switched telephone network is ultra-reliable.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_01130", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 996) system developer; organiza\ue000onal personnel with boundary protec\ue000on responsibili\ue000es]. SC-07(22)-Test [SELECT FROM: Mechanisms suppor\ue000ng and/or implemen\ue000ng separate network addresses/di\ufb00erent subnets]. SC-07(23) BOUNDARY PROTECTION | DISABLE SENDER FEEDBACK ON PROTOCOL VALIDATION FAILURE ASSESSMENT OBJECTIVE: Determine if: SC-07(23) feedback to senders is disabled on protocol format valida\ue000on failure. CHAPTER FOUR PAGE 541 Reference produced from open data h\ue003ps://github.com/usnistgov/oscal-content T h i s p u b l i c a \ue000 o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h \ue003 p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P. 8 0 0 - 5 3 A r 5 NIST SP 800-53A, REV. 5 ASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS SC-07(23) BOUNDARY PROTECTION | DISABLE SENDER FEEDBACK ON PROTOCOL VALIDATION FAILURE POTENTIAL ASSESSMENT METHODS AND OBJECTS: SC-07(23)-Examine [SELECT FROM: System and communica\ue000ons protec\ue000on policy; procedures addressing boundary protec\ue000on; system design documenta\ue000on; system hardware and so\ue002ware; system architecture; system con\ufb01gura\ue000on se\ue001ngs and associated documenta\ue000on; system audit records; system security plan; other relevant documents or records]. SC-07(23)-Interview [SELECT FROM: System/network administrators; organiza\ue000onal personnel with informa\ue000on security responsibili\ue000es; system developer; organiza\ue000onal personnel with boundary protec\ue000on responsibili\ue000es]. SC-07(23)-Test [SELECT FROM: Mechanisms suppor\ue000ng and/or implemen\ue000ng the disabling of feedback to senders on protocol format valida\ue000on failure].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01131", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Web Transactions_ TLS Server Certificate Management provide? (Section 356) the inventory system and act upon the status of any certificate (e.g., report a certificate that is expired, about to expire, or does not conform to policy, or it can replace an expired certificate). It can also send expiration reports and notifications to certificate owners and can support disaster recovery by quickly replacing a large number of certificates located throughout the network architecture. The certificate manager can be used in conjunction with the CAs to enroll and provision certificates (and keys), store attributes with those certificates, and discover the absence of an expected certificate from a machine where it should be installed. The certificate manager can revoke certificates and change the owner associated with that certificate. The certificate network scanning tool can discover certificates not being managed by the inventory. The certificate log server can record all certificate and private-key management operations, including certificate creation, installation, and revocation; key pair generation; certificate requests and request approvals; certificate and key copying; and certificate and key replacement. All components in this portion of the architecture-except for the certificate database-are configured to use the HSM, which can securely generate, store, manage, and process the private key corresponding to the TLS server's certificate. The HSM is capable of storing and protecting the symmetric keys that secure sensitive data in the certificate database, and can generate, store, manage, and process internal CAs' signing keys. Figure 1-2 depicts the physical architecture of the example implementation deployed in the NCCoE laboratory.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_01132", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 988) curity responsibili\ue000es; organiza\ue000onal personnel with boundary protec\ue000on responsibili\ue000es; system users]. SC-07(12)-Test [SELECT FROM: Mechanisms implemen\ue000ng host-based boundary protec\ue000on capabili\ue000es]. T h i s p u b l i c a \ue000 o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h \ue003 p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P. 8 0 0 - 5 3 A r 5 CHAPTER FOUR PAGE 536 Reference produced from open data h\ue003ps://github.com/usnistgov/oscal-content NIST SP 800-53A, REV. 5 ASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS SC-07(13) BOUNDARY PROTECTION | ISOLATION OF SECURITY TOOLS, MECHANISMS, AND SUPPORT COMPONENTS ASSESSMENT OBJECTIVE: Determine if: SC-07(13)_ODP informa\ue000on security tools, mechanisms, and support components to be isolated from other internal system components are de\ufb01ned; SC-07(13) <SC-07(13)_ODP informa\ue000on security tools, mechanisms, and support components> are isolated from other internal system components by implemen\ue000ng physically separate subnetworks with managed interfaces to other components of the system. POTENTIAL ASSESSMENT METHODS AND OBJECTS: SC-07(13)-Examine [SELECT FROM: System and communica\ue000ons protec\ue000on policy; procedures addressing boundary protec\ue000on; system design documenta\ue000on; system hardware and so\ue002ware; system architecture; system con\ufb01gura\ue000on se\ue001ngs and associated documenta\ue000on; list of security tools and support components to be isolated from other internal system components; system audit records; system security plan; other relevant documents or records]. SC-07(13)-Interview [SELECT FROM: System/network administrators; organiza\ue000onal personnel with informa\ue000on security responsibili\ue000es; organiza\ue000onal personnel with boundary protec\ue000on responsibili\ue000es]. SC-07(13)-Test [SELECT FROM: Mechanisms suppor\ue000ng and/or implemen\ue000ng the isola\ue000on of informa\ue000on security tools, mechanisms, and support components].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01133", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Federal and Commercial Information Security Needs provide? (Section 51) portion of the evaluation themselves, the vast majority wanted an independent third party evaluation. A federal government-operated or commercial government-accredited process was the most desirable. Many factors contributed to each organization's attitude toward certification, including sensitivity of the applications, corporate culture, time and cost considerations, mission criticality, past experience with vendors, and availability of assessment sources. The vast majority of the organizations interviewed felt that administering computer security, particularly access control, was burdensome in a heterogeneous, distributed environment. Given their other responsibilities, this function took more time and effort than they felt was appropriate. Interviewees wanted computer security-related products that would easily implement organization security policy and manage security functions. These functions included centralized network security administration and single logon for network data and services. Organizations felt that improved security administrator interfaces were essential to balance the increasing need for protection and limitations on the staff resources devoted to it. Most organizations felt that vendors should provide a strong password management capability at the operating system level and it should be tailorable to specific environmental needs. Along with that, most felt NIST should continue to promote research on improving the integrity of the identification and authentication process. Technologies such as smart cards, signature verification, and voice authentication have a potential place in an overall approach to security. However, for most organizations, only a low-cost solution would be practical due to a large number of users. For EDI to be a practical alternative to the exchange of paper, organizations want specific assurances that EDI messages are authentic and properly authorized.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Assessing Federal and Commercial Information Security Needs."}]}
{"id": "nist_01134", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is https according to Domain Name System-Based Electronic Mail Security? https: //www.cvedetails.com/vulnerability-list/vendor\\_id-73/product\\_id-1950/version\\_id-8545/MacromediaFlash-Player-6.0.29.0.html.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_01135", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio say about Plan and Execute Risk Response Strategies? (Part 1) According to Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio, Plan and Execute Risk Response Strategies: Plan and Execute Risk Response Strategies The fifth step of the risk management life cycle is to determine the appropriate response to each risk. The goal of effective risk management, including ICT risks, is to identify ways to keep risk aligned with the risk appetite or tolerance in as cost-effective a way as possible. In this stage, the practitioner will determine whether the exposure associated with each risk in the register is within acceptable levels based on the potential consequences. If not, that practitioner can identify and select cost-effective risk response options to achieve ICT objectives. Planning and executing risk responses are iterative activities and should be based on the risk strategy guidance described in Sec. 3.1.3. As the risk oversight authorities monitor the success of those responses, they will provide operational leaders with financial and mission guidance to inform future risk management activities. In some cases, risk evaluation may lead to a decision to undertake further analysis to confirm estimates or more closely monitor results (as described in Sec. 5.1.2). Note that risk responses themselves may introduce new risks. For example, adding multi-factor authentication to a business system to reduce an access control risk may introduce a new risk of decreased productivity when users have difficulty authenticating. While there is some variance among the terms used by risk management frameworks, there are four types of actions available (as described in Table 5 ) for responding to negative ICT risks: accept, transfer, mitigate, and avoid . Table 5.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, multi-factor. Contains security framework guidance for authentication systems. Source: Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio."}]}
{"id": "nist_01136", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.2.7 Modems and Terminal Servers according to NIST SRI International_ Improving the Security of Your UNIX System According to SRI International_ Improving the Security of Your UNIX System, 2.2.7 Modems and Terminal Servers: Modems and terminal servers (terminal switches. Annex boxes, etc.) present still another potential security problem. The main problem with these devices is one of configuration - misconfigured hardware can allow security breaches. Explaining how to configure every brand of modem and terminal server would require volumes. However, the following items should be checked for on any modems or terminal servers installed at your site: 1. If a user dialed up to a modem hangs up the phone, the system shouir' him out. If it doesn't, check the hardware connections and the kernel configurauon of the serial ports. 2. If a user logs off, the system should force the modem to hang up. Again, check the hardware connections if this doesn't work. 3. If the connection from a terminal server to the system is broken, the system should log the user off. * Oo Sun systems, /infers/ is stored in lusrletclin.fingerd. On most other systems, it is called !etc!fingerd. 4. - If the terminal server is connected to modems, and the user hangs up, the terminal server should inform the system that the user has hung up. Most modem and terminal server manuals cover in detail how to properly connect these devices to your system. In particular you should pay close attention to the 'Carrier Detect,' 'Clear to Send,' and 'Request to Send' connections.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: SRI International_ Improving the Security of Your UNIX System."}]}
{"id": "nist_01137", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? (Part 28) Control HA-1: g able to use a finer grained distributed trust model, and of being able to use multiple origin site authorities (and private keys) to issue and sign the authentication and attribute assertions. In many origin sites a single back end LDAP server is the sole authoritative source for both authentication and attribute information. Typically Shibboleth sites implement stage one by issuing a Bind operation on their LDAP server, using the username and password provided by the user to the web login prompt. If the Bind succeeds, the user has been successfully authenticated against the password stored in the LDAP server. Stage two is implemented ## 4th Annual PKI R&amp;D Workshop -- Proceedings by searching the LDAP server for the attributes stored in the user's entry, and filtering these against the Shibboleth origin's attribute release policy before returning them to the Shibboleth target site as signed SAML attribute assertions. One can see that in such an implementation, and as a consequence of the Shibboleth trust model, the Shibboleth target site has no choice but to make access control decisions based on these attributes, without knowing who actually issued them to the user, whether they are still valid or not, or whether they are even the correct attributes for the particular user, since the user's name is not provided to the target site for privacy reasons. The Shibboleth origin doesn't trust anyone to see the attributes except the trusted targets, but even they are not allowed to see the binding between the attributes and the owner's identity. (The two reasons given for this in the Shibboleth documentation are user privacy and legal requirements for universities to protect a student's privacy). The target site thus has no option but to indirectly trust the contents of the origin site's LDAP server or other attribute repository, since it trusts the origin site directly.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_01138", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain SOFTWARE OOVKKKD according to NIST Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems According to Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems, SOFTWARE OOVKKKD: List each critical software (operating system and applications). What supports: | ID | Name | Version | Vendor | Language | |------|--------|-----------|----------|-------------| | | | | | Responsible |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems."}]}
{"id": "nist_01139", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Bluetooth Security provide? (Section 34) until after authentication, encryption, and authorization have been performed. Once a device has been authenticated, service-level authorization is not typically performed by a Security Mode 3 device. However, NIST recommends that servicelevel authorization should be performed to prevent 'authentication abuse'-that is, an authenticated remote device using a Bluetooth service without the local device owner's knowledge. All 2.0 and earlier devices can support Security Mode 3, but 2.1 and later devices can only support it for backward compatibility purposes. Similar to Security Mode 2, Security Mode 4 (introduced in Bluetooth 2.1 + EDR) is a service-levelenforced security mode in which security procedures are initiated after physical and logical link setup. Security Mode 4 uses Secure Simple Pairing (SSP), in which ECDH key agreement is utilized for link key generation (see Section 3.1.1). Until Bluetooth 4.0, the P-192 Elliptic Curve was used for the link key generation, and the device authentication and encryption algorithms were identical to the algorithms in Bluetooth 2.0 + EDR and earlier versions. Bluetooth 4.1 introduced the Secure Connections feature, which allowed the use of the P-256 Elliptic Curve for link key generation. In Bluetooth 4.1 the device authentication algorithm was upgraded to the FIPS-approved Hash Message Authentication Code Secure Hash Algorithm 256-bit (HMAC-SHA-256). The encryption algorithm was upgraded to the FIPS-approved AES-Counter with CBC-MAC (AES-CCM), which also provides message integrity. Security requirements for services protected by Security Mode 4 must be classified as one of the following: - Level 4: Authenticated link key using Secure Connections required - Level 3: Authenticated link key required - Level 2: Unauthenticated link key required - Level 1: No security required - Level 0: No security required.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Guide to Bluetooth Security."}]}
{"id": "nist_01140", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.2 HyTrust DataControl Setup according to NIST Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments According to Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments, 4.2 HyTrust DataControl Setup: Follow the directions on these pages: 1. Creating a Cloud VM Set 2. Installing [the Policy Agent] Interactively on Windows 3. Registering the Policy Agent Using the HyTrust Policy Agent GUI 4. Encrypting a Disk Using the webGUI", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments."}]}
{"id": "nist_01141", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Supporting Roles according to NIST_SP_800-37r2_Risk_Management_Framework? Supporting Roles: Senior Accountable Official for Risk Management or Risk Executive (Function); Authorizing Official or Authorizing Official Designated Representative; Information Owner or Steward; System Security Officer; System Privacy Officer.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_01142", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Section 404) ? | | Manufacturer | | How does the manufacturer assess, prioritize, and remediate reported product or service vulnerabilities? | | Manufacturer | | How does the manufacturer ensure that product or service vulnerabilities are remediated in a timely period to reduce the window of opportunity for attackers? | | Manufacturer | | Does the manufacturer maintain and manage a Product Security Incident Reporting and Response program (PSRT)? | | Manufacturer | | What is the manufacturer's process for ensuring that customers and external entities (such as government agencies) are notified of an incident when their product or service is impacted? | | Manufacturer | Define threat analysis as well as the criteria that will be utilized to assess the threat of the product, service, or supplier. Include a rubric with categorical definitions to encourage the transparency of assessment results. The C-SCRA threat analysis evaluates and characterizes the level of threat to the integrity, trustworthiness, and authenticity of the product, service, or supplier as described below. This analysis is based on a threat actor's capability and intent to compromise or exploit the product, service, or supplier being introduced into the supply chain. Following completion of the analysis, one of the following threat levels is assigned: - Critical: Information indicates that an adversarial or non-adversarial threat is imminent (e.g., an adversary is actively engaged in subversion, exploitation, or sabotage of the product, service, or supplier).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, threat actor, adversary. Contains technical security guidance that could inform defensive posture. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_01143", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-1 in Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers? (Part 46) Control CM-1: ltiple fields that collectively identify the goal of the test, the specifics required to implement the test, and how to assess the results of the test. Table 7-1 describes each field in the test case. Table 7-1 Test Case Fields | Test Case Field | Description | |--------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Parent Requirement | Identifies the top-level requirement, or the series of top-level requirements, leading to the testable requirement. | | Testable Requirement | Guides the definition of the remainder of the test case fields. Specifies the capability to be evaluated. | | Description | Describes the objective of the test case. | | Associated Test Cases | In some instances, a test case may be based on the outcome of (an)other test case(s). For example, analysis-based test cases produce a result that is verifiable through various means (e.g., log entries, reports, alerts). | | Associated Cybersecurity Framework Subcategories | Lists the Cybersecurity Framework Subcategories addressed by the test case. | | Preconditions | The starting state of the test case. Preconditions indicate various starting state items, such as a specific capability configuration required or specific protocol and content. | | Procedure | The step-by-step actions required to implement the test case.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_01144", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide for Security-Focused Configuration Management of Information Systems provide? (Section 62) isabling or uninstalling unused/unnecessary operating system (OS) functionality, protocols, ports, and services, and limiting the software that can be installed and the functionality of that software. Implementing secure configurations is part of the Identifying and Implementing Configurations phase of SecCM and supports the implementation of NIST [SP 800-53] controls CM-6 Configuration Settings and CM-7 Least Functionality. A baseline configuration is a set of specifications for a system, or Configuration Item (CI) within a system, that has been formally reviewed and agreed on at a given point in time, and which can be changed only through change control procedures. The baseline configuration is used as a basis for future builds, releases, and/or changes. The baseline configuration of a system may evolve over time depending on the stage of the system development life cycle (SDLC). Early in the SDLC when a system is being initiated and acquired, the baseline may be a set of functional requirements. As the system is developed and implemented, the baseline may expand to include additional configuration items such as the technical design, the software load, the architecture, and configurations of the system and its individual components. A baseline configuration may also represent different information computing environments such as development, test, and production. When a new baseline configuration is established, the implication is that all of the changes from the last baseline have been approved. Older versions of approved baseline configurations are maintained and made available for review or rollback as needed. Developing and documenting the baseline configuration for a system is part of the Identifying and Implementing Configurations phase of SecCM and supports the implementation of NIST [SP 800-53] control CM-2 Baseline Configuration.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_01145", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Conformance Test for FDDI Medium Access Control (MAC) say about Continued from previous page.? (Part 1) According to A Conformance Test for FDDI Medium Access Control (MAC), Continued from previous page.: Continued from previous page. | Behaviour Description | Label | Constraint Reference | V | Comments | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------| | # ? CLAIM START TRT # # # ! TOKEN # # # # # # ? TOKEN # 70THERWISE ?", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, token. Contains security framework guidance for authentication systems. Source: A Conformance Test for FDDI Medium Access Control (MAC)."}]}
{"id": "nist_01146", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways? (Part 61) Control AM-1: | Refs. | |--------|---------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------| | SM 2.4 | Does the system use or contain an option to enable the use of NIST- certified cryptographic standards for protecting data in transit? | Data in transit is encrypted using TLS version 1.2. | | | SM 2.5 | Does the system support performing regular backups and restorations? | Daily backups and snapshots of the production environment are taken and stored via Amazon's S3 service within multiple zones and U.S. regions. Regular integrity checks occur through restorations occurring multiple times annually. These restores populate new production instances which are then verified and monitored. | | | SM 3.1 | Does the product list all software dependencies and currently installed applications/services? | The Lookout MES Console provides a full application inventory list of all devices within the customer's user fleet. | | | SM 3.2 | Does the platform allow for the deployment of patches and OS updates? | Patches to the Lookout MES Console are controlled and maintained by Lookout backoffice support. | | | SM 4.1 | Does the security tool support logging and sending that data to rsyslog or a SIEM?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_01147", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Trust Considerations for Digital Twin Technology provide? (Section 18) tion is the process of digital twin definition authoring and encoding. While it may be possible to author definitions using a text editor, this practice could become supplanted by more advanced tools. This is similar to how not many people hand-code HTML or XML anymore [7]. Moreover, the complexity of digital twin definitions could entirely preclude the ability to craft definitions by hand. Many industries use sophisticated software applications to create digital artifacts that represent what they plan to build. Some of these software applications support the 'export' of their artifacts in standard file formats and encodings, such as the 3D PDF standard [8]. However, the majority of these applications use their own proprietary file formats and encodings to define, capture, and persist the models, drawings, and various artifacts that they create. Like existing commercial applications, any future digital twin standard should include a language for describing and defining a digital twin, including formal grammar , syntax , and semantics . It would have to be comprehensive enough to support the definition of artifacts to represent any arbitrary real-world entity that a digital twin can represent [5]. Most likely, a standard would accommodate the creation of static and dynamic 2D, 3D, VR, and AR models for visual presentation to human users. It may also accommodate the creation, manipulation, and persistence of presentation forms that are intended for machine rather than human consumption. Digital twin definitions will likely be available from libraries to enable reuse by software applications. Software can execute a digital twin definition to create a specific instantiation linked to a real-world object. Software can both read and modify digital twin definitions and their instantiations, which would allow for modeling, simulation, monitoring, and other applications.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Trust Considerations for Digital Twin Technology."}]}
{"id": "nist_01148", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.1.10.1 Local Domain A uthority ID Check according to NIST Secure Data Network Systems (SDNS) Access Control Documents According to Secure Data Network Systems (SDNS) Access Control Documents, 4.1.10.1 Local Domain A uthority ID Check: Inputs: Local Primary Certificate LDA ID Remote Primary Certificate LDA ID Outputs: Common LDA = Pass/Fail Functionality: The function of the LDA ID Check is to determine if the LDA identified in both the Local and Remote Primary Certificate is the same. The Local Domain Authority Identifier field within the Primary Certificate will contain the ID of the LDA associated with that Primary Certificate (assuming there is an LDA associated with this certificate, otherwise the field will be null). If either the LDA ID found in both Primary Certificates is null or the LDA ID in both Primary Certificates is found to be different, then an AV is not used for this association, LDA Check = Fail, and the Additional Access Control Information function is called to perform its processing. If the LDA ID is found to be the same in both Primary Certificates, then LDA Check Pass, and the AV' Implemented Check function is called to perform its processing.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Access Control Documents."}]}
{"id": "nist_01149", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Introduction to Cybersecurity for Commercial Satellite Operations provide? (Section 5) | Executive Summary................................................................................................................. 1 | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| | Purpose and Scope.................................................................................................... | Report Structure ......................................................................................................... 2 | Purpose and Scope.................................................................................................... | | | Conceptual High-Level Architecture of Satellite Operations ........................................ | Space Architecture Segments ....................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Introduction to Cybersecurity for Commercial Satellite Operations."}]}
{"id": "nist_01150", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Weaknesses: according to NIST Guidelines for Securing Radio Frequency Identification (RFID) Systems According to Guidelines for Securing Radio Frequency Identification (RFID) Systems, Weaknesses:: - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Adversaries can often obtain valuable information from the identifier alone. For example, knowledge of the EPC manager ID and object class bits in certain EPC formats may reveal the make and model of a tagged object concealed in a container. An adversary might target containers based on the perceived worth of their contents. - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Placing data in the enterprise subsystem makes the availability of that data contingent on the availability of the network. Retrieving data over a network also introduces a small delay, which could be unacceptable for some applications. Section 3.3.3 discusses why organizations might choose to store data on tags even after taking into consideration the risks of doing so.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_01151", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain C O M P U T E R S E C U R I T Y according to NIST Directions in Security Metrics Research According to Directions in Security Metrics Research, C O M P U T E R S E C U R I T Y: Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 April 2009 <!-- image --> U.S. Department of Commerce Gary Locke, Secretary National Institute of Standards and Technology Patrick D. Gallagher, Deputy Director", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Directions in Security Metrics Research."}]}
{"id": "nist_01152", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control II-4 in Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out? (Part 46) Control II-4: prove the plan or return it for revision. Task 2 will not begin before plan approval. ## Task 2 - Perform Data Collection The Contractor shall perform data collection according to the SCAR Work plan. This data will include at a minimum for the &lt;Appiication Name&gt;: - o OMB Bulletin 90-08 Computer Security and Privacy Plan; - o assignments of responsibility; - o security specifications; - o design reviews and test results; - o audits results and certification and accreditation statements; and - o contingency plans. ## Task 3 - Prepare SCAR Report The Contractor shall analyze the information collected during Task 2 and prepare a SCAR report. The SCAR report shall contain the following: - o an executive summary of not more than two pages; - o a discussion of the objectives and authority for the review; - o a description of the appiication and its criticality and sensitivity status at the time the review was conducted; - o the identified strengths and weaknesses in the application's security/internal control procedures (automated and manual); - o the recommendations for improvements (if any), rated as to their potential effect on the security environment (low, moderate, high) and an implementation priority proposal; and - o a draft certification statement which includes the Contractor's recommendation whether the application should be certified acceptable, not acceptable, or acceptable with qualification. If the Contractor makes a recommendation of certification with qualification, the draft certification statement shall also include those recommendations that must be implemented to obtain an unqualified acceptable certification. The Contractor shali deliver the SCAR Report to the COTR. ## DELIVERABLES (NOTE; See Appendix G for a sample text on SOIA/ deliverables.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out."}]}
{"id": "nist_01153", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6.2.10 De-Identification according to NIST Security Architecture Design Process for Health Information Exchanges (HIEs) According to Security Architecture Design Process for Health Information Exchanges (HIEs), 6.2.10 De-Identification: Definition: To ensure that individuals' records have all data elements removed before the data is shared for statistical, research, public health, or other reasons that do not benefit the data subject directly, and for which no authorization has been provided, such that there is no reasonable basis to believe that the information can be used to identify an individual. De-identification can be accomplished by removing the data permanently (anonymization); permanently replacing each data element removed with a placeholder, sometimes called a 'token' (pseudonymization); or replacing each datum with a unique token and maintaining a record (usually through a third party) such that it is possible to re-identify the individual through appropriate channels, such as having a third party contact the individual's care provider (reversible pseudonymization, or reidentification). Illustration: Researcher at Hospital wants to study the records of all patients with a particular form of cancer within a certain age range. The Researcher contacts their organization's research review board to confirm that the protocol will be conducted ethically and within all state, federal, and local laws and guidelines. The Researcher then contacts all providers in the HIE and asks them to help populate a database of de-identified information. Providers contact all patients fitting the profile and secure their consent. Each provider then uses the De-Identification enabling service to remove all potentially identifying information from each consenting patient's record, and then sends the record to Researcher. Thereafter, no further patient consent will be required to further share or disclose the de-identified data. Because ages are a relevant research parameter, birth years are retained in each record, although exact birth dates are removed. 11", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, token. Contains security framework guidance for authentication systems. Source: Security Architecture Design Process for Health Information Exchanges (HIEs)."}]}
{"id": "nist_01154", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Web Transactions_ TLS Server Certificate Management say about 4.3.1.1 Venafi Trust Protection Platform? (Part 3) According to Securing Web Transactions_ TLS Server Certificate Management, 4.3.1.1 Venafi Trust Protection Platform: - \uf0a7 agent-based automated certificate life-cycle management - \uf0a7 standard protocol support, including simple certificate enrollment protocol (SCEP) and ACME - \uf0a7 DevOps framework integration - \uf0a7 cloud platform integration, including Amazon Web Services and Azure - \uf0a7 Representational state transfer (REST)-based application programming interfaces (APIs) - \uf0a7 dual-control enforcement through workflow gates that can be applied at specific steps in the certificate life cycle, and can be assigned to groups and individuals with sufficient knowledge of application context to review and approve certificate requests - \uf0a7 integration with HSMs for private-key security - \uf0a7 integration with identity systems (e.g., Microsoft Active Directory, Lightweight Directory Access Protocol [LDAP] directories) - \uf0a7 central logging of all certificate management operations - \uf0a7 configurable event-based alerts, including delivery via simple mail transfer protocol, syslog, security incident and event management systems, ticketing systems, file, or database - \uf0a7 certificate revocation list (CRL) expiration monitoring to prevent outages caused by expired CRLs - \uf0a7 trust anchor management (e.g., root certificates) on TLS clients that act as relying parties for TLS server certificates - \uf0a7 load balanced architecture to support scalability, fault tolerance, and geographic distribution to support enterprise certificate operations - \uf0a7 Common Criteria certified", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_01155", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Automation Support for Security Control Assessments_ Software Asset Management provide? (Section 161) --------------------------------------------------------| | CM-7(b){1} | SWAM- F01 | Unauthorized software executes | the execution of unauthorized software. | | CM-7(b){1} | SWAM- F03 | Unauthorized software directory/folder location | the execution of software not loaded from an approved directory/folder location. | Control: The organization: - a. Develops and documents an inventory of information system components that: 1. Accurately reflects the current information system; 2. Includes all components within the authorization boundary of the information system; 3. Is at the level of granularity deemed necessary for tracking and reporting; and 4. Includes [Assignment: organization-defined information deemed necessary to achieve effective information system component accountability]. | Determination Statement ID | Determination Statement Text | |------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | CM-8(a){1} | Determine if the organization: develops and documents an inventory of system components {for software} that: (1) accurately reflects the current system; and (2) includes all components within the authorization boundary of the system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_01156", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Situational Awareness for Electric Utilities say about 4.2.2 Example Solution Data Aggregation and Analysis Lab Build? (Part 2) According to Situational Awareness for Electric Utilities, 4.2.2 Example Solution Data Aggregation and Analysis Lab Build: in enterprise. The sensor (O10) sends data files to the server (E8) for analysis. When the server detects a change to the assets on the ICS network in operations, it sends an event to ArcSight (E12). The PACS in the example solution is implemented by RS2 AccessIT! (E7). Door open/close events from the RS2 door controller (O4) in operations are sent to AccessIT! (E7) and stored in an internal database. An ArcSight database connector is used to extract these events and send them to ArcSight (E12). The enterprise historian is provided by the OSIsoft PI Historian (E4). ICS data from the operations Pi Historian (O8) is replicated to the enterprise PI Historian (E4). This data is used by the ICS behavioral monitoring component in the example solution, implemented by ICS2 OnGuard (E5), to detect unusual ICS behavior. OnGuard (E5) reports this unusual behavior to ArcSight (E12). The enterprise log collector/aggregator component in the example solution is provided by TDi Technologies ConsoleWorks (E6). This instance of ConsoleWorks (E6) receives files from the operations instance (O9). The files contain integrity-sealed syslog records. The enterprise instance of ConsoleWorks (E6) verifies the integrity seal on the records and sends the syslog records to ArcSight (E12). Siemens RUGGEDCOM CROSSBOW (E9), which implements part of the remote management connection described in Section 5.3, sends log information about remote management actions to ArcSight (E12). The analysis workflow engine, analysis tools, and visualization tools in the example solution are implemented by RSA SecOps (E13). This product extracts event data from ArcSight (E12) and performs analyses to identify potential cyber incidents.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Situational Awareness for Electric Utilities."}]}
{"id": "nist_01157", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain : rsassaPss according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, : rsassaPss: Signature Algorithm Hash Algorithm: sha256 Mask Algorithm: mgf1 with sha256 Salt Length: 0x20 Trailer Field: 0xBC (default) Issuer : CN=Test RSA 3072-bit CA for Test PIV Cards v2, ou=Test CA, o=Test Certificates 2020, c=US Validity : Not Before: Aug 5 08:30:00 2019 GMT, Not After: Dec 31 08:30:00 2040 GMT Subject : CN=T\u00ebst Cardholder Jr. (affiliate), ou=Test Agency, ou=Test Department, o=U.S. Government, c=US", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_01158", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST provide? (Section 75) but its capabilities have not been fully tested as of the moment. 3. Excalibur operates on UNIX platforms as well as PCs running Microsoft Windows. 4. The approximate cost of the system is $35,000. 1. InfoSelect is a personal information manager (PIM) which allows users to organize their personal information such as phone numbers, client lists, plans and projects, etc. It is not a generalized DBMS but rather a program that uses stacks and windows - like pieces of paper on a desk. It offers a number of predefined forms so that users do not have to create fields and enter information in a particular way. 2. InfoSelect has already been used by some NIST scientists to organize their information, which could be extended for ERN use. It is claimed to be very easy to use. The drawbacks are that it is strictly a personal information management tool and not designed to support sharable databases. 3. InfoSelect operates on PCs and compatible computers running Microsoft Windows. 4. The approximate cost is $150. 1. Lotus Notes is a cross between database software and network application packages for workgroup communications. Lotus Notes provides an easy user interface to allow users to create data definitions with many point and click options. The system has a simple macro language which allows users to define views so that selective queries may be displayed with a customized reporting style. All Windows applications can be \"cut and pasted\" into Notes, including data in the form of pictures, graphs, and bitmap images (In the future voice and video will be included.). Lotus Notes also incorporates public-key signature verification features. 2. Notes can be used to organize public ERN files and report and display different views of lab notebook contents for retrieval, browsing or reading. The key feature is that multiple clients may access a central server computer in order to manipulate multiple databases.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST."}]}
{"id": "nist_01159", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain IT Asset Inventory according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case, IT Asset Inventory: | Description | Quantity | |-----------------------------|------------| | SuperMicro Servers | 6 | | Allen Bradley 5700 Switches | 2 | | Allen Bradley 8300 Router | 1 | | HP Tower Workstation | 1 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case."}]}
{"id": "nist_01160", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Section 97) d in Appendix D. - When an approved elliptic-curve group is used, and the corresponding ECC domain parameters are ( q, FR, a, b { , SEED } , G, n, h ), the private keys are in the interval [1, n - 1]. The owner of a static or ephemeral key-establishment key pair shall obtain an initial assurance that the private key is an integer in the correct interval by using one of the following methods: - a. For both a static and ephemeral key pair: The owner generates the key pair as specified in Section 5.6.1, or - b. For a static key pair (only): After receiving a static key pair from a trusted third party (trusted by the owner), the owner performs a separate check to determine that the private key is in the correct interval. (While an entity can accept ownership of a static key pair that was generated by a TTP, an ephemeral key pair shall only be generated by its owner.) To renew this assurance for a static key pair (if desired), the owner shall perform a separate check to determine that the private key is in the correct interval as determined by the domain parameters. Prior to a key-establishment transaction, the owner of a key pair shall obtain an initial assurance that the public key has the expected representation for a non-identity element of the correct cryptographic subgroup, as determined by the domain parameters, using one of the following methods: - a. For either a static key pair or an ephemeral key pair: The owner generates the key pair as specified in Section 5.6.1 and performs a full public-key validation or an equivalent procedure as part of its generation process (see Section 5.6.2.3.1 for FFC, and Section 5.6.2.3.3 for ECC); or - b.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}]}
{"id": "nist_01161", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD) provide? (Section 210) tocol: It sends a configuration request to the Micronets Gateway, receives a configuration response from the Micronets Gateway, and responds by sending a configuration result to the Micronets Gateway. As noted earlier, configuration may happen on a frequency different from the one used for authentication. This completes the onboarding process. As a result of the configuration message it received, the device has learned the SSID and the unique credential that it needs to connect to the home/small-business network. In addition, the Micronets Gateway has been provided with both the micronet to which the device will be assigned upon connection to the network and ACLs that express the device\u2019s communications profile, as specified in its MUD file. NIST SP 1800-15B: Securing Small-Business and Home Internet of Things Devices 142 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 \uf0a7 With onboarding complete, the device initiates a standard Wi-Fi handshake and presents its newly provisioned credentials to connect to the network. It will be assigned its provisioned IP address, it will be located in a micronet that had been specified by the user of the Micronets mobile application at onboarding time, and it will be able to send and receive messages in accordance with both its micronet and the rules specified in its MUD file (i.e., it will not be permitted to communicate with any local devices that are in a different micronet unless such communication is explicitly permitted by its MUD file). 8.3.3.2 Onboarding Non-MUD-Capable Devices Figure 8-5 depicts the message flows involved in the process of onboarding devices that are Wi-Fi Easy Connect-capable but not MUD-capable in Build 3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_01162", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Privacy control according to An Introduction to Privacy Engineering and Risk Management in Federal Systems? Privacy control: The administrative, technical, and physical safeguards employed within an agency to ensure compliance with applicable privacy requirements and manage privacy risks. 83", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: An Introduction to Privacy Engineering and Risk Management in Federal Systems."}]}
{"id": "nist_01163", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Examine according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, Examine: [SELECT FROM: security policies and procedures associated with the protection of CUI; audit findings; system security plan; other relevant documents or records]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_01164", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Web Transactions_ TLS Server Certificate Management say about Recommended Responsibilities :? According to Securing Web Transactions_ TLS Server Certificate Management, Recommended Responsibilities :: - \uf0a7 Certificate Services team: provide automated certificate and key management services that remove the need for administrators to manually access private keys, alleviating the need to replace certificates and private keys when a system administrator is reassigned or terminated - \uf0a7 Certificate owners: ensure manually managed certificates and private keys are replaced when a system administrator with access is reassigned or terminated", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_01165", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations say about 03.14.01 Flaw Remediation? According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, 03.14.01 Flaw Remediation: - a. Identify, report, and correct system flaws. - b. Install security-relevant software and firmware updates within [ Assignment: organization-defined time period ] of the release of the updates.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_01166", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Framework for Designing Cryptographic Key Management Systems provide? (Section 46) | 11.1.3 Functional and Security Testing................................................................... | | 11.1.4 Penetration Testing....................................................................................... | 87 87 | 11.1.4 Penetration Testing....................................................................................... | | 11.2 Periodic Security Review ................................................................................... Assessment....................................................................... | 87 | 11.2 Periodic Security Review ................................................................................... Assessment....................................................................... | | 11.3 Incremental Security | 11.3 Incremental Security | 11.3 Incremental Security | | 11.4 Security Maintenance ......................................................................................... | 88 | 11.4 Security Maintenance ......................................................................................... | | 12.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_01167", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Framework Manufacturing Profile provide? (Section 42) rs, actuators, robots, machine firmware, network switches, routers, power supplies, and other networked components or System component inventory is reviewed and updated as defined by the organization. deemed necessary for effective accountability of manufacturing system components for example, hardware inventory specifications, component owners, networked or devices, machine names and network addresses. Inventory specifications include, | 62443-2-1:2009 4.2.3.4 62443-3-3:2013 SR 7.8 CM-8 | | | Asset Management | ID.AM-1 | Document Manufacturing tools, devices. Information includes, components for example, manufacturer, device type, model, serial number, and physical location. | 62443-2-1:2009 4.2.3.4 62443-3-3:2013 SR 7.8 CM-8 | | | Asset Management | ID.AM-1 | Moderate | 62443-2-1:2009 4.2.3.4 62443-3-3:2013 SR 7.8 CM-8 | | | Asset Management | ID.AM-1 | Identify individuals who are both responsible and accountable for administering manufacturing system components.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile."}]}
{"id": "nist_01168", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-002 in Guidelines for Smart Grid Cybersecurity? (Part 135) Control IP-002: ments; 146 3. The organization ensures that the incident response security policy and procedures comply with applicable federal, state, local, tribal, and territorial laws and regulations; and 4. The organization identifies potential interruptions and classifies them as to \u201ccause,\u201d \u201ceffects,\u201d and \u201clikelihood.\u201d Supplemental Guidance The incident response policy can be included as part of the general information security policy for the organization. Incident response procedures can be developed for the security program in general, and for a particular smart grid information system, when required. The various types of incidents that may result from system intrusion need to be identified and classified as to their effects and likelihood so that a proper response can be formulated for each potential incident. The organization determines the impact to each smart grid system and the consequences associated with loss of one or more of the smart grid information systems. Requirement Enhancements None. Additional Considerations None. Impact Level Allocation Low: SG.IR-1 Moderate: SG.IR-1 High: SG.IR-1 SG.IR-2 Incident Response Roles and Responsibilities Category: Common Governance, Risk, and Compliance (GRC) Requirements Requirement 1. The organization\u2019s smart grid information system security plan defines the specific roles and responsibilities in relation to various types of incidents; and 2. The plan identifies responsible personnel to lead the response effort if an incident occurs. Response teams need to be formed, including smart grid information system and other process owners, to reestablish operations. Supplemental Guidance The organization\u2019s smart grid information system security plan defines the roles and responsibilities of the various employees, contractors, and third parties in the event of an incident. The response teams have a major role in the interruption identification and planning process. Requirement Enhancements None.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01169", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to 2016 NIST_ITL Cybersecurity Program Annual Report? http: / /csrc.nist.gov/publications/nistbul/itlbul2016\\_02.pdf", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01170", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Accuracy, Integrity, and Security in Computerized Vote-Tallying provide? (Section 51) by providing technical assistance to advance new uses of computer technology. In 1987, additional responsibilities were assigned to ICST due to the passage of the Computer Security Act (P.L. 100-235). In accordance with this act, ICST will develop standards and guidelines on computer security to protect the U.S. Government's sensitive but unclassified information. This report concerns measures to assure the presence of accuracy, integrity, and security in computerized vote-tallying. Accuracy is the essential requirement of a computerized vote-tallying system, but its achievement may not be possible without the implementation of integrity and security. Even if accuracy is attained, confidence in the results may not be assured unless the other two factors can be shown to be present. Thus, for votetallying systems, these factors are not mutually exclusive parameters that can be separately considered. Definitions, for the purpose of this report, are as follows: accuracy: conformity of the output data of a vote-tallying system with logically correct and acceptably precise treatment of all input data provided to the system; integrity : the state of a vote-tallying system in which it will correctly perform the functions specified for it, and only those functions security : the achievement of a desired control of access to votetallying facilities, areas, equipment, supplies, documents, media, files, and data. The origins of the current project go back to 1974. In February of that year, ICST was asked by the General Accounting Office (GAO) to \"conduct a systems analysis and evaluation of the role of automatic digital processing equipment in the vote-tallying process.\" The year-long project, undertaken also by the author of this latest report, was completed in 1975.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, sensitive but unclassified. Contains guidance on protecting sensitive government information. Source: Accuracy, Integrity, and Security in Computerized Vote-Tallying."}]}
{"id": "nist_01171", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Common Platform Enumeration_ Naming Specification Version 2.3 say about Appendix A-References? According to Common Platform Enumeration_ Naming Specification Version 2.3, Appendix A-References: The following documents are indispensable references for understanding the application of this specification.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Platform Enumeration_ Naming Specification Version 2.3."}]}
{"id": "nist_01172", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Derived Personal Identity Verification (PIV) Credentials provide? (Section 67) es an authentica- tion certificate, which is an X.509 public key certificate that has been issued in accordance with the re- quirements of NIST SP 800-157 and the X.509 Certificate Policy for the U.S. Federal PKI Common Pol- icy Framework [25] | PR.AC-1 | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | Component | Product | Version | Function | Cybersecurity Framework Subcategories | |------------------------------------------|------------------------------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------| | PKI Certificate Authority | Verizon Shared Service Pro- vider | Not appli- cable | Entity that issues an authentica- tion certificate, which is an X.509 public key certificate that has been issued in accordance with the re- quirements of NIST SP 800-157 and the X.509 Certificate Policy for the U.S.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, certificate authority. Contains security framework guidance for authentication systems. Source: Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_01173", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-128 in Recommendation for Random Bit Generator (RBG) Constructions? (Part 102) Control ES-128: ce The source of an ideal random sequence of bits. Each bit of an ideal random sequence is unpredictable and unbiased with a value that is independent of the values of the other bits in the sequence. Prior to an observation of the sequence, the value of each bit is equally likely to be 0 or 1, and the probability that a particular bit will have a particular value is unaffected by knowledge of the values of any or all the other bits. An ideal random sequence of n bits contains n bits of entropy. ## independent entropy sources Two entropy sources are independent if knowledge of the output of one entropy source provides no information about the output of the other entropy source. ## initial randomness source The randomness source for the root RBGC construction in a DRBG tree of RBGC constructions. ## instantiate The process of initializing a DRBG with sufficient randomness to generate pseudorandom bits at the desired security strength. ## internal state (of a DRBG) The collection of all secret and non-secret information about an RBG or entropy source that is stored in memory at a given point in time. ## known answer test A test that uses a fixed input/output pair to detect whether a deterministic component was implemented correctly or continues to operate correctly. ## legacy implementation (of DRBGs) DRBG implementations that may not conform to the current SP 800-90A version but do conform to a previous version of SP 800-90A. ## min-entropy A lower bound on the entropy of a random variable. The precise formulation for min-entropy is ( -log2 max pi ) for a discrete distribution having probabilities p 1 , ..., pk . Min-entropy is often used as a measure of the unpredictability of a random variable. ## must Used to indicate a requirement that may not be testable by a CAVP/CMVP testing lab. Note: Must may be coupled with not to become must not . ## noise source A source of unpredictable data that outputs raw discrete digital values.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Bit Generator (RBG) Constructions."}]}
{"id": "nist_01174", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Securing Public Web Servers say about 3.1 Installation and Deployment Planning? (Part 4) According to Guidelines on Securing Public Web Servers, 3.1 Installation and Deployment Planning: organization's reputation that could occur if the servers' integrity is compromised. In such cases, it is critical that the Web servers are located in areas that provide secure physical environments. When planning the location of a Web server, the following issues should be considered: - GLYPH&lt;c=31,font=/IEIOAF+Webdings&gt; Are the appropriate physical security protection mechanisms in place? Examples include- - \u0083 Locks - \u0083 Card reader access - \u0083 Security guards - \u0083 Physical IDSs (e.g., motion sensors, cameras). - GLYPH&lt;c=31,font=/IEIOAF+Webdings&gt; Are there appropriate environmental controls so that the necessary humidity and temperature are maintained? - GLYPH&lt;c=31,font=/IEIOAF+Webdings&gt; Is there a backup power source? For how long will it provide power? - GLYPH&lt;c=31,font=/IEIOAF+Webdings&gt; If high availability is required, are there redundant Internet connections from at least two different Internet service providers (ISP)? - GLYPH&lt;c=31,font=/IEIOAF+Webdings&gt; If the location is subject to known natural disasters, is it hardened against those disasters and/or is there a contingency site outside the potential disaster area?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Securing Public Web Servers."}]}
{"id": "nist_01175", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on PDA Forensics say about 4.2 Evidential Principles? (Part 3) According to Guidelines on PDA Forensics, 4.2 Evidential Principles: 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? - \u0084 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. In general, even outside of law enforcement investigations, evidence should be collected in a manner that makes it likely the evidence could be admissible in court. It may not be obvious when an investigation is initiated, for example, when a computer security incident is first detected, that a court action will ensue. Important evidence might be overlooked, improperly handled, or accidentally destroyed before the seriousness of the incident is realized.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on PDA Forensics."}]}
{"id": "nist_01176", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Secure Web Services provide? (Section 68) formation, and documents by which an entity's identity is verified, identity documents and credentials are issued to the entity, and entity identities are authenticated at point of entry into the SOA. In the SOA, an entity's identity forms the basis for both authorization and trust. An Identity Management System (IDMS), such as that pictured in Figure 3-1, is responsible for verifying the identities of entities, registering them, and issuing them digital identifiers. In accordance with Homeland Security Presidential Directive (HSPD) 12, Subject: Policy for a Common Identification Standard for Federal Employees and Contractors 27 , NIST Federal Information Processing Standard (FIPS) 201-1, Personal Identity Verification of Federal Employees and Contractors 28 , describes a number of requirements that must be satisfied before a human entity may be registered in a Federal IDMS, including a National Agency Check and Inquiries (NACI) background check. Non-government organizations may have different rules for registration. For example, users who wish to gain access to many e-commerce sites often need to provide only a valid email address and a credit card number. 27 HSPD-12, Policy for a Common Identification Standard for Federal Employees and Contractors , is available at 28 FIPS 201-1, Personal Identity Verification of Federal Employees and Contractors , is available at http://csrc.nist.gov/publications/fips/. Figure 3-1. Identity Management Overview <!-- image --> Once an entity has been issued a digital identifier, that identifier can be used within that organization to associate other information with the entity, such as role and authorization attributes. The identifier may also become part of the digital credential that authorizes the entity to access different resources in the SOA. Once registered, an entity must provide a portion of its credentials sufficient to authenticate that entity's identity.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, identity management, sso. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services."}]}
{"id": "nist_01177", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Guidelines for Storage Infrastructure provide? (Section 90) ct violations to the pattern, which sends notifications, should also be implemented. AC-SS-R31 Users that do need to authenticate should be disabled (e.g., Anonymous, null, guest, or 'public access'). An exception may be provided to allow organization-critical functions such as network discovery, but in such cases these class of users should be mapped to the 'nobody' user group and not to \"ID 0\". AC-SS-R32 - Regular audits of all the security settings mentioned above for storage data of all types (e.g., Files, Objects) should be performed to ensure that there are no drifts. Audit results should be documented. AC-SS-R33 - Scan files containing sensitive information with anti-malware tools on-access: Every time a file with sensitive information is accessed, it should first be scanned with organization approved anti-malware tools to ensure that it has not been compromised. AC-SS-R34 - Granular permission assignment: For file and object sharing systems (e.g., NFS, CIFS, cloud object stores), permissions should be granted at a finer level of granularity rather than a coarser one (e.g., file or object over folder, and label over share or bucket). AC-SS-R35 - Secure NFS by restricting root access: This includes the use of the 'nosuid' option, and avoidance of use of 'no\\_root\\_squash' to prevent programs from being executed as a root user on the client, and modification of shared files by remote root users. In general, NFS clients should not be allowed to run 'suid' and 'sgid' programs on exported file systems. AC-SS-R36: In NFS, for files that are to be used in the 'read only' mode, the mount configuration for corresponding NFS shares should always have the 'noexec' option. AC-SS-R37 Export of administrative file systems should not be allowed: This includes the '/' filesystems and restricted OS or storage array system folders.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Guidelines for Storage Infrastructure."}]}
{"id": "nist_01178", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identity and Access Management for Electric Utilities provide? (Section 231) / / 1 1 0 0 6 6 0 0 2 2 8 8 / / N N I I S S T T . . S S P P 1 1 8 8 0 0 0 0 - - 2 2 . . . . From System >View Submitted tasks, click Search. Verify that the Create User task completed successfully. Connect to the AE Database. Verify that the user was created successfully. Connect to the Active Directory Domain Controller. Verify that the user was created successfully. Repeat all of the steps above for Modify User, Enable User, and Disable User. 6.18 Test Creation of a User with a CSV file Download the file HRBulkUsers4.csv from and unzip to use. Modify the CSV file to enter the desired values for the new users to be created. Keep in mind the policy rules that must be followed as described above. From System > Bulk Loader, Browse for the CSV file. What field represents the action to perform on the object: action. What field will be used to uniquely identify the object: uid. Click Next. What is the Primary Object: USER. Select a task to execute for action \u201ccreate\u201d: Create User Click Finish. Repeat Steps 4 through 7 above, and the steps from Section 6.17, to approve the users and to verify that they were successfully created. Identity Management and Governance: RSA (Build #2) 7 RSA IMG implements the central IdAM workflow in Build #2. It receives input from an HR system, in the form of CSV files. The access and authorization for each user is based on the business and security rules implemented in workflows within RSA IMG. The workflows include management approval chains as well as approval/denial data logging. Once IMG has processed the access and authority request, the updated user access and authorization data is pushed to the central identity store. The central identity store contains the distribution mechanism for updating the various downstream (synchronized) directories with user access and authorization data.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, identity management. Contains security framework guidance for authentication systems. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_01179", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Report on the Privilege (Access) Management Workshop provide? (Section 58) cument and provides added detail-the functional boxes 'Policy Consumption,' 'Attribute Consumption', and 'Translated into Digital Policy.' It takes Figure 5 a step closer to a possible implementation. In addition, it expands the scope of privilege management to include the box labeled 'Governance and 'P'olicy. This addition seems reasonable and leads to a number of new questions that one could address-for example, what kind of automated assistance makes sense and how would it interface to 'Translated into Digital Policy.' Also, the overall architecture displayed in the proffered diagram leads to the question of how the details and increased scope can be dealt with in the alternate architecture described in Figure 6 of this document. Thus, there are many considerations here that could inform an approach for a follow-on workshop on privilege management.] [Editor: The figure and caption in question are as follows: Figure 5. Interfaces of Privilege Management - View One <!-- image --> -end of Editor comment.]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Report on the Privilege (Access) Management Workshop."}]}
{"id": "nist_01180", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EU-73 in Design Alternatives for Computer Network Security? (Part 79) Control EU-73: e handled by merely adding one more relay operation; namely from the destination ICD back to the Master-ICD at the SC. This would complete the \"loop and thereby inform the SC of the connection status. It would require that the destination ICD \"fill in the blanks,\" e.g., insert a condition-code, to indicate the status, and would require that the SC set up one additional encipherment key to be utilized for this ICD-to-SC (Master-ICD) transmission. For the non relay mode, in which the Master-ICD would \"prime\" ti\\e two end ICD's, a different approach would be necessary. Either one of the ICD's could be charged with performing this function (or both) in a similar manner to that required to notify the SC when a connection is broken. However, the two function are quite different when an ICD has a single port to work with, since in the former case it is \"tied up\" with the working connection, while it is free after having broken a connection. ## 4.4 ACCESS CONTROL AT THE ICD LEVEL; USAGE OF A CONNECTION In the simplest case, two ICD's might be considered to be in-line with the communications and therefore would be transparent to the usage of the line, just as a pair of modems perform their transformation/inverse transformation, and otherwise are transparent to the communication. However, the cryptographic equipments do introduce side effects, primarily related to their synchronization requirement Therefore, we should consider the various options that we have in this area, and determine their network-related tradeoffs. We also need to consider the impact of utilizing multiplexed cryptographic equipment, particularly at multi-port devices such as HOST computers, and the associated problems that multiplexing introduces due to the need to pass more control information past the encryption mechanism. Finally, we need to consider the effects of errors on all of these factors and the performance degradation due to the usage of the ICD's.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Design Alternatives for Computer Network Security."}]}
{"id": "nist_01181", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Version 1.1 Manufacturing Profile say about 7. Manufacturing Profile Subcategory Guidance? (Part 27) According to Cybersecurity Framework Version 1.1 Manufacturing Profile, 7. Manufacturing Profile Subcategory Guidance: IDENTIFY | Supply Chain (ID.SC) | | Identify and document key personnel from suppliers and third-party partners to include as stakeholders in response and recovery planning activities. | CP-4, IR-3, IR-4 | | Function | Category | Subcategory | Manufacturing Profile Guidance | Reference | |------------|----------------------------------------------------------------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------| | PROTECT | Identity Management, Authentication and Access Control (PR.AC) | PR.AC-1 | Low Impact Establish and manage identification mechanisms and credentials for users of the manufacturing | ISA/IEC 62443-2- 1:2009 4.3.3.5.1; SR 1.1, 1.2, 1.3, 1.4, 1.5,1.7 IA-Family AC-2(1) | | PROTECT | Identity Management, Authentication and Access Control (PR.AC) | PR.AC-1 | system.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, identity management. Contains security framework guidance for authentication systems. Source: Cybersecurity Framework Version 1.1 Manufacturing Profile."}]}
{"id": "nist_01182", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Section 98) Federal enterprises should establish processes to effectively engage with the FASC's government agencies and acting as a central, government-wide facilitator for C-SCRM information-sharing activities. information-sharing agency, which is responsible for facilitating information sharing among NIST SP 800-150 describes key practices for establishing and participating in SCRI-sharing relationships, including: - Establish information-sharing goals and objectives that support business processes and security policies - Identify existing internal sources of SCRI - Specify the scope of information-sharing activities 27 - Establish information-sharing rules - Join and participate in information-sharing efforts - Actively seek to enrich indicators by providing additional context, corrections, or suggested improvements - Use secure, automated workflows to publish, consume, analyze, and act upon SCRI - Proactively establish SCRI-sharing agreements - Protect the security and privacy of sensitive information - Provide ongoing support for information-sharing activities As shown in Table 2, below, SCRI describes or identifies the cybersecurity supply chain relevant characteristics and risk factors associated with a product, service, or source of supply. It may exist in various forms (e.g., raw data, a supply chain network map, risk assessment report) and should be accompanied by the metadata that will facilitate an assessment of a level of confidence in and credibility of the information. Enterprises should follow established processes and procedures that describe whether and when the sharing or reporting of certain information is mandated or voluntary and if there are any necessary requirements to adhere to regarding information handling, protection, and classification.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_01183", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IR-7864 in The Common Misuse Scoring System (CMSS)_ Metrics for Software Feature Misuse Vulnerabilities? (Part 54) Control IR-7864: ervice that impacts the availability of network functions, yet non-network functions remain available. With the base metric scores described above, the base score for this misuse vulnerability is 4.8. Temporal metrics describe the general prevalence of attacks against this vulnerability and the general availability of remediation measures. The General Remediation Level for the ARP cache poisoning vulnerability would be considered 'Low' because there are limited mitigation techniques available. For very small networks, administrators can configure static IP addresses and static ARP tables, but this approach quickly becomes unmanageable as the network grows in size. For larger networks, switches can be configured to allow only one MAC address for each physical port. ARP cache poisoning attacks occur against typical systems rarely, so the General Exploit Level is scored as 'Low'. Since the General Remediation Level is also scored as 'Low,' the temporal score would be 3.7. In general, the temporal score can be lower than the base score when the General Exploit Level is lower than 'Medium' or the General Remediation Level is higher than 'None.' Environmental metrics describe the vulnerability severity with respect to a particular organization. Consider an organization in which the Local Vulnerability Prevalence is 'High,' the Perceived Target Value is 'Medium', and the Local Remediation Level is rated 'None.' Because the Local Vulnerability Prevalence is higher than the default value and the Local Remediation Level is lower than the General Remediation Level, the exploitability subscore calculation for the environmental score is higher than the temporal exploitability subscore. Now consider the impact subscore of the environmental score. When the Collateral Damage Potential is 'None,' this metric does not modify the impact subscore in the environmental score calculation.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: The Common Misuse Scoring System (CMSS)_ Metrics for Software Feature Misuse Vulnerabilities."}]}
{"id": "nist_01184", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6.1 \u958b\u59cb\u30d5\u30a7\u30fc\u30ba according to NIST Application Container Security Guide According to Application Container Security Guide, 6.1 \u958b\u59cb\u30d5\u30a7\u30fc\u30ba: \u7d44\u7e54\u306f\u3001\u4ed6\u306e\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30dd\u30ea\u30b7\u30fc\u304c\u30b3\u30f3\u30c6\u30ca\u306b\u3088\u3063\u3066\u3069\u306e\u3088\u3046\u306a\u5f71\u97ff\u3092\u53d7\u3051\u308b\u304b\u3092\u691c\u8a0e\u3057\u3001\u30b3\u30f3\u30c6\u30ca\u3092\u8003\u616e\u306b\u5165\u308c \u308b\u305f\u3081\u306b\u3001\u5fc5\u8981\u306b\u5fdc\u3058\u3066\u3053\u308c\u3089\u306e\u30dd\u30ea\u30b7\u30fc\u3092\u8abf\u6574\u3059\u308b\u3053\u3068\u304c\u671b\u307e\u3057\u3044\u3002\u4f8b\u3048\u3070\u3001\u30a4\u30f3\u30b7\u30c7\u30f3\u30c8\u30ec\u30b9\u30dd\u30f3\u30b9\uff08\u7279\u306b\u30d5\u30a9 \u30ec\u30f3\u30b8\u30c3\u30af\uff09\u3084\u8106\u5f31\u6027\u7ba1\u7406\u306e\u30dd\u30ea\u30b7\u30fc\u306f\u3001\u30b3\u30f3\u30c6\u30ca\u306e\u7279\u6b8a\u306a\u8981\u4ef6\u3092\u8003\u616e\u3059\u308b\u305f\u3081\u306e\u8abf\u6574\u304c\u5fc5\u8981\u3068\u306a\u308b\u5834\u5408\u304c\u3042\u308b\u3002 \u30b3\u30f3\u30c6\u30ca\u6280\u8853\u306e\u5c0e\u5165\u306f\u3001\u7d44\u7e54\u5185\u306e\u65e2\u5b58\u306e\u6587\u5316\u3068\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u958b\u767a\u65b9\u6cd5\u8ad6\u3092\u6df7\u4e71\u3055\u305b\u308b\u53ef\u80fd\u6027\u304c\u3042\u308b\u3002\u30b3\u30f3\u30c6\u30ca\u304c\u63d0\u4f9b \u3059\u308b\u30e1\u30ea\u30c3\u30c8\u3092\u6700\u5927\u9650\u306b\u6d3b\u7528\u3059\u308b\u305f\u3081\u306b\u306f\u3001\u3053\u306e\u65b0\u3057\u3044\u30a2\u30d7\u30ea\u306e\u958b\u767a\u3001\u5b9f\u884c\u3001\u30b5\u30dd\u30fc\u30c8\u65b9\u6cd5\u3092\u30b5\u30dd\u30fc\u30c8\u3059\u308b\u3088\u3046\u306b\u7d44 \u7e54\u306e\u30d7\u30ed\u30bb\u30b9\u3092\u8abf\u6574\u3059\u308b\u3053\u3068\u304c\u671b\u307e\u3057\u3044\u3002\u5f93\u6765\u306e\u958b\u767a\u624b\u6cd5\u3001\u30d1\u30c3\u30c1\u9069\u7528\u6280\u8853\u3001\u304a\u3088\u3073\u30b7\u30b9\u30c6\u30e0\u306e\u30a2\u30c3\u30d7\u30b0\u30ec\u30fc\u30c9\u30d7\u30ed \u30bb\u30b9\u306f\u3001\u30b3\u30f3\u30c6\u30ca\u5316\u3055\u308c\u305f\u74b0\u5883\u306b\u76f4\u63a5\u9069\u7528\u3055\u308c\u306a\u3044\u5834\u5408\u304c\u3042\u308a\u3001\u7d44\u7e54\u5185\u306e\u5f93\u696d\u54e1\u304c\u65b0\u3057\u3044\u30e2\u30c7\u30eb\u306b\u7a4d\u6975\u7684\u306b\u9069\u5fdc\u3059\u308b \u3053\u3068\u304c\u91cd\u8981\u3067\u3042\u308b\u3002\u65b0\u3057\u3044\u30d7\u30ed\u30bb\u30b9\u3067\u306f\u3001\u6280\u8853\u306e\u5909\u5316\u306b\u3088\u3063\u3066\u3082\u305f\u3089\u3055\u308c\u308b\u6f5c\u5728\u7684\u306a\u30ab\u30eb\u30c1\u30e3\u30fc\u30b7\u30e7\u30c3\u30af\u3092\u8003\u616e\u3059\u308b \u3053\u3068\u304c\u3067\u304d\u3001\u307e\u305f\u3001\u5bfe\u51e6\u3067\u304d\u308b\u3002\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u958b\u767a\u30e9\u30a4\u30d5\u30b5\u30a4\u30af\u30eb\u306b\u95a2\u308f\u308b\u3059\u3079\u3066\u306e\u4eba\u306b\u6559\u80b2\u3068\u30c8\u30ec\u30fc\u30cb\u30f3\u30b0\u3092\u63d0\u4f9b \u3059\u308b\u3053\u3068\u306b\u3088\u3063\u3066\u3001\u4eba\u3005\u304c\u30a2\u30d7\u30ea\u3092\u69cb\u7bc9\u3001\u914d\u5e03\u3001\u5b9f\u884c\u3059\u308b\u305f\u3081\u306e\u65b0\u3057\u3044\u65b9\u6cd5\u306b\u6163\u308c\u308b\u3053\u3068\u304c\u3067\u304d\u308b\u3002", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Application Container Security Guide."}]}
{"id": "nist_01185", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain General Issues: according to NIST A Threat Analysis on UOCAVA Voting Systems According to A Threat Analysis on UOCAVA Voting Systems, General Issues:: Leaking sensitive personal information from voters. Available and integrity of voter registration database.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Threat Analysis on UOCAVA Voting Systems."}]}
{"id": "nist_01186", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Device Security_ Bring Your Own Device (BYOD) provide? (Section 115) --------------------------------| | | | DE.CM-5: Unauthorized mobile code is detected. | SC-18: Mobile Code SI-7: Software, Firmware, and Information Integrity | A.12.5.1: Installation of Software on Operational Systems A.12.6.2: Restrictions on Software Installation | CSC 7: Email and Web Browser Protections CSC 8: Malware Defenses | PR-CDA-001: Cyber Defense Analyst SP-DEV-002: Secure Software Assessor | | IBM MaaS360 Mobile Device Management (SaaS) Version 10.73 | Enforces organizational mobile endpoint security policy | ID.AM-1: Physical devices and systems within the organization are inventoried.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_01187", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EP-67 in Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)? (Part 51) Control EP-67: There are already academic conference series such as PQC and workshops have been established by ETSI/IQC [i.1] and NIST. The European Commission has recently granted funding to two QSC projects under the Horizon 2020 framework: SAFEcrypto [i.2] and PQCrypto [i.3] and [i.4]. The present document draws on all these research efforts. The present document will cover three main areas. Clauses 4 and 5 discuss the types of primitives being considered and describe an assessment framework; clauses 6 to 10 discuss some representative cryptographic primitives; and clause 11 gives a preliminary discussion of key sizes. | | | ETSIGR QSC 003 V1.1.1 (2017-02) | ETSI | Quantum Safe Cryptography; Case Studies and Deployment Scenarios The present document examines a number of real-world uses cases for the deployment of quantum-safe cryptography (QSC). Specifically, it examines some typical applications where cryptographic primitives are deployed today and discusses some points for consideration by developers, highlighting features that may need change to accommodate quantum-safe cryptography. The main focus of the document is on options for upgrading public-key primitives for key establishment and authentication, although several alternative, non-public-key options are also discussed. The present document gives an overview of different technology areas; identify where the security and cryptography currently resides; and indicate how things may have to evolve to support quantum-safe cryptographic primitives. Clauses five and six discuss network security protocols, using TLS and S/MIME as typical examples. These are contrasted in clauses seven and eight by an examination of security options for IoT and Satellite use cases, which have very different requirements and constraints than traditional Internet-type services. Some alternatives to public key protocols are reviewed in clause nine.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_01188", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Validating the Integrity of Computing Devices say about 2.1.1.1.3 CentOS 7 Image Creation? (Part 2) According to Validating the Integrity of Computing Devices, 2.1.1.1.3 CentOS 7 Image Creation: ning the required vmlinuz and initrd0.img files. It will also create a directory named pxelinux.cfg which contains a file named default . default contains the kernel flags necessary to boot the image. Use these files in the PXE environment detailed in Section 2.1.1.3. ``` $ livecd-iso-to-pxeboot imagename.iso ```", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validating the Integrity of Computing Devices."}]}
{"id": "nist_01189", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results provide? (Section 16) l to the internal systems will add to confidence in the authenticity of transmitted documents, and effective controlled access to sensitive databases will add to confidentiality when that is required. Commentary to 6 ; Irvin Chmielewski, in his paper, stresses \"application systems that will utilize EDI\" rather than just EDI. This leads him to consider overall security, not just data link security. He states, \"... applications, both client/server and host-based, at the manufacturers and their trading partners, must provide full security of all information and resources.\" In the paper by Horton Sorkin, the security of the data interchange is related to the internal control structure as seen by an auditor of a client's system. Sorkin states that the standard audit objectives for each transaction do not change with EDI; the same concerns are translated to the new technology. \"The loss of controlled and prenumbered paper stock is supplanted by concerns over counters, date-time mechanisms, and authorization and internal access controls. It does not appear to make much sense to be concerned about EDI transmission security if internal controls at the business application level are inadequate,\" Sorkin states. 7. There are non-cryptographic techniques that can be used to provide confidence in document integrity and originator authentication at a lower level than could be assured with cryptographic techniques. There are no non-cryptographic techniques that can provide high confidence of confidentiality in document interchange. Commentary to 7 ; Peter Weiss provides a list of computer security techniques applicable to EDI, presented in generally ascending order of security strength. The lower-level techniques presented are non-cryptographic. Weiss points out that the list of techniques is generally consistent with that contained in the American Bar Association's Model Payments Agreement and Commentary (\"Model Agreement\") . 32 Jurimetrics 601 (Summer, 1992) .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results."}]}
{"id": "nist_01190", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AN-2013 in Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet? (Part 104) Control AN-2013: | N o t e | Imp. Required | Imp. Support | Supporte d Range | Test Result | E n c . | |----------------------------------|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------| | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | Transaction-related Requirements | | XML | | an end tag of format </Name>. For all logical records - including Types 4, 7, and 8 that do not have field tags in the Traditional encoding -- data elements are tagged according to XMLrules. The format for each element shall consist of a start tag enclosed in angle brackets followed by data followed by an end tag.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet."}]}
{"id": "nist_01191", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.6.8 Example according to NIST A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications According to A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications, 2.6.8 Example: (input) \u03b5 = 11001001000011111101101010100010001000010110100011 00001000110100110001001100011001100010100010111000 (input) n = 100 (processing) N1 = 46 (processing) N0 = 47.5 (processing) d = -1.376494 (output) P-value = 0.168669 (conclusion) Since P-value \u2265 0.01 , accept the sequence as random.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications."}]}
{"id": "nist_01192", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.5 Trusted Platform Module (TPM) Key Derivation Function according to NIST Recommendation for Existing Application-Specific Key Derivation Functions According to Recommendation for Existing Application-Specific Key Derivation Functions, 5.5 Trusted Platform Module (TPM) Key Derivation Function: Version 1.2 of the Trusted Platform Module is specified in the TPM Main Specification Parts 1, 2 and 3 ([TPM Principles], [TPM Structures] and [TPM Commands], respectively). It uses a SHA-1 HMAC-based Pseudorandom Function (PRF) in its KDF to generate keying material for transport sessions between the TPM and an application running on another processor. To 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: SKEY = HMAC ( Auth , Nonce\\_even || Nonce\\_odd ), where Nonce\\_even and Nonce\\_odd are non-secret values created by the random number generators on the TPM and the application, respectively. Additional technical details for the variables in the functions are provided in Part 3 of the TPM Main Specification. SKEY is used as an HMAC key to provide data integrity for communications during the session. Further keys may be derived from SKEY to provide encryption of parts of the session. The TPM KDF is approved when the following conditions are satisfied: - (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.) - (2) HMAC and SHA-1 are used as specified in FIPS 198-1 and 180-3, respectively. Note that the KDF is a particular instance of the feedback mode as specified in Section 5.2 of SP 800-108, with an empty initial value (IV).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Existing Application-Specific Key Derivation Functions."}]}
{"id": "nist_01193", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain n : 6610559687902485989519153080327710398284046829642812192846487\\ 98304157774827374805208143723762179110965979867288366567526771 according to NIST Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters According to Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters, n : 6610559687902485989519153080327710398284046829642812192846487\\ 98304157774827374805208143723762179110965979867288366567526771: ``` (= 0x1000000 00000000 00000000 00000000 00000000 00000000 000001e2 aad6a612 f33307be 5fa47c3c 9e052f83 8164cd37 d9a21173 ) tr : -6059503967182126918765909026644927652236777310526686418445029 (=(2 m + 1) h \u22c5 n = -0x3c5 55ad4c25 e6660f7c bf48f879 3c0a5f07 02c99a6f b34422e5 ) a : 1 (= 0x0000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000001 ) ```", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters."}]}
{"id": "nist_01194", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Acknowledgments according to NIST Computer Security Division 2013 Annual Report According to Computer Security Division 2013 Annual Report, Acknowledgments: The editor, Patrick O'Reilly of the Computer Security Division, wishes to thank his colleagues in the Computer Security Division, who provided write-ups on their 2013 project highlights and accomplishments for this annual report (their names are mentioned after each project write-up). The editor would also like to acknowledge Barbara Guttman, Kevin Stine, Jim Foti (ITL, NIST), Greg Witte, Chris Johnson and Doug Rike (G2) for reviewing and providing valuable feedback for this annual report. The Editor also would like to thank Lorie Richards (Facilities Services Division, Creative and Printing Service, NIST) for designing the cover and final layout of our division's annual report. Finally, the editor would like to thank Joshua Franklin and Michaela Iorga (Computer Security Division, ITL, NIST) for their input with the 2013 annual report cover design. Verification FIPS 140-2 Biometrics Policy Machine Validated Products List This page is intentionally left blank. Assets FIPS 140-2 iometrics Access Control licy Machine Validated Products List Guidelines Risk Management Framework Systems Assets Verification FISMA Cloud Computing Cybersecurity Framework Roadmap Authorization Evaluation Standards Security Controls Mobile Devices Supply chain risk management Continuous Monitoring Critical Infrastructure Security Practices <!-- image -->", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Computer Security Division 2013 Annual Report."}]}
{"id": "nist_01195", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain National Institute of Standards and Technology Interagency Report 7622 80 pages (October 2012) according to NIST Notional Supply Chain Risk Management Practices for Federal Information Systems According to Notional Supply Chain Risk Management Practices for Federal Information Systems, National Institute of Standards and Technology Interagency Report 7622 80 pages (October 2012): 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. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. All NIST publications, other than the ones noted above, are", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Notional Supply Chain Risk Management Practices for Federal Information Systems."}]}
{"id": "nist_01196", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identity and Access Management for Electric Utilities provide? (Section 143) Universal to Door Controller ......................................................223 10.4.2 Enable TCP/IP to SQL 2008 R2 Server .......................................................................224 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . 11.2.1 System Environment .................................................................................................225 NIST SP 1800-2C: Identity and Access Management for Electric Utilities ix 11.2.2 ConsoleWorks Server Installation on the OT Network .............................................226 11.2.3 Post-Installation Configuration of ConsoleWorks on the OT Network .....................226 11.2.4 Configuring External Authentication for the OT Network ConsoleWorks Server .....227 T h i s p u b l i c a t i o n 12.2.1 Installing iSIM ............................................................................................................228 12.2.2 iEMS ..........................................................................................................................228 i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . 15.1.1 Managing the Account ..............................................................................................267 15.1.2 What Is a Profile? / Profile Management .................................................................267 15.1.3 What Is a License?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_01197", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Digital Identity Guidelines_ Federation and Assertions provide? (Section 203) ot require the server to authenticate the client. Authentication of the server is often accomplished through a certificate chain that leads to a trusted root rather than individually with each server. See protected session . The process by which a claimant proves possession and control of one or more authenticators bound to a subscriber account to demonstrate that they are the subscriber associated with that account. A category that describes the strength of the authentication process. A private or symmetric key used by an authenticator to generate the authenticator output. Something that the subscriber possesses and controls (e.g., a cryptographic module or password ) and that is used to authenticate a claimant's identity. See authenticator type and multi-factor authenticator . The establishment of an association between a specific authenticator and a subscriber account that allows the authenticator to authenticate the subscriber associated with the account, possibly in conjunction with other authenticators. A decision to grant access, typically automated by evaluating a subject 's attributes . 127 In federation , the organization, person, or entity that is responsible for making decisions regarding the release of information within the federation transaction , most notably subscriber attributes . This is often the subscriber (when runtime decisions are used) or the party operating the IdP (when allowlists are used). Communication between two systems that relies on a direct connection without using redirects through an intermediary, such as a browser. An assertion that can be presented on its own as proof of the identity of the presenter. A documented list of specific elements that are blocked, per policy decision. This concept has historically been known as a 'blacklist.' An authenticator verified by the RP in addition to an assertion at FAL3. The bound authenticator is bound to the RP subscriber account .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, sso. Contains security framework guidance for authentication systems. Source: Digital Identity Guidelines_ Federation and Assertions."}]}
{"id": "nist_01198", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Standard Security Label for GOSIP_ an Invitational Workshop say about Table of Contents? (Part 5) According to Standard Security Label for GOSIP_ an Invitational Workshop, Table of Contents: | , \"Security Labels at the Transport Layer\" (Presentation Slides) , Wayne A. Jansen (NIST) - | 95 | | 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 | | \"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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Standard Security Label for GOSIP_ an Invitational Workshop."}]}
{"id": "nist_01199", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain DHCP Server Insertion Attack according to NIST Security Considerations for Voice Over IP Systems According to Security Considerations for Voice Over IP Systems, DHCP Server Insertion Attack: It is often possible to change the configuration of a target phone by exploiting the DHCP response race when the IP phone boots. As soon as the IP phone requests a DHCP response, a rogue DHCP server can initiate a response with data fields containing false information. This attack allows for possible man in the middle attacks on the IP-media gateway, and IP Phones. Many methods exist with the potential to reboot the \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ phone remotely, e.g. 'social engineering', ping flood, MAC spoofing (probably SNMP hooks, etc.). If possible, use static IP addresses for the IP Phones. This will remove the necessity of using a DHCP server. Further, using a state based intrusion detection system can filter out DHCP server packets from IP Phone ports, allowing this traffic only from the legitimate server.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_01200", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does PBX Administrator\u2019s Security Standards say about Illegally Obtaining Authorization Codes? (Part 1) According to PBX Administrator\u2019s Security Standards, Illegally Obtaining Authorization Codes: Illegally Obtaining Authorization Codes Observation Social Engineering Schemes Operator Direct Dial Scheme easier ways to steal services. Hackmg a 14 digit code is more difficult than hackmg a PBX that is not securely administered. - Long distance providers are no longer tolerating toll fraud. They have successfully prosecuted and jailed hackers caught breaking into their systems and stealing their services. There are a variety of ways in which a hacker may illegally obtain someone's long distance authorization code. For example, hackers have been known to sit on balconies in busy aiiports or train stations overlooking telephone banks. Using telescopes or field glasses, they watch a traveler make a long distance call, and through careful observation, obtain the authorization code. Social engineering refers to a person's ability to use personality, knowledge of human namre, and social skills to steal toll calls. In one scheme, a hacker calls a long distance subscriber and claims to represent his/her long distance carrier. The hacker might claim to be doing maintenance or validating long distance access codes (PINs). He reads the first ten digits of the access code (which is the phone number of the person he is talking to) and makes up the last four digits. Human nature being what it is, the victim automatically corrects the hacker, giving him the correct PIN. The hacker thanks the subscriber and hangs up in full possession of a valid authorization code for placing long distance calls. In this scheme, a thief employs his social engineering skills to convince a switchboard operator to assist him in placing a long distance caU. Commonly, the thief dials your 800 number and asks for a particular department, such as Marketing. Once connected to that department, he says he has been connected to the wrong d^artment and asks to be transferred back to the operator.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PBX Administrator\u2019s Security Standards."}]}
{"id": "nist_01201", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 7.10.3. Procedure according to NIST Secure Data Network Systems (SDNS) Key Management Documents According to Secure Data Network Systems (SDNS) Key Management Documents, 7.10.3. Procedure: When the responder KMAP issues a response primitive with a failure result, the KMASE generates an Estat. The parameter estatus contains the result value, and the value represents a failure when it is greater than zero. The following codes represent the various failure responses: (16) (17) (18) (19) ``` service-not-available (8), - No further details service-not-available-CRL (9), service-not-available-Interactive-rekey (10), service-not-available-Staged-rekey (11), service-not-available-at-this-time (15), - Specify doNotTryBefore incorrect-value-in-protected-field incorrect-value-PDU-type incorrect-value-old-resp-kid incorrect-value-crl-ver incorrect-value-add-info incorrect-value-univ-id incorrect-value-ref-num incorrect-value-proposed-options rekey-not-complete delete-this-TEK negotiation-failure failure , - No further details , , , (20) , (21), ( 22), (23) , (24) , (126) , - Locally definable (127) , - No further details (255) ``` When the KMASE receives an Estat KPDU, it delivers a confirm primitive with estatus, and optionally doNotTryBefore, as the result parameter. The KMASE includes the doNotTryBefore parameter in the Estat when the failure is service-not-available-at-this-time. The parameter doNotTryBefore is UTC Time and is the earliest time the initiator KMAP should attempt the request again.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_01202", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Telehealth Remote Patient Monitoring Ecosystem say about C-4 Threats? (Part 5) According to Securing Telehealth Remote Patient Monitoring Ecosystem, C-4 Threats: veat in these assumptions is that HDOs that engage with telehealth platform providers should be provided assurance that third parties that they engage deploy mature privacy and cybersecurity programs. Table C-4 Threats Applied to the Telehealth Platform Provider | C, I, A | Threat Event | Description | Likelihood | |-----------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| | C | phishing | Telehealth platform provider workforce with privileged access may be susceptible to spear phishing attacks. | high | | I, A | malicious software | Telehealth platform provider workforce with privileged access to permitting allows malicious software to be introduced into the telehealth platform environment. | moderate | | I, A | command and control | Telehealth platform provider workforce with privileged access to permitting allows threat actors to execute arbitrary code and perform privileged functions. | low | | A | ransomware | Ransomware may be introduced into the telehealth platform provider environment either as links or attachments found in phishing emails or may be introduced through local media. | moderate | | C | credential escalation | Malware may be introduced to the telehealth platform provider environment that allows threat actors to execute arbitrary code and perform privileged functions. | moderate | | I, A | OS or application disruption | Malware may be introduced into the telehealth platform provider environment that disrupts the operating system or applications.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: threat actor, malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_01203", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2017 NIST_ITL Cybersecurity Program Annual Report say about NIST Cybersecurity for IoT Program? (Part 2) According to 2017 NIST_ITL Cybersecurity Program Annual Report, NIST Cybersecurity for IoT Program: ional IoT cybersecurity standards. The Task Group has 54 federal employee participants representing 13 agencies and will convene in early FY 2018 to determine the next steps for its draft report. If approved, NIST is prepared to take this document through the NISTIR process in FY 2018 to collect industry input on specific areas, such as market adoption and challenges associated with the adoption of existing standards. In FY 2018, the Cybersecurity for IoT Program will continue collaborating with stakeholders as NIST begins drafting guidance for IoT security and privacy. As part of the drafting process, the team will hold town-hall meetings for input on discussion drafts. The document is intended to educate federal agencies on common high-level security and privacy risks for IoT, and to introduce practical risk management considerations for IoT product selection, deployment, protection, and operation. Additional information regarding the broad portfolio of NIST activities for supporting secure IoT can be found on our program website.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01204", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Status Report on the Second Round of the NIST Lightweight Cryptography Standardization Process provide? (Section 86) During the final round, NIST is planning to host the fifth workshop to support the standardization process. NIST encourages further analysis of the candidates that did not advance to the final round. The candidates that proposed new modes of operation instantiated with AES might still be beneficial for general-purpose applications. The modes of operations of these candidates may be considered later under NIST's mode development project [277]. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ - [1] S\u00a8 onmez Turan M, McKay KA, C \u00b8 al\u0131k C \u00b8 , Chang D, Bassham I Lawrence E (2019) Status Report on the First Round of the NIST Lightweight Cryptography Standardization Process (National Institute of Standards and Technology), Report. https://doi.org/10.6028/NIST.IR.8268 - [2] Aagaard M, AlTawy R, Gong G, Mandal K, Rohit R (2020) Updates on ACE, Update to the NIST Lightweight Cryptography Standardization Process. documents/] round-2/status-update-sep2020/ace update.pdf. - [3] Dobraunig C, Eichlseder M, Mendel F, Schl\u00a8 affer M (2020) Status Update on Ascon v1.2, Update to the NIST Lightweight Cryptography Standardization Process. documents/round-2/status-update-sep2020/ascon update.pdf. - [4] Gueron S, Jha A, Nandi M (2020) Updates on COMET, Update to the NIST Lightweight Cryptography Standardization Process. https: //csrc.nist.gov/CSRC/media/Projects/lightweight-cryptography/documents/ round-2/status-update-sep2020/comet update.pdf. - [5] Riou S (2020) DryGASCON Status Update, Update to the NIST Lightweight Cryptography Standardization Process.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Second Round of the NIST Lightweight Cryptography Standardization Process."}]}
{"id": "nist_01205", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-11 in Guidelines for Smart Grid Cybersecurity? (Part 86) Control SI-11: at assets may be present to target for theft; introduce a virus or other attack to collect personal information. 33 As seen in the table, such data might be used in ways that raise privacy concerns. For example, granular smart grid data may allow numerous assumptions about the health of a dwelling\u2019s resident in which some insurance companies, employers, the press, civil litigants, and others could be interested. Most directly, specific medical devices may be uniquely identified through serial numbers or MAC addresses, or may have unique electrical signatures; if associated with data that identifies an individual resident, either could indicate that the resident suffers from a particular disease or condition that requires the device.82 More generally, inferences might be used to determine health patterns and risk. For example, the amount of time the computer or television is on could be compared to the amount of time the treadmill is used.83 Electricity usage data could also reveal how much the resident sleeps and whether he gets up in the middle of the night.84 Similarly, appliance usage data could indicate how often meals are cooked with the microwave, the stove, or not cooked at all, as well as implying the frequency of meals.85 Many of the parties listed in the \u201cPotential Privacy Impacts\u201d table (Table 5-3) will not be interested in the health of the resident and will wish to use the data for purposes such as efficiency monitoring, but some parties may be interested in the behavioral assumptions that could be made with such data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01206", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain VENDOR: according to NIST Computer Security Training & Awareness Course Compendium According to Computer Security Training & Awareness Course Compendium, VENDOR:: Computer Security Institute 600 Harrison Street San Francisco CA 94107 (415) 905-2626 This workshop is for data processing managers, security officers, and auditors who have little or no knowledge in the communications area. Because communications systems are so complex and vulnerable, the data processing operation is a substantial risk. You will learn about the basic concepts and the terminology needed to communicate effectively with technicians. The emphasis, however , is on vulnerabilities and the practical security safeguards you can implement Because the largest communications risk faced by most organizations is unauthorized access to their computers, considerable emphasis will be placed on how mainframe access control mechanisms interface with other communication security techniques. In particular, you will learn to address the three major risks -loss of network service, unauthorized access to your network and data center resources, and surveillance of your network traffic. \"Special Note\" You are encouraged to prepare, in advance of the Workshop, a description of specific communications security problems being faced within your own organization. Cases will be discussed as time permits and as issues arise during the Workshop. NOTE: Ask about available discount for government hosted classes. COURSE TITLE: Managing Computer Security-Mergs, Acq, and Divestitures COURSE LENGTH: 2 DAY", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Training & Awareness Course Compendium."}]}
{"id": "nist_01207", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Security-Focused Configuration Management of Information Systems say about 2.1 OVERVIEW? According to Guide for Security-Focused Configuration Management of Information Systems, 2.1 OVERVIEW: This section provides an overview of SecCM including its importance in managing organizational risks from systems, the basic terms associated with configuration management, and characterization of SecCM within the configuration management discipline.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_01208", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Digital Identity Guidelines_ Authentication and Authenticator Management provide? (Section 128) (FIPS) 140-3. NIST.FIPS.140-3 [FIPS201] National Institute of Standards and Technology (2022) Personal Identity Verification (PIV) of Federal Employees and Contractors. (U.S. Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) 201-3. NIST.FIPS.201-3 81 NIST SP 800-63B-4 July 2025 Digital Identity Guidelines Authentication and Authenticator Management [FISMA] Federal Information Security Modernization Act of 2014, Pub. L. 113-283, 128 Stat. 3073. Available at https://www.govinfo.gov/app/details/PLAW-113publ283 [IC3] Federal Bureau of Investigation (2024) Annual Reports - Internet Crime Complaint Center (IC3). Available at https://www.ic3.gov/AnnualReport/Reports/ [ISO/IEC2382-37] International Standards Organization (2022) Information technology \u2014 Vocabulary \u2014 Part 37: Biometrics (ISO, Geneva, Switzerland). Available at https: //www.iso.org/standard/73514.html [ISO/IEC9241-11] International Standards Organization (2018) ISO/IEC 9241-11 Ergonomics of human-system interaction \u2013 Part 11: Usability: Definitions and concepts (ISO, Geneva, Switzerland). Available at https://www.iso.org/standard/63500.html [ISO/IEC10646] International Standards Organization (2020) Information technology \u2014 Universal coded character set (UCS) (ISO, Geneva, Switzerland). Available at https: //www.iso.org/standard/76835.html [ISO/IEC19792] International Standards Organization (2009) Information technology \u2014 Security techniques \u2014 Security evaluation of biometrics (ISO, Geneva, Switzerland). Available at https://www.iso.org/standard/51521.html [ISO/IEC19795-1] International Standards Organization (2021) Information technology - Biometric performance testing and reporting Part 1: Principles and framework (ISO, Geneva, Switzerland).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Digital Identity Guidelines_ Authentication and Authenticator Management."}]}
{"id": "nist_01209", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT) say about Table 16 - Software Assurance Standards? (Part 13) According to Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT), Table 16 - Software Assurance Standards: Product Management: The product shall be designed and implemented such that it is possible to perform an update of the product's software, and to roll back an update Page 11, Section 11 | Approved Standard Guidance Available | Software Assurance: Standards that describe requirements and guidance for significantly decreasing the likelihood of software having vulnerabilities, either intentionally designed into the software or accidentally inserted at any time during its life cycle, and that the software functions in the intended manner. | Documents | SDO | Description | Maturity Level (Table 6) | |-------------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| | UL 2900-2-1 | UL | Security evaluation standard applies to the testing of network connected components of healthcare systems. It applies to, but is not limited to, the following key components: a) Medical devices; b) Accessories to medical devices; c) Medical device data systems; d) In vitro diagnostic devices; e) Health information technology; and f) Wellness devices.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_01210", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Users according to NIST Foundations of a Security Policy for Use of the National Research and Educational Network According to Foundations of a Security Policy for Use of the National Research and Educational Network, Users: - U2.1. Handle accounts in a responsible manner. - U2.2. Follow site procedures for security of personal data as well as for the computer system. Use file protection mechanisms to maintain appropriate file access control. - U2.3. Select and maintain good passwords. Do not share accounts. - U3.1. Help to protect the property of other individuals. Notify them of resources (e.g. files, accounts) left unprotected. - U3.2. Notify the System Administrator of a suspected or observed violation. - U5.1. Do not intentionally modify, destroy, read, or transfer information in an unauthorized manner; do not intentionally deny others authorized access to or use of network resources and information. - U5.2. Provide the correct identity and authentication information when requested and not attempt to assume any other party's identity.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Foundations of a Security Policy for Use of the National Research and Educational Network."}]}
{"id": "nist_01211", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Configure Mediator Server according to NIST Securing Telehealth Remote Patient Monitoring Ecosystem According to Securing Telehealth Remote Patient Monitoring Ecosystem, Configure Mediator Server: 1. Open File Explorer and navigate to C:\\Program Files\\LogRhythm. 2. Navigate to Mediator Server. 3. Double-click lrconfig application file. 4. In the LogRhythm Data Processor Local Configuration Manager window, provide the following information and leave the remaining fields as their default values: - a. Server: - 192.168.45.20 - b. Password: ********** 5. Click Test Connection, then follow the instruction of the alert window to complete the test connection. 6. Click Apply and then click OK. <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_01212", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.1.7 Applying Destination Group to End Points according to NIST Securing Property Management Systems According to Securing Property Management Systems, 2.1.7 Applying Destination Group to End Points: The following instructions detail how to apply a previously created destination group to a registered end point. 1. In the Cryptonite Policy tab, click Enable Editing: 2. Locate the box titled Endpoints on the right hand of the screen. Right-click on any of the end points. 3. Select Assign Endpoints to Destination Groups: <!-- image --> <!-- image --> 4. Locate and select the desired end point(s) under All Endpoints: <!-- image --> 5. Select the desired destination group(s) under Available Destination Groups: 6. Click &gt;&gt;: <!-- image --> <!-- image --> 7. Click Save.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Property Management Systems."}]}
{"id": "nist_01213", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Discussion: Do not let the adversary", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_01214", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2012 Annual Report say about Hash Algorithm Standards and Security Guidelines? (Part 3) According to Computer Security Division 2012 Annual Report, Hash Algorithm Standards and Security Guidelines: action-then-Expansion , and to discuss different approved hash-based key derivation functions. The revision was completeGLYPH(cmap:df00) anGLYPH(cmap:df00) publisheGLYPH(cmap:df00) in August 2012. In 2013, work will begin on a new revision of the stanGLYPH(cmap:df00)arGLYPH(cmap:df00) (FIPS 180-5), which will contain the new hash algorithm resulting from the SHA-3 competition discussed in the Hash Algorithms and the Secure Hash Algorithm (SHA)-3 Competition section of this report.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_01215", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Summary according to NIST Picture Password_ A Visual Login Technique for Mobile Devices According to Picture Password_ A Visual Login Technique for Mobile Devices, Summary: Picture Password is a visual login technique that matches the capabilities and limitations of most handheld devices and provides a simple and intuitive way for users to authenticate. Besides user authentication, Picture Password may also be used in other security applications where conventional passwords have been used traditionally. For example, password-based encryption, whereby a password value is transformed into a cryptographic key suitable for encrypting files or other information could rely on keys derived by the image selection technique of Picture Password. The mechanism is relatively straightforward and flexible, and one that is suitable for many users, organizations, and types of devices. The approach provides a simple and hopefully entertaining way for users to authenticate to a device, which should remove much of the burden associated with employing an authentication mechanism. Moreover, with style dependent image selection, password reuse, and embedded salting, the mechanism is superior to using traditional ASCII passwords of comparable length. While the solution is particularly well suited for handheld devices, Picture Password can also be used in a wide range of platforms, from appliances having single embedded processors, to large-scale multi-processor computers.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Picture Password_ A Visual Login Technique for Mobile Devices."}]}
{"id": "nist_01216", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2016 NIST_ITL Cybersecurity Program Annual Report say about https:/ /doi.org/10.1109/QRS.2016.29? (Part 2) According to 2016 NIST_ITL Cybersecurity Program Annual Report, https:/ /doi.org/10.1109/QRS.2016.29: led to a collaboration with NIST to provide replacements. Test Suites 45 and 46 are analyzed, discussed, and updated to improve accuracy, consistency, reciseness, and automation. Empirical results show metrics such as recall, precision, and F-Measure are all impacted by invalid base assumptions regarding the test suites. B. Stivalet and E. N. Fong, Large Scale Generation of Complex and Faulty PHP Test Cases , 2016 IEEE International Conference on Software Testing, Verification and Validation (ICST), Chicago, IL, April 2016, https:/ /doi.org/10.1109/ICST.2016.43 Developing good test cases is an intellectually demanding and critical task, and it has a strong impact on the effectiveness and efficiency of the whole testing process. This paper presents an automated generator of test cases, which are designed to evaluate source code security analyzers. The generator produces PHP: Hypertext Preprocessor (PHP) programs with most common vulnerabilities embedded in various code complexities. It also produces programs without vulnerabilities to test for false positives. The generator is modular and extensible. We describe its internal design and how it works. The generated PHP test cases were added to the Software Assurance Reference Dataset (SARD) and will be used to assess the effectiveness of static analyzers. We conclude with the current state of the tool, its benefits and future work. F. E. Boland and C. D. De Oliveira, A Real World Software Assurance Test Suite , The 27th Annual IEEE Software Technology Conference, Long Beach, CA, October 2015. The design of a test suite to test and measure software assurance using automated tools must have the following characteristics: relevance, statistical significance, and inclusion ground truth.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01217", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Telehealth Remote Patient Monitoring Ecosystem say about 3 Approach? According to Securing Telehealth Remote Patient Monitoring Ecosystem, 3 Approach: RPM is a telehealth use case wherein healthcare providers can use internet-based technologies to track biometric data from the patient's home. Patients may have chronic or recurring health conditions that require regular clinical monitoring; however, in-person visitation may be impractical or undesirable. Technology enables capturing biometric and patient-generated data, having those data relayed to systems that clinicians may use to evaluate a patient, and bidirectional communication of the data between the patient and clinician. RPM may be an appropriate means for performing healthcare in pandemic scenarios or to address patients who may live in parts of the country where healthcare settings or practitioners are scarce. The NCCoE collaborated with a healthcare Community of Interest (COI) that included technology and cybersecurity vendors, healthcare cybersecurity subject matter experts, and healthcare systems to identify RPM use cases, data workflows, ecosystem actor, and general deployment architecture. Further, with the assistance of the COI and external cybersecurity subject matter experts, a risk assessment was performed and reviewed, thereby confirming the measures and outcomes that were determined from the risk assessment activity. Additionally, this project reviewed NIST SP 800-171 Rev. 2, Protecting Controlled Unclassified Information in Nonfederal Systems and Organization s [1], as well as NIST SP 800-181 Rev. 1, Workforce Framework for Cybersecurity (NICE Framework) [2], for further guidance. These documents serve as . background for this project, with primary emphasis on the NIST Cybersecurity Framework [3], the NIST Risk Management Framework [4], and the NIST Privacy Framework [5].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_01218", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Non-Fungible Token Security provide? (Section 26) their rightful owner. 6. If a smart contract enables the contract manager to restore stolen tokens, this feature could be used by the manager to confiscate, freeze, or unilaterally transfer tokens. 7. A smart contract may not allow a manager to restore stolen tokens, but the smart contract may have a manager-controlled update mechanism whereby this feature could be added in the future (enabling the previously mentioned security concern). 8. Coding errors in the smart contract could enable attackers to steal tokens and transfer them to their accounts. 9. Fractional ownership increases the NFT attack surface by involving an additional thirdparty smart contract that handles the fractional ownership. 10. Owners of fractional shares may not be aware that they could lose their shares through a forced buyout. 11. Inaccurately stored metadata (either done maliciously or accidentally) can delink an NFT from the asset it represents and make it worthless. 12. Server errors that make a digital asset unavailable (e.g., corrupted file, server failure, or storage service discontinuation) could effectively delink an NFT from the asset it represents and make it worthless. 13. If the off-blockchain table linking NFT identifiers to URLs is compromised, an attacker could delink NFTs from their assets and/or change which NFTs represent which assets. 14. If off-blockchain tables are used to link NFT identifiers to URLs, the owner of the table could use their access to delink NFTs and/or change which NFTs represent which assets. 15. An NFT owner may not realize that their account and information on the NFTs that their account owns are public information on the associated blockchain. 16. While blockchain accounts are anonymous, they can be de-anonymized through account owner purchases that include personally identifying information (e.g., name and address). 17. A blockchain could undergo an attack enabling changes to blockchain history (this is unlikely with established blockchains). 18.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: token, sso. Contains security framework guidance for authentication systems. Source: Non-Fungible Token Security."}]}
{"id": "nist_01219", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about Examine? According to Assessing Security Requirements for Controlled Unclassified Information, Examine: [SELECT FROM: security assessment and monitoring policy and procedures; procedures for plans of action and milestones; security assessment plan; security assessment report; security assessment evidence; plan of action and milestones; system security plan; other relevant documents or records]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_01220", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Information Security Handbook_ A Guide for Managers say about 4.2 Components: Awareness, Training, Education, and Certification? According to Information Security Handbook_ A Guide for Managers, 4.2 Components: Awareness, Training, Education, and Certification: An agency's information security program policy should contain a clear and distinct section devoted to agency-wide requirements for the awareness and training program. Although security awareness and training is generally referred to as 'a' program, many organizations consider awareness and training to be two distinct functions, each with separate purposes, goals, and approaches. Proper implementation of these components (with consideration of options like education and professional certification) promotes professional development, which leads to a high-performance workforce. Requirements for the security awareness and training program should be documented in the enterprise-level policy and should include: - Definition of security roles and responsibilities; - Implementation of the program plan; and - Development of program strategy and a program plan; - Maintenance of the security awareness and training program. 32", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_01221", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2007 Annual Report say about Developing a Unified Framework for Information Security? According to Computer Security Division 2007 Annual Report, Developing a Unified Framework for Information Security: The Computer Security Division provided technical support to the Chief Information Officer, Director of National Intelligence (DNI), in a major Intelligence Community initiative to transform the certification and accreditation process for information systems and to build a common framework for information security across the federal government. The division worked with the DNI to assist the Intelligence Community in reengineering the security standards and guidelines for national security systems, building on a common foundation established by NIST in its FISMA Implementation Project. The project is using as starting points the NIST Risk Management Framework, the security controls from NIST SP 800-53, and the security categorization paradigm from FIPS 199. The DNI hopes to adopt a common foundation for information security based on NIST security standards and guidelines and build unique national security system requirements on top of that foundation, when necessary. When completed, the project will result in greater standardization of information security standards and guidelines across the federal government which will lead to more cost-effective and consistent security for federal information systems, both for national security-related systems and non national security-related systems. Contact: Dr. Ron Ross (301) 975-5390 ron.ross@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, risk management framework, fips. General security reference material without sensitive content. Source: Computer Security Division 2007 Annual Report."}]}
{"id": "nist_01222", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Minimum Security Requirements for Multi-User Operating Systems say about GLOSSARY? (Part 1) According to Minimum Security Requirements for Multi-User Operating Systems, GLOSSARY: GLOSSARY password schemes, biometrics devices, cryptographic methods, and onetime passwords (usually implemented with token based cards.) Authentication Information. Information used to establish the validity of a claimed identity. [ISO] Authorized. Entitled to a specific mode of access. Channel. An information transfer path within a system. May also refer to the mechanism by which the path is effected. [TCSEC] Clear-text. Intelligible data, the semantic content of which is available. [ISO] Configuration. The selection of one of the sets of possible combinations of features of a system. [ITSEC] Customer-Specifiable. The features of a MSR-compliant system that are set with a default value by the manufacturer, but can be reset after delivery by the customer to reflect the customer's security policy. These features are usually reset at the time of installation by an administrator or other customer authorized person and cannot be changed without the appropriate privilege at other times. Group. A named collection of userlDs. Identification. A unique, auditable representation of identity within the system usually in the form of a simple character string for each individual user, machine, software component or any other entity. Integrity. The property that data has not been altered or destroyed in an unauthorized manner. [ISO] The prevention of the unauthorized modification of information. [ITSEC] The state that exists when computerized data is the same as that in the source documents and has not been exposed to accidental or malicious alteration or destruction. [TCSEC] Mechanism. An operating system entry point or separate operating system support program that performs a specific action or related group of actions. Normal Operation. The process of using a system. [ITSEC] Owner. A user who can modify the contents of an access control list. Password. Confidential authentication information, usually composed of a string of characters. [ISO] Privilege.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, token. Contains security framework guidance for authentication systems. Source: Minimum Security Requirements for Multi-User Operating Systems."}]}
{"id": "nist_01223", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i? (Part 105) Control ES-1: ir products so that these conditions are configurable via policy. ## 5.3.3 Distinguishing RSN and Pre-RSN WLANs The outcome of the discovery phase is very important to the security posture of a WLAN. In an RSN, APs do not allow associations from pre-RSN STAs-those STAs that do not support data confidentiality and integrity mechanisms beyond WEP and that cannot create PMK security associations. For example, an ESS might contain several IEEE 802.11 STAs and three APs. Suppose that all STAs within this ESS use pre-shared keying (as opposed to the IEEE 802.1X technique) and the CCMP security method for both unicast and broadcast traffic. These parameters are negotiated through the discovery phase's security parameter negotiation. Because the three APs have allowed only RSNAs with the seven STAs, they provide an RSN. In contrast, suppose that the STAs in the ESS do not all operate with CCMP; two are using pre-RSN capabilities. These stations, forming a Transition Security Network, are using WEP and shared key authentication. As a result, this WLAN is not an RSN, even though five of its STAs are operating with CCMP. The two STAs using pre-RSN capabilities create significant security holes that can negatively impact the security of the other components of the WLAN. Not only are the communications between the STA and AP not protected strongly, but also the AP must be configured to permit the use of pre-RSN capabilities. This could allow an attacker within range of the AP to establish unauthorized connections to it, potentially gaining access to other resources. ## 5.4 Authentication Phase Upon successful completion of the discovery phase, the STA and AP enter the second phase in the establishment of an RSNA: the authentication phase. This phase provides the means for a STA to prove its identity to the WLAN. This security service is critical for preventing unauthorized access to network resources.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i."}]}
{"id": "nist_01224", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key-Derivation Methods in Key-Establishment Schemes say about 8.3 MAC Algorithms used for Extraction and Expansion? (Part 2) According to Recommendation for Key-Derivation Methods in Key-Establishment Schemes, 8.3 MAC Algorithms used for Extraction and Expansion: C algorithm selected for the implementation of a two-step key-derivation method shall be capable of supporting the targeted security strength as determined by consulting Tables 4 and 5 in Section 5.2. (This limits the use of AES-CMAC to cases where the targeted security strength is no more than 128 bits.) The imposed restrictions are intended to reduce the overall complexity of the resulting implementations, promote interoperability, and simplify the negotiation of the parameters and auxiliary functions affecting the security strength supported by the key-derivation procedure. Note: At this time, KMAC has not been specified for use in the implementation of a two-step keyderivation procedure. This restriction may be reconsidered once a KMAC-based KDF has been approved for use as a PRF-based KDF in a revision of [SP 800-108].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key-Derivation Methods in Key-Establishment Schemes."}]}
{"id": "nist_01225", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Information Security Handbook_ A Guide for Managers provide? (Section 271) blishing a successful incident response program. One of the first planning tasks should be to develop an organization-specific definition of the term 'incident' so that the scope of the term is clear. Additional tasks that should be performed during the preparation phase include the following: - Create an Incident Response Policy. The policy should define what events are considered incidents, establish the organizational structure for incident response, define roles and responsibilities, and list the organization's incident reporting requirements. - Develop Incident Response and Reporting Procedures. Based on the incident response policy, standard operating procedures (SOPs) are a delineation of the specific technical processes, techniques, checklists, and forms used by the incident response team. SOPs should be comprehensive and detailed to ensure that the organization's priorities are properly reflected in response operations. In addition, following standardized response procedures is also an effective way to minimize errors, particularly those that might be caused by incident handling pace and stress. Prior to implementation, the organization should test incident response SOPs in order to validate their accuracy and usefulness. Once validated, the SOPs must be widely disseminated throughout the organization. Incidents can occur in countless and unpredictable ways; therefore, it is impractical to develop comprehensive procedures with step-by-step instructions for handling every incident. The best that the organization can do is prepare to handle any type of incident, and more specifically, to handle common types of incidents. - Establish Guidelines for Communicating with External Parties. During the incident response process, the organization may need to communicate with outside parties, including other incident response teams, law enforcement, the media, vendors, and external victims.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_01226", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-4009 in NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3? (Part 120) Control SI-4009: | 3176 | INCITS | International Committee for Information Technology Standards | | 3177 free | IoT | Internet of Things | | 3178 | ISO | International Organization for Standardization | | 3179 of | ISSEA | International Systems Security Engineering Association | | 3180 charge | IT | Information Technology | | 3181 | ITL | Information Technology Laboratory at NIST | | 3182 | KMS | Key Management Systems | | 3183 from: | M2M | Machine to Machine | | 3184 | MAC | Media Access Control | | 3185 https://doi.org/10.6028/NIST.SP.1500-4r2 | MBSE | Model-based Systems Engineering | | 3186 | MIFE | Multi-input Functional Encryption | | | ModSim | Modeling and Simulation | | 3187 3188 | MPC | Multi-party Computations | | 3190 | NBD-PWG | NIST Big Data Public Working Group | | 3191 | NBDRA | NIST Big Data Reference | | | | Architecture | | 3192 | NBD-SPSL | NIST Big Data Security and Privacy Safety Levels | | 3193 | NSTIC | National Strategy for Trusted Identities in Cyberspace | | 3194 3195 | OASIS OECD | Organization for the Advancement of Structured Information Organisation for Economic Co-Operation", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, key management, sso. Contains security framework guidance for authentication systems. Source: NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3."}]}
{"id": "nist_01227", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain A.3.6. Data Protection 1 according to NIST Recommended Cybersecurity Requirements for Consumer-Grade Router Products According to Recommended Cybersecurity Requirements for Consumer-Grade Router Products, A.3.6. Data Protection 1: Each consumer-grade router product component protects data it stores via secure means, such as strong encryption (e.g., FIPS-approved algorithms). All stored data, including data used for authentication (e.g., salting and hashing stored passwords or passphrases) must be protected. Critical data (including firmware images) can be securely backed up and recovered. Related Standards Requirements: ``` BBF SEC.FIRMWARE.2 CL DRP-001, KEY-001, KEY-002, KEY-003, HR-003, HR-004, SB-005, OOB-002 BSI (4.1.1) IMDA 4.5 SP 800-193 4.1.1(1-4, 7), 4.1.4(1-2), 4.2.2, 4.2.3(1-2), 4.2.4(5), 4.4.1 (1, 2a, 7, 12), 4.4.2(1-2, 4, 6-8, 10) ```", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommended Cybersecurity Requirements for Consumer-Grade Router Products."}]}
{"id": "nist_01228", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2014 Annual Report say about Automated Security Testing and Test Suite Development? (Part 4) According to Computer Security Division 2014 Annual Report, Automated Security Testing and Test Suite Development: The CAVP currently has algorithm validation testing for the following cryptographic algorithms: | CRYPTOGRAPHIC ALGORITHM/COMPONENT | SPECIAL PUBLICATION OR FIPS | |----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Triple Data Encryption Standard (TDES) | SP 800-67, Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher, and SP 800-38A, Recommendation for Block Cipher Modes of Operation-Methods and Techniques | | Advanced Encryption Standard (AES) | FIPS 197, Advanced Encryption Standard, and SP 800-38A, Recommendation for Block Cipher Modes of Operation-Methods and Techniques | | Digital Signature Standard (DSS) | FIPS 186-2, Digital Signature Standard (DSS), with change notice 1 | | Digital Signature Standard (DSS) | FIPS 186-4, Digital Signature Standard (DSS) | | Elliptic Curve Digital Signature Algorithm (ECDSA) | FIPS 186-2, Digital Signature Standard (DSS), with change notice 1 and ANS X9.62 | | Elliptic Curve Digital Signature Algorithm (ECDSA) | FIPS 186-4, Digital Signature Standard (DSS), and ANS X9.62 | | RSA algorithm | ANSI X9.31 and Public Key Cryptography Standards (PKCS) #1 v2.1: RSA Cryptography Standard-2002 | | RSA algorithm | FIPS 186-4, Digital Signature Standard (DSS), and ANSI X9.31 and Public Key Cryptography Standards (PKCS) #1 v2.1: RSA Cryptography Standard-2002 | | Hashing algorithms SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224,", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_01229", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TG-15 in Audit and Evaluation of Computer Security? (Part 26) Control TG-15: above three. The objectives of a security audit can be achieved by looking for information detailed in a log on any of the above components. would show five basic types of information: This log 1. WHO\u2014 identifies initiator of an action, 2. FUNCTION\u2014 describes the processing activity, 3. WHAT\u2014 identifies objects of processing activity, 4. STATUS\u2014 refers to FUNCTION and associated initiator and affected objects 5. TIME\u2014 gives it a date-time stamp. An example is given of the security information requirements for an EFTS system. xxvii Post-processing techniques are then described under the basic four For Access and input one would use logs of components of an audit. successes, logs of failures, and a log continuity check. For Process there are manual checking, control totals, test data, integrated test facility, tagging, extended record maintenance, tracing, mapping, recom- pilation, parallel simulation, and retrieval programs. For Output there are output listings of dispositions and authorization listings. The conclusions and recommendations of the group were: 1. Existing software tools offer much but could be made easier to use by a) publishing a catalog of these tools for the auditor. b) creating facilities to easily combine the use of two of these tools. 2. Needed techniques are a) a method for maintaining the security of the security log. (Some possibilities are using present operating systems, or using a special tamper proof recording device to record all activity, or a complete hardware monitor similar to a cockpit flight recorder). b) higher level software to access and manipulate logs. SESSION ON INTERACTIVE AUDIT TOOLS AND TECHNIQUES This group responded to the question, \"What are the interactive au- dit tools and techniques available or needed to permit on-line auditing of computer security?\" This session explored a subject area which is in the very early stages of development.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Audit and Evaluation of Computer Security."}]}
{"id": "nist_01230", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide for Security-Focused Configuration Management of Information Systems? (Part 32) Control ES-1: omputing environments such as development, test, and production. When a new baseline configuration is established, the implication is that all of the changes from the last baseline have been approved. Older versions of approved baseline configurations are maintained and made available for review or rollback as needed. Developing and documenting the baseline configuration for a system is part of the Identifying and Implementing Configurations phase of SecCM and supports the implementation of NIST [SP 800-53] control CM-2 Baseline Configuration. ## 2.3.8 CONFIGURATION CHANGE CONTROL Configuration 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. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Configuration change control falls under the Controlling Configuration Changes phase of SecCM and supports the implementation of NIST [SP 800-53] control CM-3 Configuration Change Control and CM-5 Access Restrictions for Change .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_01231", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TX-100 in Security for Dial-Up Lines? (Part 6) Control TX-100: ton Quaa. #1C07 Melville, NY 11747 (516) 752-7790 | | SITE AUTHEN- TICATION DEVICE | icable Manufacturin 4800 Dundas St. Wes Toronto. ONT M9A1B1 (416) 236-1604 | | DataLock & DataKey | MicroFrame Inc, 205 Livingston New Brunswick, (201) 828-4499 Ave NJ 0 8901 | | DL 1000 WITH DK 1125 (PPD w/ tml. authen. dev.) DL 2400 WITH DK 2400 (PPD/modem & tml. authen.) | Optimum Electronics Inc p;o. Box 250 North Haven, CT 06473 (203) 239-6098 | Note: The National Bureau of Standards (NBS) endorses NO commercial products. All devices of the types specified known to the author at the time of publication have oeen included in these tables. No endorsement, approval or recommendation of them by NBS is implied by their inclusion. ## SECURITY FOR DIAL-DP LINES ## APPENDIX B ## REFERENCES AND ADDITIONAL READING - ATKIW85 Atkins, William, \"Jesse James At the Terminal,\" Harvard Business Review, July/August 1985. - CALHG83 Calhoun, George, \"Decoding the 'Secret' Password Is An Easy Key to Computer Fraud,\" Telephony . April 4, 1983. - CORNH85 Cornwall, Hugo, The Hacker's Handbook , London, Century Communications, Ltd., 1985. - DATAP83 \"Security for Dial-Up Systems Access,\" Data Processing &amp; Communications Security . September/October, 1983. - EDWAR82 Edwards, Robert W. , and Lynda E. Edwards, \"Unauthorized Entry,\" I CP Interface Administrative and Accounting . Winter, 1982, pp. 22 -26. - FIPS31 FIPS PUB 31, Guidelines for Automatic Data Processing Physical Security and Risk Management. - FIPS39 FIPS PUB 39, Glossary for Computer Systems Security. - FIPS41 FIPS PUB 41, Computer Security Guidelines for Implementing the Privacy Act of 1974. - FIPS46 FIPS PUB 46, Data Encryption Standard. - FIPS4 8 FIPS PUB 4 8, Guidelines on Evaluation of Techniques for Automated Personal Identification.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security for Dial-Up Lines."}]}
{"id": "nist_01232", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CA-7 in A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)? (Part 10) Control CA-7: df. [SP 800-108] NIST Special Publication (SP) 800-108, Recommendation for Key Derivation Using Pseudorandom Functions , October 2009. [SP 800-115] NIST Special Publication (SP) 800-115, Technical Guide to Information Security Testing and Assessment , September 2008. [SP 800-126] NIST Special Publication (SP) 800-126 Rev. 2, The Technical Specification for the Security Content Automation Protocol (SCAP): SCAP Version 1.2 , September 2011. [SP 800-130] NIST Special Publication (SP) 800-130, A Framework for Designing Cryptographic Key Management Systems , August 2013. [SP 800-131A] Draft NIST Special Publication (SP) 800-131A Revision 1, Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths , July 2015. [SP 800-133] NIST Special Publication (SP) 800-133, Recommendation for Cryptographic Key Generation , December 2012. [SP 800-137] NIST Special Publication (SP) 800-137, Information Security Continuous Monitoring for Federal Information Systems and Organizations , September 2011. ## Appendix B: Glossary This glossary defines terms that are used in this Profile, some of which may also be defined in the Framework. | Access control system | A set of procedures and/or processes, normally automated, which allows access to a controlled area or to information to be controlled, in accordance with pre-established policies and rules.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, key management. Contains security framework guidance for authentication systems. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_01233", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Policy Machine_ Features, Architecture, and Specification say about 5.1.1 Electronic Mail? (Part 3) According to Policy Machine_ Features, Architecture, and Specification, 5.1.1 Electronic Mail: r can any mail objects, if they existed, be deleted. The administrative associations and prohibitions specified for the user complement those shown above and define the remaining actions for the user. Figure 11 illustrates the authorization graph containing the additional associations and prohibitions needed. Figure 11: Authorization Graph with Administrative Associations and Prohibitions <!-- image --> The rationale behind the associations and prohibitions that are illustrated in Figure 11 is as follows: - \uf0a7 The association between ID u2 and Inboxes allows user u2 to create messages in any user's inbox, including its own. Since the inbox of every mail system user gets assigned to Inboxes when the user is established, and the properties over Inboxes are inherited, the association essentially grants a system-wide authority. - \uf0a7 The prohibition between u2 and In u2 serves as a counter to the system-wide authority granted to every user through the previous association. Prohibitions are illustrated similarly to associations, but with a different style and orientation of connector. This prohibition denies the user from creating messages within its own inbox, slightly overriding the system-wide authority to create messages in any inbox. - \uf0a7 The association between ID u2 and In u2 allows the user to delete messages from its own inbox. - \uf0a7 To create and delete messages within the containers Out ui, Draft ui, and Trash ui, an association granting such authorization is needed between ID u2 and each of those containers. A few improvements can be made to the current policy specification. For example, a user can update a copy of a sent message residing in its outbox, which can bring about an unwanted inconsistency from what was actually sent.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Policy Machine_ Features, Architecture, and Specification."}]}
{"id": "nist_01234", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Three functions are defined over WFNs according to Common Platform Enumeration_ Naming Specification Version 2.3? Three functions are defined over WFNs: new , get, and set . These functions are used in defining binding and unbinding procedures in Section 6.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Platform Enumeration_ Naming Specification Version 2.3."}]}
{"id": "nist_01235", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2014 Annual Report say about C CONTACT:? According to Computer Security Division 2014 Annual Report, C CONTACT:: Mr. Stephen Quinn (301) 975-6967 stephen.quinn@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_01236", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines on Electronic Mail Security provide? (Section 93) information, monitor users' actions (e.g., keystrokes), and perform other malicious actions. Determining whether to allow certain types of attachments can be a difficult decision for an organization. Not allowing any attachments would simplify a system and make it more secure; however, it would dramatically reduce its usefulness, and users might employ encoding tricks to work around the restriction to 'get the job done'. Ultimately, organizations choose to allow at least some email attachments. Organizations should determine which types of attachments to allow. The simplest approach is to allow all types of attachments. If this is the case, then some sort of malware scanner (e.g., anti-virus software, anti-spyware software) should be installed in the mail transit path to filter out known malware, and perhaps even some behavior blocking utility installed at the client to prevent any unwanted operations by executable attachments from occurring. A better approach is to filter potentially dangerous attachment types (e.g., .vbs, .ws, .wsc file extensions) at the mail server or mail gateway, while conducting malware scans on allowed file types. Although filtering on such extensions is a good first step, its effectiveness is limited because attackers can alter the extensions. Instead of simply checking the extension, filtering should check the file header, footer, or other identifying aspects of the file if possible to identify the attachment. Organizations might also wish to consider setting different rules for internally originated versus externally originated email or trusted versus untrusted organizations (e.g., trust .gov/.mil domains), although this latter option is subject to email address spoofing. Attachment filtering is not completely effective unless all attachments are blocked, and that is not feasible. Some of the most useful attachment types, such as those from office productivity suites, are also some of the riskiest.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_01237", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-6 in NIST_SP_800-37r2_Risk_Management_Framework? (Part 253) Control AM-6: the system owner is responsible for the development and maintenance of the security and privacy plans and ensures that the system is operated in accordance with the selected and implemented controls. In coordination with the information owner/steward, the system owner decides who has access to the system (and with what types of privileges or access rights). 122 The system owner ensures that system users and support personnel receive the requisite security and privacy training. Based on guidance from the authorizing official, the system owner informs organizational officials of the need to conduct the authorization, ensures that resources are available for the effort, and provides the required system access, information, and documentation to control assessors. The system owner receives the security and privacy assessment results from the control assessors. After taking appropriate steps to reduce or eliminate vulnerabilities or security and privacy risks, the system owner assembles the authorization package and submits the package to the authorizing official or the authorizing official designated representative for adjudication. 123 121 Organizations may refer to system owners as program managers or business/asset owners. 122 The responsibility for deciding who has access to specific information within an organizational system (and with what types of privileges or access rights) may reside with the information owner/steward. 123 The authorizing official may choose to designate an individual other than the system owner to compile and assemble the information for the authorization package. In this situation, the designated individual coordinates the compilation and assembly activities with the system owner.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_01238", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.5 Disposal Phase according to NIST Information Security Handbook_ A Guide for Managers According to Information Security Handbook_ A Guide for Managers, 3.5 Disposal Phase: The disposal phase of the system life cycle refers to the process of preserving (if applicable) and discarding system information, hardware, and software. This step is extremely important because during this phase, information, hardware, and software are moved to another system, archived, discarded, or destroyed. If performed improperly, the disposal phase can result in the unauthorized disclosure of sensitive data. When archiving information, organizations should consider the need and methods for future retrieval. While electronic information is relatively easy to store and retrieve, problems can arise if the technology used to create the records is no longer available in the future as a result of obsolescence or incompatibility with new technologies. Additionally, the organization should consider what measures must be taken for the future use of data that has been encrypted, such as taking appropriate steps to ensure the secure long-term storage of cryptographic keys. It is equally important to consider legal requirements for records retention when disposing of information systems. For federal systems, system management officials should consult with their office responsible for retaining and archiving federal records. The removal of information from a storage medium, such as a hard disk or tape, is called sanitization. There are four categories of media sanitization: disposal, 20 See Chapter 14, Configuration Management, of this guide for additional guidance on configuration management. clearing, purging, and destroying. 21 Because different kinds of sanitization provide different levels of information protection, organizations should use information security requirements as a guide for selecting the sanitization method that best suits their needs.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_01239", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Secure Data Network Systems (SDNS) Access Control Documents provide? (Section 35) and (when used) an Auxiliary Vector. (SDNS) ASSOCIATION -A communications interaction between peer entities, which may occur over either connection-oriented or connectionless communication services. (SDNS) AUDIT -An independent review and examination of system records and activities in order to test for adequacy of system controls, to ensure compliance with established policy and operational procedures, and to recommend any indicated changes in control, policy and procedures.(ISO 7498/2) AUTHENTICATION - The process of positively validating a claimed identity. Each authentication process has a corresponding degree of certainty as to the accuracy of the identity established. Both the authenticated identity and the degree of certainty are used by an access control process to select the correct subset of rights and privileges associated with that entity. (SDNS) AUTHORIZATION - The granting of rights or the subsequent possession of rights. (ISO 7498/2) AUXILIARY VECTOR (AV) - A holder for additional ID information which does not normally fit within the identity certificate or is optionally excluded from the identity certificate. The Auxiliary Vector is bound to the identity certificate. (SDNS) COMPOSITE ID -The assemblage of information contained in the identity certificate and the auxiliary vector. (SDNS) DATA ORIGIN AUTHENTICATION - The corroboration that the source of the data received is as claimed. (ISO 7498/2) END SYSTEM - Any computer-based system connected to the network and containing the necessary protocol interpreter software to initiate network access and carry out information exchange across the communications network. (Trusted Network Interpretation) ENFORCEMENT VECTOR (EV) -The resulting information from a successfully completed PAA process which denotes the evaluation of the two communicating entities' security policies. This vector is an intercomponent binding of security attributes of the requested communications association.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Access Control Documents."}]}
{"id": "nist_01240", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Protecting the Confidentiality of Personally Identifiable Information (PII) provide? (Section 49) h the database or other sources to identify specific individuals. Quantity of PII: A recent estimate indicated that the database has approximately 50 records with PII out of nearly 1000 total records. Data field sensitivity: The database's narrative text field contains user-supplied text and frequently includes information such as name, mailing address, email address, and phone numbers. Context of use: Because of the nature of the submissions (i.e., reporting claims of fraud, waste, or abuse), the disclosure of individuals' identities would likely cause some of the individuals making the claims to fear retribution by management and peers. Additionally, it could negatively impact individuals about whom accusations are made. The ensuing harm could include blackmail, severe emotional distress, loss of employment, and physical harm. A breach would also undermine employee and public trust in the organization. Access to and location of PII: The database is only accessed by a few people who investigate fraud, waste, and abuse claims. All access to the database occurs only from the organization's internal systems. Taking into account these factors, the organization determines that a breach of the database's confidentiality would likely cause catastrophic harm to some of the individuals and chooses to assign the PII confidentiality impact level of high . PII should be protected through a combination of measures, including operational safeguards, privacyspecific safeguards, and security controls. Many of these measures also correspond to several of the Fair Information Practices. Organizations should use a risk-based approach for protecting the confidentiality of PII. The PII safeguards provided in this section are complementary to other safeguards for data and may be used as one part of an organization's comprehensive approach to protecting the confidentiality of PII and implementing the Fair Information Practices.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)."}]}
{"id": "nist_01241", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does The Common Vulnerability Scoring System (CVSS) and its Applicability to Federal Agency Systems say about 3.2.1 Base Equation? According to The Common Vulnerability Scoring System (CVSS) and its Applicability to Federal Agency Systems, 3.2.1 Base Equation: The base equation is the foundation of CVSS scoring. The base equation is: ``` BaseScore = round_to_1_decimal(((0.6*Impact)+(0.4*Exploitability)-1.5)*f(Impact)) Impact = 10.41*(1-(1-ConfImpact)*(1-IntegImpact)*(1-AvailImpact)) Exploitability = 20* AccessVector*AccessComplexity*Authentication f(impact)= 0 if Impact=0, 1.176 otherwise AccessVector = case AccessVector of requires local access: 0.395 adjacent network accessible: 0.646 network accessible: 1.0 AccessComplexity = case AccessComplexity of high: 0.35 medium: 0.61 low: 0.71 Authentication = case Authentication of requires multiple instances of authentication: 0.45 requires single instance of authentication: 0.56 requires no authentication: 0.704 ConfImpact = case ConfidentialityImpact of ``` ``` none: partial: complete: 0.0 0.275 0.660 IntegImpact = case IntegrityImpact of none: 0.0 partial: 0.275 complete: 0.660 AvailImpact = case AvailabilityImpact of none: 0.0 partial: 0.275 complete: 0.660 ```", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: The Common Vulnerability Scoring System (CVSS) and its Applicability to Federal Agency Systems."}]}
{"id": "nist_01242", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation provide? (Section 228) rified. | |---------------------------------|----------------------------------------------------------------------------| | Actual Results | Test completed and functions as expected. | | Additional Comments (If Needed) | None | Test case SIDR-ROV-2.3.2 is identical to test case SIDR-ROV-2.3.1, except that IPv6 addresses are used instead of IPv4 addresses. The following configuration for Router AS65505 was updated prior to running the test: <!-- image --> <!-- image --> | Test Objective | Test SIDR Requirement CR-3.1.1. Show that the ROV-capable router correctly evaluates received routes in the following situation: A route is redistributed into BGP from an IGP. This route is initially evaluated as valid . The single ROA that had made the route valid is removed from the RPKI; there is no ROA that covers the route, so the route is re-evaluated as not found . ( valid \uf0e0 not found ) (This test case is analogous to test case SIDR-ROV-1.1.1, but this test case evaluates a route that has been redistributed into BGP from an IGP, rather than a route that was received as a BGP update.) | |------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Preconditions | The testbed is configured with the topology, IP addressing scheme, and ASNs as depicted in the Testbed Architecture in Figure E-1 and Figure E-2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_01243", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.1 Fire Service according to NIST Usability and Security Considerations for Public Safety Mobile Authentication According to Usability and Security Considerations for Public Safety Mobile Authentication, 3.1 Fire Service: Many fire situations require the coordination of all levels of government: federal, state, local, and tribal levels. For example, at the federal level, the United States Department of Agriculture (USDA) works with the Federal Emergency Management Agency (FEMA) to suppress fire situations, which often involves responding to forest and wildfires. Fire stations exist throughout the country, often run at the county or local level with volunteer firefighters sometimes composing the majority of a county level fire service. This is especially true in rural areas. The general responsibilities of the Fire Service include: - The prevention and suppression of fires, - The application of emergency medical treatment as needed, and - Assisting with search, rescue, and evacuation of fires. Firefighters often carry additional equipment beyond the minimum PPE required by National Fire Protection Association (NFPA) standards [5]. A PPE ensemble usually consists of a coat, pants, boots, helmet, gloves, hood, self-contained breathing apparatus (SCBA), flashlight, and LMR and carrying a bail-out rope system. Additionally, firefighters are often dragging a hose or carrying a thermal imager, hand tools such as an axe and/or Halligan tool, a 6-foot-long (1.8 m) pike pole, and/or a power saw, in addition to other items in their pockets. The total weight can be anywhere from approximately 34 kg to 45 kg (75 lbs. to 100 lbs.) or more of equipment [6]. Figure 1 shows an example of firefighter gear. Firefighters receive specialized training and must operate in extreme environments that require quick decisions under high stress. Most members of the Fire Service are cross-trained for medical first aid, since firefighters may respond to medical emergencies [7]. Figure 1 -Example Firefighter Gear <!-- image -->", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Usability and Security Considerations for Public Safety Mobile Authentication."}]}
{"id": "nist_01244", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices say about D.12 Education? According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, D.12 Education: Education refers to those activities that impart knowledge or understanding of a particular subject to the public. Education can take place at a formal school, college, university or other training program. This mission area includes all government programs that promote the education of the public, including both earned and unearned benefit programs.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_01245", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations say about A process to:? (Part 13) According to Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations, A process to:: onitored by entities other than those responsible for the system or application; entities either internal or external to t he organization where the system or application resides. See Common Control . | | Security Controls [FIPS 199] | The management, operational, and technical controls (i.e., safeguards or countermeasures) prescribed for an information system to protect the confidentiality, integrity, and availability of the system and its information. | | Security Domain [CNSSI 4009] | A domain that implements a security policy and is administered by a single authority. | | Security Impact Analysis [NIST SP 800-53] | The analysis conducted by an organizational official to determine the extent to which changes to the information system have affected the security state of the system. | | Security Incident | See Incident. | | Security Management Dashboard [NIST SP 800-128] | A tool that consolidates and communicates information relevant to the organizational security posture in nearreal-time to security management stakeholders. | |----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Security Objective [FIPS 199] | Confidentiality, integrity, or availability.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations."}]}
{"id": "nist_01246", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Technical Guide to Information Security Testing and Assessment say about 1.5. Document Structure? According to Technical Guide to Information Security Testing and Assessment, 1.5. Document Structure: Outlines the ROE's structure, and describes the content of each section.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technical Guide to Information Security Testing and Assessment."}]}
{"id": "nist_01247", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to SSL VPNs? (Part 6) Control ES-1: | | | | | | SSL VPN Planning and Implementation.........................................................................4-1 | SSL VPN Planning and Implementation.........................................................................4-1 | | | | 4.1 Identify Requirements..............................................................................................4-1 4.2 SSL VPNs and FIPS 140-2 Approval.......................................................................4-2 | 4.1 Identify Requirements..............................................................................................4-1 4.2 SSL VPNs and FIPS 140-2 Approval.......................................................................4-2 | | | | 4.2.1 | Versions of SSL............................................................................................4-3 | | | | 4.2.2 | Key Establishment Used by SSL..................................................................4-3 | | | | 4.2.3 | Hash Functions Used by | SSL.......................................................................4-4 | | | 4.2.4 | SSL Encryption.............................................................................................4-4 | | | | 4.2.5 | Certificates Used During SSL Negotiations..................................................4-4 | | | 4.3 | Design the Solution..................................................................................................4-5 | Design the Solution..................................................................................................4-5 | | | | 4.3.1 | Design the Access Control Policy.................................................................4-6 | | | | 4.3.2 | Design the Endpoint Security Policy.............................................................4-9 | | | | 4.3.3 | Select the Authentication Methods.............................................................4-11 | | | | 4.3.4 | Design the Architecture | ..............................................................................4-12 | | | | 4.3.5 Cryptography Policy and FIPS Compliance | ...............................................4-23 | |----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| | | 4.3.6 | Other Design Decisions..............................................................................4-23 | | | | | 4.3.7 Summary of Design Decisions | ...................................................................4-24 | | | 4.4 | Implement and Test Prototype...............................................................................4-25 | | | | | 4.4.1 Application and Client Interoperability |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Guide to SSL VPNs."}]}
{"id": "nist_01248", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 10.1. Statement Requirements according to NIST Secure Data Network Systems (SDNS) Key Management Documents According to Secure Data Network Systems (SDNS) Key Management Documents, 10.1. Statement Requirements: An implementor shall state the following: - a) the application for which conformance is claimed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_01249", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Section 169) control assessors. The assessor findings are a factual reporting of whether the controls are operating as intended and whether any deficiencies 90 in the controls are discovered during the assessment. Control assessments occur as early as practicable in the SDLC, preferably during the development phase. These types of assessments are referred to as developmental testing and evaluation, and validate that the controls are implemented correctly and are consistent with the established information security and privacy architectures. Developmental testing and evaluation activities include, for example, design and code reviews, regression testing, and application scanning. Deficiencies identified early in the SDLC can be resolved in a more cost-effective manner. Assessments may be needed prior to source selection during the procurement process to assess potential suppliers or providers before the organization enters into agreements or contracts to begin the development phase. The results of control assessments conducted during the SDLC can also be used (consistent with reuse criteria established by the organization) during the authorization process to avoid unnecessary delays or costly repetition of assessments. Organizations can maximize the use of automation to conduct control assessments to increase the speed, effectiveness, and efficiency of the assessments, and to support continuous monitoring of the security and privacy posture of organizational systems. Applying and assessing controls throughout the development process may be appropriate for iterative development processes. When iterative development processes (e.g., agile development) are employed, an iterative assessment may be conducted as each cycle is completed. A similar process is employed for assessing controls in commercial IT products that are used in the system. Organizations may choose to begin assessing controls prior to the complete implementation of all controls in the security and privacy plans.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_01250", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Security-Focused Configuration Management of Information Systems say about Acknowledgments? According to Guide for Security-Focused Configuration Management of Information Systems, Acknowledgments: The authors, Arnold Johnson, Kelley Dempsey, and Ron Ross of NIST, and Sarbari Gupta and Dennis Bailey of Electrosoft, wish to thank their colleagues Murugiah Souppaya, Karen Scarfone, John Banghart, David Waltermire, and Blair Heiserman of NIST who reviewed drafts of the document and provided insightful recommendations. Nedim Goren and Jody Jacobs completed the errata update. A special note of thanks goes to Peggy Himes and Elizabeth Lennon for their superb technical editing and administrative support. We would also like to thank all those who responded to our call for public comments for lending their time and effort to make this a better document. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_01251", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Specification for the Open Checklist Interactive Language (OCIL) Version 2.0 provide? (Section 12) irements that producers of OCIL-supporting software and OCIL documents (questionnaires) must meet to claim conformance with the OCIL 2.0 specification. This report only applies to version 2.0 of OCIL. All other versions are out of the scope of this report. The remainder of this document is organized into the following major sections and appendices: - Section 2 defines terms used within this specification and provides a list of common acronyms and other abbreviations. - Section 3 defines the conformance rules for this specification. - Section 4 provides an overview of related specifications and standards. - Section 5 presents the primary components of the OCIL data model. - Section 6 provides requirements and recommendations for OCIL content syntax, structures, and development. - Section 7 describes OCIL document processing requirements. - Appendix A discusses possible use cases for OCIL. - Appendix B defines requirements for using OCIL as a check system for the eXtensible Configuration Checklist Description Format (XCCDF). The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in Request for Comment (RFC) 2119. 1 Text intended to represent computing system input, output, or algorithmic processing is presented in fixed-width Courier font . OCIL currently does not address: - A specific method for identifying the subject or role to present an OCIL-based assessment to. This might be addressed by another specification in the future. - Specific guidelines on how to report on the evaluation of OCIL questionnaires relating to a population of IT assets - A reference architecture for integrating OCIL with other XCCDF check systems to perform a more complete assessment of a checklist - Specific guidelines on using questionnaires to collect answers strictly for informational purposes, instead of for compliance purposes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Specification for the Open Checklist Interactive Language (OCIL) Version 2.0."}]}
{"id": "nist_01252", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to SSL VPNs provide? (Section 28) packets and the IP information for each packet. However, network layer controls provide less control and flexibility for protecting specific applications than transport and application layer controls. SSL tunnel VPNs provide the ability to secure both TCP and UDP communications including client/server and other network traffic, and therefore act as network layer VPNs. - \u0084 Data Link Layer. Data link layer controls are applied to all communications on a specific physical link, such as a dedicated circuit between two buildings or a dial-up modem connection to an Internet Service Provider (ISP). Data link layer controls for dedicated circuits are most often provided by specialized hardware devices known as data link encryptors ; data link layer controls for other types of connections, such as dial-up modem communications, are usually provided through software. Because the data link layer is below the network layer, controls at this layer can protect both data and IP information. Compared to controls at the other layers, data link layer controls are relatively simple, which makes them easier to implement; also, they support other network layer protocols besides IP. Because data link layer controls are specific to a particular physical link, they cannot 2 Several Request for Comment (RFC) documents from the Internet Engineering Task Force (IETF) define S/MIME, as well as standards for using it to protect email messages. One example is RFC 3852, Cryptographic Message Syntax (CMS) , available at 3 TLS is the standards-based version of SSL version 3. More information on TLS is available in RFC 4346, The TLS Protocol Version 1.1 , available at Another good source of information is NIST SP 800-52, Guidelines on the Selection and Use of Transport Layer Security , available from http://csrc.nist.gov/publications/nistpubs/.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Guide to SSL VPNs."}]}
{"id": "nist_01253", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Extended Key Usage : according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Extended Key Usage :: TLS Web Client Authentication, Microsoft Smartcard Login, PKINIT Client Auth", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_01254", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RA-1 in Securing Wireless Infusion Pumps in Healthcare Delivery Organizations? (Part 90) Control RA-1: 1800-8C: Securing Wireless Infusion Pumps 46 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P 1 8 0 0 - 8 . . 3. In the Java console, click Policies. 4. Under the Policies tab, click Prevention or Detection. 5. On the Policies page, in the Workspace Folders, select the Workspace folder, and then right- click Add Folder. Look for a new policy folder with the name New Folder. Rename this folder as Pump Server. 6. Copy an existing policy to the Pump Server folder. 7. From the default Symantec folder, find a proper policy example, and copy it to the Pump Server folder. 8. In the Workspace pane, select a policy (e.g., \u201cwindows-baseline-detection\u201d policy in Symantec folder for Detection), and then right-click Move To. In the MoveFolder dialog box, select Pump Server to receive the policy, and then click MoveTo. 9. To edit a policy, right-click a policy, and then click Edit Policy. Configure the setting based on your security protection needs. DCS:SA provides a variety of configurable protection from application data protection, to application protection, to network protection. For example, the Windows prevention policies have a Protected Whitelisting strategy that lets you specify an application to which you always want to allow access or give permission to run. When you whitelist a process or an application, all of the other processes and applications that are not included in the list are denied access. To allow a program to run by using the Protected Whitelisting strategy, follow these steps: 1. 2. 3. 4. 5. In the management console, click the Policies tab, and then click Prevention. In the Policies workspace, click Add. In the Select a Prevention Policy Builder wizard, in the New Policy Builder section, click Launch.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Wireless Infusion Pumps in Healthcare Delivery Organizations."}]}
{"id": "nist_01255", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does United States Federal Employees' Password Management Behaviors \u2013 A Department of Commerce Case Study provide? (Section 43) | | Getting locked out of an account | | | | | | Mistyping a password | | | | | | Getting error messages when trying to change a password | | | | | | Getting error messages when trying to recover a password | | | | | | Dealing with slow or unhelpful system support | | | | | | Valid password rejected for unclear reason | | | | | | Single task requiring different logins to multiple applications, i.e., task flow interrupted by multiple logins | | | | | 17.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: United States Federal Employees' Password Management Behaviors \u2013 A Department of Commerce Case Study."}]}
{"id": "nist_01256", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations provide? (Section 33) em when required. Information System Owner (ISO)/Information Owner/Steward . The ISO establishes processes and procedures in support of system -level implementation of the organization's ISCM program. This includes developing and documenting an ISCM strategy for the information system; participating in the organization's configuration management process; establishing and maintaining an inventory of components associated with the information system; conducting security impact analyses on changes to the information system; conducting, or ensuring conduct of, assessment of security controls according to the ISCM strategy; preparing and submitting security status reports in accordance with organizational policy and procedures; conducting remediation activities as necessary to maintain system authorization; revising the system-level security control monitoring process as required; reviewing ISCM reports from common control providers to verify that the common controls continue to provide adequate protection for the information system; and updating critical security documents based on the results of ISCM. Common Control Provider. 23 The common control provider establishes processes and procedures in support of ongoing monitoring of common controls.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations."}]}
{"id": "nist_01257", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 provide? (Section 12) 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. Alternately, 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. Cryptographic 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. Audit logs are essential for tracking patient history and IMD behavior over a period of time. The audit records provide information needed for adequate patient care as well as updates to patient therapy delivered through the IMD.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012."}]}
{"id": "nist_01258", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to Security and Privacy Controls for Information Systems and Organizations? Discussion: [SP 800-56A], [SP 800-56B], and [SP 800-56C] provide guidance on cryptographic", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01259", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2012 Annual Report provide? (Section 220) at, or both encoding formats. The testing methodology makes use of specific test assertion syntax to clearly GLYPH(cmap:df00)efine the assertions associateGLYPH(cmap:df00) with each requirement. Mr. Fernando Podio fernanGLYPH(cmap:df00)o@nist.gov Mr. Dylan Yaga GLYPH(cmap:df00)ylan.yaga@nist.gov Mr. Christofer McGinnis christofer.mcginnis@nist.gov This document outlines the security components and security guiGLYPH(cmap:df00)elines neeGLYPH(cmap:df00)eGLYPH(cmap:df00) to establish a secure Basic Input/Output System (BIOS) integrity measurement anGLYPH(cmap:df00) reporting chain. UnauthorizeGLYPH(cmap:df00) moGLYPH(cmap:df00)ification of BIOS firmware constitutes a significant threat because of the BIOS's unique anGLYPH(cmap:df00) privilegeGLYPH(cmap:df00) position within the PC architecture. The GLYPH(cmap:df00)ocument focuses on two scenarios: GLYPH(cmap:df00)etecting changes to the system BIOS coGLYPH(cmap:df00)e storeGLYPH(cmap:df00) on the system flash, anGLYPH(cmap:df00) GLYPH(cmap:df00)etecting changes to the system BIOS configuration. The GLYPH(cmap:df00)ocument is intenGLYPH(cmap:df00)eGLYPH(cmap:df00) for harGLYPH(cmap:df00)ware anGLYPH(cmap:df00) software venGLYPH(cmap:df00)ors that GLYPH(cmap:df00)evelop proGLYPH(cmap:df00)ucts that can support secure BIOS integrity measurement mechanisms, and may also be of use for organizations developing enterprise procurement or deployment strategies for these technologies. Contact: Mr. AnGLYPH(cmap:df00)rew RegenscheiGLYPH(cmap:df00) anGLYPH(cmap:df00)rew .regenscheiGLYPH(cmap:df00)@nist.gov A wireless local area network (WLAN) is a group of wireless networking GLYPH(cmap:df00)evices within a limiteGLYPH(cmap:df00) geographic area, such as an office builGLYPH(cmap:df00)ing, that exchange GLYPH(cmap:df00)ata through radio communications.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_01260", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-256 in Blockchain Technology Overview? (Part 10) Control HA-256: trict read access to authorized individuals. They also may allow anyone to submit transactions to be included in the blockchain or, again, they may restrict this access only to authorized individuals. Permissioned blockchain networks may be instantiated and maintained using open source or closed source software. Permissioned blockchain networks can have the same traceability of digital assets as they pass through the blockchain, as well as the same distributed, resilient, and redundant data storage system as a permissionless blockchain networks. They also use consensus models for publishing blocks, but these methods often do not require the expense or maintenance of resources (as is the case with current permissionless blockchain networks). This is because the establishment of one's identity is required to participate as a member of the permissioned blockchain network; those maintaining the blockchain have a level of trust with each other, since they were all authorized to publish blocks and since their authorization can be revoked if they misbehave. Consensus models in permissioned blockchain networks are then usually faster and less computationally expensive. Permissioned blockchain networks may also be used by organizations that need to more tightly control and protect their blockchain. However, if a single entity controls who can publish blocks, the users of the blockchain will need to have trust in that entity. Permissioned blockchain networks may also be used by organizations that wish to work together but may not fully trust one another. They can establish a permissioned blockchain network and invite business partners to record their transactions on a shared distributed ledger. These organizations can determine the consensus model to be used, based on how much they trust one another. Beyond trust, permissioned blockchain networks provide transparency and insight that may help better inform business decisions and hold misbehaving parties accountable.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain Technology Overview."}]}
{"id": "nist_01261", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE) say about Appendix B Glossary? (Part 9) According to Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE), Appendix B Glossary: | The act of deceiving an individual into revealing sensitive information, obtaining unauthorized access, or committing fraud by associating with the individual to gain confidence and trust [55]. | | Threat | Any circumstance or event with the potential to adversely impact organizational operations (including mission, functions, image, or reputation), organizational 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 [12]. | | Threat Events | An event or situation that has the potential for causing undesirable consequences or impact [12]. | | Threat Intelligence | Threat information that has been aggregated, transformed, analyzed, interpreted, or enriched to provide the necessary context for decision-making processes [62]. | |--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Threat Sources | 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 [11]. | | Transport Layer | Layer of the TCP/IP protocol stack that is responsible for reliable connection-oriented or connectionless end-to-end communications [49]. | | Transport Layer Security (TLS) | A security protocol providing privacy and data integrity between two communicating applications. The protocol is composed of two layers: the TLS Record Protocol and the TLS Handshake Protocol [54]. | | Trusted Certificate | A certificate that is trusted by the Relying Party on the basis of secure and authenticated delivery.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_01262", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Securing Web Transactions_ TLS Server Certificate Management? (Part 69) Control HA-1: n place and managed. | The system supports replacement of large numbers of TLS server certificates and private keys in response to CA compromises, vulnerable algorithms, or cryptographic library bugs. | CP-2, CP-7, CP-12, CP-13, IR-7, IR- 8, IR-9, PE-17 | PR-CDA-001 Cyber Defense Analyst PR-CIR-001 Cyber Defense Incident Responder PR-VAM-001 Vulnerability Assessment Analyst AN-TWA-001 | | Cybersecurity Framework Function | Cybersecurity Framework Category | Cybersecurity Framework Subcategory | Applicability to TLS Server Certificates | NIST SP 800-53 Rev.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_01263", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations say about Publication History? According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, Publication History: Approved by the NIST Editorial Review Board on 2024-09-25 Supersedes NIST Special Publication 800-161r1 (May 2022) ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_01264", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations say about Vulnerability Analysis? (Part 1) According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, Vulnerability Analysis: Vulnerability Analysis For C-SCRM, a vulnerability is a weakness in an information system, system security procedures, internal controls, or implementation that could be exploited or triggered by a threat source [SP80053r5]. A vulnerability analysis is an iterative process that informs risk assessments and countermeasure selection. The vulnerability analysis works alongside the threat analysis to help inform the impact analysis and to help scope and prioritize the vulnerabilities to be mitigated. 68 Note that the threat characterization of suppliers, developers, system integrators, external system service providers, and other ICT/OTrelated service providers may be benign. Vulnerability analysis in the Assess step should use the approaches defined during the Frame step to update and refine assumptions about supply chain cybersecurity vulnerabilities. Vulnerability analysis should begin by identifying vulnerabilities that are applicable to critical mission and business processes and the systems or system components identified by the criticality analysis. An investigation of vulnerabilities may indicate the need to raise or at least reconsider the criticality levels of processes and components identified in earlier criticality analyses. Later iterations of the vulnerability analysis may also identify additional threats or opportunities for threats that were not considered in earlier threat assessments. Table 38 provides examples of applicable supply chain cybersecurity vulnerabilities that can be observed within the three levels. Table 38.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_01265", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Appendix A. List of Symbols, Abbreviations, and Acronyms according to NIST Using Business Impact Analysis to Inform Risk Prioritization and Response According to Using Business Impact Analysis to Inform Risk Prioritization and Response, Appendix A. List of Symbols, Abbreviations, and Acronyms: Selected acronyms and abbreviations used in this paper are defined below.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Using Business Impact Analysis to Inform Risk Prioritization and Response."}]}
{"id": "nist_01266", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols say about 2 References? According to Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols, 2 References: | ISO 8473 | 01 March 1986 Final Text of DIS 8473, Protocol for Providing the Connectionless-mode Network Service | |----------------|-----------------------------------------------------------------------------------------------------------------------------------------------| | ISO 8348 | 15 July 1987 Final Text of DIS 8348: Information processing systems - Data communications - Network service definition | | ISO 7498 | 15 Oct. 1987 Information Processing Systems - Open Systems Interconnection - Basic Reference Model | | ISO 7498/2 | March 1987 Information Processing Systems - Open Systems Interconnection - Security Architecture | | ISO 8348/DAD 1 | Information Processing Systems - Data 07 Aug. 1985 Communications - Network Service Definition - Addendum 1 | | ISO 8348/DAD2 | Information Processing Systems - Data 29 Feb. 1986 Communications - Network Service Definition - Addendum 2 Covering Network Layer Addressing | | ISO 8648 | Information Processing Systems - Data Communications - Internal Organization of the Network Layer | |--------------|-----------------------------------------------------------------------------------------------------| | ISO TR 8509 | Technical Report 8509, OSI Service Conventions | | RFC 986 | Guidelines for the use of Internet-IP addresses in the ISO Connectionless - Mode Network Protocol | | MIL-STD-1777 | Military Standard Internet Protocol 12 Aug 1983 - |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols."}]}
{"id": "nist_01267", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-2 in Engineering Trustworthy Secure Systems? Control IP-2: PERFORM IMPLEMENTATION - IP-2.1 Realize or adapt system elements in accordance with the security aspects of the implementation strategy and implementation procedures, as well as security-relevant constraints. Note: System elements can include: - -Hardware and Software: Hardware and software elements are either acquired or fabricated. Custom hardware fabrication and software development enable insight into the details of design and implementation. These insights often translate to increased assurance. Acquired hardware and software elements may not provide the opportunity to achieve the same insight into design and implementation and may offer more functionality and capability than required. The limits of what can be known about the internals of the elements translate to a level of uncertainty about vulnerability and the maximum assurance that can be achieved. - -Firmware: Firmware exhibits properties of hardware and software. Firmware elements may be acquired or developed to realize the software aspects and then fabricated to realize the physical form of the hardware aspects. Firmware elements, therefore, adhere to the security implementation considerations of both hardware and software elements. - -Services: System elements implemented by obtaining or leasing services are subject to the same criteria used to acquire hardware, firmware, and software but must also address the security considerations associated with utilization and support resources. - -Utilization and Support Resources: The security considerations of acquired or leased services account for the specific roles and responsibilities of individuals of the service/lease provider and their ability to account for all of the security requirements and constraints associated with the delivery, utilization, and sustainment of the service or capability being leased.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_01268", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Requirements for Cryptographic Modules say about U.S. Department of Commerce? According to Security Requirements for Cryptographic Modules, U.S. Department of Commerce: Wilbur L. Ross, Jr., Secretary National Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary for Standards and Technology", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Requirements for Cryptographic Modules."}]}
{"id": "nist_01269", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cell Phone Forensic Tools_ an Overview and Analysis Update say about Appendix G: SIM Seizure - External SIM Results? According to Cell Phone Forensic Tools_ an Overview and Analysis Update, Appendix G: SIM Seizure - External SIM Results: The scenarios were performed on a Forensic Recovery of Evidence Device (FRED) running Windows XP SP2. SIM Seizure version 1.0 build 2468.18222 was used with Paraben's SIM Card Reader to acquire data from a populated SIM.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis Update."}]}
{"id": "nist_01270", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.2 Relations according to NIST A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N According to A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N, 4.2 Relations: NGAC does not express policies through rules, but instead through configurations of relations of four types: assignments (define membership in containers), associations (derive privileges), prohibitions (specify privilege exceptions), and obligations (dynamically alter access state).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N."}]}
{"id": "nist_01271", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Security for Full Virtualization Technologies say about 4.3 Virtualized Infrastructure Security? (Part 2) According to Guide to Security for Full Virtualization Technologies, 4.3 Virtualized Infrastructure Security: control, shape, and monitor the VM network communications in a centralized location. Hypervisors sometimes offer virtual storage networks and virtual interfaces to existing hardware storage networks. These features offer the same security problems as virtual networks, namely that organizations whose security policies require monitoring those connections cannot use the same methods for virtual storage as they do for physical storage. Using physical interfaces to existing networked storage can eliminate this problem, but also reduces some of the flexibility that hypervisors offer.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Security for Full Virtualization Technologies."}]}
{"id": "nist_01272", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain digital twin instance according to NIST Security and Trust Considerations for Digital Twin Technology According to Security and Trust Considerations for Digital Twin Technology, digital twin instance: A digital data structure, object, or entity in a computer software environment that represents a specific physical instance of a real-world object whose type or class is given by an associated digital twin definition.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Trust Considerations for Digital Twin Technology."}]}
{"id": "nist_01273", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Content Filtering according to User's Guide to Telework and Bring Your Own Device (BYOD) Security? Content Filtering: The process of monitoring communications such as email and web pages, analyzing them for suspicious content, and preventing the delivery of suspicious content to users.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: User's Guide to Telework and Bring Your Own Device (BYOD) Security."}]}
{"id": "nist_01274", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain DISCLAIMER according to NIST Data Integrity_ Recovering from Ransomware and Other Destructive Events According to Data Integrity_ Recovering from Ransomware and Other Destructive Events, DISCLAIMER: Certain commercial entities, equipment, products, or materials may be identified by name or company logo or other insignia in order to acknowledge their participation in this collaboration or to describe an experimental procedure or concept adequately. Such identification is not intended to imply special status or relationship with NIST or recommendation or endorsement by NIST or NCCoE; neither is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose. National Institute of Standards and Technology Special Publication 1800-11B, Natl. Inst. Stand. Technol. Spec. Publ. 1800-11B, 54 pages, (September 2020), CODEN: NSPUE2", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Recovering from Ransomware and Other Destructive Events."}]}
{"id": "nist_01275", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 501) ecurity Objectives/Requirements \uf0b7 Confidentiality may or may not be an issue depending on whether information is public (date, time) or private (password change, Personally Identifiable Information). Some items must be confidential due to laws and regulations; confidentiality of other items, such as firmware or GPS coordinates, may be left up to local policy, \uf0b7 Integrity of meter maintenance repairs and updates is essential to prevent malicious intrusions \uf0b7 Availability is important, but only in terms of hours or maybe days to provide synchronization and coherence of devices on the network, i.e. all devices acting together for entire population 3.1 Data Privacy Considerations 82 The Customer Information Systems (CIS), Meter Data Management Systems (MDMS) and Outage Management Systems (OMS) may contain multiple types of personal data that may be impacted by meter reading and configuration changes or updates. Utility resources and authorized Third Parties should follow utility privacy policies to safeguard any personal data, including energy usage data. For example, a connectivity ping that is negative may trigger a request to an OMS and/or workforce management system to schedule an onsite repair visit. Personal data in the form of customer name and address would be needed to schedule that repair with utility or authorized Contracted Agents. That connectivity ping may also generate a report identifying unresponsive meters. Care should be exercised to minimize personal data that appears in these reports, and limits on the access to these reports by resources trained in privacy policies and practices. 3.2 Care should be exercised to ensure authorized Third Parties or other service providers do not have unnecessary access to customer information that is not required for completion of their responsibilities.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01276", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Use of ISO_IEC 24727 say about 2. ISO/IEC 24727 Discussion? (Part 2) According to Use of ISO_IEC 24727, 2. ISO/IEC 24727 Discussion: rd data and services. Through these distinct abstractions, client-applications can use identification services in real time, while the Generic Card Interface accommodates differences in card behavior. This feature of ISO/IEC 24727 enables developers to discover card capabilities and to write a client-application once and use it with different credential systems. + Platform Independence - This feature of ISO/IEC 24727 enables independence from interface devices, such as card readers, allowing compliant implementations to be used in different configurations and environments. The common device interface defined in ISO/IEC 24727 provides a generic interface for readers. This facilitates translation from a common device interface to device specific commands. + Extensible architecture - ISO/IEC 24727 includes a normative collection of basic services for authentication, signature, encryption, key establishment, and session establishment. It allows for the addition of new security protocols and authentication mechanisms to perform a variety of interoperable services. Because these services are normative, cards enabled with one or several service(s) will interoperate with ISO/IEC 24727 applications. 3 Part 3 of ISO/IEC 24727 defines services as representations of action requests and action responses to be supported at the client-application interface. Essentially, it provides a high-level interface for a clientapplication making use of information storage and processing operations of a card-application.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Use of ISO_IEC 24727."}]}
{"id": "nist_01277", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SR-12 in Security and Privacy Controls for Information Systems and Organizations? (Part 88) Control SR-12: s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ threat [SP 800-30] threat assessment [CNSSI 4009] threat modeling [SP 800-154] threat source [FIPS 200] transmission [CNSSI 4009] trusted path trustworthiness [CNSSI 4009] trustworthiness (system) user 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. Formal description and evaluation of threat to an information system. A form of risk assessment that models aspects of the attack and defense sides of a logical entity, such as a piece of data, an application, a host, a system, or an environment. The intent and method targeted at the intentional exploitation of a vulnerability or a situation and method that may accidentally trigger a vulnerability. See threat agent. The state that exists when information is being electronically sent from one location to one or more other locations. A mechanism by which a user (through an input device) can communicate directly with the security functions of the system with the necessary confidence to support the system security policy. This mechanism can only be activated by the user or the security functions of the system and cannot be imitated by untrusted software.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01278", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments say about List of Acronyms? (Part 2) According to Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments, List of Acronyms: A&amp;A Assessment &amp; Authorization ACL Access Control List ADCS Active Directory Certificate Services AWS Amazon Web Services BGP Border Gateway Protocol BIOS Basic Input/Output System CA Certificate Authority CloudSPF Cloud Security Policy Framework COSO Committee of Sponsoring Organizations of the Treadway Commission CRADA Cooperative Research and Development Agreement CSA Cloud Security Alliance DCG Data Center Group DD VE Data Domain Virtual Edition DFW Distributed Firewall DHCP Dynamic Host Configuration Protocol DISA Defense Information Systems Agency DLR Distributed Logical Router DNS Domain Name System ECMP Equal-Cost Multi-Path ESG Edge Services Gateway FAIR Factor Analysis of Information Risk FedRAMP Federal Risk and Authorization Management Program FIPS Federal Information Processing Standard FISMA Federal Information Security Modernization Act FOIA Freedom of Information Act FT Fault Tolerance GB Gb Gigabyte Gigabit GKH Good Known Host GRC Governance, Risk, and Compliance HIPAA Health Insurance Portability and Accountability Act HSM Hardware Security Module HTBC HyTrust BoundaryControl HTCA HyTrust CloudAdvisor HTCC HyTrust CloudControl HTDC HyTrust DataControl HTKC HyTrust KeyControl I/O Input/Output IaaS Infrastructure as a Service ICSV IBM Cloud Secure Virtualization IEEE Institute of Electrical and Electronics Engineers Intel AES-NI Intel Advanced Encryption Standard - New Instructions Intel CIT Intel Cloud Integrity Technology Intel TPM Intel Trusted Platform", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization, certificate authority. Contains security framework guidance for authentication systems. Source: Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments."}]}
{"id": "nist_01279", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DS-2 in Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)? (Part 64) Control DS-2: rt, or protocol (TCP or UDP) that is not explicitly permitted Procedure 1. As stipulated in the preconditions, just before this test, test IoT-1-v4 (or IoT-1-v6) must have been run successfully. 2. Local-network (ingress): Initiate communications to the IoT device from anyhost-from for specific permitted service, and verify that this traffic is received at the IoT device. 3. Local-network (egress): Initiate communications from the IoT de- vice to anyhost-from for specific permitted service, and verify that this traffic is received at the MUD PEP, but it is not forwarded by the MUD PEP, nor is it received at anyhost-from. 4. Local-network, controller, my-controller, manufacturer class (egress): Initiate communications from the IoT device to anyhost-to for specific permitted service, and verify that this traffic is received at anyhost-to. 5. Local-network, controller, my-controller, manufacturer class (in- gress): Initiate communications to the IoT device from anyhost-to for specific permitted service, and verify that this traffic is received NIST SP 1800-15D: Securing Small-Business and Home Internet of Things Devices 157 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Test Case Field Description at the MUD PEP, but it is not forwarded by the MUD PEP, nor is it received at the IoT device. 6. No associated class (egress): Initiate communications from the IoT device to unnamed-host (where unnamed-host is a host that is not from the same manufacturer as the IoT device in question and whose MUD URL is not explicitly mentioned in the MUD file as be- ing permitted), and verify that this traffic is received at the MUD PEP, but it is not forwarded by the MUD PEP, nor is it received at unnamed-host. 7.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_01280", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.2 Extensible Configuration Checklist Description Format (XCCDF) according to NIST The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2 According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2, 3.2 Extensible Configuration Checklist Description Format (XCCDF): This section lists requirements and recommendations for using the Extensible Configuration Checklist Description Format (XCCDF) to express an XCCDF benchmark or tailoring component of an SCAP source data stream (see Table 12). They are organized by the following categories: general , &lt;xccdf:Benchmark&gt; , &lt;xccdf:Profile&gt; , &lt;xccdf:Rule&gt; , &lt;xccdf:Value&gt; , and &lt;xccdf:Group&gt;.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2."}]}
{"id": "nist_01281", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-11 in Guidelines for Smart Grid Cybersecurity? (Part 520) Control SI-11: 1 - R T A s m e t s y s d n a i n o i t a c n u m m o c y c a g e L : 1 1 - R T A l s o c o t o r p e g r a l r o f t n e m e g a n a m y e K : 3 1 - R T A i s e c v e d f o s r e b m u n i s e c v e d r o f i s t n a r t s n o c t n e m e g a n a m e t a d p u d n a h c t a P : 4 1 - R T A d e t s u r t n u , e r u c e s n I : 2 1 - R T A s n o i t a c o l , y t i l i b a i r a v , y t i l i i b", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01282", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Authentication Methods : according to NIST Blockchain Networks_ Token Design and Management Overview According to Blockchain Networks_ Token Design and Management Overview, Authentication Methods :: Stateful tokens allow lightweight blockchain-based authentication methods to be built. The blockchain is essential but thinly used since only reading access is required for status verification. Blockchain-based data stores for status querying can have multiple architectures (see Section 4.4 in [18]). They can be built as smart contract registries that are user-controlled, issuer- or consortium-controlled, or ownerless. These differ from nonfungible token factory contracts in that token ownership is not meant to be reassigned. Alternatively, blockchain-based data stores can be built on UTXO-based blockchains. Finally, the querying logic may involve additional components, such as status update batching protocols 2 or cryptographic accumulators. 3 The verifiable credential standard [19] published by the World Wide Web Consortium (W3C) specifies data field formats that provide the location and querying logic of data stores for stateful token status. Additionally, blockchain-based identifier systems can make it easier to resolve and authenticate the digital signatures of cryptographically signed content. In particular, they can be used to identify the owners and issuers of stateful tokens (and any other entities whose public key is present in the token). These systems may follow the decentralized identifier (DID) standard [20] (see Section 5.1.3.2). Their data stores can have blockchain-based architectures similar to the ones discussed above (further examined in [18]), which may be complemented by additional smart contracts for public credentials registries, such as those introduced in the draft ERC-780 [21] proposal.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Blockchain Networks_ Token Design and Management Overview."}]}
{"id": "nist_01283", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is PCTS according to Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI? PCTS: 151-1 Version: 1.1 -07/01/91", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI."}]}
{"id": "nist_01284", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Information Security Handbook_ A Guide for Managers? (Part 222) Control PD-12: onse capability involves the participation of many people within the organization. Making the right planning and implementation decisions is key to establishing a successful incident response program. One of the first planning tasks should be to develop an organization-specific definition of the term 'incident' so that the scope of the term is clear. Additional tasks that should be performed during the preparation phase include the following: - Create an Incident Response Policy. The policy should define what events are considered incidents, establish the organizational structure for incident response, define roles and responsibilities, and list the organization's incident reporting requirements. - Develop Incident Response and Reporting Procedures. Based on the incident response policy, standard operating procedures (SOPs) are a delineation of the specific technical processes, techniques, checklists, and forms used by the incident response team. SOPs should be comprehensive and detailed to ensure that the organization's priorities are properly reflected in response operations. In addition, following standardized response procedures is also an effective way to minimize errors, particularly those that might be caused by incident handling pace and stress. Prior to implementation, the organization should test incident response SOPs in order to validate their accuracy and usefulness. Once validated, the SOPs must be widely disseminated throughout the organization. Incidents can occur in countless and unpredictable ways; therefore, it is impractical to develop comprehensive procedures with step-by-step instructions for handling every incident. The best that the organization can do is prepare to handle any type of incident, and more specifically, to handle common types of incidents. - Establish Guidelines for Communicating with External Parties.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_01285", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols say about 5.3.2 Security Services? (Part 2) According to Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols, 5.3.2 Security Services: ce Address within the protected header.The peer SP3 is authenticated by pairwise keying. The source end system is authenticated to be a member of the set of addresses served by the peer SP3 entity. 8. SP3 supplies in the Indication a representation (Security Labeljndicated) of a security label which has been carried with integrity. 9. SP3 supports access control. The key service external to SP3 may choose, for access control reasons, not to make a key available for communication between two SP3 entities. This decision by the key service implies an access control service at the upper interface of SP3, since SP3 will not allow communication if an appropriate key is not present. In addition, if a security label is provided for the data, then SP3 will make an access control check against this label on both transmit and receive.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols."}]}
{"id": "nist_01286", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is CHIEF INFORMATION SECURITY OFFICER according to Minimum Security Requirements for Federal Information and Information Systems? CHIEF INFORMATION SECURITY OFFICER: See Senior Agency Information Security Officer.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Minimum Security Requirements for Federal Information and Information Systems."}]}
{"id": "nist_01287", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-256 in Recommendation for Stateful Hash-Based Signature Schemes? (Part 28) Control HA-256: | 32 | 25 | ## 4.4 LMS with SHAKE256/192 When generating LMS or HSS key pairs using SHAKE256/192, the LMS and LM-OTS parameter sets shall be selected from the following two tables. Table 7: LM-OTS parameter sets for SHAKE256/192 | LM-OTS Parameter Sets | Numeric Identifier | n | w | p | |-------------------------|----------------------|-----|-----|-----| | LMOTS_SHAKE_N24_W1 | TBD | 24 | 1 | 200 | | LMOTS_SHAKE_N24_W2 | TBD | 24 | 2 | 101 | | LMOTS_SHAKE_N24_W4 | TBD | 24 | 4 | 51 | | LMOTS_SHAKE_N24_W8 | TBD | 24 | 8 | 26 | Table 8: LMS parameter sets for SHAKE256/192 | LMS Parameter Sets | Numeric Identifier | m | h | |----------------------|----------------------|-----|-----| | LMS_ SHAKE_M24_H5 | TBD | 24 | 5 | | LMS_ SHAKE_M24_H10 | TBD | 24 | 10 | | LMS_ SHAKE_M24_H15 | TBD | 24 | 15 | | LMS_ SHAKE_M24_H20 | TBD | 24 | 20 | | LMS_ SHAKE_M24_H25 | TBD | 24 | 25 | ## 5 eXtended Merkle Signature Scheme (XMSS) Parameter Sets The XMSS and XMSS MT algorithms are described in RFC 8391 [1]. This Special Publication approves the use of XMSS and XMSS MT with four different hash functions: SHA-256, SHA256/192, SHAKE256/256, and SHAKE256/192 (see Section 2.3). 5 The parameter sets that use SHA-256 are defined in RFC 8391 [1]. The parameter sets that use SHA-256/192, SHAKE256/256, and SHAKE256/192 are defined below. The WOTS + parameters that correspond to the use of each of these hash functions are specified in the following table.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Stateful Hash-Based Signature Schemes."}]}
{"id": "nist_01288", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3 provide? (Section 154) es intended to handle sensitive data, in four increasing levels of stringency. The levels are intended to cater to the degree of data sensitivity required by the applications utilizing a given module. The security levels presented in FIPS 140-2 are as follows: Security Level 1 is the lowest level which 'allows the software and firmware components of a cryptographic module to be executed on a general-purpose computing system using an unevaluated operating system. Such implementations may be appropriate for some low-level security applications when other controls, such as physical security, network security, and administrative procedures are limited or nonexistent [155].' (p.1) 'Security Level 2 enhances the physical security mechanisms of a Security Level 1 cryptographic module by adding the requirement for tamper-evidence, which includes the use of tamper-evident coatings or seals or for pick-resistant locks on removable covers or doors of the module. Tamper-evident coatings or seals are placed on a cryptographic module so that the coating or seal must be broken to attain physical access to the plaintext cryptographic keys and critical security parameters (CSPs) within the module. Tamper-evident seals or pick-resistant locks are placed on covers or doors to protect against unauthorized physical access. Security Level 2 requires, at a minimum, role-based authentication in which a cryptographic module authenticates the authorization of an operator to assume a specific role and perform a corresponding set of services [155].' (p. 2) Security Level 3: 'In addition to the tamper-evident physical security mechanisms required at Security Level 2, Security Level 3 attempts to prevent the intruder from gaining access to CSPs [critical security parameters] held within the cryptographic module.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3."}]}
{"id": "nist_01289", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain REFERENCES according to NIST Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, REFERENCES: Source Control: SC-15 Supporting Publications: None", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_01290", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Computer Security Division 2007 Annual Report? (Part 32) Control HA-1: e that includes interagency and interdepartmental participation from NIST, the National Security Agency (NSA), the Defense Information Systems Agency (DISA), and the Department of Defense (DoD). This program focuses on a standard, automated approach for the implementation of information system security controls, which includes the following objectives: - Develop requirements for automated sharing of information security data; - Customize and manage configuration baselines for various IT products; - Assess information systems and report compliance status; - Use standard metrics to weight and aggregate potential vulnerability impact; and - Remediate identified vulnerabilities. Recognizing that NIST has the responsibility to produce security configuration guidance for the U.S. Government, and that NSA and DISA provide the same service to DoD, ISAP consolidates data sources from these agencies and provides the data in a standardized XML format. Commercial-off-theshelf (COTS) and government-off-the-shelf (GOTS) software products and initiatives utilize this security-related data for the purposes of automating the identification and remediation of vulnerabilities, measuring potential impact, and conducting compliance reporting in the various computing infrastructures. The freely available information contained in ISAP files includes, but is not limited to: - Checking for vulnerabilities (security-related software flaws and misconfigurations) on an information technology asset; - Mapping to higher-level policies, such as FISMA via NIST SP 800-53, DoD 8500 Information Assurance (IA) controls, etc.; and - Providing a standard impact metric for vulnerabilities and a capability to aggregate impact scores to the agency reporting level.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: national security, defense information. Contains guidance on protecting sensitive government information. Source: Computer Security Division 2007 Annual Report."}]}
{"id": "nist_01291", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Product Supplier according to Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI? Product Supplier: Digital Equipment Corporation", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI."}]}
{"id": "nist_01292", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? (Part 22) Control HA-1: enhanced distributed trust model and authorisation decision making capability that can be implemented by using X.509 attribute certificates and a Privilege Management Infrastructure such as PERMIS. Several different combinatorial approaches can be taken, depending upon the trust models adopted by the Shibboleth target and origin sites, and each of these are described. The paper also discusses whether user privacy, which is strongly protected by Shibboleth, is bound to be weakened by the use of X.509 attribute certificates rather than simple attributes, and concludes that this does not have to be the case. ## 1. Introduction Shibboleth [1] is a distributed web resource access control system that allows federations to co-operate together to share web based resources. It has done this by defining a protocol for carrying authentication information and user attributes from a home site to a resource site. The resource site can then use the attributes to make access control decisions about the user. The Shibboleth project is run by the Internet2 consortium in the USA, and universities throughout the USA and Europe (at least) are now starting to build experimental services based upon it. At the heart of Shibboleth is a trust model that allows the members of a federation to cooperate together. This trust model, whilst functional, is somewhat limited. Basically each Shibboleth target resource site trusts each Shibboleth origin (home) site in the federation, so that whatever assertions authentication or authorisation -are digitally signed by the origin site, they will be believed and trusted by the target site. There is little scope for differentiation between authentication authorities and attribute authorities, or for allowing more sophisticated distribution of trust, such as static or dynamic delegation of authority.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_01293", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile say about 7. Manufacturing Profile Subcategory Guidance? (Part 5) According to Cybersecurity Framework Manufacturing Profile, 7. Manufacturing Profile Subcategory Guidance: | | IDENTIFY | (ID.AM) | | High Employ automated mechanisms where safe and feasible to detect the presence of unauthorized software within the system. | CM-8 (2)(3) | | Function | Category | Subcategory | Manufacturing Profile | Reference | |------------|--------------------------|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| | IDENTIFY | Asset Management (ID.AM) | ID.AM-3 | Low Document all connections within the manufacturing system, and between the manufacturing system and other systems. All connections are documented, authorized, and reviewed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile."}]}
{"id": "nist_01294", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 574) fe cycle, organizations may be able to modify the system design to reduce the critical nature of these components and functions, such as by adding redundancy or alternate paths into the system design. Criticality analysis can also influence the protection measures required by development contractors. In addition to criticality analysis for systems, system components, and system services, criticality analysis of information is an important consideration. Such analysis is conducted as part of security categorization in RA-2. Related Controls: CP-2, PL-2, PL-8, PL-11, PM-1, PM-11, RA-2, SA-8, SA-15, SA-20, SR-5. Control Enhancements: None. References: [IR 8179]. RA-10 THREAT HUNTING Control: CHAPTER THREE PAGE 247 NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ a. Establish and maintain a cyber threat hunting capability to: 1. Search for indicators of compromise in organizational systems; and 2. Detect, track, and disrupt threats that evade existing controls; and b. Employ the threat hunting capability [Assignment: organization-defined frequency]. Discussion: Threat hunting is an active means of cyber defense in contrast to traditional protection measures, such as firewalls, intrusion detection and prevention systems, quarantining malicious code in sandboxes, and Security Information and Event Management technologies and systems. Cyber threat hunting involves proactively searching organizational systems, networks, and infrastructure for advanced threats. The objective is to track and disrupt cyber adversaries as early as possible in the attack sequence and to measurably improve the speed and accuracy of organizational responses.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01295", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to General Server Security? (Part 59) Control ES-1: lnerabilities and related patches available that should be installed or configured as part of the setup process. Only after these preliminary steps are accomplished should the installation be started. Note that this section discusses only generic installation and configuration procedures; specific directions for particular servers are available from server manufacturers and from security checklist repositories. 24 A partially configured and/or patched server should not be exposed to external networks (e.g., the Internet) or external users. In addition, internal network access should be as limited as possible until all software is installed, patched, and configured securely. Insecure servers can be compromised in a matter of minutes after being placed on the Internet. While it is ideal to fully harden the platform before placing it on the network, it is not always feasible. For example, some application development tool combinations cannot be installed, configured, and tested on top of a pre-hardened OS and Web server configuration. In such situations, stepwise or incremental hardening is a viable option to consider, with full validation of complete hardening occurring at production deployment. ## 5.1 Securely Installing the Server Software In many respects, the secure installation and configuration of the server software mirrors the OS process discussed in Section 4. The overarching principle, as before, is to install only the services required for the server and to eliminate any known vulnerabilities through patches or upgrades. Any unnecessary applications, services, or scripts that are installed should be removed immediately once the installation process is complete. During the installation of the server software, the following steps should be performed: - GLYPH&lt;c=31,font=/MIJOHI+Webdings&gt; Install the server software either on a dedicated host or on a dedicated guest OS if virtualization is being employed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to General Server Security."}]}
{"id": "nist_01296", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Key Rollover according to Secure Domain Name System (DNS) Deployment Guide? Key Rollover: The process of generating and using a new key (symmetric or asymmetric key pair) to replace one already in use. Rollover is done because a key has been compromised or is vulnerable to compromise as a result of use and age.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Domain Name System (DNS) Deployment Guide."}]}
{"id": "nist_01297", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways? (Part 10) Control AM-1: implement access control across heterogeneous networks to unpatched assets. It continuously monitors all connected devices and automates response when noncompliance or unpatched assets are detected. ## 4.1.4 IBM IBM MaaS360 with Watson is a unified endpoint management (UEM) solution that transforms how organizations support users, apps, content, and data across every type of mobile device: laptops, smartphones, tablets, and IoT. IBM MaaS360 was built almost twenty years ago as a cloud-based Software-as-a-Service (SaaS) platform that integrates with preferred security and productivity tools, allowing modern business leaders to derive immediate value. IBM MaaS360 is the only UEM platform that leverages the power of the Watson Artificial Intelligence engine to deliver contextually relevant security insights for administrators, while ensuring continuous monitoring of the riskiest end users. IBM Code Risk Analyzer was developed in conjunction with IBM Research projects and customer feedback. It enables developers to quickly assess and remediate security and legal risks that they are potentially introducing into their source code, and it provides feedback directly in Git artifacts (for example, pull/merge requests) as part of continuous delivery in a DevOps pipeline. IBM Code Risk Analyzer is provided as a set of Tekton tasks, which can be easily incorporated into delivery pipelines. ## 4.1.5 Lookout Lookout is an integrated endpoint-to-cloud security solution provider with mobile endpoint protection offerings. Lookout's Mobile Endpoint Security (MES) solution provides cloud-centric behavior-based detection capabilities; it performs behavioral analysis based on telemetry data from nearly 200 million devices and over 120 million apps. This analysis enables Lookout to deliver efficient protection with a lightweight app on the device that optimizes processor speed and battery life.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_01298", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2017 NIST_ITL Cybersecurity Program Annual Report say about CONTACT:? According to 2017 NIST_ITL Cybersecurity Program Annual Report, CONTACT:: Dr. Apostol Vassilev (301) 975-3221 apostol.vassilev@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01299", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PS-140 in Computer Security Division 2003 Annual Report? (Part 15) Control PS-140: artment of Treasury, agencies participating in the Federal PKI Steering Committee and Bridge CA Project, the Federal Deposit Insurance Corporation (FDIC), and the National Security Agency (NSA). Projects in this area have worked with the American National Standards Institute's (ANSI's) X9 Committee that develops standards for the financial industry, as well as with the Internet Engineering Task Force's (IETF's) PKIX Working Group. Industry collaborators in this area have included RSA Security Entrust Technologies, IBM, Mastercard, Visa, Verizon, VeriSign, Microsoft, and others. ## ACCOMPLISHMENTS ## CRYPTOGRAPHIC STANDARDS TOOLKIT T he aim of the Cryptographic Standards Toolkit (CToolkit) project is to enable U.S. governmental agencies, and others, to select cryptographic security components and functionality for protecting their data, communications, and operations. The Toolkit helps to ensure that there is worldwide government and industry use of strong cryptography, and that secure interoperability is achieved through standard algorithms. The Toolkit also makes guidance and education available in the use of cryptography. The Toolkit currently includes a wide variety of cryptographic algorithms and techniques for encryption, authentication, non-repudiation, key establishment, and random number generation. The Toolkit is a collection of standards and guidance, and does not include any actual software implementations of the algorithms. Many of the projects discussed in this area of work are combined to form the CToolkit. The past year has seen a great deal of work go into the CToolkit. A draft version of the NIST Special Publications 800-56 Recommendation on Key Establishment Schemes and 800-57 Recommendation on Key Management were issued for public review in January 2003.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, key management. Contains security framework guidance for authentication systems. Source: Computer Security Division 2003 Annual Report."}]}
{"id": "nist_01300", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Interview according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, Interview: [SELECT FROM: personnel with assessment and auditing responsibilities; system administrators; personnel with security responsibilities]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_01301", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Electronic Mail Security say about 4.6 General Information System Security Principles? (Part 2) According to Guidelines on Electronic Mail Security, 4.6 General Information System Security Principles: e security administrator. - GLYPH&lt;c=31,font=/HABHKN+Webdings&gt; Least Privilege -This principle dictates that each task, process, or user is granted the minimum rights required to perform its job. By applying this principle consistently, should a task, process, or user be compromised, the scope of damage is constrained to the limited resources available to the compromised entity. - GLYPH&lt;c=31,font=/HABHKN+Webdings&gt; Psychological Acceptability -Users should understand the necessity of security. This can be provided through training and education. In addition, the security mechanisms in place should present users with sensible options that give them the usability they require on a daily basis. If users find the security mechanisms too cumbersome, they may devise ways to work around or compromise them. The objective is not to weaken security so it is understandable and acceptable, but to train, educate, and design security mechanisms and policies that are usable and effective. - GLYPH&lt;c=31,font=/HABHKN+Webdings&gt; Least Common Mechanism -When providing a feature to the system, it is best to have a process or service gain some function without granting the same function to other parts of the system. The ability for the mail server process to access a backend database, for instance, should not also enable other applications on the system to access the backend database. - GLYPH&lt;c=31,font=/HABHKN+Webdings&gt; Defense in Depth -Organizations should understand that a single security mechanism would generally prove insufficient. Security mechanisms (defenses) need to be layered so that compromise of a single security mechanism is insufficient to compromise a host or network. There is no 'silver bullet' for information system security. - GLYPH&lt;c=31,font=/HABHKN+Webdings&gt; Work Factor -Organizations should understand what it would take to break the system or network's security features.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_01302", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Note according to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case? Note: The software is tied to a Windows user account. Any changes made by a user would not be visible to a different user logging in to the same system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case."}]}
{"id": "nist_01303", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DS-3 in Cryptographic Key Management Workshop Summary -- June 8-9, 2009? (Part 71) Control DS-3: , and use (recall that the electronic distribution of wrapped keys led to an improvement over manually distributed keys, and public key-based key distribution led to an improvement over key wrapping). - A holistic approach to enterprise key management is needed, where a complete standard set of key management capabilities would be widely available for information protection. - Customers want to defer to authorities to tell them what key management system is good, better, and best. There is a need for a public-private partnership that allows the new CKM technologies to incubate and be evaluated, so that consumers will accept the solutions when they become available. The RSA algorithm had to be vetted for some time before it became accepted. - We must have a uniform solution to a uniform family of problems. We need a glossary of security to minimize undefined buzzwords that are used to sell commercial products. A well-understood standard lexicon is needed in security. ## 3.13 New Technologies New CKM technologies are needed to keep up with the increased demand for security, due to significant increases in computer capability, applications, and usage. New or greatly improved technologies are needed in: quantum cryptographic algorithms/computing, cloud computing, identity-based cryptography, security improvements, speed improvements, usability improvements, and cost reductions. The following are highlights of presentations from the workshop that are related to new technologies. - In computer technology, we keep moving faster and faster. We have seen an improvement of price-performance in computer technology by a factor of nearly one million in the past 30 years. - Cloud computing will provide convenient, remote, on-demand utilization (e.g., rental) of computing power and applications that the user cannot afford to maintain locally, but may need from time to time.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cryptographic Key Management Workshop Summary -- June 8-9, 2009."}]}
{"id": "nist_01304", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i say about 10.4 IEEE 802.11 RSN Operation? (Part 1) According to Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i, 10.4 IEEE 802.11 RSN Operation: 10.4 IEEE 802.11 RSN Operation IEEE 802.11 RSN operation is based on a frame exchange protocol used to transfer frames between WLAN components-STAs, APs, and ASs. The protocol uses three types of IEEE 802.11 frames, as follows: - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; Data frames , which encapsulate upper layer protocol packets, including user data (e.g., e-mail, Web pages). - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; Management frames , which include the management of association and deassociation activities, authentication, probes, and beacons. - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; Control frames , which are used for requesting and controlling access to the wireless media, such as sending an acknowledgement after receiving a data frame. By grouping the frame exchanges within the frame exchange protocol by function, IEEE 802.11 RSN operation may be thought of as occurring in five distinct phases: - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; RSN Operation Phase 1: Discovery. The STA identifies an AP for a WLAN with which it wishes to communicate. The STA locates an AP either by receiving one of the AP's periodic transmissions of Beacon frames, or by sending a Probe Request to solicit a Probe Response from an AP. After the STA has identified an AP, the STA and the AP exchange frames to negotiate various parameters for their communications. By the end of the phase, the STA and AP have agreed on an authentication method. - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; RSN Operation Phase 2: Authentication. During this phase, the STA and AS prove their identities to each other. The authentication frames pass through the AP, which also blocks nonauthentication traffic from the STA using IEEE 802.1X port-based access control. The actual authentication mechanism is implemented by the STA and AS using EAP.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, sso. Contains security framework guidance for authentication systems. Source: Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i."}]}
{"id": "nist_01305", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-128 in A Framework for Designing Cryptographic Key Management Systems? (Part 39) Control ES-128: ate Applications for the Key: This element specifies applications for which the key may be used. Examples include Kerberos, Signed E-Mail, Trusted Time Stamp, Code Signing, File Encryption, and IPSEC. - n) Key Security Policy Identifier: This element identifies the security policy applicable to the key or key type. A Key Security Policy is a set of security controls that are used to protect the key or key type during the lifecycle of the key from generation to destruction (see Section 6.7 and [RFC 3647]). A Key Security Policy is typically represented by an object identifier registered by the CKMS organization. The Key Security Policy for individual keys or key types is part of, and should be consistent with, the CKMS Security Policy. 5 Key type also implies key usage, since usage is one of the two factors that define key type. Thus, the key usage implied by the key type should be consistent with the application of the key. SP 800-130 August 2013 - o) Key Access Control List (ACL) 6 : An access control list identifies the entities that can access and/or use the keys as constrained by the key and metadata management functions (see Section 6.7). This Framework does not specify the access control list structure. The following are examples of such structures: a Microsoft Windows file/folder access control list consisting of zero or more access control entries, a Sun File System access control list, and while not a list, the Unix protection bits. In cases where interoperability is desired, the following items may require standardization: the syntax and semantics of the separators among access control entries, the ordering of entity and 'access modes' within an access control entry, the entity identifier, and the designation of bits for different 'access modes'.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, key management. Contains security framework guidance for authentication systems. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_01306", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 8.2.2.4 BER-TLV for the Derived PIV Data Objects according to NIST Derived PIV Application and Data Model Test Guidelines According to Derived PIV Application and Data Model Test Guidelines, 8.2.2.4 BER-TLV for the Derived PIV Data Objects: | Test Assertion | TA-08.02.02.04 | |----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Purpose | Confirms the BER-TLV tags for the data objects implemented within the Derived PIV Application. | | DTR(s) | \u2022 DTR-06.02.02.10 | | Vendor Documentation | The vendor to provide in its documentation the list of all the data objects implemented in the Derived PIV Application with the BER-TLV tags associated with each of them. |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_01307", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Attribute Based Access Control (ABAC) Definition and Considerations say about 3.2.2.7 A Shared Repository for Subject Attributes? According to Guide to Attribute Based Access Control (ABAC) Definition and Considerations, 3.2.2.7 A Shared Repository for Subject Attributes: Direct use of shared repositories for subject attributes should be considered where there is sufficient network connectivity to take advantage of economies of scale, increased quality control, and standard interfaces. Another advantage of using shared attribute repositories is that they provide a single access point for data from multiple sources. Building and managing a connection to a single access point may be less complex than managing multiple connections. In some cases, limited connectivity, insufficient bandwidth, or intermittent connections may prevent authorization service providers from being able to use shared repositories reliably. It may be necessary to maintain local copies of data that cannot be continuously in sync with a shared attribute repository, and thus not have access to current data.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Guide to Attribute Based Access Control (ABAC) Definition and Considerations."}]}
{"id": "nist_01308", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Interfaces for Personal Identity Verification_ Part 1 \u2013 PIV Card Application Namespace, Data Model and Representation provide? (Section 86) -|---------------------------------------------------|----------|------------| | Data Element (TLV) | Tag | Type | Max. Bytes | | Certificate | 0x70 | Variable | 1856 27 | | CertInfo | 0x71 | Fixed | 1 | | MSCUID (Optional) | 0x72 | Variable | 38 | | Error Detection Code | 0xFE | LRC | 0 | Table 31. Retired X.509 Certificate for Key Management 11 | Retired X.509 Certificate for Key Management 11 | Retired X.509 Certificate for Key Management 11 | 0x100B | 0x100B | |---------------------------------------------------|---------------------------------------------------|----------|------------| | Data Element (TLV) | Tag | Type | Max. Bytes | | Certificate | 0x70 | Variable | 1856 27 | | CertInfo | 0x71 | Fixed | 1 | | MSCUID (Optional) | 0x72 | Variable | 38 | | Error Detection Code | 0xFE | LRC | 0 | Table 32.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interfaces for Personal Identity Verification_ Part 1 \u2013 PIV Card Application Namespace, Data Model and Representation."}]}
{"id": "nist_01309", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 1 \u2013 General say about B.3.10 Static Key-Agreement Key Pairs? According to Recommendation for Key Management_ Part 1 \u2013 General, B.3.10 Static Key-Agreement Key Pairs: Static key-agreement key pairs are used to establish shared secrets between entities (see SP 80056A and SP 800-56B), sometimes in conjunction with ephemeral key pairs (see SP 800-56A). Each entity uses its private key-agreement key(s), the other entity's public key-agreement key(s), and possibly its own public key-agreement key(s) to determine the shared secret. The shared secret is subsequently used to derive shared keying material. Note that in some key-agreement schemes, one or more of the entities may not use a static key-agreement pair (see SP 800-56A and SP 80056B).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_01310", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report of the Workshop on Software Measures and Metrics to Reduce Security Vulnerabilities (SwMM-RSV) say about William R. Nichols, Software Engineering Institute? (Part 1) According to Report of the Workshop on Software Measures and Metrics to Reduce Security Vulnerabilities (SwMM-RSV), William R. Nichols, Software Engineering Institute: William R. Nichols, Software Engineering Institute A recent update to a major mobile OS included security patches to address violations of least privilege, buffer overflows and multiple cases of memory corruption, all of which were common security problems as long ago as the 1990s. It's striking that after all these years, common implementation defects remain a major source of software security vulnerabilities, including such well known examples as OpenSSL Heartbleed and Apple 'goto fail.' Research literature shows that software defect rates contribute to these vulnerabilities, providing evidence that 1% to 3% of all released defects in the Windows and Linux operating systems were potentially exploitable. Based on this, we at the SEI believed that 1) quality attributes such as security are undermined by defects, 2) defective software cannot be secure, and 3) we can estimate the number of vulnerabilities if we know the overall defect level. To test this, we examined a small number of industry software products that have very low levels of defects. In these products, we found proportionally lower levels of vulnerabilities or safety critical issues. What the products had in common was a robust measurement framework supporting early and effective defect removal; this framework allowed the system developers to manage the quality processes during implementation. We therefore concluded that improving the quality in implementation is something that can be and is being done right now to reduce security vulnerabilities. While the current quality improvements are a step in the right direction, they're only one part of making secure software. The software development lifecycle can incorporate many tools that can statically analyze source code, statically and dynamically analyze executables, examine for code coverage, scan web services, implement numerous testing techniques, and so forth.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Workshop on Software Measures and Metrics to Reduce Security Vulnerabilities (SwMM-RSV)."}]}
{"id": "nist_01311", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Interview according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, Interview: [SELECT FROM: personnel with account management responsibilities; system administrators; personnel with information security responsibilities; system developers]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_01312", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Bluetooth Security provide? (Section 71) itiator to B, encryption setup will begin after that initial authentication. If the encryption setup being successful is good enough to satisfy B, then B may never bother to attempt to authenticate A. | 1.0 1.1 1.2 2.0 2.1 3.0 | Bluetooth offers several benefits and advantages, but the benefits are not provided without risk. Bluetooth and associated devices are susceptible to general wireless networking threats, such as denial of service attacks, eavesdropping, MITM attacks, message modification, and resource misappropriation, 31 and are also threatened by more specific Bluetooth related attacks, such as the following: - Bluesnarfing. Bluesnarfing 32 enables attackers to gain access to a Bluetooth-enabled device by exploiting a firmware flaw in older (circa 2003) devices. This attack forces a connection to a Bluetooth device, allowing access to data stored on the device including the device's international mobile equipment identity (IMEI). The IMEI is a unique identifier for each device that an attacker could potentially use to route all incoming calls from the user's device to the attacker's device. 31 Additional information on general wireless security threats is available in Section 3 of NIST SP 800-48 Revision 1, Guide to Securing Legacy IEEE 802.11 Wireless Networks (https://doi.org/10.6028/NIST.SP.800-48r1). 32 - Bluejacking. Bluejacking is an attack conducted on Bluetooth-enabled mobile devices, such as cell phones. An attacker initiates bluejacking by sending unsolicited messages to the user of a Bluetooth-enabled device. The actual messages do not cause harm to the user's device, but they may entice the user to respond in some fashion or add the new contact to the device's address book. This message-sending attack resembles spam and phishing attacks conducted against email users. Bluejacking can cause harm when a user initiates a response to a bluejacking message sent with a harmful intent.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Guide to Bluetooth Security."}]}
{"id": "nist_01313", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Access Control for SAR Systems provide? (Section 40) EP is the system entity that performs access control by making decision requests and enforcing authorization decisions by the PDP. The PEP receives access requests from an Access Requester . An Access Requester may be any entity that requires access to a resource including a machine process requiring access to a file or a user requiring access to a database record. The Policy Information Point (PIP) provides the interface to access subject, resource and other attributes. A more detailed description of the XACML data-flow model is found in [OASIS-a]. Figure 3. XACML Data-Flow Model [OASIS-a]. <!-- image --> The PET system embodies a simplification of the XACML data-flow model architecture. For instance, PET combines the functionality of the PEP and Context Handler into a single PEP entity. In addition, certain components of the XACML data-flow model are omitted including the PAP (since the implemented PDP provides direct access to the system's policies) and obligation services. The simplified PET architecture is shown in Figure 4. The operation of the PET begins with a user authentication process. During the user authentication process, a user submits a login ID and password to the PEP via the PET (login) web interface. After receiving a user ID and password, the PEP attempts to authenticate the user by matching the received user ID and password against entries in the Subject (User) database. If a match exists, the PEP will (1) authorize the user for access to the PET system, (2) create a new user session, and (3) return the main PET page. If a match does not exist, however, the PEP returns an error to the user. The PET user authentication process is shown in Figure 5. Figure 4. PET architecture. <!-- image --> Figure 5. PET user authentication. <!-- image --> After being authorized by the PEP, the user may then query the system for SAR records.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Access Control for SAR Systems."}]}
{"id": "nist_01314", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Password-Based Key Derivation_ Part 1_ Storage Applications say about Recommendation for Password-Based Key Derivation Part 1: Storage Applications? According to Recommendation for Password-Based Key Derivation_ Part 1_ Storage Applications, Recommendation for Password-Based Key Derivation Part 1: Storage Applications: Meltem S\u00f6nmez Turan, Elaine Barker, William Burr, and Lily Chen Computer Security Division Information Technology Laboratory", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Password-Based Key Derivation_ Part 1_ Storage Applications."}]}
{"id": "nist_01315", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 11.1.2.2 Verify id-fpki -com mon-authentication OID according to NIST PIV Data Model Test Guidelines According to PIV Data Model Test Guidelines, 11.1.2.2 Verify id-fpki -com mon-authentication OID: 11.1.2.2 Verify id-fpki -com mon-authentication OID | Purpose | Confirms that the PIV Authentication certificate asserts the id-fpki- common-authentication OID. | |--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Reference(s) | 1. AS07.01.06 | | Precondition | 1. A valid PIV card is inserted into the contact reader. 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 sible through card handle. nt which is acces 4. A PIV authentication key and corresponding certificate are prese on the PIV card. | | Test Steps | 1. Set cardHandle := <<valid card handle>> <PIV Authentication Certificate d values from the certificate 2. Set OID := < (2.16.840.1.101.3.7.2.1.1)>> 3. Call pivGetData w/ \u2022 (IN) cardHandle \u2022 (IN) OID \u2022 (OUT) data 4. Extract certificatePolicies->policyIdentifier extension fiel | | Expected Result(s) | A policyIdentifier field in the certificatePolicies extension asserts id- fpki-common-authentication. |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_01316", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PE-6 in Identity and Access Management for Electric Utilities? (Part 68) Control PE-6: ide. Firewall Configurations 3.2 The firewalls were deployed to minimize the allowed traffic among the silo networks, as well as to minimize the traffic received from the DMZ and the public internet. The goal was to limit the cross- network traffic/connections to only those required to support the use case. The following firewall configurations include the rules that were implemented in each of the firewalls for the build implementation (Table 3-1 through Table 3-5). These configurations are provided to enable the reader to reproduce the traffic filtering/blocking that was achieved in the build implementation.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_01317", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Guidelines for Storage Infrastructure say about Table of Contents? (Part 17) According to Security Guidelines for Storage Infrastructure, Table of Contents: | Authentication Recommendations...................................................... 34 | |---------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| | | 4.3.2 Password Recommendations............................................................. | 34 | | | 4.3.3 Account Management Recommendations.......................................... | 35 | | | 4.3.4 Privilege and Session Management | Recommendations .................... 36 | | | 4.3.5 SAN-Specific Recommendations | .......................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Guidelines for Storage Infrastructure."}]}
{"id": "nist_01318", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control OC-01 in Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile? (Part 69) Control OC-01: t Task Force Transformation Initiative (2012) Guide for Conducting Risk Assessments. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-30r1. | | [SP800-37r2] | 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) NIST SP 800-37r2. | [SP800-61r2] Cichonski PR, Millar T, Grance T, Scarfone KA (2012) Computer Security Incident Handling Guide. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-61r2. https://doi.org/10.6028/NIST.SP.800-61r2 [SP800-84] Grance T, Nolan T, Burke K, Dudley R, White G, Good T (2006) Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-84. [SP800-92r1] Scarfone K, Souppaya M (2023) Cybersecurity Log Management Planning Guide. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-92r1 ipd. https://doi.org/10.6028/NIST.SP.800-92r1.ipd [SP800-150] Johnson CS, Waltermire DA, Badger ML, Skorupka C, Snyder J (2016) Guide to Cyber Threat Information Sharing.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, csf, risk management framework. General security reference material without sensitive content. Source: Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile."}]}
{"id": "nist_01319", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AN-2013 in Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet? (Part 17) Control AN-2013: | Notation | | Integer Set | Set of all Integers (positive and negative integral values, including zero) represented as a Set-Int. | Integers | | Numeric Leading Zero | The string value is a Regular Expression in the form: Str(^(\\+|-){0,1}0([0-9]+|[0-9]+\\.[0-9]+)$) The expression represents any numeric value (with or without a + or - sign) that has a leading zero followed by one or more numeric digits (which optionally may be followed by a decimal point and one or more numeric digits after the decimal). | LeadingZer oNum | | Time Index | The string value is a Regular Expression in the form: Str(^([0,1][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9].[0-9]{3}$) The expression represents time in the form hh:mm:ss.nnn, where hh is the two- digit hour,mm is the two-digit minute, ss is the two-digit seconds, and nnn is the three-digit milliseconds. (See section 7.7.2.5 of the standard). | ValidTimeI dx | | Date Range Estimate | The string expression is a Regular Expression in the form: ^((Y[0-9]{1,2}){0,1}(M[0-9]{1,2}){0,1}(D[0-9]{1,2}){0,1})$ The expression represents the amount of time used as an offset (plus or minus), in the form Y yy M mm D dd . Any of Y yy, M mm, or D dd may be omitted. Bold letters are constants; yy is the 2-digit year offset, mmis the 2-digit month offset, and dd is the 2-digit day offset. The bold letters are constants. | DateRange Estimate | | Date Time Range Estimate | The string expression is a Regular Expression in the form: ^((Y[0-9]{1,2}){0,1}(M[0-9]{1,2}){0,1}(D[0-9]{1,2}){0,1}(h[0-9]{1,2}){0,1}(m[0- 9]{1,2}){0,1})$ The expression represents the amount of time used as an offset (plus or minus), in the form Y yy M mm D dd h hh m mm. Any of Y yy, M mm, D dd, h hh, or m mmmay be omitted. The bold letters are constants.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet."}]}
{"id": "nist_01320", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.8 Deactivation according to NIST Contingency Planning Guide for Federal Information Systems According to Contingency Planning Guide for Federal Information Systems, 5.8 Deactivation: Once all activities have been completed and documentation has been updated, the {system owner} will formally deactivate the ISCP recovery and reconstitution effort. Notification of this declaration will be provided to all business and technical POCs.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Contingency Planning Guide for Federal Information Systems."}]}
{"id": "nist_01321", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Storage Encryption Technologies for End User Devices provide? (Section 1) <!-- image --> Karen Scarfone Murugiah Souppaya Matt Sexton NIST Special Publication 800-111 Guide to Storage Encryption Technologies for End User Devices Recommendations of the National Institute of Standards and Technology Karen Scarfone Murugiah Souppaya Matt Sexton Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 November 2007 <!-- image --> U.S. Department of Commerce Carlos M. Gutierrez, Secretary National Institute of Standards and Technology James M. Turner, Acting Director The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL's responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Special Publication 800-series reports on ITL's research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-111 Natl. Inst. Stand. Technol. Spec. Publ. 800-111, 40 pages (Nov. 2007) Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, secret. Contains guidance on protecting sensitive government information. Source: Guide to Storage Encryption Technologies for End User Devices."}]}
{"id": "nist_01322", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Technical Guide to Information Security Testing and Assessment say about 4.4.3 Wireless Device Location Tracking? According to Technical Guide to Information Security Testing and Assessment, 4.4.3 Wireless Device Location Tracking: Security personnel who operate the wireless scanning tool should attempt to locate suspicious devices. RF signals propagate in a manner relative to the environment, which makes it important for the operator to understand how wireless technology supports this process. Mapping capabilities are useful here, but the main factors needed to support this capability are a knowledgeable operator and an appropriate wireless antenna. If rogue devices are discovered and physically located during the wireless scan, security personnel should ensure that specific policies and processes are followed on how the rogue device is handled-such as shutting it down, reconfiguring it to comply with the organization's policies, or removing the device completely. If the device is to be removed, security personnel should evaluate the activity of the rogue device before it is confiscated. This can be done through monitoring transmissions and attempting to access the device. If discovered wireless devices cannot be located during the scan, security personnel should attempt to use a WIDPS to support the location of discovered devices. This requires the WIDPS to locate a specific MAC address that was discovered during the scan. Properly deployed WIDPSs should have the ability to assist security personnel in locating these devices, and usually involves the use of multiple WIDPS sensors to increase location identification granularity. Because the WIDPS will only be able to locate a device within several feet, a wireless scanning tool may still be needed to pinpoint the location of the device.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technical Guide to Information Security Testing and Assessment."}]}
{"id": "nist_01323", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for the Secure Deployment of IPv6 provide? (Section 294) systems to secure IPv4 tunnel endpoints from IPv4-based attacks. They should also check the consistency of the IPv4 and IPv6 addresses used in tunneled traffic and apply ingress and egress filtering. Finally, they should only accept DSTM traffic on their internal interfaces to avoid being used as an open relay. Perhaps the most serious resource exhaustion DOS attack is against the supply of IPv4 addresses. Authenticating the client-server protocol allows such attacks to be tracked down easily. For several years, dual stack hosts and routers have been promoted as the most practical transition plan. However, this approach faces a new problem today. Dual stack means having IPv4 and IPv6 addresses, but the world is running out of IPv4 addresses. It is expected that IPv4 will be needed to support IPv4only devices in the home and IPv4-only content on the Internet long past the exhaustion of the pool of globally routable IPv4 addresses. The emphasis in this transition strategy is on helping service providers plan for a situation in which not enough globally-routable IPv4 addresses are available for the WAN-facing (Wide Area Network) side of customers' NAT boxes. Several proposals have been made to deploy native IPv6 along with some method of sharing globally reachable IPv4 addresses among broadband customers needing both IPv4 and IPv6 access. All of these involve some kind of centralized network address translation (NAT), which is frequently called -carriergrade NAT.\u2016 In this context, -carrier grade\u2016 essentially means centralized, and it may also imply high capacity, shared, or multiplexed. At least four choices for how a customer's site achieves IPv4 connectivity with a carrier-grade NAT 57 have been described. One, called -IPv4-&gt;IPv4-&gt;IPv4,\u2016 provides the customer with a non-routable (typically network 10.0.0.0/8) IPv4 address between the customer's gateway and the carrier-grade NAT.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_01324", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Reference according to Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework? Reference: NEMA SG-AMI 1-2009, Section 4.3", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework."}]}
{"id": "nist_01325", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability say about 1. Introduction? (Part 1) According to Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability, 1. Introduction: 1. Introduction This work provides a novel security metric to determine the likelihood that a vulnerability has been observed to be exploited. Only a small fraction of the tens of thousands of software and hardware vulnerabilities that are published every year will be exploited. Predicting which ones is important for the efficiency and cost effectiveness of enterprise vulnerability remediation efforts. One study shows that only 5 % of vulnerabilities have been observed to be exploited in the wild [2], while the monthly vulnerability remediation rate for companies is 16 % [3]. The remediation rate is so low because it is expensive for companies to address vulnerabilities. Security patches must be tested with enterprise software to ensure continuity of operations; some vulnerabilities require non-patch remediations that require human deployment. This situation would not be a problem if the 16 % were to cover the 5 %, but metrology is lacking to accurately make that calculation. Thus, predicting which vulnerabilities will be exploited is critically important for the efficiency and cost-effectiveness of enterprise vulnerability remediation efforts. One effort that has made great progress towards this goal is the Exploit Prediction Scoring System (EPSS). EPSS provides probabilities that a vulnerability will be observed to be exploited in the wild within the next 30 days [4]. However, its probabilities are known to be inaccurate for vulnerabilities that have been previously observed to be exploited; this is stated in the EPSS documentation itself [1]. Fortunately, the probabilities are not randomly inaccurate; they underestimate the true probability. Another area that is foundational for vulnerability remediation prioritization are Known Exploited Vulnerability (KEV) lists. KEV lists are enumerations of vulnerabilities that have definitively been exploited in the past (e.g., [5] and [6]).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability."}]}
{"id": "nist_01326", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification say about 4.7 Secret Shared Betwen Physical Token and Cardholder? (Part 1) According to A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification, 4.7 Secret Shared Betwen Physical Token and Cardholder: 4.7 Secret Shared Betwen Physical Token and Cardholder The verification of the Person Identifier - Token Secret binding (established by Personal Authentication Certificate) and the verification of the Token Secret - Physical Token binding (established by the non-shared secret object, i.e., Private Cryptographic Key) involves mechanisms that does not require cardholder participation and hence authentication use cases that involve these mechanisms will be successful even in situations where the cardholder is an imposter (i.e., not the card owner/credential holder). Thus the presence of the Personal Authentication Certificate Object and the Physical Token-exclusive secret object (Sec. 4.6) are not sufficient for providing assurance against a stolen card. To provide this assurance, an object that is of the nature of a shared secret and that establishes the binding between the physical token and the cardholder must be created in the smart identity token. Verification of this binding then provides the assurance that the cardholder is indeed the legitimate owner of the token/credentials. Fortunately, the smart card technology provides the capability to define a 'PIN' object whose verification can be made as an access control condition for reading certain \"sensitive objects\" or for performing certain 'sensitive operation.' Using this feature, the identity verification application on the card can be configured to have the 'PIN Verification' as an access control condition for the 'private key operation' (i.e., digitally signing a random challenge sent by the authentication system using a private cryptographic key), which is one of integral operations of the protocol for testing the presence of a private cryptographic key on the card. Making the card recipient choose a PIN value at the time of issuance in the presence of the card issuer thus completes the process of establishing the Physical Token - Cardholder binding .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, token. Contains security framework guidance for authentication systems. Source: A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification."}]}
{"id": "nist_01327", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.2 Usability Research Methodology according to NIST Usability and Security Considerations for Public Safety Mobile Authentication According to Usability and Security Considerations for Public Safety Mobile Authentication, 2.2 Usability Research Methodology: In order to achieve the objectives of UCD, usability research methods must be applied. There are a variety of qualitative and quantitative research methods, each appropriate at different phases of the product development lifecycle. Qualitative research methods include such techniques as contextual inquiry, user needs analysis, user profiling, behavioral observation, task analysis, workflow analysis, interviews, focus groups, and participatory design. Formal usability testing and laboratory experiments are examples of quantitative research methods that often use statistical analyses. Some methods, such as questionnaires and user modeling, can be both qualitative and quantitative. It is common to begin with qualitative research to understand users' characteristics, needs, tasks, and environments. Qualitative research focuses on the rich and detailed information provided by smaller numbers of users [4] rather than the statistical analyses from larger numbers of users in quantitative research. An in-depth qualitative approach is especially crucial for domains with specialized personnel, such as public safety, given their challenging operating environments and interactions with specialized tools, technologies, and equipment. Given the exploratory nature of this effort to investigate the impacts of public safety mobile authentication, we chose to use a qualitative approach. Three NIST researchers met with six public safety subject matter experts (SMEs) in the areas of Fire, EMS, and Law Enforcement and gathered background information focused on public safety field operations. The individual semi-structured collegial discussions allowed for flexibility and the ability to follow SMEs' leads during the discussions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Usability and Security Considerations for Public Safety Mobile Authentication."}]}
{"id": "nist_01328", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Accuracy, Integrity, and Security in Computerized Vote-Tallying provide? (Section 228) lertsen (from Illinois Issues, November, 1985, pp. 1215) . - [67] Oklahoma County Purchasing Department, Report of Engineering Examination and Election Use of the DIMS Precinct Work Station PWS 1000 . December 10, 1984 (photocopy) - [68] Oklahoma State Election Board, Rules and Regulations, Section 21-8, \"After The Polls Close.\" - [69] The Sunday Oklahoman . \"Security of Elections Described,\" by Kay Morgan Atkins, January 25, 1987, p. 3 -A. - [70] Board of County Commissioners, Oklahoma County, Memorandum to Commissioner Shirley Darrell-Daniels, \"Evaluation of Voting Devices,\" by Kimberly Statum, February 27, 1987. - [71] The Sunday Oklahoman . \"Uncertain Vote Count Puzzling to Analysts,\" by Kay Morgan Atkins, January 25, 1987, p. 1-A. - [72] In the Circuit Court of the Fifteenth Judicial Circuit of Florida, In and For Palm Beach County, Civil Division, Case No. 84-7180 CA(L)H, Complaint , filed Nov. 29, 1984. - [73] Palm Beach Post . \"Re-Count Lawsuit Dismissed,\" March 2, 1985. - [74] In the Circuit Court of the Fifteenth Judicial Circuit of Florida, In and For Palm Beach County, Civil Action Case No. 84-7180 CA(L)H, Amended Complaint , filed Apr. 4, 1985, item 6 (i) , p. 2 . - [75] op. cit... Defendant Walker's First Requests for Admission To Plaintiff , filed Jan. 22, 1985. - [76] op. cit.. Amended Complaint , filed Apr. 4, 1985, item 6(p) , p. 3. - [77] op. cit. , Amended Motion to Dismiss of Rebecca E. Walker , filed Jan. 16, 1985. - [78] op. cit.. Order, by Circuit Court Judge Richard I. Wennet, Sept. 10, 1985. - [79] Salt Lake Tribune . \"County Election Computer Fails To Deliver Vote Total on Time,\" by Dave Jonsson, November 6, 1980, p. B-1. - [80] Election Administration Reports , vol. 16, no. 15, July 21, 1986, \"Audit of Recount Detects Error, Restores Stark County, Ohio Commissioner Victor,\" pp. 2-4. - [81] National Bureau of Standards, Federal Information Processing Standard 31.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Accuracy, Integrity, and Security in Computerized Vote-Tallying."}]}
{"id": "nist_01329", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cloud Computing Synopsis and Recommendations say about 8.5.1 Risk of Unintended Data Disclosure? According to Cloud Computing Synopsis and Recommendations, 8.5.1 Risk of Unintended Data Disclosure: Unclassified government systems are often operated in a manner where a single system is used to process PII, FOUO, or proprietary information, as well as to process non-sensitive, public information. In a typical scenario, a user will store sensitive and nonsensitive information in separate directories on a system or in separate mail messages on an email server. By doing so, sensitive information is expected to be carefully managed to avoid unintended distribution. If a consumer wishes to use cloud computing for non-sensitive computing, while retaining the security advantages of on premises resources for sensitive computing, care must be taken to store sensitive data in encrypted form only.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, fouo. Contains guidance on protecting sensitive government information. Source: Cloud Computing Synopsis and Recommendations."}]}
{"id": "nist_01330", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007 say about Table of Contents? (Part 2) According to Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007, Table of Contents: | Introduction....................................................................................................................1 | Introduction....................................................................................................................1 | |--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| | 1.1 | Background...............................................................................................................1 | | 1.2 | Need for Conformance Testing to Biometric Standards...........................................1 | | 1.3 | Support for the ANSI/NIST- ITL 1-2007 Standard....................................................2 | | 1.4 | Requirements in the Standard and Conformance Test Assertions ..........................2 | | 1.5 | Hierarchy of Conformance Tests..............................................................................3 | | 1.6 | Target Audience .......................................................................................................4 | | 2 CTA/CTS Overview ........................................................................................................5 | 2 CTA/CTS Overview ........................................................................................................5 | | 2.1 | High-Level Architecture ............................................................................................5 | | 2.2 | Software Details........................................................................................................6 | | 3 Quick Start......................................................................................................................7 | 3 Quick Start......................................................................................................................7 | | 3.1 | Installation.................................................................................................................7 | | 3.2 | Loading and Running Implementations ....................................................................8 | | 4 Test Results .................................................................................................................10 | 4 Test Results .................................................................................................................10 | | 4.1 | Overall Results........................................................................................................10 | | 4.2 | Detailed Results......................................................................................................10 | | Annex A - Code Structure..................................................................................................16 | Annex A - Code Structure..................................................................................................16 | | Annex B - References ........................................................................................................19 | Annex B - References ........................................................................................................19 | | Annex C - Standard Requirements and Conformance Test Assertions .......................20 | Annex C - Standard Requirements and Conformance Test Assert", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007."}]}
{"id": "nist_01331", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Secure Data Network Systems (SDNS) Key Management Documents provide? (Section 103) SREKEYcnf MSTR_SRKEY | | | | | SREKEYcnf- MSTR_SRKEY | IDLE | | MSTR_SRKEY | | | SRKRQ (note 1) WF_SRKRS | | CRRQ WF_CRRS | | SRDRQ (note 1) WF_SRDRS | | | IDLE | | WF_NKRS | | EXCcnf + MSTR SRKEY | | | | | | | | IDLE | | DOSSV yisiAi | NKRQ | WF_NKR5 | | | | | | | | IDLE | | IDLE | MSTR_ASSOC | | | | | | | | | IDLE | | | ASSOCJNIT | EXCreq NKRS | SREKEYreq | SRKRS | CRLreq | CRRS | SDLIVRreq | SRDRS | ESTAT | ASSOC_TER | Note 1 -See SDN.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_01332", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PM-8200 in Cell Phone Forensic Tools_ an Overview and Analysis? (Part 182) Control PM-8200: and LOCIGPRS data was found and reported, but had to be manually decoded for interpretation. (Meet) EMS Data: Active/deleted incoming EMS Messages that exceed 160 characters were found and reported. An EMS message containing an embedded picture was found, but neither the text nor the image were correctly decoded and presented. (Below) Foreign Language Data: SMS messages containing French language characters were found and reported correctly, but French language ADN entries were presented incorrectly in both the user interface and the HTML generated report. SMS messages containing Japanese language characters were found, but reported incorrectly in the user interface and the generated HTML report. The Japanese language ADN entries were presented correctly in the HTML report, but not in the user interface. (Below) ## SIM 8778 The scenarios above were conducted using a Cingular SIM. The attempt to acquire the Cingular SIM 8778 was unsuccessful. The error thrown reported: 'In this SIM card this type of directory not present.' (MISS) ## SIM 1144 The following scenarios were conducted using an AT&amp;T SIM. Service Provider Name (SPN) was not allocated. No FPLMN entries were registered. Basic Data: The following data was found and reported: IMSI, ICCID, Language Preference (LP), Abbreviated Dialing Numbers (ADN), Last Numbers Dialed (LND) and active/deleted SMS messages. However, long ADN text entries were truncated by one character in the Data view, but not the Binary data view. (Meet) Location Data: All LOCI and LOCIGPRS data was found and reported, but had to be manually decoded for interpretation. (Meet) EMS Data: Active/deleted incoming EMS Messages that exceed 160 characters were found and reported. An EMS message containing an embedded picture was found, but neither the text nor the image were correctly decoded and presented.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_01333", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Attribute-based Access Control for Microservices-based Applications using a Service Mesh say about 4 Authentication and Authorization Policy Configuration in Service Mesh? According to Attribute-based Access Control for Microservices-based Applications using a Service Mesh, 4 Authentication and Authorization Policy Configuration in Service Mesh: Fine-grained access control for microservices can be enforced through the configuration of authentication and access control policies. These policies are defined in the control plane of the service mesh, mapped into low-level configurations, and pushed into the sidecar proxies that form the data plane of the service mesh. The configurations enable the proxies to enforce the policies at application runtime (or request time), thus making the proxies act as Policy Enforcement Points (PEPs). As stated in the introduction, the objective of this document is to provide guidance for the deployment of an authentication and authorization framework that is external to the application and agnostic to the platform hosting the application and the service mesh product that implements the application infrastructure. However, Kubernetes is used as the reference application platform and Istio as the service mesh infrastructure platform to provide concrete examples of the concepts and to allow for recommendations with more clarity and specificity.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Attribute-based Access Control for Microservices-based Applications using a Service Mesh."}]}
{"id": "nist_01334", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Media Protection according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance, Media Protection: Media protection solutions enable a manufacturer to restrict the use of portable media within the manufacturing system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance."}]}
{"id": "nist_01335", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 816) device Uses closed-loop or advisory methods to isolate the faulted segment Once the fault is isolated, it determines how best to restore service to unfaulted segments through feeder reconfiguration. Smart Grid Characteristics \uf0b7 Provides power quality \uf0b7 Optimizes asset utilization \uf0b7 Anticipates and responds to system disturbances Cybersecurity Objectives/Requirements \uf0b7 Integrity of outage information is critical \uf0b7 Availability to detect large-scale outages usually involve multiple sources of information \uf0b7 Confidentiality is not very important Potential Stakeholder Issues \uf0b7 Customer safety \uf0b7 Customer device standards \uf0b7 Demand response acceptance by customers 111 Category: Distribution Automation Overall Use Case #26 Scenario: Load Management Category Description A broad definition of \u201cdistribution automation\u201d includes any automation that is used in the planning, engineering, construction, operation, and maintenance of the distribution power system, including interactions with the transmission system, interconnected distributed energy resources, and automated interfaces with end-users. No one approach is optimal for a utility or its customers. Certain distribution automation functions, such as optimal volt/VAR control, can be more beneficial to one utility or even a few feeders in one utility, while other distribution automation functions, such as fault detection, isolation, and service restoration, could be far more beneficial in other utilities. Increasingly, distribution automation will entail closed-loop control, where distribution algorithms, applied to real-time models of the distribution system, will increase reliability and/or efficiency of the distribution system without direct operator involvement.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01336", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain https:/ /doi.org/10.1145/2809826.2809834 according to NIST 2016 NIST_ITL Cybersecurity Program Annual Report According to 2016 NIST_ITL Cybersecurity Program Annual Report, https:/ /doi.org/10.1145/2809826.2809834: Cyber attacks inevitably have negative impacts on relevant missions. However, concrete methods to accurately evaluate such impacts are rare. In this paper, we propose a probabilistic approach based on Bayesian networks for quantitative mission impact assessment. A System Object Dependency Graph (SODG) is first built to capture the intrusion propagation process at the low operating system level. On top of the SODG, a mission-task-asset (MTA) map can be established to associate the system objects with corresponding tasks and missions. Based on the MTA map, a Bayesian network can be constructed to leverage the collected intrusion evidence and infer the probabilities of tasks and missions being tainted. This approach is promising for effective quantitative mission impact assessment. <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01337", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways? (Part 48) Control AM-1: 2 | Does the platform monitor the security and vulnerabilities associated with all software and dependencies used? | There is an audit trail of users who have logged in and the actions they performed. Updates are also sent out to help remediate software running on the platform. | | | SM 4.3 | Is anti-malware or antivirus able to be installed on the system running your platform? | Eclypsium scanners and the Eclypsium backend are compatible with running other endpoint security software on the same device. | | | SM 4.4 | Does the platform allow for logging connection events to the tool? | In cloud deployments, Eclypsium manages network security protections. In an on- premises deployment, this would be inherited from the environment into which Eclypsium is deployed. | | | SM 4.5 | Are there training courses or procedures in the event of an incident involving the tool or platform? | Eclypsium security operations personnel receive security and incident response training. Customer training is available from Eclypsium to cover firmware security and incident response scenarios. | | | SM 5.1 | Are there training courses in how to use the products? Are there different courses for different roles? | Eclypsium has the latest training catalog. | | | SM 5.2 | Are there training courses for teaching administrators how to utilize the platform? | Eclypsium has the latest training catalog. | | | SM 5.3 | Are trainings updated and metrics collected to improve trainings? | Eclypsium has the latest training catalog. | | ## A.2.4 Forescout Platform Support of Security Measures | SM # | Question | Technical Mechanism or Configuration | Refs.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, incident response. Contains technical security guidance that could inform defensive posture. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_01338", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Issuer according to NIST Test Personal Identity Verification (PIV) Cards Version 2? Issuer: CN=Test ECC P-256 CA for Test PIV Cards v2, ou=Test CA, o=Test Certificates 2020, c=US", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_01339", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Information Security Handbook_ A Guide for Managers provide? (Section 128) gure 5-6 plots system category along the vertical axis and corrective action impact along the horizontal axis. The notional agency systems are denoted as the small letters at the top of each quadrant. In this example, systems 'N' and 'F' were found to have category rankings of 'high' and corrective action impacts of 'great.' 41 Figures 4-6 and 4-8 on pages 31 and 34 (respectively) in NIST SP 800-65 provide examples of how spreadsheets can be used to facilitate the prioritization process. Figure 5-6. Joint Prioritization with Costs <!-- image --> Drawn from the perspective of the enterprise, Figure 5-6 plots agencydetermined security controls importance along the vertical axis and corrective action impact along the horizontal axis. The numbers (1-17) represent the seventeen NIST SP 800-53 security control areas used for this example. Security control area 12 ranked 'high' in importance but had a 'basic' corrective action impact. The dollar figures in Figure 5-6 represent the total cost to implement all corrective actions within that cell. For example, looking at cell HG, it would cost the agency $85,961 to implement corrective actions for systems 'N' and 'F' and topic area '4.' After plotting all of its systems, the agency should perform executive validation of the placement of the various systems to ensure that stakeholders' priorities are met. Agency information security stakeholders should review the prioritization results to ensure that the prioritization is appropriate and given the opportunity to reprioritize their inputs if the results of the process are found to be unsatisfactory. Assuming the agency stakeholders agree that all prioritized corrective actions are appropriate, as displayed in Figure 5-6, the analysis can proceed accordingly.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_01340", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for the Use of PIV Credentials in Facility Access say about 2.4 Infrastructure Requirements? According to Guidelines for the Use of PIV Credentials in Facility Access, 2.4 Infrastructure Requirements: The qualities and benefits of the complete PIV System can only be achieved if its implementation is supported by bi-directional communications infrastructure used in modern PACS. The following areas have significant influence on the rate at which the complete PIV System integration can be achieved by PACS, and should therefore be supported by PACS upgrades and new PACS procurements: 1. Fast network or two-way serial communication among PACS readers and controllers, panels and head-end components. 2. Fast network communication for PIV status and validation services. Point (1) allows the PACS to quickly issue commands to cards and receive responses while Point (2) allows direct access to PIV status and validation services, if needed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Use of PIV Credentials in Facility Access."}]}
{"id": "nist_01341", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Appendix B - NVD Scoring Methodology according to NIST CVSS Implementation Guidance According to CVSS Implementation Guidance, Appendix B - NVD Scoring Methodology: This appendix describes the process NVD uses to collect, analyze, and score vulnerabilities in accordance with the CVSS. An overview of the CVSS is provided within section 2. Version 2.0 of the CVSS was first established as the vulnerability scoring system used by SCAP in specification version 1.0 [2] and has been used as primary guidance by the NVD since September 2007. Vulnerabilities scored prior to September 2007 used version 1.0 of the CVSS and were approximated to version 2.0's metrics without human analysis and are noted as 'incomplete approximation' in the description.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: CVSS Implementation Guidance."}]}
{"id": "nist_01342", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography say about 6.4.1.5 Owner Assurance of Private-Key Possession? (Part 2) According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography, 6.4.1.5 Owner Assurance of Private-Key Possession: te key corresponding to PubKeyU , where PubKeyV and PubKeyU are the public keys associated with parties V and U, respectively, that were used during that KAS2-Party\\_V-confirmation transaction. 4. -The KAS2-Party\\_U-confirmation scheme in Section 8.3.3.3 can be used to provide assurance to a key-pair owner, acting as party V, that both parties are in possession of the correct private key; i.e., when the key confirmation is successful, party V has obtained assurance that party U possesses the private key corresponding to PubKeyU and that party V possesses the private key corresponding to PubKeyV , where PubKeyU and PubKeyV are the public keys associated with parties U and V, respectively, that were used during that KAS2-Party\\_U-confirmation transaction. 5. -The KAS2-bilateral-confirmation scheme in Section 8.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.e., when the bilateral key-confirmation is successful, each party has obtained assurance that party U possesses the private key corresponding to PubKeyU , and that party V possesses the private key corresponding to PubKeyV , where PubKeyU and PubKeyV are the public keys associated with parties U and V, respectively, that were used during that KAS2-bilateral-confirmation transaction.' 3. The owner receives assurance via an encrypted certificate - The key-pair owner uses the private key while engaging in a key-establishment transaction with a Certificate Authority (trusted by the owner) using a scheme in this Recommendation after providing the CA with the corresponding public key. As part of this transaction, the CA generates a (new) certificate containing the owner's public key and encrypts that certificate using (some portion of) the symmetric keying material that has been established. Only the encrypted form of the certificate is provided to the owner.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: certificate authority, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography."}]}
{"id": "nist_01343", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI) say about 2.5 Authorization Boundary of the Issuer? (Part 1) According to Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI), 2.5 Authorization Boundary of the Issuer: 2.5 Authorization Boundary of the Issuer The first step in authorizing an issuer is to identify the appropriate authorization boundary. The authorization boundary defines the specific operations that are to be the target of the assessment and authorization. A PCI comprises the complete set of functions required for the issuance and maintenance of PIV Cards while a DPCI comprises of the complete set of functions required for the issuance and maintenance of Derived PIV Credentials. In determining the authorization boundary, the organization must consider if the functions are being performed identically in all issuing facilities, are using identical information technology components, and are under the same direct management control. For instance, an organization may have two sub-organizations, each of which has distinct processes and management structures. The organization may decide to establish two separate issuers, each with its own authorization boundary. In this example, two separate assessments would be undertaken. Each assessment would result in an independent authorization decision. In drawing an authorization boundary, an organization may want to include only a subset of its issuing facilities. For example, if a PCI has several facilities, some of which are ready for operation and some that are still in the development stage, the organization may choose to define the authorization boundary to include the PCI and only those facilities that are ready to be assessed. If the authorization is successful, the PCI and a subset of its issuing facilities will be authorized to operate and begin issuing PIV Cards. The remaining issuing facilities can continue with implementation and be included in the authorization boundary at a later date.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_01344", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE) say about Time Frame Supported:? According to Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE), Time Frame Supported:: Because this was the first risk assessment performed by Orvilia, the process was more time-intensive than it will be in future risk management cycles. Orvilia completed the initial risk assessment within six months.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_01345", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain D.5 Address Holder Environments according to NIST Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, D.5 Address Holder Environments: It is assumed that address holders understand the usage of RPKI resources and have agreements in place with a Regional Internet Registry (RIR) or other authority that enables route origin authorizations (ROAs) for addresses that they hold to be created and signed. The address holder has two options for creating the ROAs: the hosted or delegated model.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, pki. Contains security framework guidance for authentication systems. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_01346", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Misnamed Files according to Cell Phone Forensic Tools_ an Overview and Analysis? Misnamed Files: Misnamed files (e.g., . txt file renamed with a . dll extension) were found and reported in the Files folder and could be viewed with the proper application after saved to the forensic workstation. (Meet)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_01347", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Contact: according to NIST Computer Security Division 2013 Annual Report According to Computer Security Division 2013 Annual Report, Contact:: Mr. David Waltermire (301) 975-3390 david.waltermire@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2013 Annual Report."}]}
{"id": "nist_01348", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-06(05) in Assessing Security Requirements for Controlled Unclassified Information? (Part 104) Control AC-06(05): Strategies, Tools, and Methods ## ASSESSMENT OBJECTIVE ## Determine if: A.03.17.02[01]: acquisition strategies, contract tools, and procurement methods are developed to identify supply chain risks. A.03.17.02[02]: acquisition strategies, contract tools, and procurement methods are developed to protect against supply chain risks. A.03.17.02[03]: acquisition strategies, contract tools, and procurement methods are developed to mitigate supply chain risks. A.03.17.02[04]: acquisition strategies, contract tools, and procurement methods are implemented to identify supply chain risks. A.03.17.02[05]: acquisition strategies, contract tools, and procurement methods are implemented to protect against supply chain risks. A.03.17.02[06]: acquisition strategies, contract tools, and procurement methods are implemented to mitigate supply chain risks.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_01349", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Rodney Petersen | 2016 Government Leadership of the Year according to NIST 2017 NIST_ITL Cybersecurity Program Annual Report According to 2017 NIST_ITL Cybersecurity Program Annual Report, Rodney Petersen | 2016 Government Leadership of the Year: Awarding Organization: The Colloquium for Information Systems Security Education (CISSE) <!-- image --> Rodney Petersen is the director of the National Initiative for Cybersecurity Education (NICE) at the National Institute of Standards and Technology (NIST). He previously served as the Managing Director of the EDUCAUSE Washington Office and a Senior Government Relations Officer. He founded and directed the EDUCAUSE Cybersecurity Initiative and was the lead staff liaison for the Higher Education Information Security Council. Prior to joining EDUCAUSE, he worked at two different times for the University of Maryland - first as Campus Compliance Officer in the Office of the President and later as the Director of IT Policy and Planning in the Office of the Vice President and Chief Information Officer. He also completed one year of federal service as an Instructor in the Academy for Community Service for AmeriCorps' National Civilian Community Corps. He is the co-editor of a book entitled 'Computer and Network Security in Higher Education.' He received his law degree from Wake Forest University and bachelors degrees in political science and business administration from Alma College. He was awarded a certificate as an Advanced Graduate Specialist in Education Policy, Planning, and Administration from the University of Maryland. Source: https:/ /cisse.info/about/award-recipients/634-2016-government-leadership-of-the-year-rodney-petersen", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01350", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cryptographic Key Management Workshop Summary -- June 8-9, 2009 say about 3.4 Usability? (Part 2) According to Cryptographic Key Management Workshop Summary -- June 8-9, 2009, 3.4 Usability: s to know the prospective user and to understand that security is not the primary task of the user. A system must be efficient, effective and understandable; there is no complex system that is secure. - Conventional wisdom is that 'computer security systems can't be effective unless they are complex and difficult to use.' - PKI enrollment is often the most difficult computer task to perform. Usability is more than just the user interface. CKM designers have to adopt the mantra of making it easy for users to do the right thing. Designers have to align the design to the user's conceptual model of a security system. The interface has to use terminology that is intuitively obvious to the general computer user. The complexity of the CKM system has to be minimized for the user if it is to be used effectively. - Certificate pop-ups have to be minimized, because users have become accustomed to ignoring pop-ups. Factors that inhibit the adoption of new technologies have to be eliminated, and those that promote the adoption of effective security technologies have to be encouraged. - Applicable Models: Cryptographic key life cycle (key birth to death management); security analysis; model all system actors and their actions; information management models must be the foundation of key management. - Users of a CKM System are humans, devices, applications, programmers, and administrators. - Design Considerations must include a mix of long-term symmetric and asymmetric keys for some applications, algorithm agility, security parameters, and a desire to keep it simple and keep it cheap. - When the CKM policies, components, and recommended security practices are properly selected from the CKM System Design Framework and combined properly in a CKM system design, we have a well-defined CKM solution. - We would like to see a leap in ease of implementation, management, and use; we have already made significant progress in this area.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, key management. Contains security framework guidance for authentication systems. Source: Cryptographic Key Management Workshop Summary -- June 8-9, 2009."}]}
{"id": "nist_01351", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-256 in PIV Data Model Test Guidelines? (Part 65) Control HA-256: Extract Finger View Header fie on ld . a. b. Extract contents of Finger Position c. Extract contents of View Number. . d. Extract contents of Impression Type e. Extract contents of Finger Quality. f. Extract contents of Number of Minutiae. 5.Repeat steps 4a through 4f for the second view header. | |--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Expected Result(s) | The expected values for each of the fields parsed in Step 4 above are given below: a. Finger View Header shall have the value 'A' b. Finger Position value shall be between 0 and 14. c. View Number shall be 0 if there is only one minutiae record for a finger. d. Impression Type is 0 or 2. 100. e. Finger Quality value shall be between 60 and een 0 and 128. The expected values for each of the fields parsed in Step 5 is the same as above. f. Number of Minutiae value shall be betw | ## 9.3.3 Fingerprint Minutiae Data | Purpose | Verify that each instance of Fingerprint Minutiae data conforms to specifications in Table 3 of SP80076.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_01352", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain CONTACT: according to NIST 2016 NIST_ITL Cybersecurity Program Annual Report According to 2016 NIST_ITL Cybersecurity Program Annual Report, CONTACT:: Dr. Michaela Iorga (301) 975-8431 michaela.iorga@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01353", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1.4 provide? (Section 163) ement> <xsd:complexType name=\"valueType\"> <xsd:annotation> <xsd:documentation xml:lang=\"en\"> Data type for the Value element, which represents a tailorable string, boolean, or number in the Benchmark. </xsd:documentation> </xsd:annotation> <xsd:complexContent> <xsd:extension base=\"cdf:itemType\"> <xsd:sequence> <xsd:element name=\"value\" type=\"cdf:selStringType\" minOccurs=\"1\" maxOccurs=\"unbounded\"/> <xsd:element name=\"default\" type=\"cdf:selStringType\" minOccurs=\"0\" maxOccurs=\"unbounded\"/> <xsd:element name=\"match\" type=\"cdf:selStringType\" minOccurs=\"0\" maxOccurs=\"unbounded\"/> <xsd:element name=\"lower-bound\" type=\"cdf:selNumType\" minOccurs=\"0\" maxOccurs=\"unbounded\"/> <xsd:element name=\"upper-bound\" type=\"cdf:selNumType\" minOccurs=\"0\" maxOccurs=\"unbounded\"/> <xsd:element name=\"choices\" type=\"cdf:selChoicesType\" minOccurs=\"0\" maxOccurs=\"unbounded\"/> <xsd:element name=\"source\" type=\"cdf:uriRefType\" minOccurs=\"0\" maxOccurs=\"unbounded\"/> <xsd:element name=\"signature\" type=\"cdf:signatureType\" minOccurs=\"0\" maxOccurs=\"1\"/> </xsd:sequence> <xsd:attribute name=\"type\" type=\"cdf:valueTypeType\" default=\"string\" use=\"optional\"/> <xsd:attribute name=\"operator\" type=\"cdf:valueOperatorType\" default=\"equals\" use=\"optional\"/> <xsd:attribute name=\"interactive\" type=\"xsd:boolean\" default=\"0\" use=\"optional\"/> <xsd:attribute name=\"interfaceHint\" use=\"optional\" type=\"cdf:interfaceHintType\"/> </xsd:extension> </xsd:complexContent> </xsd:complexType> <!-- ************************************************************** --> <!-- *************** Value-related Types ************************ --> <!-- ************************************************************** --> <xsd:complexType name=\"selChoicesType\"> <xsd:annotation> <xsd:documentation xml:lang=\"en\"> The choice element specifies a list of legal or suggested choices for a Value object. It holds one or more choice elements, a mustMatch attribute, and a selector attribute.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1.4."}]}
{"id": "nist_01354", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity say about 1.2 Solution? According to Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity, 1.2 Solution: The NCCoE collaborated with stakeholders in the electricity sector, UMD, and cybersecurity technology providers to build an environment that represents a distribution utility interconnected with a campus DER microgrid. Within this ecosystem, we explore how information exchanges among DERs and electric distribution grid operations can be protected from certain cybersecurity compromises. The example solution demonstrates the following capabilities: - \uf0a7 communications and data integrity to ensure that information is not modified in transit - \uf0a7 authentication and access control to ensure that only known, authorized systems can exchange information - \uf0a7 command register that maintains an independent, immutable record of information exchanges between distribution grid and DER operators - \uf0a7 malware detection to monitor information exchanges and processing to identify potential malware infections - \uf0a7 behavioral monitoring to detect deviations from operational norms - \uf0a7 analysis and visualization processes to monitor data, identify anomalies, and alert operators The example solution documented in the practice guide uses technologies and security capabilities from our project collaborators. The solution aligns with the security standards and guidelines of the NIST Cybersecurity Framework; NIST Interagency or Internal Report 7628 Revision 1: Guidelines for Smart Grid Cybersecurity [1]; and NIST Special Publication (SP) 1108r4, Framework and Roadmap for Smart Grid Interoperability Standards, Release 4.0 [2].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity."}]}
{"id": "nist_01355", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study say about 1 Introduction? (Part 2) According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study, 1 Introduction: challenges and recommendations abound, it is currently unknown whether these apply to programs within the U.S. government (federal) sector and if government organizations experience additional issues. To address this gap, NIST completed research to better understand the needs, challenges, practices, and necessary competencies of federal security awareness teams and programs. The research consisted of two phases: eight focus groups of federal security awareness professionals which informed the development of a follow-on, online survey completed by 96 federal employees involved in their security awareness programs. Research results are directly informing government efforts to produce guidance and resources to aid federal security awareness programs. This report provides an overview of the research, including a description of the research methodologies and the participants, organizations, and security awareness programs represented in the study. Two companion documents report on the results of the study. Each document addresses an overarching theme focused on a subset of research questions: NIST 8420A 'Approaches and Challenges of Federal Cybersecurity Awareness Programs' - What approaches and techniques do federal agencies employ in their security awareness programs? - What's working well with respect to security awareness programs in federal agencies? - What's not working well? What are the challenges and concerns of federal security awareness programs? - How do organizations determine the effectiveness of the security awareness program? - What resources and guidance are used to inform the security awareness programs? \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ - What do programs feel like they need to be more successful? What kinds of resources would be most beneficial?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study."}]}
{"id": "nist_01356", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2009 Annual Report provide? (Section 32) d new ones were added. 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. In FY2010, we will continue the momentum to expand the number of sample practices and policies made available to federal agencies and the public. We are currently identifying robust sources for more samples to add to this growing repository. We plan to take advantage of the advances in communication technology and combine this outreach with other outreach areas for information security in order to reach many in the federal agencies and the public. Contacts: Ms. Pauline Bowen (301) 975-2938 pauline.bowen@nist.gov Mr. Mark Wilson (301) 975-3870 mark.wilson@nist.gov What do a business's invoices have in common with e-mail? If both are done on the same computer, the business owner may want to think more about computer security. Information - payroll records, proprietary information, client or employee data - is essential to a business's success. A computer failure or other system breach could cost a business anything from its reputation to damages and recovery costs.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Computer Security Division 2009 Annual Report."}]}
{"id": "nist_01357", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Implementing a Zero Trust Architecture_ High-Level Document provide? (Section 61) s to Resource Data Based on Requesting Endpoint - the subject will be granted full or limited access to different levels of data based on whether the requesting endpoint is enterprise-managed or BYOD. - \uf0a7 Scenario H-3: Internet Access restricted when Accessing High Level Data - while a subject has an active access session to a resource storing data with high classification, the enterprise will restrict that subject from accessing public internet resources. - \uf0a7 Scenario H-4: Accessing High Level Data Triggers MFA Challenge - if a subject already as an active access session with a resource and is accessing low-classification data, a request to access high-classification data at that resource will trigger a multi-factor authentication challenge. - \uf0a7 Scenario H-5: Just-in-Time Access to High-Level Data - the enterprise can grant a subject temporary access privileges to high-level data when needed. - \uf0a7 Scenario H-6: Operations Denied When Accessing High Level Data - a subject that is authorized to fully access (e.g., read and write) high classification data when using an enterprise-managed endpoint and located on premises or at a branch office can have their access privileges limited to read-only when using a BYOD or when located remote from enterprise infrastructure. - \uf0a7 Scenario H-7: High Classified Data Has Extra Protection When Stored on Endpoints - when a subject downloads or copies high classification data onto the subject's endpoint, the data is encrypted or has some further protection that requires the subject to pass a challenge before accessing or performing actions on the local copy of the data. The summary and detailed functional demonstration results are shown in the sections below.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, mfa. Contains security framework guidance for authentication systems. Source: Implementing a Zero Trust Architecture_ High-Level Document."}]}
{"id": "nist_01358", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Block Cipher Modes of Operation_ the CCM Mode for Authentication and Confidentiality say about 4.1 Definitions and Abbreviations? (Part 1) According to Recommendation for Block Cipher Modes of Operation_ the CCM Mode for Authentication and Confidentiality, 4.1 Definitions and Abbreviations: 4.1 Definitions and Abbreviations | 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. | |-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Associated Data | Input data to the CCM generation-encryption process that is authenticated but not encrypted. | | Authenticity | The property that data originated from its purported source. | |-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Bit | A binary digit: 0 or 1. | | Bit Length | The number of bits in a bit string. | | Bit String | An ordered sequence of bits. | | Block | A bit string whose length is the block size of the block cipher algorithm. | | Block Cipher Algorithm | A family of functions and their inverses that is parameterized by cryptographic keys; the functions map bit strings of a fixed length to bit strings of the same length. | | Block Size | The bit length of an input (or output) block of the block cipher. | | CBC-MAC | Cipher Block Chaining-Message Authentication Code | | CCM | Counter with Cipher Block Chaining-Message Authentication Code. | | Ciphertext | The output of the CCM encryption-generation process. | | Cryptographic Key | A parameter used in the block cipher algorithm that determines the forward cipher function. | | CTR | Counter.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Block Cipher Modes of Operation_ the CCM Mode for Authentication and Confidentiality."}]}
{"id": "nist_01359", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PE-3 in Guide to Operational Technology (OT) Security? Control PE-3: Physical Access Control", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_01360", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Conclusion according to NIST Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS) According to Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS), Conclusion: The whole Group unanimously felt that the opportunity to participate in the Workshop was an extremely valuable experience, and one that none of us would have liked to miss. We feel that some extremely useful progress has been made, and, at an absolute minimum, we are beginning to develop a useful vocabulary which can be used to discuss the problem. We would like to sincerely thank the organizers for the opportunity and would like to express an eagerness to continue our participation in the future. On a personal note, as the Group Leader, I would like to sincerely thank the members of the Group, and Stuart Katzke who joined us for some of our discussions, for providing a very exciting forum and what I consider to be some very valuable ideas", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)."}]}
{"id": "nist_01361", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security_ Selected Articles say about The Cuckoo's Egg , by Clifford Stoll. Doubleday 1989. 326 pages.? (Part 2) According to Computer Security_ Selected Articles, The Cuckoo's Egg , by Clifford Stoll. Doubleday 1989. 326 pages.: vice is provided on the requirements for security detection controls to produce information acceptable as criminal evidence. Analyses of federal and several state computer crime statutes are included. Organizing for Computer Crime Investigation and Prosecution, by Catherine H. Conlv. NCJ 118216. National Institute of Justice. 1989. 124 pages. Dedicated Computer Crime Units, by J. Thomas McEwen. NCJ 118215. National Institute of Justice. 1989. 129 pages. Information Technology Installation Security, Federal Systems Integration and Management Center, Office of Technical Assistance, 5203 Leesburg Pike, Suite 400, Falls Church, VA 22051. December 1988. 98 pages. This publication addresses all government managers having responsibility for information technology. The publication is intended to assist them in developing, implemendng, and maintaining security policies, procedures and techniques. Computer Viruses: Dealing with Electronic Vandalism and Programmed Threats, by Eugene Spafford, Kathleen Heaphy and David Ferbrache. ADAPSO, 1300 North Seventeenth Street, Suite 300, Arlington, VA 22209. 1989. 109 pages. This book presents a high-level discussion of computer viruses, explaining how they work, who writes them, and what they do. It is not a technical reference on viruses. The book dispels common myths about viruses and provides simple, effective suggestions on how to protect computer systems against threats. Managing Information Resources: New Directions In State Government, Dr. Sharon L. Caudel, Dr. Donald A. Marchand with Dr. Stuart L Bretschneider, Ms. Particia T. Fletcher, and Mr. Kurt M. Thurmaier. School of Information Studies, Syracuse University, 4-206 Center for Science and Technology, Syracuse, NY 13244-4100. August, 1989. 307 pages. This report is a joint effort between the National Association for State Information Systems, Inc., information processing industry companies, and Syracuse University's School of Information Studies which directed the research.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security_ Selected Articles."}]}
{"id": "nist_01362", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Secure Biometric Match-on-Card Feasibility Report provide? (Section 15) . The size of the generated certificates was kept consistent by changing only the public key modulus and exponent associated with each certificate to match the public/private key pair stored on a DUT. For tests using Rivest Shamir Adleman (RSA) 1024, the size of the certificate used was 1,345 bytes and for RSA 2048, the certificate size was 1,477 bytes. Testing consisted of sending matching and non-matching sample fingerprint templates to a DUT for verification in alternating sequence. First, sample fingerprint templates containing a minutia count of 41 were sent to the DUT for verification and time values were recorded. The process was repeated for sample fingerprint templates containing a minutia count of 34 and 27. Live fingerprint scans were not used in the tests since it was desirable to maintain a controlled test environment where the minutia count of the sample fingerprint templates could be regulated. Instead, the sample fingerprint templates were read from files generated from fingerprint scans beforehand. For each test case, 200 trials were run so that 100 time values could be collected each for matching and non-matching templates. The DUT was powered continuously during the automated sequence of 200 trials. As a consequence, transaction delays that could result from operations at DUT power-up, for example FIPS 140-2 power-up diagnostic tests, are not visible in the measurements. Table 3 provides a summary of the DUTs used in the feasibility study. Multiple DUTs may correspond to the same physical card but have been given unique names to differentiate the test configurations. Note that the DUTs submitted are prototypes constructed to meet the requirements stated in Appendix D. In conformance with the 'no endorsement' policy of NIST, the participants' DUT names have been omitted. Table 3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Biometric Match-on-Card Feasibility Report."}]}
{"id": "nist_01363", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Web Transactions_ TLS Server Certificate Management say about 2.3.1.2.5 Security Assertion Markup Language (SAML) Single Sign-On Prerequisites? According to Securing Web Transactions_ TLS Server Certificate Management, 2.3.1.2.5 Security Assertion Markup Language (SAML) Single Sign-On Prerequisites: SAML is a highly recommended DigiCert feature for secure user authentication. However, it is not required to duplicate the TLS lab setup. For more information on SAML, please refer to guidance at: - \uf0a7 https://pages.nist.gov/800-63-3/sp800-63-3.html Before beginning, make sure the following prerequisites are met: - \uf0a7 Have a CertCentral account. - \uf0a7 Have SAML enabled on the CertCentral account. (To get the SAML features turned on for the CertCentral account, contact the DigiCert account representative or the DigiCert support team. Once activated, in the sidebar menu, under Settings, see the Single Sign-On and SAML Certificate Request menu options.) - \uf0a7 Have an identity provider (IdP). - \uf0a7 Have the IdP metadata (dynamic or static). - \uf0a7 Have admin privileges on the CertCentral account (or have manager privileges on the CertCentral account with the Allow access to SAML settings permission).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, single sign-on. Contains security framework guidance for authentication systems. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_01364", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet say about AN-2013 Annex G: Mapping to the NIEM IEPD? (Part 71) According to Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet, AN-2013 Annex G: Mapping to the NIEM IEPD: | | X | | Req. # - ID | Ref. in Base Std. | Requirement Summary | L e v e l | Assertion ID | Test Assertion | N o t e s | Imp. Required | Imp. Support | Supporte d Range | Test Result | E n c .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet."}]}
{"id": "nist_01365", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain SHARE YOUR FEEDBACK according to NIST Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity According to Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity, SHARE YOUR FEEDBACK: You can view or download the guide at Help the NCCoE make this guide better by sharing your thoughts with us as you read it. If you adopt this solution for your own organization, please share your experience and advice with us. We recognize that technical solutions alone will not fully enable the benefits of our solution, so we encourage organizations to share lessons learned and best practices for transforming the processes associated with implementing this guide. To provide comments or to learn more by arranging a demonstration of this example implementation, contact the NCCoE at energy\\_nccoe@nist.gov.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity."}]}
{"id": "nist_01366", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Understanding Stablecoin Technology and Related Security Considerations provide? (Section 41) (Coin Minting and Burning): Stablecoins have different policies for minting (coin creation) and burning (coin deletion). Most stablecoin architectures create coins only upon the receipt of collateral. For redemption, they return the provided collateral funds in exchange for receipt of the minted coins (burning them to remove them from circulation). Other stablecoins allow for arbitrary printing of coins without the need to receive collateral. A few even allow for arbitrary burning (and minting) of coins while coins are in the users' possession (apart from any actions by the users) in order to stabilize the coin value. Stablecoins are often collateralized with fiat currency, really 'cash-equivalent reserves (deposits, T-bills, commercial paper)' [1]. Cryptocurrencies (both stable and volatile) may also be used for collateral. Some have reserves held in physical commodities, such as gold or diamonds, where a large degree of value can be stored in a small form factor. Others have reserve funds that represent asset values but are invested in mutual funds or exchange traded funds (ETFs). Others may hold their reserve in an investment account that trades in futures and options to keep a reserve pool that tracks a particular asset value. Some stablecoins have no reserve pool and, thus, no collateral type. Such stablecoins rely on the ability to arbitrarily print volatile companion coins to generate reserve funds on demand. Cryptocurrency-backed stablecoins are often 'over-collateralized', having more cryptocurrency value in reserve than the total value of all issued stablecoin tokens. They do this when the value of their reserves may have high volatility. Fiat currency and non-currency asset collateralized stablecoins are often 'fully collateralized', having a reserve pool of equal value to all issued stablecoin tokens. However, some are only 'partially collateralized', keeping in reserve only a fraction of the value of the issued tokens.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Understanding Stablecoin Technology and Related Security Considerations."}]}
{"id": "nist_01367", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Considerations for Remote Electronic UOCAVA Voting say about 2.2.4 Auditors / observers? According to Security Considerations for Remote Electronic UOCAVA Voting, 2.2.4 Auditors / observers: Auditors and observers will need access to information generated or observed during an election in order to perform their functions. In general, auditors and observers will have limited information collected through observation due to the distributed nature of remote electronic voting systems. Most of the information auditors and observers will have access to will be electronically generated by the remote electronic voting system with a possible exception when paper ballots are used or a voter verified paper audit trial is produced. The integrity and accuracy of the information used by the auditors and observers will greatly impact the effectiveness of their functions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Remote Electronic UOCAVA Voting."}]}
{"id": "nist_01368", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events say about D.2 Data Integrity Use Case Requirements? (Part 7) According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events, D.2 Data Integrity Use Case Requirements: | The downloads are identified as mali- cious, using a denyl- ist. | Data Integrity DR-4 | | CR 4.i | | The downloads are identified as mali- cious through analy- sis, and the denylist is updated. | Data Integrity DR-4 | | CR 4.j | | The malicious exe- cutable is halted or deleted. | Data Integrity DR-4 | | CR 4.k | | Suspicious network traffic is detected, and denylist is up- dated. | Data Integrity DR-4 | | CR 5 | The DI example imple- mentation shall detect and respond to changes to the database made through a web server vulnerability in custom code. | | Data Integrity DR-5 | | CR 5.a | | Database integrity changes are col- lected and logged. | Data Integrity DR-5 | | CR 5.b | | Information about the client interact- ing with the web service is collected and logged.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events."}]}
{"id": "nist_01369", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-4 in Security and Privacy Controls for Information Systems and Organizations? (Part 2) Control CM-4: nesses, incompatibility, or intentional malice. Discussion: A separate test environment requires an environment that is physically or logically separate and distinct from the operational environment. The separation is sufficient to ensure that activities in the test environment do not impact activities in the operational environment and that information in the operational environment is not inadvertently transmitted to the test environment. Separate environments can be achieved by physical or logical means. If physically separate test environments are not implemented, organizations determine the strength of mechanism required when implementing logical separation. Related Controls: SA-11, SC-7. (2) IMPACT ANALYSES | VERIFICATION OF CONTROLS CHAPTER THREE PAGE 101 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ After system changes, verify that the impacted controls are implemented correctly, operating as intended, and producing the desired outcome with regard to meeting the security and privacy requirements for the system. Discussion: Implementation in this context refers to installing changed code in the operational system that may have an impact on security or privacy controls. Related Controls: SA-11, SC-3, SI-6. References: [SP 800-128].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01370", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Integrating Forensic Techniques into Incident Response provide? (Section 17) | Application Layer........................................................................................ | 6-2 | | | 6.1.2 | Transport Layer.......................................................................................... | 6-2 | | | 6.1.3 | IP Layer ..................................................................................................... | 6-3 | | | 6.1.4 | Hardware Layer..........................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Integrating Forensic Techniques into Incident Response."}]}
{"id": "nist_01371", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6.1 Generation-Encryption Process according to NIST Recommendation for Block Cipher Modes of Operation_ the CCM Mode for Authentication and Confidentiality According to Recommendation for Block Cipher Modes of Operation_ the CCM Mode for Authentication and Confidentiality, 6.1 Generation-Encryption Process: The following is a specification of the generation-encryption process of CCM: Prerequisites: block cipher algorithm; key K ; counter generation function; formatting function; MAC length Tlen . Input : valid nonce N ; valid payload P of length Plen bits; valid associated data A ; Output : ciphertext C.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Block Cipher Modes of Operation_ the CCM Mode for Authentication and Confidentiality."}]}
{"id": "nist_01372", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters provide? (Section 10) | 33 | | 4.1 | Overview................................................................................33 | Overview................................................................................33 | | | 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....................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters."}]}
{"id": "nist_01373", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Guide to Integrating Forensic Techniques into Incident Response? (Part 9) Control HA-1: yption often presents challenges for analysts. Users might encrypt individual files, folders, volumes, or partitions so that others cannot access their contents without a decryption key or passphrase. 51 The encryption might be performed by the OS or a third-party program. Although it is relatively easy to identify an encrypted file, it is usually not so easy to decrypt it. The analyst might be able to identify the encryption method by examining the file header, identifying encryption programs installed on the system, or finding encryption keys (which are often stored on other media). Once the encryption method is known, the analyst can better determine the feasibility of decrypting the file. In many cases, it is not possible to decrypt files because the encryption method is strong and the authentication (e.g., passphrase) used to perform decryption is unavailable. Although an analyst can detect the presence of encrypted data rather easily, the use of steganography is more difficult to detect. Steganography , also known as steg , is the embedding of data within other data. Digital watermarks and the hiding of words and information within images are examples of steganography. Some techniques an analyst can use to locate stegged data include looking for multiple versions of the same image, identifying the presence of grayscale images, searching metadata and registries, using histograms, and using hash sets to search for known steganography software. Once certain that stegged data exists, analysts might be able to extract the embedded data by determining what software created the data and then finding the stego key, or by using brute force and cryptographic attacks to determine a password. 52 However, such efforts are often unsuccessful and can be extremely timeconsuming, particularly if the analyst does not find the presence of known steganography software on the media being reviewed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Integrating Forensic Techniques into Incident Response."}]}
{"id": "nist_01374", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Appendix H according to NIST A Study of Federal Agency Needs for Information Technology Security According to A Study of Federal Agency Needs for Information Technology Security, Appendix H: federal managers to share information, build upon the experience of other agencies, and avoid duplication of effort. The forum promotes broad dissemination of useful computer security materials within the federal government in a timely manner.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of Federal Agency Needs for Information Technology Security."}]}
{"id": "nist_01375", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information say about 2.5. The Importance of Phishing Resistance? (Part 1) According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information, 2.5. The Importance of Phishing Resistance: 2.5. The Importance of Phishing Resistance All MFA has security benefits compared to using a single factor, but not all forms of MFA are created equal, even if they are at the same AAL. One important differentiator among various types of MFA is the ability for the authenticator to resist phishing attacks. Phishing attacks attempt to lure a user (usually through an email) into interacting with a counterfeit webpage or application and trick the user into revealing information (typically passwords or one-time codes) that can be used to masquerade as that user to the real web page or application. See Fig. 4 for an example of how a phishing attack occurs. <!-- image --> Fig. 4. An example of a phishing attack. <!-- image --> Tip: Not all authenticators are phishing resistant, but phishing-resistant MFA solutions are now commonly supported by identity platforms. Commercially, Fast Identity Online (FIDO) authenticators paired with the World Wide Web Consortium's ( W3C) Web Authentication API are the most widely available phishing-resistant authenticators. Agencies should ask vendors what phishing-resistant authentication options they support, to include support for phishingresistant, syncable authenticators as described in NIST 800-63B-4 [4]. Phishing attacks are a significant cybersecurity challenge, as they are often conducted remotely and at scale, meaning that an attacker may send a phishing email to thousands of employees, needing only to trick a single employee into providing their login information to gain unauthorized access to data and/or applications. Phishing-resistant authentication systems do not require the user to recognize an attack and make the right decision, but rather have phishing resistance built into the authentication protocol itself. NIST published a blog post on phishing-resistant authenticators and how they mitigate common attacks [5].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, mfa. Contains security framework guidance for authentication systems. Source: Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information."}]}
{"id": "nist_01376", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT) say about 8.8 Physical Security? According to Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT), 8.8 Physical Security: IoT components may be in remote and unattended locations where physical access is almost unrestricted. Due to their cost model, very low cost IoT components cannot be protected by physically hardening the component or by adding anti-tampering features. Where physical access can be controlled, there are sector specific and generic standards available, such as the six-part ISO/IEC TS 22237 for data center facilities and infrastructures and Security Industry Association (SIA) Open Supervised Device Protocol (OSDP) v2.1.7 for interoperability among access control and security products.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_01377", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 317) al mission and business functions despite disruption, compromise, or failure in organizational systems. Related Controls: CP-2, CP-6, CP-8, CP-9, CP-10, MA-6, PE-3, PE-11, PE-12, PE-17, SC-36, SI-13. Control Enhancements: (1) ALTERNATE PROCESSING SITE | SEPARATION FROM PRIMARY SITE Identify an alternate processing site that is sufficiently separated from the primary processing site to reduce susceptibility to the same threats. Discussion: Threats that affect alternate processing sites are defined in organizational assessments of risk and include natural disasters, structural failures, hostile attacks, and errors of omission or commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate processing sites based on the types of threats that are of concern. For threats such as hostile attacks, the degree of separation between sites is less relevant. Related Controls: RA-3. (2) ALTERNATE PROCESSING SITE | ACCESSIBILITY Identify potential accessibility problems to alternate processing sites in the event of an area-wide disruption or disaster and outlines explicit mitigation actions. Discussion: Area-wide disruptions refer to those types of disruptions that are broad in geographic scope with such determinations made by organizations based on organizational assessments of risk. Related Controls: RA-3. (3) ALTERNATE PROCESSING SITE | PRIORITY OF SERVICE Develop alternate processing site agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives). Discussion: Priority of service agreements refer to negotiated agreements with service providers that ensure that organizations receive priority treatment consistent with their availability requirements and the availability of information resources for logical alternate processing and/or at the physical alternate processing site.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01378", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST_SP_800-37r2_Risk_Management_Framework say about Acknowledgements? According to NIST_SP_800-37r2_Risk_Management_Framework, Acknowledgements: This publication was developed by the Joint Task Force Interagency Working Group. The group includes representatives from the Civil, Defense, and Intelligence Communities. The National Institute of Standards and Technology wishes to acknowledge and thank the senior leaders from the Departments of Commerce and Defense, the Office of the Director of National Intelligence, the Committee on National Security Systems, and the members of the interagency working group whose dedicated efforts contributed significantly to the publication.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_01379", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DS-3 in Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches? (Part 28) Control DS-3: . In this build, Duo offers a variety of authentication options, such as a hardware-based authenticator. Organizations should audit tools to deter- mine what information they are using and collecting. Disassociability: Organizations should ex- plore capabilities and configurations that allow for the de-identification of phone numbers and other personal information, such as the capability to replace a phone- number with placeholder text or privacy- enhancing cryptographic techniques to limit the tracking of users. | ## 5.3.2 Authentication to Virtual Desktop Interface Solution The reference architecture in this document demonstrates a Virtual Desktop Interface (VDI) solution to facilitate secure access to organizational resources and data. Organizations may allow users' personal devices to access corporate resources using the VDI solution. Organizations should consider the privacy risk of installing VDI software on personally owned devices, information revealed by the VDI protocol, and monitoring of user activity while in the virtual environment. Figure 5-2 Virtual Desktop Interface Data Flow Diagram <!-- image --> Table 5-10 Virtual Desktop Interface Data Actions | Data Type | Data Action | Privacy Impact | |----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------| | Username | The username is stored by the user workstation and active directory. It is transferred as part of the authentication pro- cess.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches."}]}
{"id": "nist_01380", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 293) . \uf0b7 Local autonomy: All authentication processes between devices, or between users and devices will be able to operate even if a centralized service over a network is not available at any given time. For example, this is to ensure that if a network connection in a substation becomes unavailable, but a critical operation needs to be accomplished by local personnel, they would not in any way be inhibited from doing so. \uf0b7 Revocation management: The ability to revoke credentials in a system in an ordered manner that ensures that all affected devices and users are notified and can take appropriate actions and adjustments to their configurations. Examples can include handling revoked PKI certificates and ensuring that entities with revoked certificates cannot be authenticated to protected services and functions. \uf0b7 Key material provisioning: The processes and methods used to securely enter key material initially into components and devices of a system, as well as changing key materials during their operation. \uf0b7 Key material destruction: The secure disposal of all key material after its intended use and lifetime, for example, the zeriozation/erasure of CSPs. Making key material unavailable is an acceptable alternative for systems where destruction is not possible. \uf0b7 Credential span of control: The number of organizations, domains, systems or entities controlled or controllable through the use of the key material associated with the credential. This does not explicitly address keys used for purposes other than control nor 241 include asymmetric keys that are indirectly used for control, such as those associated with root or intermediate certification authorities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, sso. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01381", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? (Part 33) Control HA-1: the Issuer at the Origin, and it doesn't have to be understood by the AC verifier at the Target site. See section 6 for a fuller discussion of this issue. trust for the access control decision making. When the PERMIS PDP is initialised, it is given the name of the trusted authority, and the ID of the policy to use (each policy has a globally unique identifier). PERMIS reads in the policy certificates from the authority's LDAP entry, checks their signatures, and keeps the one with the correct ID. It now has the correct trusted policy with which to make access control decisions. PERMIS thus forms a good basis for demonstrating the distributed management of trust with Shibboleth. ## 4.1 The PERMIS PDP Policy The PERMIS policy contains a list of trusted attribute authorities, the set of attributes they are trusted to assign, and the groups of users they can be assigned to. This is called the role allocation sub-policy (RAP). Attribute authorities can be distributed worldwide, and can be trusted to issue ACs to users from any domain, according to the RAP. When the PERMIS PDP is passed a set of attribute certificates by Shibboleth, it can determine from the RAP which are trusted to keep, and which should be discarded as untrusted. All the trusted attributes are extracted and stored for later access control decision making. The PERMIS policy also contains the set of targets that are being protected by this policy, the associated actions that can be performed on them (along with their parameters), and the attributes (or roles) that a user needs in order to be granted the access. In addition, constraints can be placed on these grants, such as, only between 9am and 5pm, or only if the user holds nonconflicting roles 3 , or only if the size is less than 3Mbytes etc. This is called the target access sub-policy (TAP).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, pki, sso. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_01382", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Federal S_MIME V3 Client Profile? (Part 8) Control HA-1: eiving Signed and Encrypted Messages | ........................................................... 9 | | 2.3.5 | Processing Return Receipts..................................................................................... | 9 | | 2.4 Certificate Processing ..................................................................................................... | 2.4 Certificate Processing ..................................................................................................... | 9 | | 2.4.1 | X.509 Certificate Processing .................................................................................. | 9 | | 2.4.2 | X.509 CRL Processing............................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Federal S_MIME V3 Client Profile."}]}
{"id": "nist_01383", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ST-1 in National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook? (Part 2) Control ST-1: 3. AVAILABILITY T ORDER FROM NATIONAL TECHNICAL INFORMATION SERVICE (NTIS), SPRINGFIELD,VA 22161. UNUMITED FOR OFFICIAL DISTRIBUTION. DO NOT RELEASE TO NATIONAL TECHNICAL INFORMATION SERVICE (NTIS). ORDER FROM SUPERINTENDENT OF DOCUMENTS, U.S. GOVERNMENT PRINTING OFFICE, WASHINGTON, DC 20402. 14. NUMBER OF PRINTED PAGES 106 15. PRICE A06", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook."}]}
{"id": "nist_01384", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i provide? (Section 155) to achieve this requirement is EAP-TLS with certificates on PIN or password-protected smart cards. Another approach is PEAP or EAP-TTLS with Generic Token Card (GTC) or possibly a biometric solution. | EAP authentication methods such as EAP-TLS, EAP-TTLS, EAP-FAST, and PEAP use certificates to authenticate the AS to the STA. One potential pitfall to this approach is that it enables an adversary to impersonate the WLAN infrastructure if that adversary can present a valid certificate, and if WLAN clients are not configured properly. It is common for a WLAN client to be configured by default to accept certificates signed by any certification authority (CA) for which it has a corresponding CA certificate. In most cases, a variety of third-party CA certificates are already installed on the client. This allows an attacker to impersonate the WLAN infrastructure successfully with an SSID and a valid certificate signed by any of the third-party CAs that the client recognizes. Once the attacker has tricked the client into associating with the bogus AP, it might be able to capture the authentication credentials needed to access the real infrastructure. In this scenario, the security of the RSN is circumvented simply as a result of having multiple CA certificates on the STA, which is a common configuration on many computers. To prevent this situation, STAs should be configured to authenticate to specific servers only, not just any server with a valid certificate. Ideally, servers should be identified by their fully qualified domain name (e.g., as1.xyzAgency.gov) so that the name listed in the AS's certificate can be compared with the name specified in the STA's configuration. STAs should also be configured to accept certificates only from the CA that signed the server certificates. With these two controls in place, the attacker would either have to breach the CA or get it to provide it a certificate with the same name as the authentication server.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token, sso. Contains security framework guidance for authentication systems. Source: Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i."}]}
{"id": "nist_01385", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Threat Analysis on UOCAVA Voting Systems provide? (Section 121) fficial offices have too few resources (e.g. bandwidth, servers) to handle legitimate traffic. Election official offices have too few resources (e.g., bandwidth, servers) to handle legitimate traffic. | Network Operators Election Officials Network Operators Election Officials | Low Low | High High | Avail-High Avail-High | IR-4, IR-5 IR-4, IR-5 | | Sensitive personal information or ballot selections are intercepted between the voter and election official on the Internet. Sensitive personal information or ballot selections are intercepted between the voter and election official on the Internet. | Hostile Organizations Network Operators Hostile Organizations Network Operators | High High | Low Low | Confid.-Mod Confid.-Mod | PE-4, SC-9, SC-12, SC-13 PE-4, SC-9, SC-12, SC-13 | | Voted ballots are modified while being transmitted to the election official (e.g. on e-mail servers) Voted ballots are modified while being transmitted to the election official (e.g.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Threat Analysis on UOCAVA Voting Systems."}]}
{"id": "nist_01386", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to Computer Security Division 2015 Annual Report? http: //www.nist.gov/itl/csd/biometrics/biocta\\_download. cfm", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2015 Annual Report."}]}
{"id": "nist_01387", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Secure Biometric Match-on-Card Feasibility Report provide? (Section 44) ecurity objectives without reader-to-smart-card authentication or associated key management infrastructure. These security objectives are aligned with the high-level security objectives of FIPS 201-1. They protect both the integrity of the biometric authentication transaction and the privacy of the cardholder's biometric data, while avoiding the potential cost of reader authentication key management. The Device Under Test (DUT) shall be a smart card having ISO/IEC 7810 physical and mechanical characteristics. The Device Under test shall be capable of contact (via ISO/IEC 7816-3 methods, consistent with NIST SP800-73-1) and contactless (via ISO/IEC 14443 methods, consistent with NIST SP800-73-1). Preferably, the DUT is listed on the General Services Administration (GSA) HSPD-12 Approved Product List, and modified only by the addition of BMOC firmware. The DUT may also be a type of smart card not on the GSA Approved Product List (APL). In this case, NIST will determine if the DUT could host a PIV card-application at reasonable development cost, and if so, the DUT will be tested. The DUT may not have an NPIVP or a Cryptographic Module Validation Program (CMVP) certificate. In this case, NIST will determine if the DUT could pass NPIVP and CMVP testing at reasonable development cost, and if so, the DUT will be tested. The DUT should perform a Biometric Match-On-Card authentication transaction and meet the security objectives described in Section D.2. The biometric matching algorithm on the DUT should demonstrate accuracy meeting the criteria of SP800-76-1 Section 8.10 by testing in either the NIST MINEX II or Ongoing MINEX activity. (Note: accuracy testing may run concurrently with performance and security testing.) The fingerprint sample template sent from the reader to the DUT should be represented following either ISO 19794-2 finger minutiae card or ANSI 378 format. Any extensions or options must be fully documented in the submitted protocol documentation.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: Secure Biometric Match-on-Card Feasibility Report."}]}
{"id": "nist_01388", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Understanding Stablecoin Technology and Related Security Considerations say about Table of Contents? (Part 6) According to Understanding Stablecoin Technology and Related Security Considerations, Table of Contents: | Insufficient Reserves.................................................................................................37 | | | 7.1.2. | Reserve Type Mismatch ...........................................................................................38 | | | | Stablecoin Manager Actions........................................................................................38 | | | 7.2.1. | Account Denylisting | ..................................................................................................38 | | 7.2.2. | Managing Organization Dissolution ..........................................................................38 | | | 7.2.3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Understanding Stablecoin Technology and Related Security Considerations."}]}
{"id": "nist_01389", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to NIST Test Personal Identity Verification (PIV) Cards Version 2? http: //smime2.nist.gov/PIVTest2/RSA2048IssuingCA.crl", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_01390", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Information Security Handbook_ A Guide for Managers? (Part 135) Control PD-12: ystem resources. All federal systems have some level of sensitivity and require protection as part of good management practice. The protection of a system must be documented in a system security plan. The completion of system security plans is a requirement of the OMB Circular A-130, Management of Federal Information Resources, Appendix III, Security of Federal Automated Information Resources , and Title III of the E-Government Act, FISMA. For the plans to adequately reflect the protection of the resources, a senior management official must authorize a system to process information or operate. This authorization provides an important quality control. By authorizing processing in a system, the manager accepts its associated risk. Management authorization should be based on an assessment of management, operational, and technical controls. Since the system security plan establishes and documents the security controls, it should form the basis for the authorization, supplemented by the assessment report and the POA&amp;Ms. In addition, a periodic review of controls should also contribute to future authorizations. Reauthorization should occur prior to a significant change in processing, but at least every three years. ------------------------------------------------- ## Website: www.csrc.nist.gov ## References: Public Law 107-347 [H.R. 2458], The E-Government Act of 2002, Title III of this Act is the Federal Information Security Management Act of 2002 (FISMA) , December 17, 2002. Office of Management and Budget Circular A-130, Management of Federal Information Resources , November 2000. Federal Information Processing Standard 199, Standards for Security Categorization of Federal Information and Information Systems , February 2004. Federal Information Processing Standard 200 , Minimum Security Requirements for Federal Information and Information Systems, March 2006.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_01391", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EN-18 in Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007? (Part 97) Control EN-18: | 3 | | 14.012- ConfirmedBPX | 19.1.12 | Field 14.012 shall contain the number of bits used to represent a pixel. | 2 | M | 14.012-JPEGB- JPEGL-CBPX | {14.012} EQ {BPX} | 3 | | 14.012- ConfirmedBPX | 19.1.12 | Field 14.012 shall contain the number of bits used to represent a pixel. | 2 | M | 14.012-JP2-JP2L- CBPX | IF {4 th parameter of Image Header box} NEQ '255', THEN {14.012} EQ {BPX} | 3 | | 14.012- ConfirmedBPX | 19.1.12 | Field 14.012 shall contain the number of bits used to represent a pixel. | 2 | M | 14.012-PNG-CBPX | {14.012} EQ {BPX} | 3 | | 14.012- ConfirmedBPX | 19.1.12 | Field 14.012 shall contain the number of bits used to represent a pixel. | 2 | M | 14.012-WSQ-CBPX | No Implementation | 4 | | Table_12_Subfields | 19.1.13 | The field value shall be selected from Table 12.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007."}]}
{"id": "nist_01392", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Government Smart Card Interoperability Specification, Version 2.1? (Part 46) Control HA-1: eter shall be in ASCII hexadecimal format. unAIDLen: AID value length in bytes. TagArray: An array containing the list of tags for the selected container. ## punNbTags: Number of tags in TagArray . Return Codes: ``` BSI_OK BSI_BAD_HANDLE BSI_SC_LOCKED BSI_BAD_AID BSI_BAD_PARAM BSI_CARD_REMOVED BSI_NO_CARDSERVICE BSI_ACCESS_DENIED BSI_INSUFFICIENT_BUFFER BSI_UNKNOWN_ERROR ``` ## Discovery Mode: Parameters: hCard: Card connection handle from gscBsiUtilConnect (). uszAID: Target container AID value. unAIDLen: AID value length in bytes. TagArray: Set to NULL. punNbTags: Number of tags which would be contained in a resulting TagArray . Return Codes: ``` BSI_OK BSI_BAD_HANDLE BSI_SC_LOCKED BSI_BAD_AID BSI_BAD_PARAM BSI_CARD_REMOVED BSI_NO_CARDSERVICE BSI_ACCESS_DENIED BSI_UNKNOWN_ERROR ``` ## E.5.5 gscBsiGcReadValue() Purpose: Returns the Value associated with the specified Tag. ``` Prototype: ``` Parameters: Return Codes: ## Discovery Mode: Parameters: hCard: Card connection handle from gscBsiUtilConnect (). uszAID: Target container AID value. unAIDLen: AID value length in bytes. ``` unsigned long IN UTILCardHandle IN unsigned char * IN unsigned long IN GCtag INOUT unsigned char * INOUT unsigned long * ); gscBsiGcReadValue ( hCard , uszAID , unAIDLen , ucTag , uszValue , punValueLen ``` hCard: uszAID: unAIDLen: ucTag: uszValue: Card connection handle from gscBsiUtilConnect() . Target container AID value. The parameter shall be in ASCII hexadecimal format. AID value length in bytes. Tag value of data item to read. Value associated with the specified tag. The caller must allocate the buffer. punValueLen: Size of the buffer allocated by the caller to hold the returned Value (input). Size of the Value returned (output).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_01393", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Required Test Procedures: according to NIST Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements According to Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements, Required Test Procedures:: SCAP.T.3010.1: The tester SHALL import a known valid XCCDF component content without &lt;xccdf:Profile&gt; elements that is part of SCAP data streams for the target platform into the vendor product and execute it according to the product operation instructions provided by the vendor. The tester will inspect the product output ensuring XCCDF components are compliant with the XCCDF specification. SCAP.T.3010.2: The tester SHALL validate the resulting XCCDF component results within an SCAP result data stream output using the SCAPVal utility. This validation MUST NOT produce any validation errors. SCAP.T.3010.3: The tester SHALL compare the product results to the expected results ensuring that all the results match the expected results. SCAP.R.3100: For all CCE IDs in the SCAP source data stream, the product SHALL correctly display the CCE ID with its associated XCCDF Rule in the product output. SCAP Capability: \uf0fe ACS \uf0a8 CVE \uf0a8 OCIL Required Vendor Information: SCAP.V.3100.1: The vendor SHALL provide instructions on where the XCCDF Rules and their associated CCE IDs can be visually inspected within the product output.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements."}]}
{"id": "nist_01394", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-1 in Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers? (Part 55) Control CM-1: | Description | Show that the MFA example implementation can determine that a purchase is lower risk and therefore does not require additional U2F authentication. | | Associated Test Cases | CR 1 | | Associated Cybersecurity Framework Subcategories | ID.RA-4, ID.RA-5, PR.AC-7 | | Preconditions | (CR 1.a) RSA, StrongKey, and Magento capabilities are implemented and operational in the lab environment. Yubico FIDO U2F authenticator is registered to a purchaser account on the e-commerce platform. The purchase dollar-amount threshold has been set to determine when U2F authentication is activated. | | Procedure | The returning purchaser logs into the e-commerce platform's website with their customer ID and password and initiates and completes a lower-risk purchase that does not require U2F use by the returning purchaser. | | Expected Results | (CR 1) The MFA example implementation determines that U2F authentication is not needed. (CR 1.a) U2F authentication with Yubico (CR 1.a.1) is not activated because the purchase dollar-amount is below the set threshold.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, mfa, sso. Contains security framework guidance for authentication systems. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_01395", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1 say about 1.3. Summary of Changes since Version 1.0? (Part 1) According to Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1, 1.3. Summary of Changes since Version 1.0: 1.3. Summary of Changes since Version 1.0 XCCDF 1.0 received some review and critique after its release in January 2005. Most of the additions and changes in 1.1 come directly from suggestions by users and potential users. The list below gives the major changes; other differences are noted in the text. - Persistent/standard identifiers - To foster standardization and re-use of XCCDF rules, community members suggested that Rule objects bear long-term, globally unique identifiers. Support for identifiers, along with the scheme or organizations which assigns them, is now part of the Rule object. - Versioning - To foster re-use of XCCDF rules, and to allow more precise tracking of benchmark results over time, Benchmarks, Rules, and Profiles all support a version number. The version number now supports a timestamp, too. - Severity - Rules can not support a severity level: info, low, medium, and high. Severity levels can be adjusted via Profiles. - Signatures - Each object that can be a standalone XCCDF documents can have an XML digital signature: Benchmark, Group, Rule, Value, Profile, and TestResult. - Rule result enhancements - Added the override property for rule-result members of the TestResult object. Clarified the use of different rule result status values in scoring, and added several new rule result status values. Added better instance details, for multiply-instantiated rules. - Enhancements for remediation - Added several minor enhancements to the Rule's properties for automated and interactive remediation (fix and fixtext elements). - Interactive Value tailoring - Added the 'interactive' property to Value objects; it gives a benchmark checking tool a hint that it should solicit a new value prior to each application of the benchmark. Added the 'interfaceHint' property to allow the author to suggest a UI model to the tool. - Scoring models - Added the notion of multiple scoring models and described two new models.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1."}]}
{"id": "nist_01396", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2015 Annual Report say about Conference Papers? (Part 1) According to Computer Security Division 2015 Annual Report, Conference Papers: Conference Papers J. Boyar and M. Find, 'Constructive Relationships Between Algebraic Thickness and Normality,' 20th International 1 0 2 Symposium on Fundamentals of Computation Theory (FCT 2015), Gda\u0144sk, Poland, August 17-19, 2015. In Lecture Notes in Computer Science 9210, Fundamentals of Computation Theory, A. Kosowski and I. Walukiewicz, eds., Berlin: Springer International, 2015, pp. 106-117. doi: 10.1007/978-3-319-22177-9\\_9. We study the relationship between two measures of Boolean functions; 'algebraic thickness' and 'normality'. For a function f , the algebraic thickness is a variant of the 'sparsity', the number of nonzero coefficients in the unique F 2 polynomial representing f , and the normality is the largest dimension of an affine subspace on which f is constant. We show that for 0 &lt; \u03b5 &lt; 2, any function with algebraic thickness n 3\u03b5 is constant on some affine subspace of dimension \u03a9( n \u03b5 /2 ) . Furthermore, we give an algorithm for finding such a subspace. This is at most a factor of \u0398( \u221a n ) from the best guaranteed, and when restricted to the technique used, is at most a factor of \u0398( \u221a logn ) from the best guaranteed. We also show that a concrete function, majority, has algebraic thickness \u03a9( 2 n 1/6 ) . R. Chandramouli, 'Analysis of Network Segmentation Techniques in Cloud Data Centers,' 2015 International Conference on Grid &amp; Cloud Computing and Applications (GCA '15), Las Vegas, Nevada, United States, July 27-30, 2015, pp. 64-70. Cloud Data centers are predominantly made up of Virtualized hosts. The networking infrastructure in a cloud (virtualized) data center, therefore, consists of the combination of a physical IP network (data center fabric) and the virtual network residing in virtualized hosts.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2015 Annual Report."}]}
{"id": "nist_01397", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cryptographic Key Management Workshop Summary -- June 8-9, 2009 say about 4. Summary of Comments Received Subsequent to Workshop? (Part 1) According to Cryptographic Key Management Workshop Summary -- June 8-9, 2009, 4. Summary of Comments Received Subsequent to Workshop: 4. Summary of Comments Received Subsequent to Workshop NIST created an Email address and a WebLog 6 (Blog) to facilitate discussion among participants regarding cryptographic key management subsequent to the workshop and to disseminate new information to the workshop participants and other interested parties. Five initial questions (A through E) were posted on the blog in order to initiate discussion. Each question had multiple sub-questions. This is a summary of the comments or responses received from the public. Question A dealt with leap-ahead technologies. A comment was received from Stephen Lange Ranzini who thought that an on-demand Federated Identity Management System, based on the Liberty Alliance's Identity Assurance Framework, would enable a leap-ahead in securing cyberspace. He believes that this would be a major improvement in both security and ease of use over the existing user name and password systems. The Federated system would not require multiple one-time password tokens. Mr. Ranzini feels that banks are best equipped to provide this single sign-on service, and notes that strong security across the Internet for users is identified in various Federal Government cybersecurity strategy documents as one of the top hard problems that need to be addressed. Question B asked 'What constitutes a key management framework? Mike Markowitz responded to a comment by Santosh Chokhani who stated that the security of keys 'can be ensured using standards, such as FIPS 140-2.' Mr. Markowitz quoted a portion of FIPS 140-2 that states that 'conformance to this standard is not sufficient to ensure that a particular module is secure.' He feels that there is a perception that standards accomplish much more than they actually do. Mr. Markowitz proposed that a Question F be posted that asks 'What can we expect to accomplish with a KM standard?' As a result, Question F was posted.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: identity management, key management, token. Contains security framework guidance for authentication systems. Source: Cryptographic Key Management Workshop Summary -- June 8-9, 2009."}]}
{"id": "nist_01398", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT) provide? (Section 115) device manufacturers and security vendors may need to develop device-specific agents and interfaces for monitoring until the standards are tailored for the various IoT use cases and implemented in products; - \uf0a7 Software Assurance: standards for avoiding vulnerabilities in software should be investigated (e.g., malware; integration of best practices for software development into standards for IoT contributing disciplines); - \uf0a7 Supply Chain Risk Management (SCRM): generic standards (e.g., ISO/IEC 27036) are not specific to IoT and should be reviewed to determine if they are sufficient or require revision for IoT systems; and - \uf0a7 System Security Engineering: generic system security engineering standards (e.g., ISO/IEC 15026) should be reviewed for application to IoT systems.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_01399", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ID-19 in Securing Telehealth Remote Patient Monitoring Ecosystem? (Part 17) Control ID-19: ...............................................................................................41 | | | 4.2.2 | Broadband Pathways..................................................................................................42 | | 4.3 | Data and Process Flows...............................................................................................43 | Data and Process Flows...............................................................................................43 | | 4.4 | Security Capabilities ....................................................................................................46 | Security Capabilities ....................................................................................................46 | | | 4.4.1 | Telehealth Platform Provider......................................................................................47 | | | 4.4.2 | Identity Management, Authentication, and Access Control ......................................48 | | | 4.4.3 Data Security...............................................................................................................50 | 4.4.3 Data Security...............................................................................................................50 | | | 4.4.4 Anomalies and Events and Security Continuous Monitoring .....................................50 | 4.4.4 Anomalies and Events and Security Continuous Monitoring .....................................50 | |---------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 5 | 4.5 | Final Architecture ........................................................................................................50 | | | Security and Privacy Characteristic Analysis ......................................51 | Security and Privacy Characteristic Analysis ......................................51 | | | 5.1 | Assumptions and Limitations ......................................................................................52 | | | 5.2 | Pervasive Controls.......................................................................................................52 | | | 5.3 | Telehealth Platform Providers ....................................................................................53 | | | 5.4 | Risk Assessment (ID.RA and ID.RA-P)..........................................................................54 | | | 5.5 | Identity Management, Authentication, and Access Control (PR.AC and PR.AC-P) Protective Technology (PR.PT-P).................................................................................54 | | | 5.6 | Data Security (PR.DS and PR.DS-P)..............................................................................56 | | | 5.7 | Anomalies and Events, Security Continuous Monitoring (DE.AE, DE.CM), and Data Processing Management (CT.DM-P) ...........................................................................56 | | 6 | Functional Evaluation........................................................................57 | Functional Evaluation........................................................................57", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, identity management. Contains security framework guidance for authentication systems. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_01400", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance say about Map Data Flows? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance, Map Data Flows: Data flow diagrams enable a manufacturer to understand the flow of data between networked components of the manufacturing system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance."}]}
{"id": "nist_01401", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3. On-Card Cryptographic Requirements according to NIST Cryptographic Algorithms and Key Sizes for Personal Identity Verification According to Cryptographic Algorithms and Key Sizes for Personal Identity Verification, 3. On-Card Cryptographic Requirements: FIPS 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cryptographic Algorithms and Key Sizes for Personal Identity Verification."}]}
{"id": "nist_01402", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Overview and Considerations of Access Control Based on Attribute Encryption say about 4.2. Key-Policy Attribute-Based Encryption? (Part 2) According to Overview and Considerations of Access Control Based on Attribute Encryption, 4.2. Key-Policy Attribute-Based Encryption: ey PK to the data owner. 4. Data owners generate ciphertext for the data (i.e., message) based on the applied attribute set and public key PK and then upload the data to the data resource provider. 5. The requester retrieves and decrypts ciphertext from the data source provider using their secret key SKx and attributes associated with the access structure. Fig. 5. Basic process steps of KP-ABE scheme <!-- image --> In general, the size of the public key of KP-ABE is linear to the total number of applied attribute sets. That is, the public key size is linear to the maximum number of attributes effectively used in encryption. However, it can be a fixed size in a random oracle large universe construction with hash function [GOLIC]. Using the example in Fig. 4 , instead of a policy structure of data, it now represents an attribute structure of a data requester. The following demonstrates an example of KP-ABE's algorithms of setup, encryption, key generation, and decryption functions.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Overview and Considerations of Access Control Based on Attribute Encryption."}]}
{"id": "nist_01403", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Authority Information Access : according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Authority Information Access :: CA Issuers - IIssuingCA.p7c CA Issuers - ldap://smime2.nist.gov/cn=Test%20PIV-I%20RSA%202048- bit%20CA%20for%20Test%20PIV%20Cards%20v2,ou=Test%20CA,o=Test%20Certificat es%202020,c=US?cACertificate;binary,crossCertificatePair;binary OCSP - ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_01404", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.1 About the Package according to NIST A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications According to A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications, 5.1 About the Package: This toolbox was specifically designed for individuals interested in conducting statistical testing of cryptographic (P)RNGs. Several implementations of PRNGs utilized during the development phase of the project have also been included. This package will address the problem of evaluating (P)RNGs for randomness. It will be useful in: - identifying (P)RNGs which produce weak (or patterned) binary sequences, - designing new (P)RNGs, - verifying that the implementations of (P)RNGs are correct, - studying (P)RNGs described in standards, and - investigating the degree of randomness by currently used (P)RNGs. The objectives during the development of the NIST statistical test suite included: - Platform Independence: The source code was written in ANSI C. However, some modification may have to be made, depending on the target platform and the compiler. - Flexibility: The user may freely introduce their own math software routines. - Extensibility: New statistical tests can easily be incorporated. - Versatility: The test suite is useful in performing tests for PRNGs, RNGs and cipher algorithms. - Portability: With minor modifications, source code may be ported to different platforms. The NIST source code was ported to a Windows XP system running Visual Studio 2005 compiler and a Ubuntu Linux system running gcc. - Orthogonality: A diverse set of tests is provided. - Efficiency: Linear time or space algorithms were utilized whenever possible.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications."}]}
{"id": "nist_01405", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations according to NIST Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations According to Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations, Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations: Kelley Dempsey Nirali Shah Chawla Arnold Johnson Ronald Johnston Alicia Clay Jones Angela Orebaugh Matthew Scholl Kevin Stine", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, continuous monitoring. General security reference material without sensitive content. Source: Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations."}]}
{"id": "nist_01406", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SC-38 in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? (Part 5) Control SC-38: i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 1 6 0 v 2 r 1 . I NIST SP 800-160, VOL. 2, REV. 1 DEVELOPING CYBER-RESILIENT SYSTEMS _________________________________________________________________________________________________ The consequence model for cyber resiliency encompasses consequences to information and information systems (i.e., a loss of confidentiality, integrity, or availability, as defined in [FIPS 199]). These general consequences can be translated into more specific harms to information and systems that include or are enabled by cyber resources: degraded or disrupted functionality or performance; modified, corrupted, or fabricated information; usurped or misused system resources; or exfiltrated or exposed information. However, the consequence model for cyber resiliency also considers the potential consequences to the missions or business functions supported by the system, to the organization, and sometimes to other stakeholders (e.g., individuals whose personal information may be exfiltrated or exposed, members of the public affected by environmental harms resulting from the failure of a critical infrastructure system). In general, a cyber resiliency solution identified and implemented for a given scope is intended to reduce risks at the next level; for example, implementing a solution at the system level can mitigate risks to mission or business functions. Consequences to a mission or business function or to an organization can be defined in terms of impacts on the performance of required functions or on preserving required properties. The risk model for cyber resiliency, therefore, aligns well with mission risk models [Musman18].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_01407", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain National Institute of Standards and Technology Interagency or Internal Report 8286A 61 pages (November 2021) according to NIST Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management According to Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management, National Institute of Standards and Technology Interagency or Internal Report 8286A 61 pages (November 2021): This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8286A 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. 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 ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management."}]}
{"id": "nist_01408", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control II-4 in 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)? (Part 12) Control II-4: UATION GUIDE - E. OMB BULLETIN 89-17 - F. ABBREVIATIONS AND ACRONYMS - G. APPLICABLE LAWS AND REGULATIONS AS REPORTED BY CSPPs - H. APPLICABLE GUIDANCE AS REPORTED BY CSPPs - I . REFERENCES - J. EXAMPLES OF AGENCY REACTIONS TO CSPP REVIEWS | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| ## I.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)."}]}
{"id": "nist_01409", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines on Active Content and Mobile Code provide? (Section 27) ser and able to interpret such content directly. To keep the browser safe from sources that have varying levels of trust, the program components must take precautions against arbitrary input received. Because these programs are contained within the browser, the browser manufacturer is able to impose security constraints on them. Built-in functionality is also a means for the manufacturer to distinguish its product from others in various ways such as offering proprietary extensions to standard script languages, close integration and interworking with other product offerings, and entirely new content handling capabilities. Built-in functionality should follow an explicit security model to ensure security. For example, enforcing the same origin policy, which prevents content loaded from one 'origin' (i.e., the context defined by host domain name, protocol, and port) from getting or setting properties of a document loaded from a different 'origin,' is a fundamental policy employed by present-day browsers. The implementation of secure JavaScript in Mozilla illustrates the range of considerations involved in defining a security model [Anu98]. The implementation controls access to resources and external interfaces, prevents residual information from being retained and accessible among different contexts operating simultaneously or sequentially, and allows policy, which partitions the name space for access control purposes, to be specified independently of mechanism. Differences can and do exist in the security models used by different browsers. - GLYPH&lt;c=31,font=/BAADDB+Webdings&gt; Components installed to extend the browser functionality. A significant innovation in the design of Web browsers is the ability to extend them beyond their built-in functionality through a defined interface.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Active Content and Mobile Code."}]}
{"id": "nist_01410", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 879) e c v r e S i m e t s y S n o i t a m r o f n I d i r G t r a m S ) A M G S . ( e c n a n e t n a M d n a i t n e m p o e v e D l X X X X X X X X X X X X X X X X 149 ) . C A G S ( l o r t n o C s s e c c A X Architecting for bounded recovery and reaction Architecting Real- time security Calibrating assurance and timeliness trade- offs Legacy system integration Resiliency Management and Decision Support Efficient Composition of Mechanisms Risk Assessment and Management r o w t e N Safe use of g n k COTS/Publicly Available i Smart Grid Security Requirements Families ) R I . G S ( e s n o p s e R t n e d c n I i t n e m e g a n a M t n e m u c o D d n a n o i t a m r o f n I ) D I . G S ( ) P M G S . ( n o i t c e t o r P a d e M i ) . S P G S ( y t i r u c e S l e n n o s r e P y t i r u c e S l a t n e m n o r i v n E d n a ) . E P G S ( l i a c s y h P ) L P G S . ( i l g n n n a P c g e t a r t i S n o i t a z i r o h t u A d n a t n e m s s e s s A y t i r u c e S ) . A C G S ( ) M P G S . ( t n e m e g a n a M m a r g o r P y t i r u c e S ) L P G S . ( i g n n n a P l d n a m e t s y S n o i t a m r o f n I d i r G t r a m S ) . C S G S ( n o i t c e t o r P n o i t a c n u m m o C i d n a m e t s y S n o i t a m r o f n I d i r G t r a m S ) I . S G S ( y t i r g e t n I n o i t a m r o f n I d n a m e t s y S n o i t a m r o f n I d i r G t r a m S ) . A S G S i ( n o i t i s u q c A s e c v r e S i m e t s y S n o i t a m r o f n I d i r G t r a m S ) A M G S . ( e c n a n e t n a M d n a i t n e m p o e v e D l ) . P C G S ( s n o i t a r e p O f o y t i u n i t n o C ) A I . G S ( n o i t a c i t n e h t u A d n a n o i t a c i f i t n e d I X X X X X X X X X X X X X X X ) T A G S . i i ( g n n a r T d n a s s e n e r a w A X ) .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01411", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-6 in Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy? (Part 171) Control AM-6: al Institute of Standards and Technology Federal Information Processing Standards Publication 199, Standards for Security Categorization of Federal Information and Information Systems , February 2004. https://doi.org/10.6028/NIST.FIPS.199 | | [FIPS 200] | National Institute of Standards and Technology Federal Information Processing Standards Publication 200, Minimum Security Requirements for Federal Information and Information Systems , March 2006. https://doi.org/10.6028/NIST.FIPS.200 | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | [SP 800-18] | National Institute of Standards and Technology Special Publication 800-18, Revision 1, Guide for Developing Security Plans for Federal Information Systems , February 2006. https://doi.org/10.6028/NIST.SP.800-18r1 | |----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [SP 800-30] | National Institute of Standards and Technology Special Publication 800-30, Revision 1, Guide for Conducting Risk Assessments , September 2012. | | [SP 800-39] | National Institute of Standards and Technology Special Publication 800-39, Managing Information Security Risk: Organization, Mission, and Information System View , March 2011.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, fips, security control. General security reference material without sensitive content. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_01412", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is URI according to NIST Test Personal Identity Verification (PIV) Cards Version 2? URI: urn:uuid:26092f20-f792-4f7f-94b2-d0923cce6c7a", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_01413", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to Securing Wireless Infusion Pumps in Healthcare Delivery Organizations? http: //nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-124r1.pdf [accessed 2/8/18].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Wireless Infusion Pumps in Healthcare Delivery Organizations."}]}
{"id": "nist_01414", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4 Federal Research in the Area according to NIST Symposium on Federally Funded Research on Cybersecurity of Electric Vehicle Supply Equipment (EVSE) According to Symposium on Federally Funded Research on Cybersecurity of Electric Vehicle Supply Equipment (EVSE), 4 Federal Research in the Area: Six projects, supported by federal dollars, presented their research: - Threat Model of Vehicle Charging Infrastructure (Sandia National Labs) - Enabling Secure and Resilient XFC: A Software/Hardware-Security Co-Design Approach ( Virginia Tech) - Consequence-Driven Cybersecurity for High-Power Charging Infrastructure ( Idaho National Labs) - Cybersecurity for Grid Connected eXtreme Fast Charging (XFC) Station (CyberX) (ABB) 5 National ZEV Investment Plan: Cycle 2 Public Version - February 4, 2019, Electrify America - EVSE Cybersecurity Projects (National Motor Freight Traffic Association/DOT Volpe Center) - Developing a Reference Architecture XFC-Integrated Charging Security Infrastructure Ecosystem ( The Electric Power Research Institute EPRI) The full agenda is included in Appendix A, and presentation slides may be found in Appendix B.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Symposium on Federally Funded Research on Cybersecurity of Electric Vehicle Supply Equipment (EVSE)."}]}
{"id": "nist_01415", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 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 say about UNITED STATES? (Part 4) 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 , UNITED STATES: , federalist system of government which encourages local experimentation and favors state-sponsored solutions. This has resulted in a dispersion of authority to make, interpret, and apply privacy law. See generally Appendix 4. For example, the two-hundred year-old U.S. Constitution (most of its safeguards which apply to the states) demarcates a zone of privacy around the individual by restricting the means by which Government can collect information about individuals and the uses which it can make of such information (see Fourth Amendment restrictions and First Amendment and Equal Protection clause protections) . It also ensures procedural fairness by requiring that individuals be given a fair opportunity to challenge adverse governmental actions against them and scrutinize the factual records upon which they have been based (see Due Process clause safeguards). Privacy safeguards are also found in the \"common law,\" a body of legal rules which originated in historical usages and customs in the British laws given recognition by early U.S. courts, and which is continuously evolving through judicial interpretation. Common-law rules, for example, limit intrusive collection of personal information, penalize unwarranted disclosure of such data, and protect against disclosure of erroneous data about individuals. Responsibility for interpreting and applying these rules lies primarily with state courts Statutory law has played an increasingly important role during the past twenty years in the development of U.S. privacy law. These statutes often build upon existing common-law rules --clarifying, redefining, and sometimes creating new rights - rather than supplanting them, and often also are influenced by constitutional principles. Statutory law and related regulations are primarily responsible for developing the interests of individuals to learn the contents of records about them and to participate in setting conditions for their use.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. 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 ."}]}
{"id": "nist_01416", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Noun according to Recommendation for Random Bit Generator (RBG) Constructions? Noun: The combination of seed material and (optional) personalization string or additional input.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Bit Generator (RBG) Constructions."}]}
{"id": "nist_01417", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Access Control on NoSQL Databases say about 3.2.3. Graph Model? (Part 1) According to Access Control on NoSQL Databases, 3.2.3. Graph Model: 3.2.3. Graph Model Attributes in the graph model can be constructed differently since Graph edges do not necessarily have hierarchical relationships between nodes. Instead, edges connected by nodes may form cyclic relationships rather than a tree structure. As shown in Fig. 9, attributes in a graph database can be described through a sequence of edges and/or nodes without hierarchical relationships. Fig. 9. Example of defining subject and object attributes for a graph model <!-- image --> For example, a subject attribute can be described as user x (node) in (edge) group y (node) works for (edge) company z (node), and an object attribute can be described as file f (node) managed by (edge) department d (node) belongs to (edge) organization o (node). An access control policy based on attributes can then be specified, such as 'the user x in group y who works for company z can read file f managed by department d that belongs to organization o ,' or 'any users in company z can read objects that belong to organization o ' if only applied to attributes without specific subjects or objects. Edges in the graph model are flexible and can be used to implement either an attribute or a permitted action in an access control rule. If implemented as a permitted action, the access control rule can be directly embedded in the database, treating a sequence of links as a rule. In other words, there is no need to store the access control rule outside of the database. An example graph in Fig. 10 contains the following nodes and edges: user x (node) in (edge directed to group y node) can read (edge directed to file y node). Fig. 10.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Access Control on NoSQL Databases."}]}
{"id": "nist_01418", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Common Platform Enumeration_ Name Matching Specification Version 2.3 say about 6.1 Attribute Comparison Relations? (Part 1) According to Common Platform Enumeration_ Name Matching Specification Version 2.3, 6.1 Attribute Comparison Relations: 6.1 Attribute Comparison Relations The first of two CPE name matching phases, the attribute comparison process compares each A-V pair in a source name to its corresponding A-V pair in a target name, matching it to one of the four possible set relations. For example, comparing the source A-V vendor=ANY to the target A-V vendor=\"microsoft\" matches to set relation number 1 in Table 6-1 ( \u2283 ), where the source A-V represents a superset of the target A-V. Table 6-2 enumerates all combinations of CPE WFN A-Vs and defines the set relation for each comparison. The following key describes the attribute value notation for Table 6-2. 1. ANY and NA are logical values as defined in [CPE23-N:5.3.1] 2. i is a wildcard-free attribute-value string, e.g., \"foo\" 3. k is a wildcard-free attribute-value string that is not identical to i, e.g., \"bar\" 4. m + wild cards is an attribute-value string containing a legal combination of unquoted question mark or asterisk wild cards at the beginning and/or the end of the string, e.g., \"*b??\" Table 6-2: Enumeration of Attribute Comparison Set Relations | No.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Platform Enumeration_ Name Matching Specification Version 2.3."}]}
{"id": "nist_01419", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3 say about Appendix H: Bibliography? (Part 13) According to NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3, Appendix H: Bibliography: | | 3389 3390 | [50] | Z. Khayyat et al. , 'BigDansing: A System for Big Data Cleansing,' in Proceedings of the 2015 ACM SIGMOD International Conference on Management of Data SE - SIGMOD '15 , 2015, pp. | | 3391 | | 1215-1230 [Online]. Available: citeulike-article-id:14396286 | |--------|------|--------------------------------------------------------------------------------------------------| | 3392 | [51] | L. A. Pachano, T. M. Khoshgoftaar, and R. Wald, 'Survey of Data Cleansing and Monitoring for | | 3393 | | Large-Scale Battery Backup Installations,' in 2013 12th International Conference on Machine | | 3394 | | Learning and Applications , 2013, vol. 2, pp. 478-484 [Online]. Available: citeulike-article- | | 3395 | | id:14396282 | | 3396 | [52] | M. Fazio and A. Puliafito, 'Virtual Resource Management Based on Software Transactional | | 3397 | | Memory,' in 2011 First International Symposium on Network Cloud Computing and Applications | | 3398 | | 2011, pp. 1-8 [Online]. Available: | | 3399 | | 84856349781&partnerID=tZOtx3y1 | | 3400 | [53] | A. Celesti, M. Fazio, and M. Villari, 'SE CLEVER: A secure message oriented Middleware for | | 3401 | | Cloud federation,' in Proceedings - International Symposium on Computers and Communications | | 3402 | | 2013, pp. 35-40. | | 3403 | [54] | W. Jun, Z. Di, L. Meng, X. Fang, S. Hu-Lin, and Y.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3."}]}
{"id": "nist_01420", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Supporting Roles according to NIST_SP_800-37r2_Risk_Management_Framework? Supporting Roles: Chief Information Officer; Authorizing Official or Authorizing Official Designated Representative; Information Owner or Steward; Senior Agency Information Security Officer; Senior Agency Official for Privacy; Chief Acquisition Officer.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_01421", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Organizations should use centralized management for all deployments of storage encryption except for standalone deployments and very small-scale deployments. according to NIST Guide to Storage Encryption Technologies for End User Devices According to Guide to Storage Encryption Technologies for End User Devices, Organizations should use centralized management for all deployments of storage encryption except for standalone deployments and very small-scale deployments.: Centralized management is recommended for most storage encryption deployments because of its effectiveness and efficiency for policy verification and enforcement, key management, authenticator management, data recovery, and other management tasks. Centralized management can also automate deployment and configuration of storage encryption software to end user devices, distribution and installation of updates, collection and review of logs, and recovery of information from local failures.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Storage Encryption Technologies for End User Devices."}]}
{"id": "nist_01422", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6.18.2 Potential System Impacts according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance, 6.18.2 Potential System Impacts: Authentication and authorization tools can potentially impact the manufacturing system. These tools typically require a software agent to be installed on the device or require network processes that might induce latency or interrupt manufacturing processes. Backup authentication and authorization servers should be considered to prevent operator 'loss of view' and 'loss of control' incidents. Manufacturers should determine where authentication and authorization are not advisable for performance, safety, or reliability reasons.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance."}]}
{"id": "nist_01423", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Management_ Part 1 \u2013 General provide? (Section 269) | | | Framework (Internet Engineering Task Force (IETF) Network Working Group), IETF Request for Comments (RFC) 3647. https://doi.org/10.17487/RFC3647 | |-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | RFC 8032 | Josefsson S, Liusvaara I (2017) Edwards-Curve Digital Signature Algorithm (EdDSA). (Internet Research Task Force (IRTF)), IRTF Request for Comments (RFC) 8032. https://doi.org/10.17487/RFC8032 | | SP800-32 | Kuhn DR, Hu VC, Polk WT, Chang S-jH (2001) Introduction to Public Key Technology and the Federal PKI Infrastructure. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-32. https://doi.org/10.6028/NIST.SP.800-32 | | SP800-37 | 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. | | SP800-38 | Recommendation for Block Cipher Modes of Operation (all parts).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_01424", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Common Platform Enumeration_ Dictionary Specification Version 2.3 provide? (Section 33) le title of the name. To support uses intended for multiple languages, the <cpe_dict:title> element supports the @xml:lang attribute. At most one <cpe_dict:title> element MAY appear for each language. | | Property | Type | Count | Description | |----------------------|-------------------------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | notes (element) | cpe_dict:NotesType | 0-n | Optional descriptive material. To support uses intended for multiple languages, the <cpe_dict:notes> element supports the @xml:lang attribute. At most one <cpe_dict:notes> element MAY appear for each language. | | references (element) | cpe_dict:ReferencesType | 0-1 | External references to additional descriptive material. Each reference consists of a piece of text (intended to be human-readable) and a URI (intended to be a URL pointing to a real resource). | | check (element) | cpe_dict:CheckType | 0-n | Calls out a check, such as an OVAL definition, that can confirm or reject an IT system as an instance of the named platform. Includes a REQUIRED check system specification URI (e.g., the URI for a particular version of OVAL), a REQUIRED check identifier, and an OPTIONAL external file reference (for example, a pointer to the file where the check is defined).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Platform Enumeration_ Dictionary Specification Version 2.3."}]}
{"id": "nist_01425", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook provide? (Section 93) n, or maintenance of computer systems or automated applications, centers could estimate the percentage of that funding that is (or will be) directed toward computer security activities. - a. Purpose . The purpose of the DPI-CSP is to provide a document that serves as the management summary of more detailed information that may be associated with the basic elements of the DPI's computer security program. It should serve as a basis for informing management of security needs, performing security assessments, performing management and compliance reviews, and facilitating the extraction of summary information in response to center, HQ, or other Federal agency requests for planning information. The extent to which this planning activity is integrated into the center planning activities is left to the discretion of each CCSM; however, a DPI must comply with the center's CSP. - b. Content . The DPI-CSP must be kept current and should include elements that are relative to the coverage of the plan and to the computing environment of the DPI, as follows (see Exhibit 5-3): - (1) Summary of the management process describing the general administrative, technical, physical, and personnel protective measures employed at the DPI. If special provisions apply to selective computer systems or applications, this information should be included. 4. (2) 5. Reference to list(s) that uniquely identify computer applications that process sensitive or mission-critical information, the sponsors and/or owners of such applications, and the computer systems that provide processing support - Current Controls - Application Sensitivities - Contingency Plans - Actions Schedule - Review Results - Awareness &amp; Training - Security Tools - Incident identification - Security Contacts - (3) Reference to contingency and disaster recovery plans. - (4) Reference to schedules indicating planned and completed risk assessments, certifications/recertifications, compliance reviews, and CSAT sessions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook."}]}
{"id": "nist_01426", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to a Secure Enterprise Network Landscape say about 5.1.2 Microsegmentation - Implementation Approaches? (Part 2) According to Guide to a Secure Enterprise Network Landscape, 5.1.2 Microsegmentation - Implementation Approaches: ed by a VLAN ID. The group of applications that will run in that particular VLAN segment can be defined using different criteria, one of which is 'all applications with similar security requirements'. Another criterion is that 'all tiers (web front-end, application logic servers, and database servers) associated with a particular application' should run in a single microsegment, as shown in Figure 1. Fig. 1. Segment-based Microsegmentation <!-- image --> <!-- image --> The following are some approaches that are employed to implement microsegmentation [22]: - a. Virtualized server-based approach: This approach is only applicable to networks that contain virtualized servers since it is implemented in the hypervisor. There are two possible mechanisms: 1. Using virtual firewalls inside a hypervisor to isolate traffic destined for different VMs inside the hypervisor 2. Using encapsulation techniques to create overlays (e.g., Virtual Extensible LAN ( VXLAN)) that run on top of an underlying network that consists of IP addresses designations; access control policies are enforced on the hypervisor itself outside of the workload (application or microservice) - b. Host-based microsegmentation: Alternatively (or additionally), host-based microsegmentation can be implemented using software agents on the endpoint artifacts (e.g., servers). It leverages native firewall functionality built into the host. Software agents can overlay a software-defined segmented network across data centers, cloud, bare metal, and hybrid environments. The agent provides context awareness and visibility for each workload and enables the definition and enforcement of fine-grained policies. - c. Identity-based microsegmentation: Identity-based microsegmentation policies use contextual, application-driven identifiers (e.g., order processing front-end service can communicate with inventory back-end service) instead of network parameters (permit calls from 192.168.10.x subnet to 10.0.0.31) [24].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Guide to a Secure Enterprise Network Landscape."}]}
{"id": "nist_01427", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain NC-SS-R20 - SNMP security: according to NIST Security Guidelines for Storage Infrastructure According to Security Guidelines for Storage Infrastructure, NC-SS-R20 - SNMP security:: - (a) If SNMP if not in use, it should be disabled. - (b) Change the default, known community strings, even if SNMP is not enabled. The configured strings should meet the organizational password policy. - (c) Use different community strings for devices that differ in levels of confidentiality. - (d) Use at least SNMP version 3. - (e) SNMP authentication and encryption (privacy) features should be enforced. - (f) Do not configure SNMP with read-write access unless it is absolutely needed. In this case, limit and control the use of read-write SNMP. - (g) Use access control lists to control access to devices through SNMP. - (h) Validation that SNMP traps are sent to authorized, intended managers should be periodically performed. - (i) Refer to Department of Homeland Security Cybersecurity &amp; Infrastructure Security (DHS CISA) TA17-156A [39] for additional guidance. NC-SS-R21 The authenticity of directory, domain, and similar services (e.g., AD, Domain Name System (DNS), LDAP): The service configurations in all storage elements (e.g., devices, switches, management workstations, management software) should be actively and periodically reviewed to make sure that the approved ones are used, and for remediating any discrepancies.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, password policy. Contains security framework guidance for authentication systems. Source: Security Guidelines for Storage Infrastructure."}]}
{"id": "nist_01428", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 2016 NIST_ITL Cybersecurity Program Annual Report provide? (Section 268) rity performance, which was posted for public comment on the Baldridge Cybersecurity Initiative website (see https:/ /www.nist.gov/baldrige/products-services/ baldrige-cybersecurity-initiative). The BCEB is a voluntary self-assessment tool that enables organizations to better understand the effectiveness of their cybersecurity risk management efforts. Publications are available for download from CSRC (see http:/ /csrc.nist.gov/publications/), the NCCoE website (see https:/ /nccoe.nist.gov/library) and the main NIST Publications site (see https:/ /www.nist.gov/publications/). The following lists summarize the most-downloaded ITL publications for FY 2016, using weblog data (and excluding traffic from spiders and web crawlers): 1. SP 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations (303,162); 2. SP 800-145, The NIST Definition of Cloud Computing (235,191); 3. Framework for Improving Critical Infrastructure Cybersecurity, version 1.0 (180,163); 4. SP 800-61 Revision 2, Computer Security Incident Handling Guide (153,723); 5. SP 800-30 Revision 1, Guide for Conducting Risk Assessments (116,991); 6. SP 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach (112,104); 7. FIPS 197, Advanced Encryption Standard (AES) (108,162); 8. SP 800-122, Guide to Protecting the Confidentiality of Personally Identifiable Information (PII) (81,887); 9. SP 800-12, An Introduction to Computer Security: the NIST Handbook (81,768); and 10. SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations (80,960). 1. FIPS 197, Advanced Encryption Standard (AES) (108,162); 2. FIPS 140-2, Security Requirements for Cryptographic Modules (79,565); and 3.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01429", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 say about ADVERSARY EFFECTS? (Part 4) According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171, ADVERSARY EFFECTS: | Reduce likelihood of occurrence and (to a lesser extent) reduce likelihood of impact. | \u2022 The adversary's efforts cease. \u2022 The adversary actions are mistargeted or misinformed. | | Deter Discourage the adversary from undertaking further activities by instilling fear (e.g., of attribution or retribution) or doubt that those activities would achieve intended effects (e.g., that targets exist). | Reduce likelihood of occurrence. | \u2022 The adversary ceases or suspends activities. Example : The defender uses disinformation to make it appear that the organization is better able to detect attacks than it is and is willing to launch major counterstrikes. Therefore, the adversary chooses to not launch an attack due to fear of detection and reprisal. | | Divert Direct the threat event toward defender-chosen resources. | Reduce likelihood of occurrence. | \u2022 The adversary refocuses activities on defender-chosen resources. \u2022 The adversary directs activities toward targets beyond the defender's purview (e.g., other organizations). \u2022 The adversary does not affect resources that the defender has not selected to be targets. Example : The defender maintains an Internet-visible enclave with which untrusted external entities can interact and a private enclave accessible only via a VPN for trusted suppliers, partners, or customers (predefined segmentation). Example : The defender uses non-persistent information and obfuscation to hide critical resources combined with functional relocation of cyber resources and disinformation to lure the adversary toward a sandboxed enclave where adversary actions cannot harm critical resources. | | Deceive Lead the adversary to believe false information about defended systems, missions, or organizations or about defender capabilities or TTPs. | Reduce likelihood of occurrence and/or reduce likelihood of impact. | \u2022 The adversary's efforts are wasted as the assumptions on which the adversary bases attacks are false.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_01430", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SC-8 in Security and Privacy Controls for Information Systems and Organizations? (Part 4) Control SC-8: _____________________ Implement cryptographic mechanisms to conceal or randomize communication patterns unless otherwise protected by [Assignment: organization-defined alternative physical controls]. Discussion: Concealing or randomizing communication patterns addresses protection from unauthorized disclosure of information. Communication patterns include frequency, periods, predictability, and amount. Changes to communications patterns can reveal information with intelligence value, especially when combined with other available information related to the mission and business functions of the organization. Concealing or randomizing communications prevents the derivation of intelligence based on communications patterns and applies to both internal and external networks or links that may be visible to individuals who are not authorized users. Encrypting the links and transmitting in continuous, fixed, or random patterns prevents the derivation of intelligence from the system communications patterns. Alternative physical controls include protected distribution systems. Related Controls: SC-12, SC-13. (5) TRANSMISSION CONFIDENTIALITY AND INTEGRITY | PROTECTED DISTRIBUTION SYSTEM Implement [Assignment: organization-defined protected distribution system] to [Selection (one or more): prevent unauthorized disclosure of information; detect changes to information] during transmission. Discussion: The purpose of a protected distribution system is to deter, detect, and/or make difficult physical access to the communication lines that carry national security information. Related Controls: None. References: [FIPS 140-3], [FIPS 197], [SP 800-52], [SP 800-77], [SP 800-81-2], [SP 800-113], [SP 800-177], [IR 8023].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01431", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-6 in Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy? (Part 116) Control AM-6: _\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ the organization's privacy program, including any privacy functions performed by independent assessors. The senior agency official for privacy is responsible for providing privacy information to the authorizing official. References: [FIPS 199]; [SP 800-30]; [SP 800-53A]; [SP 800-55]. ## ASSESSMENT PLAN TASK A-2 Develop, review, and approve plans to assess implemented controls. Potential Inputs: Security, privacy, and SCRM plans; program management control information; common control documentation; organizational security and privacy program plans; SCRM strategy; system design documentation; supply chain information; enterprise, security, and privacy architecture information; security, privacy, and SCRM policies and procedures applicable to the system. Expected Outputs: Security and privacy assessment plans approved by the authorizing official. Primary Responsibility: Authorizing Official or Authorizing Official Designated Representative; Control Assessor. Supporting Roles: Senior Agency Information Security Officer; Senior Agency Official for Privacy; System Owner; Common Control Provider; Information Owner or Steward; System Security Officer; System Privacy Officer. System Development Life Cycle Phase: New - Development/Acquisition; Implementation/Assessment. Existing - Operations/Maintenance. Discussion: Security and privacy assessment plans are developed by control assessors based on the implementation information contained in security and privacy plans, program management control documentation, and common control documentation. Organizations may choose to develop a single, integrated security and privacy assessment plan for the system or the organization. An integrated assessment plan delineates roles and responsibilities for control assessment. Assessment plans also provide the objectives for control assessments and specific assessment procedures for each control.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, fips, security control. General security reference material without sensitive content. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_01432", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Biometric Specifications for Personal Identity Verification say about 4.5.2 Minimum interoperability specification? According to Biometric Specifications for Personal Identity Verification, 4.5.2 Minimum interoperability specification: The core cross-vendor interoperability specification is met by establishing requirements on template generators and template matchers as described in the following two sub-sections.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Biometric Specifications for Personal Identity Verification."}]}
{"id": "nist_01433", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Technology Assessment_ Methods for Measuring the Level of Computer Security provide? (Section 72) X | X | X | | X | X | X | X | X | X | | 1801 MVUOOUd | | | | | | X | X | X | X | X | | X | X | X | X | X | X | | ISO! 31U | | X | | X | X X | X | | X | X | X | X | X | X | X | X | X | X | | aiVIUdOHddVNI | | | | | | X | X | X | X | | X | X | | X | X | X | | | 133UU03NI | | | | | | X X | X X | X | X X | X | X X | | | X X X | X | X | | | ai31dN03NI | | | | | | | X | X | X | X | | X X | | X | | X | | | | | | | | | | | | | | | X | | | | | | | aiK}33tl ONOUM | | | | | | X | X | X | X | X | | | X | X | X | X | X | | anid ONOHM ATIVNU31NI 3iVlllNI | X | X | | X X | | X X | | | X | X | X | X | X | X | X | X | X | | NOUVZIUOHinV iSXNVlfl | X | | | | | | | | | | | | | | | | | | 0301100311 U3A3N | X | | | | | | | | | | | | | | | | | | VIVO 0NIS8IN | X | X | X | | | X | | | | | | | | | | | | | oaivondna | X | X | | X | | X | | | | | | | | | | | | | iS01 | X | X | | | | X | | | | | | | | | | | | | | | | X | | | | | | | | | | | | | | | c o \u00b7H (0 W e v a 4J T3 0) c a 0) en o CO 09 O &lt;u J3 O o H CO ON <!-- image --> <!-- image --> | ^ - - o 5 \" \u00a3 = \u00ab O >- ^ I f o i*j \u00a3 : E D 2 Z ^ o u r i < ir (J \u2022 3 J - 1 - 1 | - .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technology Assessment_ Methods for Measuring the Level of Computer Security."}]}
{"id": "nist_01434", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to IPsec VPNs say about 3.1 Overview of IKE? (Part 3) According to Guide to IPsec VPNs, 3.1 Overview of IKE: four-byte Initiator SPI.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to IPsec VPNs."}]}
{"id": "nist_01435", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations provide? (Section 132) the guidelines and procedures for key recovery operations. - k. Compromise Recovery: The procedures for recovering from the exposure of sensitive keying material to unauthorized entities. - k. Disciplinary Actions : A specification of the consequences for willful or negligent mishandling of keying material. - l. Change Procedures: A specification of the procedures for effecting changes to key management planning documentation. The following key management-related information for cryptographic product development may be useful to determine and resolve potential impacts to the key management infrastructure or other keying material acquisition processes in a time frame that meets user requirements. Yes/no responses should be provided to the following questions as well as additional information for each 'yes' response. To the extent practical, SP 800-160, 112 should be followed in the development of cryptographic products. 1. Are unique key management products 113 and services 114 required by the cryptographic product for proper operation? 2. Are there any cryptographic capabilities to be supported by a CKMS that are not fully configurable in the cryptographic product? 3. Does the cryptographic module implement a software download capability for importing updated cryptographic functions? 115 4. Does the cryptographic module use any non-keying material CKMS products or services (such as CKL/CRLs, seed key 116 conversion, etc.)? 5. Does the cryptographic module design preclude the use of any approved cryptographic algorithm? 112 SP 800-160 Volume 1, Systems Security Engineering: Considerations for a Multidisciplinary Approach in the Engineering of Trustworthy Secure Systems . 113 Key management products: e.g., keys, certificates, tokens, etc. 114 Key management services: The generation, establishment, distribution, destruction, revocation, and recovery of keys. 115 Cryptographic functions: algorithms and modes of operation.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, token. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations."}]}
{"id": "nist_01436", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is System Supplier according to Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI? System Supplier: Data General Corporation", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI."}]}
{"id": "nist_01437", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Practical Combinatorial Testing provide? (Section 84) as an input validity check that issues an error message if input is not acceptable. The assertion gives conditions that must hold for the function to operate properly, in this case a non-zero divisor. It is the responsibility of the programmer to ensure that a zero divisor is never passed to the function. The distinction between assertions and input validation code is that assertions are intended to catch programming mistakes , while input validation detects errors in user or file/database input. With a sufficient number of assertions derived from a specification, the program can have a self-checking property [27, 60, 47]. The assertions can serve as a sort of embedded proof of important properties, such that if the assertions hold for all executions of the program, then the properties encoded in the assertions are guaranteed to hold. Then, if the assertions form a chain of logic that implies a formal statement of program properties, the program's correctness with respect to these properties can be proven. We can take advantage of this scheme in combinatorial testing by demonstrating that the assertions hold for all t -way With self-checking through assertions, thousands of tests can often be run at very low cost, allowing highstrength interaction coverage. combinations of inputs. While this is not the same as a correctness proof, it is an effective way of integrating formal methods for correctness with program testing, and an extensive body of research has developed this idea for practical use (for a survey, see [4]). Some modern programming languages, such as Eiffel [52], include extensive support for including assertions that encode program properties, and tools such as the Java Modeling Language [42] have been designed to integrate assertions with testing.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Practical Combinatorial Testing."}]}
{"id": "nist_01438", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cryptographic Key Management Workshop Summary -- June 8-9, 2009 say about 2.1.9 2010 Transitions: Elaine Barker, NIST? According to Cryptographic Key Management Workshop Summary -- June 8-9, 2009, 2.1.9 2010 Transitions: Elaine Barker, NIST: - The talk described NIST recommendations to transition from algorithms and key sizes that are believed to be too weak (i.e., no longer secure) to a stronger set of algorithms and key sizes, including deadlines for transition from the old set to the new set. - A security strength (AKA 'bits of security') is a number associated with the expected amount of work (often measured in binary operations) that is required to obtain any given key used by an application by testing all possible keys. The security strength is specified in bits and is currently a value from the set {80, 112, 128, 192, 256}. 80 bits of security are good through December 31, 2010. Thereafter, NIST recommends 112 bits as the minimum. - Material was provided from NIST SP 800-57, Part 1 (for algorithms, key sizes, security strengths, and recommended transition times), FIPS 186-3 (for digital signatures), and FIPS 180-3 (hash functions). See the presentation slides or referenced documents for details and comparisons among algorithms and parameters.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Cryptographic Key Management Workshop Summary -- June 8-9, 2009."}]}
{"id": "nist_01439", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Log Entry according to Guide to Computer Security Log Management? Log Entry: An individual record within a log.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Computer Security Log Management."}]}
{"id": "nist_01440", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Threat Analysis on UOCAVA Voting Systems say about 6.1.1 Postal Mail? (Part 2) According to A Threat Analysis on UOCAVA Voting Systems, 6.1.1 Postal Mail: ld 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. In some cases it might be difficult to identify these materials from other pieces of mail without opening the Table 2: Threat Matrix for Postal Mail Registration and Ballot Request | Threat | Threat-Sources | Effort | Detection | Impact | Possible Controls | |--------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|----------|-------------|----------------|------------------------------------------| | Ineligible individual allowed to register to vote. | Hostile Individuals | Low | Mod. | Integrity-Mod. | IA-1, IA-2, IA-4, IA-5 | | Valid voter's ballot request information, such as address, is modified in transit. | Hostile Individuals Postal Workers System Operators Election Officials | Mod. | Low | Integrity-Mod. | MP-5, MP-5(1) | | Registration/Request materials are accidentally lost or destroyed in transit. | Postal Workers | Low | High | Avail.-High | MP-5 | | Registration/Request materials are intentionally delayed or destroyed in transit by a malicious party. | Hostile individuals Hostile Organizations Postal workers | High | High | Avail.-High | MP-5 | | Sensitive personal information is viewed in transit.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Threat Analysis on UOCAVA Voting Systems."}]}
{"id": "nist_01441", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6.1 Security Risks according to NIST Guidelines for the Secure Deployment of IPv6 According to Guidelines for the Secure Deployment of IPv6, 6.1 Security Risks: This section provides an overview of risks organizations may face when moving from an IPv4 to IPv4/IPv6 and eventually IPv6 environment. The deployment of IPv6 is inevitable. The IPv4 address space is almost exhausted and the only long-term solution is to deploy IPv6. IPv6 is not backwards compatible with IPv4, which means organizations will have to change their network infrastructure and systems to deploy IPv6. Organizations should begin now to understand the risks and the risk mitigation strategies. Planning will enable an organization to make a smooth, secure and successful transition. Some general risks an organization may face include: - \uf03c The attacker community's use of IPv6 - \uf03c Unauthorized deployment of IPv6 on existing IPv4 production networks - \uf03c Vulnerabilities present in IPv6, including -day zero\u2016 vulnerabilities that are inherent in any new or revised system - \uf03c Complexity added by dual IPv4/IPv6 operations - \uf03c Immaturity of IPv6 security products and processes - \uf03c Possible lack of vendor support.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_01442", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Codes for Identification of Federal and Federally-Assisted Organizations? (Part 90) Control PD-12: Memorial Cemetery Commission ## MULTILATERAL DEVELOPMENT BANKS | 11DB | African Development Fund | |--------|--------------------------------------------------------------------| | 11DE | Asian Development Bank | | 11DK | European Bank for Reconstruction and Development | | 11DT | Inter-American Defense Board | | 11DH | Inter-American Development Bank | | 11DR | International Bank for Reconstruction and Development (World Bank) | | 11DA | International Development Association | | 11DF | International Finance Corporation | | 11DG | International Fund for Agricultural Development | | 11DM | International Monetary Fund | | 11DW | Multilateral Investment Guarantee Agency | | 11DN | North American Development Bank | ## REGIONAL ORGANIZATIONS | 19RJ | Asia-Pacific Economic Cooperation | |--------|--------------------------------------------------------------------------------------| | 19RC | Colombo Plan Council for Technical Cooperation | | 19RD | Colombo Plan for Cooperative Economic and Social Development in Asia and the Pacific | | 11RF | Multinational Force and Observers | | 19RA | North Atlantic Assembly | | 19RN | North Atlantic Treaty Organization | | 19RE | Organization for Economic Cooperation and Development | | 19RP | South Pacific Commission | ## TABLE OF ORGANIZATIONS AND CODES OTHER INDEPENDENT FEDERAL AGENCIES, BOARDS, COMMISSIONS, COUNCILS, FOUNDATIONS, OFFICES, QUASI-FEDERAL ORGANIZATIONS AND", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Codes for Identification of Federal and Federally-Assisted Organizations."}]}
{"id": "nist_01443", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974 say about Data at Rest? According to Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974, Data at Rest: As contrasted to data in motion, data at rest is data in a semipermanent file -data on magnetic tape, data on Magnetic Disk, or even data in main storage. The amount of encryption that can be performed depends, of course, on the cost and performance of the encryption devices available. For the moment we will assume the existence of an encryption device having no cost and having no performance limitations. Later, we will consider cost and performance constraints.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974."}]}
{"id": "nist_01444", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways provide? (Section 6) HowTo Guides , which provide specific product installation, configuration, and integration instructions for building the example implementation, allowing you to replicate all or parts of this project. You can view or download the guide at Help the NCCoE make this guide better by sharing your thoughts with us as you read the guide. If you adopt this solution for your own organization, please share your experience and advice with us. We recognize that technical solutions alone will not fully enable the benefits of our solution, so we encourage organizations to share lessons learned and best practices for transforming the processes associated with implementing this guide. To provide comments or to learn more by arranging a demonstration of this example implementation, contact the NCCoE at cyberhygiene@nist.gov. Collaborators participating in this project submitted their capabilities in response to an open call in the Federal Register for all sources of relevant security capabilities from academia and industry (vendors and integrators). Those respondents with relevant capabilities or product components signed a Cooperative Research and Development Agreement (CRADA) to collaborate with NIST in a consortium to build this example solution. Certain commercial entities, equipment, products, or materials may be identified by name or company logo or other insignia in order to acknowledge their participation in this collaboration or to describe an experimental procedure or concept adequately. Such identification is not intended to imply special status or relationship with NIST or recommendation or endorsement by NIST or NCCoE; neither is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_01445", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2013 Annual Report say about Apple OS X Security Configuration? (Part 1) According to Computer Security Division 2013 Annual Report, Apple OS X Security Configuration: Apple OS X Security Configuration CSD is working with Apple to develop secure system configuration baselines supporting different operational environments for Apple OS X, Version 10.8, Mountain Lion. These configuration guidelines will assist organizations with hardening OS X technologies and provide a basis for unified controls and settings for OS X workstations and for mobile system security configurations for federal agencies. The configurations will be based on a collection of resources, including the existing NIST OS X configuration guidance, the OS X security configuration guide, the Department of Defense (DoD) OS X Recommended Settings, and the Defense Information Systems Agency (DISA) OS X Security Technical Implementation Guide (STIG). Our team is aggregating appropriately 400 initial settings, determining which settings will be included in the configuration baseline, and determining appropriate values for each included setting. As the desired configuration items are established, our team is developing shell scripts that apply the settings to an OS X 10.8 system. The settings are organized into three key baselines, which are appropriate for different environments: - \u0097 Enterprise baseline is appropriate for centrally managed, networked systems. - \u0097 Small Office Home Office baseline is appropriate for systems that are deployed remotely but need to connect to enterprise networks. - \u0097 Special Security Limited Functionality baseline is appropriate for systems where security requirements are more stringent and where the implementation of security safeguards is likely to reduce functionality. SCAP, defined and discussed in other sections of this report, is used to express configuration settings and check system configuration compliance.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2013 Annual Report."}]}
{"id": "nist_01446", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 03.08.03 Media Sanitization according to NIST Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, 03.08.03 Media Sanitization: Sanitize system media that contain CUI prior to disposal, release out of organizational control, or release for reuse.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_01447", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Virtualization according to Guide to Security for Full Virtualization Technologies? Virtualization: The simulation of the software and/or hardware upon which other software runs.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Security for Full Virtualization Technologies."}]}
{"id": "nist_01448", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Test Personal Identity Verification (PIV) Cards Version 2 say about Security Object:? According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Security Object:: Includes unsigned data objects but not CHUID, Cardholder Fingerprints, or Cardholder Facial Image.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_01449", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Required Vendor Information according to NIST PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance) According to PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance), Required Vendor Information: VE05.29.01: The vendor shall state in its documentation that the card supports the assertion made in AS05.29.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)."}]}
{"id": "nist_01450", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-2 in Proceedings of the Workshop of the Federal Criteria for Information Technology Security? (Part 32) Control AC-2: privilege to increase or decrease a process' priority may be allocated to non-TCB subjects). Oth^ noted that the FC should not discuss 'trusted subjects' at all, since it is an implementation detail. In most cases, it should suffice to simply distinguish between TCB and non-TCB (and possibly Reference Monitor and the non-RM TCB). ## Summary and Conclusions The DAWG did not achieve consensus (Hi a lot of the issues discussed. This was due in part to the small amount of time available for discussion. Nonetheless, many excellent points were raised, the most significant of which are hopefully ccHitained in the material presented above. In the mcxlerator's opinion, th^ was general agreement on a number of important issues: - Few were ha{^y with the current contents of Chapter 5. There was not a consensus on what Chapter 5 should l(X)k like, but many opinicHis w^given (as discussed above). - Most participants liked the idea of components in principle. However, nearly everyone had serious concerns about the concept in i^ctice, and in particular, about the FC's components as currently defined. The principle concerns focused on the possibility of reconstructing meaningless (and possibly harmful) assurance requirements from ccHuponents, the lack of control over the quality of individual components, and the loss of meaning by breaking assurance requirements into components and then reconstructing new assurance requirements. This issue consumed most of the DAWG's lime. - Nearly all participants had serious concerns about some of the technical assurance concepts introduced in the FC. Many felt that some of the concepts were not wellaccepted, and that some of the 'new' concepts were not well described Others were concerned that some well-accepted concepts were replaced by less-accepted or poorly described 'new' concepts. The group consensus was that the FC should stick to accepted concerts and ideas (but not close the dcx)r on new ideas being introduced in the future).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: rmf, fips, security control. General security reference material without sensitive content. Source: Proceedings of the Workshop of the Federal Criteria for Information Technology Security."}]}
{"id": "nist_01451", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Section 6) owing 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. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ This publication is a supplement to NIST Special Publication 800-171 [SP 800-171]. It contains recommendations for enhanced security requirements to provide additional protection for Controlled Unclassified Information (CUI) in nonfederal systems and organizations when such information is associated with critical programs or high value assets. The enhanced security requirements are designed to respond to the advanced persistent threat (APT) and supplement the basic and derived security requirements in [SP 800-171]. While the security requirements in [SP 800-171] focus primarily on confidentiality protection, the enhanced security requirements in this publication address confidentiality, integrity, and availability protection. The enhanced security requirements are implemented in addition to the basic and derived requirements since those requirements are not designed to address the APT. The enhanced security requirements apply to those components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. There is no expectation that all of the enhanced security requirements will be selected by federal agencies implementing this guidance. The decision to select a particular set of enhanced security requirements will be based on the mission and business needs of federal agencies and guided and informed by ongoing risk assessments.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_01452", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Currently there are nine laboratories accredited to perform Cryptographic Module testing according to Computer Security Division 2004 Annual Report? Currently there are nine laboratories accredited to perform Cryptographic Module testing: five in the United States, two in Canada and two in the United Kingdom. Seven laboratories are to be re-accredited in 2005 and three or more new laboratories should complete accreditation. Currently there are nine Common Criteria testing laboratories.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2004 Annual Report."}]}
{"id": "nist_01453", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Device Security_ Cloud and Hybrid Builds say about 4.3.1 Default Policies? (Part 19) According to Mobile Device Security_ Cloud and Hybrid Builds, 4.3.1 Default Policies: application store.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Cloud and Hybrid Builds."}]}
{"id": "nist_01454", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Guidance according to Security Guidance for First Responder Mobile and Wearable Devices? Guidance: Most modern handsets and mobile devices contain the latest features and enhancements regarding data integrity protections. Similarly, devices typically have data integrity mechanisms built-in and enabled by default, requiring little or no user intervention. Older devices may lack features to protect against modern attacks, therefore it is important to keep devices up to date with the latest OS patches and upgrades. Devices that are no longer supported by the hardware vendor or OS manufacturer should be retired out of service.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Guidance for First Responder Mobile and Wearable Devices."}]}
{"id": "nist_01455", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Section 26) 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. However, the security of this operation is ensured by not allowing the connections to be very long (usually as long as the time to live [TTL] of the service's identity certificate or as short as 15-30 minutes, depending on the configuration). - ID-SEG-REC-3: Service to service authorization - Services should leverage runtime service identity (ID-SEG-REC-2) to enforce granular policies and have the capability to call external authorization services if the mesh-level proxies are insufficient to enforce dynamic authorization policies. - ID-SEG-REC-4: End user authentication - Since all application requests are triggered by user actions, a robust identity management system is required to assign and maintain user identities and enforce robust protocols with phishing-resistant multi-factor authentication (MFA). This system should be used to issue a cryptographically verifiable runtime token that represents the user principal to the rest of the infrastructure (e.g., a JSON Web Token [JWT]), and services should authenticate the credential at each hop. Note on the above recommendation: Authenticating the user in session at every hop is impractical at scale. Therefore, NIST recommends using short-lived end user credentials (e.g., OAuth 2.0 tokens) for external users and exchanging them for a locally authenticatable token, like a JWT, that is authenticated at each hop. - ID-SEG-REC-5: End user to resource authorization - As part of each service access request, the system must ensure that the authenticated end user principal (ID-SEG-REC4) is authorized to act on the resources designated in the request.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments."}]}
{"id": "nist_01456", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does De-Identifying Government Datasets_ Techniques and Governance say about 3.6. Disclosure Review Boards? (Part 5) According to De-Identifying Government Datasets_ Techniques and Governance, 3.6. Disclosure Review Boards: f evaluating data releases, the DRB should require that written applications be submitted to the DRB that specify the nature of the dataset, the deidentification methodology, and the result. An application may require that the proposer present the re-identification risk, the risk to individuals if the dataset is re-identified, and a proposed plan for detecting and mitigating successful re-identification. In addition, the DRB should require that when individuals are informed that their information will be deidentified, they also be informed that privacy risks may remain despite de-identification. The DRB should keep accurate records of its request memos, their associated documentation, the DRB decision, and the actual files released. These records should be appropri- 24 For example, in 2022, the Census Bureau's DRB had 12 voting members: two technical co-chairs, a representative from the Policy Coordination Office, a representative from the Associate Director for Communications, two representatives from the Center for Enterprise Dissemination-Disclosure Avoidance (CED-DA), two representatives from the Economic Programs Directorate, two representatives from the Demographic Programs Directorate, and two representatives from the Decennial Programs Directorate [29]. ately archived and curated so that they can be recovered. In the case of large data releases, the definitive version of the released data should be curated using an externally validated procedure, such as a recorded cryptographic hash value or signature, and a digital object identifier (DOI) [83]. DRBs may wish to institute a two-step process in which the applicant first proposes and receives approval for a specific de-identification process that will be applied to a specific dataset and then submits and receives approval for the release of the dataset that has been de-identified according to the proposal.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: De-Identifying Government Datasets_ Techniques and Governance."}]}
{"id": "nist_01457", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automation Support for Security Control Assessments_ Software Asset Management say about Roles and Assessment Methods? According to Automation Support for Security Control Assessments_ Software Asset Management, Roles and Assessment Methods: | Determination Statement ID | Implemented By | Assessment Boundary | Assessment Responsibility | Assessment Methods | Selected | Rationale for Risk Acceptance | Frequency of Assessment | Impact of Not Implementing | |------------------------------|------------------|-----------------------|-----------------------------|----------------------|------------|---------------------------------|---------------------------|------------------------------| | SI-3(c){2} | ISCM-Ops | ISCM-TN | ISCM-Sys | Test | | | | |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_01458", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security provide? (Section 18) ), and remote access communications. The document emphasizes the importance of securing sensitive information stored on telework devices and transmitted through remote access across external networks. This document provides recommendations for creating telework-related policies and for selecting, implementing, and maintaining the necessary security controls for remote access servers and clients. This document is primarily intended for security, system, and network engineers and administrators, as well as computer security program managers, who are responsible for the technical aspects of preparing, operating, and securing remote access solutions and client devices. Portions of the document are also intended for higher-level management, such as the individuals responsible for creating telework policies. The material in this document is technically oriented, and it is assumed that readers have at least a basic understanding of remote access, networking, network security, and system security. The remainder of this document is organized into the following sections: - \uf03c Section 2 provides an overview of enterprise telework and remote access security. It discusses general vulnerabilities and threats against telework and remote access solutions. It also describes the highlevel architectures of common remote access methods and the security characteristics of each architecture. Finally, it discusses concerns particular to BYOD use of organization networks. - \uf03c Section 3 presents recommendations for securing remote access solutions, including server security, server placement, and client software security. It also covers authentication, authorization, and access control for remote access solutions. - \uf03c Section 4 offers recommendations for securing telework client devices and protecting data on them. - \uf03c Section 5 discusses security throughout the telework and remote access life cycle.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security."}]}
{"id": "nist_01459", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Summary Report for \u201cWorkshop on Updating Manufacturer Guidance for Securable Connected Product Development\u201d say about Contact Information? According to Summary Report for \u201cWorkshop on Updating Manufacturer Guidance for Securable Connected Product Development\u201d, Contact Information: iotsecurity@nist.gov National Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Summary Report for \u201cWorkshop on Updating Manufacturer Guidance for Securable Connected Product Development\u201d."}]}
{"id": "nist_01460", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure provide? (Section 236) . | ISA/IEC 62443-2- 1:D4E1 EVENT 1.2 ISA/IEC 62443-3- 3:2013 SR 6.1 | | DP-4 | Cloud/Third-Party | Applicable, but no additional Cloud/Third-Party-specific considerations. | [NIST-SP800-53r5] AU-6, CA-2, CA-7 | | DP-4 | Utility/Building Management System | Applicable, but no additional Utility/Building Management System specific considerations. | ISA/IEC 62443-2- 1:D4E1 EVENT 1.2 ISA/IEC 62443-3- 3:2013 SR 6.1 | | DP-5: Detection processes are continuously improved. | Ecosystem: These improvements may take the form of additional or increased tool use, activities, or Cyber Threat Intelligence use. | [NIST-SP800-53r5] CA-2, CA-7, PL-2, PM-14, RA-5, SI-4 | | DP-5 | EV | Applicable, but no additional EV-specific considerations. | [NIST-SP800-53r5] CA-2, CA-7, PL-2, PM-14, RA-5 | | DP-5 | XFC/EVSE | Applicable, but no additional EVSE-specific considerations. | ISA/IEC 62443-2- 1:D4E1 ORG 1.1 | | DP-5 | Cloud/Third-Party | Applicable, but no additional Cloud/Third-Party-specific considerations. | [NIST-SP800-53r5] CA-2, CA-7, PL-2, PM-14, RA-5 | | DP-5 | Utility/Building Management System | Applicable, but no additional Utility/Building Management System-specific considerations. | ISA/IEC 62443-2- 1:D4E1 ORG 1.1 | The activities in the Respond function support the ability to contain the impact of an incident by developing and implementing the appropriate responses to a detected cybersecurity attack or anomalous incident. The Respond function actions are triggered by the outputs generated by the Detect function and the Protect function provides the ability to execute the proper response to an incident according to a pre-defined plan.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure."}]}
{"id": "nist_01461", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management say about 2.1.2 Enterprise Strategy for Cybersecurity Risk Coordination? (Part 5) According to Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management, 2.1.2 Enterprise Strategy for Cybersecurity Risk Coordination: | | 4. Assessing CSRM and reporting system level risk response through CSRRs | Security plans; risk response; system authorization (or denial of authorization with referral back for plan revision) | Risk assessment results; CSRRs describing residual risk and response actions taken; risk categorization and metrics that support ongoing assessment, authorization, and continuous monitoring | | 5.Aggregating organization level CSRRs | CSRRs showing system level risk decisions and metrics; internal reports from compliance/auditing processes to confirm alignment with enterprise risk strategy; observations regarding CSRM achievement in light of risk strategy | CSRRs aggregated and normalized based on enterprise-defined risk categories and measurement criteria; refinement of risk tolerance statements, if needed, to ensure balance among value, resources, and risk | | 6.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management."}]}
{"id": "nist_01462", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 say about COMMON ABBREVIATIONS? (Part 4) According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171, COMMON ABBREVIATIONS: | Tactics, Techniques, and Procedures | | USC | United States Code | | US-CERT | United States Computer Emergency Response Team | | VLAN | Virtual Local Area Network | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_01463", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2014 Annual Report? (Part 151) Control HA-3: emented in hardware or protected firmware so that malware cannot tamper with the functions they provide. Roots of trust provide a firm foundation from which to build security and trust. NIST CSD's work aims to encourage the use of roots of trust in computers to provide stronger security assurances. A focus area for this work has been securing mobile devices, using roots of trust to provide device integrity, data and application isolation, and protected storage. As part of this work, CSD is revising SP 800-164, Guidelines on HardwareRooted Security in Mobile Devices, based on the public comments that were received on the draft. A revised draft will be released in FY 2015. Meanwhile, the draft guideline is being used as the basis for an effort with the National Cybersecurity Center of Excellence (NCCoE) to encourage the adoption of stronger security technologies in mobile devices. Using draft SP 800-164 as a foundational document, the NCCoE and CSD developed the Mobile Device Security for Enterprises building block, which will demonstrate commercially available technologies that provide protection to both organization-issued and personally owned mobile platforms. The NCCoE will invite mobile device, operating system, and management software vendors, as well as application developers, to participate in this building block activity and demonstrate how their technologies could be used together to meet existing security requirements. The CSD also continued its work to protect platform firmware in FY 2014. Boot firmware, commonly known as the Basic Input/Output System (BIOS), is a critical firmware component, due to its unique and privileged position within modern computing architectures. CSD has been working with key members of the computer industry on the use of roots of trust to improve the security of BIOS.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_01464", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Note according to Engineering Trustworthy Secure Systems? Note: This includes the criteria defined by regulatory, certification, evaluation, and other approval authorities.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_01465", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CP-09 in Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations? (Part 130) Control CP-09: Maintenance (MA) | NIST SP 800-53 CONTROLS MODERATE BASELINE | NIST SP 800-53 CONTROLS MODERATE BASELINE | TAILORING CRITERIA | SECURITY REQUIREMENT | |---------------------------------------------|---------------------------------------------|----------------------|------------------------| | MA-01 | System Maintenance Policy and Procedures | CUI | 03.15.01 | | MA-02 | Controlled Maintenance | NCO | - | | NIST SP 800-53 CONTROLS MODERATE BASELINE | NIST SP 800-53 CONTROLS MODERATE BASELINE | TAILORING CRITERIA | SECURITY REQUIREMENT | |---------------------------------------------|--------------------------------------------------|----------------------|------------------------| | MA-03 | Maintenance Tools | CUI | 03.07.04 | | MA-03(01) | Maintenance Tools | Inspect Tools | CUI | 03.07.04 | | MA-03(02) | Maintenance Tools | Inspect Media | CUI | 03.07.04 | | MA-03(03) | Maintenance Tools | Prevent Unauthorized Removal | CUI | 03.07.04 | | MA-04 | Nonlocal Maintenance | CUI | 03.07.05 | | MA-05 | Maintenance Personnel | CUI | 03.07.06 | | MA-06 | Timely Maintenance | NCO | - | Table 12.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_01466", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-2 in Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations? (Part 91) Control HA-2: n: the CCM Mode for Authentication and Confidentiality. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-38C, Includes updates as of July 20, 2007. https://doi.org/10.6028/NIST.SP.800-38C - [29] Eastlake D, III, (2011) Transport Layer Security (TLS) Extensions: Extension Definitions. (Internet Engineering Task Force (IETF)), IETF Request for Comments (RFC) 6066. https://doi.org/10.17487/RFC6066 - [30] Eronen P, Tschofenig H (2005) Pre-Shared Key Ciphersuites for Transport Layer Security (TLS). (Internet Engineering Task Force (IETF), Network Working Group), IETF Request for Comments (RFC) 4279. https://doi.org/10.17487/RFC4279 - [31] Federal Public Key Infrastructure Policy Authority (2019) X.509 Certificate Policy For The U.S. Federal PKI Common Policy Framework. - [32] Freier A, Karlton P, Kocher P (2011) The Secure Sockets Layer (SSL) Protocol Version 3.0. (Internet Engineering Task Force (IETF)), IETF Request for Comments (RFC) 6101. https://doi.org/10.17487/RFC6101 - [33] Gutmann P (2014) Encrypt-then-MAC for Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS). (Internet Engineering Task Force (IETF)), IETF Request for Comments (RFC) 7366. https://doi.org/10.17487/RFC7366 - [34] Hoffman P, Schlyter J (2012) The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA. (Internet Engineering Task - Force (IETF)), IETF Request for Comments (RFC) 6698. https://doi.org/10.17487/RFC6698 - [35] Huitema C, Rescorla E (2018) Issues and Requirements for SNI Encryption in TLS. (Internet Engineering Task Force (IETF) Transport Layer Security Working Group), Internet-Draft draft-ietf-tls-sni-encryption-04.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations."}]}
{"id": "nist_01467", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Card Technology Developments and Gap Analysis Interagency Report say about Workshop topics:? (Part 3) According to Card Technology Developments and Gap Analysis Interagency Report, Workshop topics:: PM | LUNCH | | | 2:05 PM- 3:35 PM | PANEL DISCUSSION: INTEROPERABILITY REQUIREMENTS/ISSUES | | | 3:35 PM- 3:55 PM | QUESTIONS AND COMMENTARY | | | 3:55 PM- 4:10 PM | BREAK | | | 4:15 PM- 4:45 PM | PANEL DISCUSSION: TECHNOLOGYROAD MAP & GAP ANALYSIS | | | 4:45 PM- 5:00PM | QUESTIONS AND COMMENTARY | | | 5:00 PM- 5:15PM | WORKSHOPWRAP-UP | |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Card Technology Developments and Gap Analysis Interagency Report."}]}
{"id": "nist_01468", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is This report is intended for two main audiences according to Common Platform Enumeration_ Name Matching Specification Version 2.3? This report is intended for two main audiences: IT management tool developers and the authors and editors of CPE content. Readers of this report should already be familiar with CPE naming concepts and conventions as defined in [CPE23-N].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Platform Enumeration_ Name Matching Specification Version 2.3."}]}
{"id": "nist_01469", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Status Report on the Second Round of the NIST Lightweight Cryptography Standardization Process provide? (Section 96) thenticated Encryption and Hash Family, Submission to the NIST Lightweight Cryptography Standardization Process. https://csrc.nist.gov/ Projects/lightweight-cryptography/round-2-candidates. - [52] Goudarzi D, Jean J, K\u00a8 olbl S, Peyrin T, Rivain M, Sasaki Y, Sim SM (2019) Pyjamask \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ - v1.0, Submission to the NIST Lightweight Cryptography Standardization Process. lightweight-cryptography/round-2-candidates. - [53] Iwata T, Khairallah M, Minematsu K, Peyrin T (2019) Romulus v1.2, Submission to the NIST Lightweight Cryptography Standardization Process. https://csrc.nist.gov/ Projects/lightweight-cryptography/round-2-candidates. - [54] Naito Y, Matsui M, Sakai Y, Suzuki D, Sakiyama K, Sugawara T (2019) SAEAES, Submission to the NIST Lightweight Cryptography Standardization Process. https: //csrc.nist.gov/Projects/lightweight-cryptography/round-2-candidates. - [55] Canteaut A, Duval S, Leurent G, Naya-Plasencia M, Perrin L, Pornin T, Schrottenloher A (2019) Saturnin: A Suite of Lightweight Symmetric Algorithms for Post-Quantum Security, Submission to the NIST Lightweight Cryptography Standardization Process. lightweight-cryptography/ round-2-candidates. - [56] Beierle C, Jean J, K\u00a8 olbl S, Leander G, Moradi A, Peyrin T, Sasaki Y, Sasdrich P, Sim S (2019) SKINNY-AEAD and SKINNY-Hash v1.1, Submission to the NIST Lightweight Cryptography Standardization Process. lightweight-cryptography/round-2-candidates.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Second Round of the NIST Lightweight Cryptography Standardization Process."}]}
{"id": "nist_01470", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications provide? (Section 75) uences occurring in the tested sequence is too large or too small relative to the expected behavior of that cumulative sum for random sequences. This cumulative sum may be considered as a random walk. For a random sequence, the excursions of the random walk should be near zero. For certain types of non-random sequences, the excursions of this random walk from zero will be large. CumulativeSums( mode,n ), where: - n The length of the bit string. Additional input for the function, but supplied by the testing code: - \u03b5 The sequence of bits as generated by the RNG or PRNG being tested; this exists as a global structure at the time of the function call; \u03b5 = \u03b5 1 , \u03b5 2 , \u2026 , \u03b5 n . mode A switch for applying the test either forward through the input sequence ( mode = 0 ) or backward through the sequence ( mode = 1 ). - z: The largest excursion from the origin of the cumulative sums in the corresponding (-1, +1) sequence. The reference distribution for the test statistic is the normal distribution. - (1) Form a normalized sequence: The zeros and ones of the input sequence ( \u03b5 ) are converted to values Xi of -1 and +1 using Xi = 2 \u03b5 i - 1. For example, if \u03b5 = 1011010111 , then X = 1, (-1), 1, 1, (-1), 1, (-1), 1, 1, 1 . - (2) Compute partial sums Si of successively larger subsequences, each starting with X1 (if mode = 0 ) or Xn (if mode = 1 ). | Mode = 0 (forward) | Mode = 1 (backward) | |--------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| | S 1 = X 1 S 2 = X 1 + X 2 S 3 = X 1 + X 2 + X 3 . . S k = X 1 + X 2 + X 3 +\u2026+X k . .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications."}]}
{"id": "nist_01471", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Training & Awareness Course Compendium say about TANDEM? According to Computer Security Training & Awareness Course Compendium, TANDEM: COURSE TITLE: Audit and Security of Tandem Systems COURSE LENGTH: 2 DAYS", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Training & Awareness Course Compendium."}]}
{"id": "nist_01472", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Telehealth Remote Patient Monitoring Ecosystem say about C-2 Information and Information System Categorization? (Part 2) According to Securing Telehealth Remote Patient Monitoring Ecosystem, C-2 Information and Information System Categorization: Table C-1, Information Types and Categorizations, and provisional impact levels were captured, with the category levels corresponding to the recommended value found in NIST SP 800-60 Volume II [31]. . Table C-1 Information Types and Categorizations | Information Type | NIST SP 800-60 Volume II Reference (e.g., C.2.8.9) | Confidentiality | Integrity | Availability | Justification (to change an impact level) | |--------------------------------------|------------------------------------------------------|-------------------|-------------|----------------|---------------------------------------------| | personal identity and authentication | C.2.8.9 | moderate | moderate | moderate | N/A | | access to care | D.14.1 | low | moderate | low | N/A | | Overall Rating | Overall Rating | moderate | moderate | moderate | N/A | After identifying the information categories, one may determine the security objectives. Security objectives use a scale of low, medium, and high. FIPS 199 provides guidance in applying security categorization (SC). This practice guide identifies two information types: personal identity and authentication, as well as access to care. RPM \u02bc s SC may be expressed as {( confidentiality, MODERATE), ( integrity, MODERATE), ( availability, MODERATE)} [29]. The SC provides a base guide for security controls selection.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_01473", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AT-1 in Building a Cybersecurity and Privacy Learning Program? (Part 56) Control AT-1: ith privileged access; reviewing these issues with the offices of the CIO, CISO, and/or CPO; and aligning learning goals for these risks to the available budget for impacted personnel and departments. Evaluating organizational policies, program reviews, internal audits, self-assessments, and spot-checks can also help CPLP managers identify additional topics to address. ## 4.1.4. Developing New Materials for Those With Significant Cybersecurity and/or Privacy Responsibilities The customized and individualized nature of ongoing skills development and training for personnel with significant cybersecurity and/or privacy responsibilities requires a more detailed and nuanced learning program approach. For example, multiple requirements documents may be needed to develop new learning program elements and identify training that will satisfy learning objectives. The CPLP manager should partner and coordinate these efforts with the organization's human capital office, CLO, training and curriculum developers, and the individual managers and supervisors for the personnel in this learning program audience segment. CPLP managers should ensure that the complexity of the training is commensurate with the role and needs of the people who will undergo the learning effort. Cybersecurity and privacy role-based training materials can be developed at a beginning level for a person who is just learning a discipline. Materials can be developed at an intermediate level for someone who has more experience and, therefore, more responsibility in their workplace. Advanced materials can be developed for agency SMEs whose jobs incorporate the highest level of trust and an accompanying high level of cybersecurity or privacy responsibilities. ## 4.1.5. Acquiring Learning Materials From External Sources CPLP managers should evaluate available materials from a variety of external sources, including federal programs and repositories, industry vendors, and academic institutions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Building a Cybersecurity and Privacy Learning Program."}]}
{"id": "nist_01474", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Section 48) - 3.9.1e Conduct [ Assignment: organization-defined enhanced personnel screening ] for individuals and reassess individual positions and access to CUI [ Assignment: organization-defined frequency ]. Personnel security is the discipline that provides a trusted workforce based on an evaluation or assessment of conduct, integrity, judgment, loyalty, reliability, and stability. The extent of the vetting is commensurate with the level of risk that individuals could bring about by their position and access to CUI. For individuals accessing Federal Government facilities and systems, the Federal Government employs resources, information, and technology in its vetting processes to ensure a trusted workforce. These screening processes may be extended all or in part to persons accessing federal information, including CUI that is resident in nonfederal systems and organizations through \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ contractual vehicles or other agreements established between federal agencies and nonfederal organizations. Examples of enhanced personnel screening for security purposes include additional background checks. Personnel reassessment activities reflect applicable laws, executive orders, directives, policies, regulations, and specific criteria established for the level of access required for assigned positions. Damage-Limiting Operations. See [SP 800-160-2]: [ Preclude (Expunge); Impede (Exert)]. If adverse information develops or is obtained about an individual with access to CUI which calls into question whether the individual should have continued access to systems containing CUI, actions are taken (e.g., preclude or limit further access by the individual, audit actions taken by the individual) to protect the CUI while the adverse information is resolved. Damage-Limiting Operations.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_01475", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.2.7 PR.AC-7: Users, devices, and other assets are authenticated (e.g., singlefactor, multifactor) commensurate with the risk of the transaction (e.g., individuals' security and privacy risks and other organizational risks) according to NIST Securing Property Management Systems According to Securing Property Management Systems, 5.2.7 PR.AC-7: Users, devices, and other assets are authenticated (e.g., singlefactor, multifactor) commensurate with the risk of the transaction (e.g., individuals' security and privacy risks and other organizational risks): Authentication that is commensurate with the risk of the transaction is an intrinsic part of the example implementation. Transactions/users/systems/applications are authenticated based upon the level of risk. Based upon configured policies, the access control platform, TDi ConsoleWorks 5.2-0u1, determines what level of authentication is required for a particular request as determined by the risk level associated.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, sso. Contains security framework guidance for authentication systems. Source: Securing Property Management Systems."}]}
{"id": "nist_01476", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog? Discussion: Data backups must be made to support IoT device customers' organizational requirements and as required by each organization's applicable laws, executive orders, directives, regulations, or other legal requirements regarding specific categories of information (e.g., personal health information). Manufacturers can provide education explaining and/or demonstrating how to back-up the data collected, derived from, stored, transmitted and/or processed by the IoT device, in addition to the IoT device system-level information including, if applicable, system state information, operating system software, middleware, application software, and licenses.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog."}]}
{"id": "nist_01477", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automation Support for Security Control Assessments_ Software Asset Management say about Determination Statement 1? According to Automation Support for Security Control Assessments_ Software Asset Management, Determination Statement 1: | Determination Statement ID | Determination Statement Text | |------------------------------|----------------------------------------------------------------------------------------------------------------------------| | CM-11(b){1} | Determine if the organization: enforces software installation policies through [Assignment: organization-defined methods]. |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_01478", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AU-09(07) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control AU-09(07): PROTECTION OF AUDIT INFORMATION | STORE ON COMPONENT WITH DIFFERENT OPERATING SYSTEM ASSESSMENT OBJECTIVE: Determine if:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01479", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT) provide? (Section 366) Food and Drug Administration | | FDIS | Final Draft International Standard | | FIDO | Fast Identity Online | | FIPS | Federal Information Processing Standard | | GCMP | Galois/Counter Mode Protocol | | GSMA | Groupe Speciale Mobile Association | | GW | Gateway | | EHR | Electronic Health Records | | HIPAA | Health Insurance Portability and Accountability Act of 1996 | | HIT | Health Information Technology | | HITRUST | Health Information Trust Alliance | | HL7 | Health Level 7 | | HTTP | Hypertext Transfer Protocol | | HVAC | Heating, Ventilation, and Air Conditioning | | IACS | Industrial Automation and Control Systems | | ICS | Industrial Control Systems | ICT Information and Communications Technology IDMEF Intrusion Detection Message Exchange Format IEC International Electrotechnical Commission IEEE Institute of Electrical and Electronics Engineers IETF Internet Engineering Task Force IICSWG Interagency International Cybersecurity Standardization Working Group IIC Industrial Internet Consortium IODEF Incident Object Description Exchange Format IoT Internet of Things IPv6 Internet Protocol version 6 ISA International Society of Automation ISMS Information Security Management Systems ISO International Organization for Standardization IT Information Technology ITS JPO Intelligent Transportation System Joint Program Office", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_01480", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Description according to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog? Description: Ability to establish controls for the connections made to the IoT device.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog."}]}
{"id": "nist_01481", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is https according to Recommendations for Key-Encapsulation Mechanisms? https: //doi.org/10.6028/NIST.SP.800-108r1-upd1", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendations for Key-Encapsulation Mechanisms."}]}
{"id": "nist_01482", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Stateful Hash-Based Signature Schemes say about 9.3 Revocation? (Part 3) According to Recommendation for Stateful Hash-Based Signature Schemes, 9.3 Revocation: | | [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 | |-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [9] | Gen\u00eat 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 | | [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 | | [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 | | [12] | Buchmann J, Dahmen E, Hulsing A (2011) XMSS - A Practical Forward Secure Signature Scheme based on Minimal Security Assumptions . Cryptology ePrint Archive , Report 2011/484. https://eprint.iacr.org/2011/484.pdf | | [13] | Bruinderink LG, H\u00fclsing A (2016) 'Oops, I did it again' - Security of One- Time Signatures under Two-Message Attacks. Cryptology ePrint Archive , Report 2016/1042.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Stateful Hash-Based Signature Schemes."}]}
{"id": "nist_01483", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2016 NIST_ITL Cybersecurity Program Annual Report say about NISTIR 8074 (2 volumes)? According to 2016 NIST_ITL Cybersecurity Program Annual Report, NISTIR 8074 (2 volumes): Volume 1: Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01484", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-7 in Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments? (Part 150) Control CM-7: nected to the ESXi host run the following command: Get-VMHost | Get-AdvancedSetting -Name Syslog.global.logHost If Syslog.global.logHost is not set to a site-specific syslog server, this is a finding. | udp://sfo01vrli01.s fo01.rainpole.lo- cal:514 | | CCE- 8447 0-4 | NIST800 53-VI- ESXi- CFG- 00165 | Built-in | ESXi | From a PowerCLI command prompt, while connected to the ESXi host run the following command: Get-VMHost | Get-AdvancedSetting -Name Security.AccountUnlockTime If Security.AccountUnlockTime is not set to 900, this is a finding. | 900 | | CCE- 8447 1-2 | NIST800 53-VI- ESXi- CFG- 00166 | Built-in | ESXi | From a PowerCLI command prompt, while connected to the ESXi host run the following command: Get-VMHost | Get-AdvancedSetting -Name Config.HostAgent.plugins.solo.enableMob If Config.HostAgent.plugins.solo.enableMob is not set to false, this is a finding. | FALSE | | CCE- 8447 2-0 | NIST800 53-VI- ESXi- CFG- 00167 | Built-in | ESXi | From a PowerCLI command prompt, while connected to the ESXi host run the following command: Get-VMHost | Get-AdvancedSetting -Name Config.HostAgent.plugins.hostsvc.esxAdminsGroup For systems that do not use Active Directory and have no local user accounts, other than root, dcui, and/or vpxuser, this is not applicable.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments."}]}
{"id": "nist_01485", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Stateless Hash-Based Digital Signature Standard say about 3.1 Additional Requirements? (Part 1) According to Stateless Hash-Based Digital Signature Standard, 3.1 Additional Requirements: 3.1 Additional Requirements This section specifies requirements for cryptographic modules that implement SLH-DSA. Section 3.2 discusses issues that implementers of cryptographic modules should take into consideration but that are not requirements. SP 800-89, Recommendation for Obtaining Assurances for Digital Signature Applications [3], specifies requirements that apply to the use of digital signature schemes. Randomness generation. SLH-DSA key generation (Algorithm 21) requires the generation of three random \ud835\udc5b -byte values: PK .seed, SK .seed, and SK .prf, where \ud835\udc5b is 16, 24, or 32, depending on the parameter set. For each invocation of key generation, each of these values shall be a fresh (i.e., not previously used) random value generated using an approved random bit generator (RBG), as prescribed in SP 800-90A, SP 800-90B, and SP 800-90C [14, 15, 16]. Moreover, the RBG used shall have a security strength of at least 8\ud835\udc5b bits. See Table 2 for the value of \ud835\udc5b for each parameter set. Destruction of sensitive data. Data used internally by key generation and signing algorithms in intermediate computation steps could be used by an adversary to gain information about the private key and thereby compromise security. The data used internally by verification algorithms is similarly sensitive for some applications, including the verification of signatures that are used as bearer tokens (i.e., authentication secrets) or signatures on plaintext messages that are intended to be confidential. Intermediate values of the verification algorithm may reveal information about its inputs (i.e., the message, signature, and public key), and in some applications, security or privacy requires one or more of these inputs to be confidential. Therefore, implementations of SLH-DSA shall ensure that any local copies of the inputs and any potentially sensitive intermediate data are destroyed as soon as they are no longer needed. Key checks.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Stateless Hash-Based Digital Signature Standard."}]}
{"id": "nist_01486", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.2.5.3 ArcSight Content according to NIST Situational Awareness for Electric Utilities According to Situational Awareness for Electric Utilities, 3.2.5.3 ArcSight Content: - Filter for any of the following: - ArcSight Category events: - /Modify/Configuration - /Found/Misconfigured - tftp protocol - tftp port - Filter for following ArcSight Category Device Groups: - /Firewall - /Network Equipment - /VPN - /IDS - or Category Object: - /Network - Data Monitor and Dashboard to display results of the above", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Situational Awareness for Electric Utilities."}]}
{"id": "nist_01487", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain that are addressed are: according to NIST Technology Assessment_ Methods for Measuring the Level of Computer Security According to Technology Assessment_ Methods for Measuring the Level of Computer Security, that are addressed are:: internal audit administrative security physical security standards processing security operating system security software security data base security communications security applications security Each of these ten areas has then been broken out into a comprehensive set of four to seven subtopics. The questionnaires (checklists) developed in DPSE address numerous relevant questions in each of the subtopic areas.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technology Assessment_ Methods for Measuring the Level of Computer Security."}]}
{"id": "nist_01488", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices say about Availability? According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Availability: The availability impact level is based on the specific mission and the data supporting that mission, not on the time required to re-establish access to subsidies information. Subsidies processes are generally tolerant of delay. In most cases, disruption of access to subsidies information can be expected to have only a limited adverse effect on agency operations, agency assets, or individuals. Recommended Availability Impact Level: The provisional availability impact level recommended for subsidies information is low .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_01489", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2012 Annual Report? (Part 237) Control HA-3: Exchange Formats Framework (CBEFF) specifieGLYPH(cmap:df00) in national anGLYPH(cmap:df00) international stanGLYPH(cmap:df00)arGLYPH(cmap:df00)s is also proviGLYPH(cmap:df00)eGLYPH(cmap:df00). BioCTS 2012 for ANSI/NIST-ITL 1-2011 is currently designed to support testing of implementations that include any of the RecorGLYPH(cmap:df00) T ypes GLYPH(cmap:df00)efineGLYPH(cmap:df00) in AN-2011, but conformance testing is only performed for the selected Record Types (1, 4, 10, 13, 14, 15, anGLYPH(cmap:df00) 17). Plans exist to extend the test tool to support additional Record Types. Information regarGLYPH(cmap:df00)ing BioCTS 2012 testing architectures, coGLYPH(cmap:df00)e structure, anGLYPH(cmap:df00) other software design details is provided. ## Contacts: Mr. Fernando Podio fernanGLYPH(cmap:df00)o.poGLYPH(cmap:df00)io@nist.gov Mr. Dylan Yaga GLYPH(cmap:df00)ylan.yaga@nist.gov ## NISTIR 7874 , Guidelines for Access Control System Evaluation Metrics Nearly all applications include some form of access control (AC). AC is concerneGLYPH(cmap:df00) with GLYPH(cmap:df00)etermining the alloweGLYPH(cmap:df00) activities of legitimate users, meGLYPH(cmap:df00)iating every attempt by a user to access a resource in the system. AC systems come with a wiGLYPH(cmap:df00)e variety of features anGLYPH(cmap:df00) administrative capabilities, and their operational impact can be significant. In particular , this impact can pertain to administrative and user productivity, as well as to the organization's ability to perform its mission. Therefore, it is reasonable to use quality metrics to verify the mechanical properties of AC systems. This document discusses the administration, enforcement, performance, and support properties of AC mechanisms that are embedded in each AC system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_01490", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Blockchain Networks_ Token Design and Management Overview say about Transaction Mixers :? According to Blockchain Networks_ Token Design and Management Overview, Transaction Mixers :: Transaction mixers are meant to provide transaction untraceability. A first approach consists of users sending equal amounts of a given token to an intermediary who, in return, sends the funds back to other addresses owned by the same users [76]. The intermediary can be a trusted custodian or a non-custodial smart contract vault. Another approach to transaction mixing aggregates transactions to obscure the linkage between senders and recipients, as in CoinJoin [77].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain Networks_ Token Design and Management Overview."}]}
{"id": "nist_01491", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Report on the Privilege (Access) Management Workshop say about Definitions and Standards? (Part 1) According to A Report on the Privilege (Access) Management Workshop, Definitions and Standards: Definitions and Standards The ability to control access to sensitive data in accordance with policy is a fundamental security requirement. Definitions enable discourse and standards facilitate implementation in support of enterprise-level access management and privilege management in particular. Definitions generally in use, as in NISTIR-7298 Glossary of Key Information Security Terms and those explicitly referenced in Annex A: Authorization and Attributes Glossary, serve the purpose of effective discourse. However, no generally accepted definition of privilege management appears to be in use. The Identity, Credential, and Access Management (ICAM) Subcommittee of the Federal Information Security &amp; Identity Management Committee is developing implementation guidance for access management, which includes a draft definition of privilege management, as follows: 'Privilege Management is the definition and management of policies and processes that define the ways in which the user is provided access rights to enterprise systems. It governs the management of the data that constitutes the user's privileges and other attributes, including the storage, organization and access to information in directories.' [FICAM-09] This definition is in accord with the view taken in this report; some architectural details in the referenced document relative to privilege management differ. Both this report and the referenced document view privilege management as one part of a larger access management capability. The eXtensible Access Control Markup Language (XACML 10 ), an OASIS 11 standard for managing access control policy, provides some of what is needed to support enterprise-level privilege management. It includes a policy language and a query language that results in a Permit, Deny, Intermediate (error in query), or Not Applicable response.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization, identity management. Contains security framework guidance for authentication systems. Source: A Report on the Privilege (Access) Management Workshop."}]}
{"id": "nist_01492", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Security-Focused Configuration Management of Information Systems say about MEMBERSHIP? According to Guide for Security-Focused Configuration Management of Information Systems, MEMBERSHIP: &lt;List the members of this CCB. The CCB typically includes representatives from program management, project management, software engineering, hardware engineering, testing, documentation, customer support, and marketing. One individual is designated as the CCB Chair. Keep the CCB as small as possible, to facilitate its ability to make rapid decisions, but make sure that the critical perspectives are represented.&gt;", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_01493", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-12 in Engineering Trustworthy Secure Systems? (Part 104) Control AM-12: of the element. This approach forces the system designer to assume that things will not go right and to rigorously seek evidence that demonstrates the effectiveness of the design when things go wrong. Considerations for system element non-performance include: - -An expectation that elements will behave and produce outcomes that are inconsistent with their design intent - -The constraints, assumptions, and preconditions that are associated with achieving threshold performance - -Intentional and unintentional events and conditions, typically referred to by terms like fault, error, failure, and compromise ## References: [2] [21] [50] ## E.30. Trustworthy System Control Principle: The design for system control functions conforms to the properties of the generalized reference monitor. Note: The trustworthy system control principle reflects the generalization of the reference monitor concept to provide a uniform design assurance basis for trustworthy system control mechanisms or constraint-enforcing mechanisms that compose to provide system control functions. 84 Adapted from a statement made by John Rushby, SRI International, about the need for software to be treated as 'guilty until proven innocent' at a Layered Assurance Workshop (LAW). The reference monitor concept (Section D.4.2) is a foundational access control concept for secure system design. It is defined as a trustworthy abstract machine that mediates all accesses to objects by subjects [38]. As a concept for an abstract machine, the reference monitor does not address any specific implementation. A reference validation mechanism, which is a combination of hardware and software, realizes the reference monitor concept to provide the access mediation foundation for a secure system [37].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_01494", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Cryptochecksum according to Securing Wireless Infusion Pumps in Healthcare Delivery Organizations? Cryptochecksum: 9ffa4947d875e0c501e036c54e80ee93", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Wireless Infusion Pumps in Healthcare Delivery Organizations."}]}
{"id": "nist_01495", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to Computer Security Division 2009 Annual Report? http: //csrc.nist.gov/groups/SMA/forum/", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2009 Annual Report."}]}
{"id": "nist_01496", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain e. GUIDANCE FOR CALCUUATINQ SOFTWARE AND DATA REPLACEMENT COSTS: according to NIST U.S. Department of Energy Risk Assessment Methodology According to U.S. Department of Energy Risk Assessment Methodology, e. GUIDANCE FOR CALCUUATINQ SOFTWARE AND DATA REPLACEMENT COSTS:: - For \"Off-the-shelf\" Software Prices: - For Software and Data Development Costs: - -Consult computer catalogs and advertisements, as well as government price schedules and local vendor price lists available from your organization's computer support group or Procurement Office - Consult contract labor cost rates available from the Procurement Office or the contract's COTR OR - -Develop the total cost by multiplying approx, hours spent times average labor cost per hour. Accepted labor costs for your use are provided: - \u00b7 Clerclal: $5-10/hr. - \u00b7 Junior Professional or Programmer: .. Senior Professional or Programmer: - Approximate No. of work hours per: - (Holidays and weekends are not - Included) - 1 Year: 2,080 6 Months: 1,040 1 Month: 170 - . Personnel Management - . Manufacturing/Control - . Mathematics/Statistical - . Security - . Training $1 5-20/hr. $20-30/hr.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: U.S. Department of Energy Risk Assessment Methodology."}]}
{"id": "nist_01497", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Card Technology Developments and Gap Analysis Interagency Report say about SESSION: SECURITY AND PRIVACY ISSUES? (Part 3) According to Card Technology Developments and Gap Analysis Interagency Report, SESSION: SECURITY AND PRIVACY ISSUES: ard technology with a second technology which is completely different to the chip-card technology. The idea is to combine diffractive optical technology with the state of the art chip card technology. Technology and Integration: The idea is to have a diffractive optical technology, a Kinegram\u00ae, and combine it with the state of the art chip card technology. The secret is to combine these two technologies, so that the optical technology enhances the chip-card technology. We want to impart physical security and additional logical security. Security: Physical security is important, while it allows you to say this chip card is real, this is not a copy of the chip card. Security and Integration: The problem is that the information on how to attack chip cards is very easily disseminated. We enhance the security measures for chip cards by adding a non-holographic diffraction technology. The Kinegram\u00ae itself allows quick and easy authentication as a first line feature and the machine-verifiable Kinechip\u00ae enhances the physical and logic security of the chip card. Security: We can classify three main threats against the components of chip card security: data manipulation, re-engineering of chip cards and stolen secret keys. Requirement : The Kinechip\u00ae is used to secure specific data in the chip card; this specified data will be constant over the lifetime of the card, e.g. fingerprint data or personal data. You take this constant data, apply an encryption algorithm to this data to get a digital certificate, which is then stored permanently in the diffractive linear code of the Kinechip\u00ae. This digital certificate which is in the diffractive linear code of the Kinechip\u00ae can be any length up to 1,000 bits. Typically 80 - 160 bits are used in the digital certificate of the Kinechip\u00ae. Security: We use an irreversible process, laser ablation, to write the data. You cannot change these data bits from a '1' to a '0' or from a '0' to a '1'; you can erase a data bit (e.g.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Card Technology Developments and Gap Analysis Interagency Report."}]}
{"id": "nist_01498", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) provide? (Section 34) | | | | 112 | | 11.1.1 Review of Third-Party Testing and Verification of Test | 11.1.1 Review of Third-Party Testing and Verification of Test | 11.1.1 Review of Third-Party Testing and Verification of Test | | | | Results......................................................................................113 | | 11.1.2 Architectural Review of System Design ....................................114 11.1.3 Functional and Security Testing................................................115 11.1.4 Penetration Testing...................................................................115 Periodic Security Review ............................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_01499", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Metrics and Methodology for Hardware Security Constructs provide? (Section 24) ig. 3. Resource mapping of CAPEC standard attack patterns <!-- image --> For example, white-box access is required to launch white-box reverse engineering attack 167 against an exploitable weakness. However, black-box access is needed to launch black-box reverse engineering attack 189. If there is a higher probability for an adversary to have blackbox access than white-box access, mitigation of 189 should be a higher priority than mitigation of 167. This work addresses the critical issue of threats that arise from hardware weaknesses by presenting a comprehensive methodology to quantify the vulnerabilities that these weaknesses introduce and the potential threats from various attacks that can exploit them. The methodology helps designers understand different hardware weaknesses and attack patterns in order to prioritize and plan effective mitigation efforts. Given 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. - [1] Kocher P, Horn J, Fogh A, Genkin D, Gruss D, Haas W, Hamburg M, Lipp M, Mangard S, Prescher T, Schwarz M, Yarom Y (2019) Spectre attacks: Exploiting speculative execution. 2019 IEEE Symposium on Security and Privacy (SP 2019) (IEEE, San Francisco, California), pp 1-19.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, adversary. Contains technical security guidance that could inform defensive posture. Source: Metrics and Methodology for Hardware Security Constructs."}]}
{"id": "nist_01500", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Recommended Confidentiality Impact Level according to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices? Recommended Confidentiality Impact Level: The provisional confidentiality impact level recommended for formula grants information is low .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_01501", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Framework Version 1.1 Manufacturing Profile provide? (Section 78) AC) | PR.AC-7 | Perform a risk assessment on manufacturing user transactions to document and implement the authentication mechanisms required (e.g. single- or multi-factor) for each transaction. | IA-1, IA-2, IA-4, IA-5, IA-8 | | PROTECT | Identity Management, Authentication and Access Control (PR.AC) | PR.AC-7 | Moderate Impact | | | PROTECT | | PR.AC-7 | Perform a risk assessment on manufacturing system transactions and the associated user, device, or other asset authentication mechanism to document and implement the authentication mechanisms required (e.g. single- or multi-factor) for each transaction. | IA-1, IA-2, IA-4, IA-5, IA-8 | | PROTECT | | PR.AC-7 | Implement multi-factor or certificate-based authentication for transactions within the manufacturing systems determined to be critical.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, identity management. Contains security framework guidance for authentication systems. Source: Cybersecurity Framework Version 1.1 Manufacturing Profile."}]}
{"id": "nist_01502", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Module-Lattice-Based Digital Signature Standard say about 3.6.3 Intermediate Values? (Part 1) According to Module-Lattice-Based Digital Signature Standard, 3.6.3 Intermediate Values: 3.6.3 Intermediate Values The data used internally by the key generation and signing algorithms in intermediate computation steps could be used by an adversary to gain information about the private key and thereby compromise security. The data used internally by verification algorithms is similarly sensitive for some applications, including the verification of signatures that are used as bearer tokens (i.e., authentication secrets) or the verification of signatures on plaintext messages that are intended to be confidential. Intermediate values of the verification algorithm may reveal information about its inputs (i.e., the message, signature, and public key), and in some applications, security or privacy requires one or more of these inputs to be confidential. Therefore, implementations of ML-DSA shall ensure that any potentially sensitive intermediate data is destroyed as soon as it is no longer needed. Two particular cases in which implementations may refrain from destroying intermediate data are: 1. The seed \ud835\udf09 generated in step 1 of ML-DSA . KeyGen can be stored for the purpose of later expansion 3 In addition, when signing is deterministic, there is leakage through timing side channels of information about the message but not the private key). If the signer does not want to reveal the message being signed, hedged signatures should be used (see Section 3.2 in [6]). using ML-DSA . KeyGen \\_ internal . As the seed can be used to compute the private key, it is sensitive data and shall be treated with the same safeguards as a private key. 2. The matrix \ud835\udc00 \u0302 generated in step 3 of ML-DSA . KeyGen \\_ internal can be stored so that it need not be recomputed in later operations. Likewise, the matrix \ud835\udc00 \u0302 generated in step 5 of the verification algorithm ML-DSA . Verify \\_ internal can also be stored. In either case, the matrix \ud835\udc00 \u0302 is data that is easily computed from the public key and does not require any special protections.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Module-Lattice-Based Digital Signature Standard."}]}
{"id": "nist_01503", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2016 NIST_ITL Cybersecurity Program Annual Report say about F O R M O R E I N F O R M AT I O N , S E E :? According to 2016 NIST_ITL Cybersecurity Program Annual Report, F O R M O R E I N F O R M AT I O N , S E E :: BioCTS - Biometric Conformance Test Tools: https:/ /www.nist.gov/itl/csd/biometrics/biometricconformance-test-software-biocts BioCTS for ANSI/NIST-ITL User Guide: https:/ /csrc.nist.gov/Projects/Biometric-Conformance-TestSoftware/publications", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01504", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters say about 3.2.2.1. Curve25519? According to Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters, 3.2.2.1. Curve25519: The elliptic curve Curve25519 is the Montgomery curve MA , B defined over the prime field GF( p ) with p = 2 255 -19 and parameters A = 486662 and B = 1 [RFC\\_7748]. This curve has order h \u22c5 n , where h = 8, and n is a prime number. For this curve, A 2 -4 is not a square in GF( p ), whereas A +2 is. The quadratic twist of this curve has order h 1 \u22c5 n 1, where h 1 = 4, and n 1 is a prime number. This curve has domain parameters D = ( p , h , n , Type , A , B , G ), where the Type is 'Montgomery curve,' and the other parameters are defined as follows: ``` p : 2 255 -19 (= 0x7fffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffed ) h : 8 ``` ``` n : 72370055773322622139731865630429942408\\ 57116359379907606001950938285454250989 (=2 252 + 0x14def9de a2f79cd6 5812631a 5cf5d3ed ) tr : -221938542218978828286815502327069187962 (=( p+ 1) h \u22c5 n = -0xa6f7cef5 17bce6b2 c09318d2 e7ae9f7a ) A : 486662 B : 1 Gu : 9 (= 0x9 ) Gv : 43114425171068552920764898935933967039\\ 370386198203806730763910166200978582548 (= 0x5f51e65e 475f794b 1fe122d3 88b72eb3 6dc2b281 92839e4d d6163a5d 81312c14 ) ``` Curve25519 is isomorphic to the curve W-25519 specified in Section 3.2.2.1 and is birationally equivalent to the curve Edwards25519. See Appendices B.1 and B.2 for more details.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters."}]}
{"id": "nist_01505", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PE-09(02) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control PE-09(02): automa\ue000c voltage controls for <PE-09(02)_ODP cri\ue000cal system components> are employed. POTENTIAL ASSESSMENT METHODS AND OBJECTS:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01506", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Biometric Specifications for Personal Identity Verification say about Table of Contents? (Part 28) According to Biometric Specifications for Personal Identity Verification, Table of Contents: Minimum accuracy specifications.........................................................................................................39 | | 10.1 | Scope...........................................................................................................................................................39 | Scope...........................................................................................................................................................39 | | 10.2 | Approach.....................................................................................................................................................39 | Approach.....................................................................................................................................................39 | | 10.3 | Operating threshold specification .............................................................................................................39 | Operating threshold specification .............................................................................................................39 | | 10.4 | Conformance to accuracy specifications...................................................................................................40 | Conformance to accuracy specifications...................................................................................................40 | | | 10.4.1 Use of multiple samples with fixed thresholds...........................................................................40 Agency consideration of false rejection performance..............................................................................40 | 10.4.1 Use of multiple samples with fixed thresholds...........................................................................40 Agency consideration of false rejection performance..............................................................................40 | | 11.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Biometric Specifications for Personal Identity Verification."}]}
{"id": "nist_01507", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Derived PIV Application and Data Model Test Guidelines provide? (Section 255) | | Issuer Documentation | None. | |------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Precondition(s) | \u2022 A token with the Derived PIV Application is inserted into an appropriate token reader. \u2022 Suitable drivers have been loaded between the test system and an instance of the reader. \u2022 A Derived PIV Authentication certificate is present within the Derived PIV Application. | | Test Scenario | 1. Send the SELECT command with \u2022 AID == 'A0 00 00 03 08 00 00 20 00 01 00' 2. Send the GET DATA command with \u2022 Data field of the command containing the tag ('5FC105') of the X.509 Certificate for Derived PIV Authentication data object 3. Extract the the value of the authorityInfoAccess extension from the certificate. | | Expected Result(s) | 1. From Step 1, the command returns the application property template with the status word '90 00'. 2. From Step 2, the command the requested data object along with the returns status word '90 00'. 3. From Step 3, an accessMethod containing id-ad-ocsp (1.3.6.1.5.5.7.48.1) is present that contains an accessLocation of type uniformResourceIdentifier where the scheme is 'http' (not 'https').", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_01508", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Securing Public Web Servers say about 9.4.2 Penetration Testing? According to Guidelines on Securing Public Web Servers, 9.4.2 Penetration Testing: 'Penetration testing is security testing in which evaluators attempt to circumvent the security features of a system based on their understanding of the system design and implementation' [NISS99]. The purpose of penetration testing is to exercise system protections (particularly human response to attack indications) by using common tools and techniques developed by attackers. This testing is highly recommended for complex or critical systems. Penetration testing can be an invaluable technique to any organization's information security program. However, it is a very labor-intensive activity and requires great expertise to minimize the risk to targeted systems. At a minimum, it may slow the organization's network response time because of network mapping and vulnerability scanning. Furthermore, the possibility exists that systems may be damaged or rendered inoperable in the course of penetration testing. Although this risk is mitigated by the use of experienced penetration testers, it can never be fully eliminated. Penetration testing does offer the following benefits [NIST02b]: - GLYPH&lt;c=31,font=/IEIOAF+Webdings&gt; Tests the network using the same methodologies and tools employed by attackers - GLYPH&lt;c=31,font=/IEIOAF+Webdings&gt; Verifies whether vulnerabilities exist - GLYPH&lt;c=31,font=/IEIOAF+Webdings&gt; Goes beyond surface vulnerabilities and demonstrates how these vulnerabilities can be exploited iteratively to gain greater access - GLYPH&lt;c=31,font=/IEIOAF+Webdings&gt; Demonstrates that vulnerabilities are not purely theoretical - GLYPH&lt;c=31,font=/IEIOAF+Webdings&gt; Provides the 'realism' necessary to address security issues - GLYPH&lt;c=31,font=/IEIOAF+Webdings&gt; Allows for testing of procedures and susceptibility of the human element to social engineering.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit, penetration test. Contains technical security guidance that could inform defensive posture. Source: Guidelines on Securing Public Web Servers."}]}
{"id": "nist_01509", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification say about National Institute of Standards and Technology Interagency or Internal Report 7849 40 pages (March 2014)? According to A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification, National Institute of Standards and Technology Interagency or Internal Report 7849 40 pages (March 2014): 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. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. All NIST Computer Security Division publications, other than the ones noted above, are available at ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification."}]}
{"id": "nist_01510", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Privacy Controls for Information Systems and Organizations provide? (Section 646) , system components, and system services may deviate significantly from the functional and design specifications created during the requirements and design stages of the system development life cycle. Therefore, updates to threat modeling and vulnerability analyses of those systems, system components, and system services during development and prior to delivery are critical to the effective operation of those systems, components, and services. Threat modeling and vulnerability analyses at this stage of the system development life cycle ensure that design and implementation changes have been accounted for and that vulnerabilities created because of those changes have been reviewed and mitigated. Related controls: PM-15, RA-3, RA-5. (3) DEVELOPER TESTING AND EVALUATION | INDEPENDENT VERIFICATION OF ASSESSMENT PLANS AND EVIDENCE (a) Require an independent agent satisfying [Assignment: organization-defined independence criteria] to verify the correct implementation of the developer security and privacy assessment plans and the evidence produced during testing and evaluation; and CHAPTER THREE PAGE 277 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ (b) Verify that the independent agent is provided with sufficient information to complete the verification process or granted the authority to obtain such information. Discussion: Independent agents have the qualifications\u2014including the expertise, skills, training, certifications, and experience\u2014to verify the correct implementation of developer security and privacy assessment plans.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01511", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Secure Web Services provide? (Section 91) particular attribute. The relying party uses the information supplied by the asserting party to make decisions, including, but not limited to, whether or not to trust the asserting party's assertion. By trusting the asserting party's information, the relying party can provide services without requiring the principal to authenticate again. SAML assertions contain a number of required elements (except where otherwise noted): - ID . Uniquely identifies this assertion - IssueInstant . Timestamp indicating when the SAML assertion was created - Issuer . Information about the entity that created the assertion - Signature . Digital signature of the SAML assertion (optional) - Subject . Information about the entity to which this assertion applies (optional) - Conditions . Information used to determine the validity of the assertion, such as a validity period (optional) - Advice . Information that may be useful in processing the assertion (optional) - Statements . SAML statements can provide information about subject authentication, authorization decision or attributes. Additional types of statements can be defined by an extension. (optional) Figure 3-8 shows a SAML assertion containing a single authentication statement. This assertion indicates that John Doe was authenticated on January 15, 2007 at 14:15:07 UTC via X.509 certificate and that this assertion is valid for one hour from the initial time of authentication. ``` <saml:Assertion xmlns:saml='urn:oasis:names:tc:SAML:2.0:assertion' Version=\"2.0\" IssueInstant=\"2007-01-15T14:15:07Z\"> <saml:Issuer Format=urn:oasis:names:SAML:2.0:nameid-format:entity> </saml:Issuer> <saml:Subject> <saml:NameID Format=\"urn:oasis:names:tc:SAML:1.1:nameid-format:x509SubjectName\"> CN=Doe.John, OU=NIST, O=U.S.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services."}]}
{"id": "nist_01512", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.21.1.6 Categorization File according to NIST Situational Awareness for Electric Utilities According to Situational Awareness for Electric Utilities, 2.21.1.6 Categorization File: - Create a .csv file containing the text below, and copy this file to /opt/arcsight/&lt;connector directory&gt;/current/user/agent/acp/categorizer/current/&lt;deviceproduct&gt;/deviceproduct.csv | event. | set.event. | set.event. | set.event. | set.event. | set.event. | set.event. | |----------|--------------|--------------|--------------|--------------|--------------|--------------| | device | category | category | category | category | category | category | | Product | Object | Behavior | Technique | DeviceGroup | Significance | Outcome | CyberLens /Host /Found /Traffic Anomaly /IDS/Network /Informational /attempt", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Situational Awareness for Electric Utilities."}]}
{"id": "nist_01513", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Labels for Open Systems_ an Invitational Workshop provide? (Section 64) associations. While a CIPSO, labeling individual IP datagrams, is an important element in supporting rule-based security policies, it is not the only element and its use will not always be obligatory. The primary need for CIPSO per-datagram labeling arises in cases when an entity needing to make an RBAC authorization decision is unable to determine the access class of a datagram based on state information available to the determinin g entity; clear examples include: - connectionless communications - connection-oriented communications in which data of varying access classes may be carried on a single connection - mediation of RBAC policies by intermediate systems (e.g., routers) Many entities and channels will have fixed access class designations, allowing implicit labeling. In some other cases, implicit labeling can be achieved on a per-association basis, based on bindings established in the course of association initiation procedures. Further, it is important to remember that customer requirements for security do not always imply requirements for rule-based security policies. Identity-based policies, at the granularity of hosts and/or users, can satisfy many customer needs in and of themselves, in a decentralized fashion without need for the centralized infrastructure needed to support RBAC. Many customer requirements will be best addressed with hybrid approaches employing both rule-based and identity-based policies. In the commercial environment, labeling authorities correspond to customer organizations, organizational subunits, or established consortia thereof (e.g., the set of corporate participants in a joint venture). Labeling authorities define and coordinate the infrastructure (assignment of clearances to entities and of access class designations to data) which underlies RBAC. Related observations: - The number of labeling authorities is large and unpredictable.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Security Labels for Open Systems_ an Invitational Workshop."}]}
{"id": "nist_01514", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Managing Information Security Risk_ Organization, Mission, and Information System View say about D.12 INFORMATION SYSTEM SECURITY ENGINEER? According to Managing Information Security Risk_ Organization, Mission, and Information System View, D.12 INFORMATION SYSTEM SECURITY ENGINEER: The information system security engineer is an individual, group, or organization responsible for conducting information system security engineering activities. Information system security engineering is a process that captures and refines information security requirements and ensures that the requirements are effectively integrated into information technology component products and information systems through purposeful security architecting, design, development, and configuration. Information system security engineers are an integral part of the development team (e.g., integrated project team) designing and developing organizational information systems or upgrading legacy systems. Information system security engineers employ best practices when implementing security controls within an information system including software engineering methodologies, system/security engineering principles, secure design, secure architecture, and secure coding techniques. System security engineers coordinate their security-related activities with information security architects, senior information security officers, information system owners, common control providers, and information system security officers.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Managing Information Security Risk_ Organization, Mission, and Information System View."}]}
{"id": "nist_01515", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain system development life cycle according to NIST Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, system development life cycle: The scope of activities associated with a system, encompassing the system's initiation, development and acquisition, implementation, operation and maintenance, and ultimately its disposal. [SP80034r1, adapted]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_01516", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-1 in Derived Personal Identity Verification (PIV) Credentials? (Part 30) Control AC-1: ng mechanisms, remote wipe, and other mobile device security best practices to mitigate risk of a stolen device. Further- more, multifactor authentication prevents unauthorized use of the private key. | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | Authenticator Threats/Attacks | Examples | Applicability to DPC | |---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Duplication | A software PKI authenticator (pri- vate key) is copied. | A DPC stored in a software-based container on a mobile device could be copied from the device. Use device sandboxing mecha- nisms, cryptographic techniques, and mal- ware detection mechanisms as mitigation. | | Eavesdropping | Memorized secrets are obtained by watching keyboard entry.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_01517", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Privacy Controls for Information Systems and Organizations provide? (Section 660) within developer organizations. Vulnerability information is available from a variety of public and private sector sources, including the NIST National Vulnerability Database. Related Controls: None. (9) DEVELOPMENT PROCESS, STANDARDS, AND TOOLS | USE OF LIVE DATA [Withdrawn: Incorporated into SA-3(2).] (10) DEVELOPMENT PROCESS, STANDARDS, AND TOOLS | INCIDENT RESPONSE PLAN Require the developer of the system, system component, or system service to provide, implement, and test an incident response plan. Discussion: The incident response plan provided by developers may provide information not readily available to organizations and be incorporated into organizational incident response plans. Developer information may also be extremely helpful, such as when organizations respond to vulnerabilities in commercial off-the-shelf products. Related Controls: IR-8. (11) DEVELOPMENT PROCESS, STANDARDS, AND TOOLS | ARCHIVE SYSTEM OR COMPONENT Require the developer of the system or system component to archive the system or component to be released or delivered together with the corresponding evidence supporting the final security and privacy review. CHAPTER THREE PAGE 283 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ Discussion: Archiving system or system components requires the developer to retain key development artifacts, including hardware specifications, source code, object code, and relevant documentation from the development process that can provide a readily available configuration baseline for system and component upgrades or modifications.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, incident response. Contains technical security guidance that could inform defensive posture. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01518", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2 say about 3.5 Common Platform Enumeration (CPE)? (Part 1) According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2, 3.5 Common Platform Enumeration (CPE): 3.5 Common Platform Enumeration (CPE) This section lists requirements and recommendations for using Common Platform Enumeration (CPE) to express a CPE component of an SCAP source data stream (see Table 12). The Official CPE Dictionary data feed 15 MAY be used by SCAP components to reference CPE names. If use of the Official CPE Dictionary is impractical, a subset of the dictionary MAY be used instead. Creating the reduced official dictionary involves first identifying every CPE in &lt;xccdf:platform&gt; and &lt;cpe2:fact-ref&gt; elements contained within referenced &lt;cpe2:platformspecification&gt; elements in every benchmark in the data stream. Then these CPEs MUST be matched against every entry in the Official CPE Dictionary using the CPE name matching algorithm [CPE-M]. All CPEs matched in the official dictionary with a result of EQUAL or SUPERSET MUST be included in the reduced official dictionary. One or more third-party dictionaries MAY be included in a data stream as well. All such third-party dictionaries SHOULD follow the requirements of the CPE Dictionary specification [CPE-D]. If including an entire third-party dictionary is impractical, a subset of the dictionary MAY be used instead. The reduced dictionary MUST be created using the same procedure outlined for creating a subset of the official dictionary. In all cases, a dictionary component MAY be remote to the data stream collection. Each CPE name [CPE-N] in an &lt;xccdf:platform&gt; or &lt;cpe2:fact-ref&gt; element within an XCCDF document SHALL match at least one CPE entry in a dictionary referenced by the data stream. A match is considered an EQUAL or SUPERSET result when matching the CPE name to a dictionary entry, 15 The Official CPE Dictionary is located at http://nvd.nist.gov/cpe.cfm. as defined in the CPE Name Matching specification [CPE-M]. Only non-deprecated names SHOULD be used.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2."}]}
{"id": "nist_01519", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2005 Annual Report provide? (Section 28) of NIST Special Publication 800-53A, Guide for Assessing the Security Controls in Federal Information Systems , was completed in July 2005 with the final publication expected in March 2006. The guideline will help achieve more secure information systems within the federal government by- - Enabling more consistent, comparable, and repeatable assessments of security controls - Facilitating more cost-effective assessments of security control effectiveness - Promoting a better understanding of the risks to organizational operations, organizational assets, or individuals resulting from the operation of information systems, and - Creating more complete, reliable, and trustworthy information for organizational officials-to support security accreditation decisions and the annual FISMA reporting requirements. Contacts: Dr. Ron Ross (301) 975-5390 ron.ross@nist.gov Mr. Arnold Johnson (301) 975-3247 arnold.johnson@nist.gov P hase II of the FISMA Implementation Project will focus on the development of a program for accrediting public and private sector organizations to provide security certification services for federal agencies. The term 'accreditation' is used in two different contexts in the FISMA Implementation Project. 'Security accreditation' is the official management decision to authorize operation of an information system. 'Organizational accreditation' involves comprehensive proficiency testing and the demonstration of specialized skills in a particular area of interest. A security certification is a comprehensive assessment of the management, operational and technical security controls in an information system, made in support of security accreditation, to determine the extent to which the controls are implemented correctly, operating as intended and producing the desired outcome with respect to meeting the security requirements for the system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2005 Annual Report."}]}
{"id": "nist_01520", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Operational Technology (OT) Security provide? (Section 230) ing execution details may help organizations during the post-incident review process to determine whether any gaps or potential opportunities for improvement in the recovery plan should be considered. Due to the time sensitivity of recovery efforts, organizations may want to consider other techniques (e.g., reviewing logs, reviewing video footage captured during the recovery activities, or interviewing recovery personnel) if capturing execution details impacts safety or increases the time to complete the recovery plan. Supplemental guidance for recovery planning can be found in the following documents: \u2022 NIST SP 800-184, Guide for Cybersecurity Event Recovery \u2022 NIST SP 800-209, Security Guidelines for Storage Infrastructure 6.5.2. Recovery Improvements (RC.IM) As a recovery effort is ongoing, the recovery steps taken should be documented to identify lessons learned. These lessons can be used to improve recovery plans and processes. Supplemental guidance for recovery improvements can be found in the following document: \u2022 NIST SP 800-184, Guide for Cybersecurity Event Recovery 137 NIST SP 800-82r3 September 2023 Guide to Operational Technology (OT) Security 6.5.3. Recovery Communications (RC.CO) Restoration activities are coordinated with internal and external parties. In addition to operational recovery, an organization may need to manage public relations and repair its reputation. Supplemental guidance for recovery communications can be found in the following document: \u2022 NIST SP 800-184, Guide for Cybersecurity Event Recovery OT-Specific Recommendations and Guidance A list of internal and external resources for recovery activities should be developed as part of the recovery planning effort. During an event, this list should be used to get all necessary personnel on-site, as required, to recover within the RTO and RPO.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_01521", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services say about 4.2.4. Information Protection Processes and Procedures Category? (Part 10) According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services, 4.2.4. Information Protection Processes and Procedures Category: 5 CP-1, CP-2, CP-7, CP-10, CP-12, CP13, IR-1, IR-7, IR-8, IR-9, PE-17 NIST SP 800-160 Rev.1 Appendix F.2.6 RTCA 356 5.6.6 USG FRP 1.7.3, 6 | | Protect Information Protection Processes and Procedures | Applicability to PNT | References (PNT-Specific) | |-----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| | Subcategory | fault mode, identify detection and compensation strategies, effects on the computed PNT data, and effects on the applications dependent on the data to determine whether the response and recovery plans are adequate to meet business continuity objectives.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_01522", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for Derived Personal Identity Verification (PIV) Credentials say about 1.1 Background? (Part 1) According to Guidelines for Derived Personal Identity Verification (PIV) Credentials, 1.1 Background: 1.1 Background FIPS 201 originally required that all PIV credentials and associated keys be stored in a PIV Card. While the use of the PIV Card for electronic authentication works well with traditional desktop and laptop computers, it is not optimized for mobile devices. In response to the growing use of mobile devices within the Federal government, FIPS 201 was revised to permit the issuance of an additional credential, a Derived PIV Credential, for which the corresponding private key is stored in a cryptographic module with an alternative form factor to the PIV Card. Derived PIV Credentials leverage the current investment in the PIV infrastructure for electronic authentication and build upon the solid foundation of well-vetted and trusted identity of the PIV cardholder - achieving substantial cost savings by leveraging the identityproofing results that were already performed to issue PIV cards. This document provides the technical guidelines for the implementation of Derived PIV Credentials. The use of a Derived PIV Credential is one possible way to PIV-enable a mobile device. In other cases it may be practical to use the PIV Card itself with the mobile device, using either the PIV Card's contact or contactless interface, rather than issuing a Derived PIV Credential. Mobile devices are generally too small to integrate smart card readers into the device itself, requiring alternative approaches for communicating between the PIV Card and the mobile device. Some of these approaches are possible by today's set of available products. Other, newer technologies are addressed by new guidelines in the existing set of PIV Special Publications. The current solution for PIV enablement directly uses PIV Cards with mobile devices through smart card readers. This has the advantage of avoiding the additional time and expense required to issue and manage Derived PIV Credentials.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Guidelines for Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_01523", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to IPsec VPNs say about 10.6 Post Quantum Key Exchange? (Part 9) According to Guide to IPsec VPNs, 10.6 Post Quantum Key Exchange: ask Force (IETF) Network Working Group), IETF Request for Comments (RFC) 2104. https://doi.org/10.17487/RFC2104 - [48] Frankel S, Herbert H (2003) The AES-XCBC-MAC-96 Algorithm and Its Use With IPsec. (Internet Engineering Task Force (IETF) Network Working Group), IETF Request for Comments (RFC) 3566. https://doi.org/10.17487/RFC3566 - [49] Black D, McGrew D (2008) Using Authenticated Encryption Algorithms with the Encrypted Payload of the Internet Key Exchange version 2 (IKEv2) Protocol. (Internet Engineering Task Force (IETF) Network Working Group), IETF Request for Comments (RFC) 5282. https://doi.org/10.17487/RFC5282 - [50] Viega J, McGrew D (2005) The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP). (Internet Engineering Task Force (IETF) Network Working Group), IETF Request for Comments (RFC) 4106. https://doi.org/10.17487/RFC4106 - [51] Frankel S, Glenn R, Kelly S (2003) The AES-CBC Cipher Algorithm and Its Use with IPsec. (Internet Engineering Task Force (IETF) Network Working Group), IETF Request for Comments (RFC) 3602. https://doi.org/10.17487/RFC3602 - [52] Kent S (2005) Extended Sequence Number (ESN) Addendum to IPsec Domain of Interpretation (DOI) for Internet Security Association and Key Management Protocol (ISAKMP). (Internet Engineering Task Force (IETF)), IETF Request for Comments (RFC) 4304. https://doi.org/10.17487/RFC4304 - [53] Pauly T, Touati S, Mantha R (2017) TCP Encapsulation of IKE and IPsec Packets. (Internet Engineering Task Force (IETF)), IETF Request for Comments (RFC) 8229. https://doi.org/10.17487/RFC8229 - [54] McDonald D, Metz C, Phan B (1998) PF\\_KEY Key Management API, Version 2. (Internet Engineering Task Force (IETF) Network Working Group), IETF Request for Comments (RFC) 2367. https://doi.org/10.17487/RFC2367 - [55] Salim J, Khosravi H, Kleen A, Kuznetsov A (2003) Linux Netlink as an IP Services Protocol.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Guide to IPsec VPNs."}]}
{"id": "nist_01524", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RC-20 in Blockchain Networks_ Token Design and Management Overview? (Part 44) Control RC-20: attribute-based access control, or hybrid/finegrained access control (e.g., a list of authorized users that enables token transfers with different identity verification tiers and transfer limits). For fungible tokens, those restrictions may apply to a user's entire account balance or a portion of it [7]. Sending an unauthorized transaction means that the transaction will fail to execute and the state of the blockchain will remain at its starting point. Note that some publications categorize tokens in two types-'token-based' and 'accountbased'-depending on whether transfers are subject to controls or the representation type used (as discussed in Section 2.1.1) [64]. ## Role-Based Access Control : In role-based access control (see NIST definition [65]), role assignation follows either a top-down approach, where privileged entities act as system owners and directly manage the roles, or a bottom-up approach, where roles are self-assigned by users with predefined conditions and time delays during which system owners may be allowed to cancel new role assignations. Roles are implemented through role manager smart contracts that are integrated with token factory contracts. Smart contract libraries that offer role-based access control have been developed, such as the Open-Zeppelin library [66]. It is also possible to implement roles in blockchains that follow the UTXO model by modifying the input and output parameters in the transaction format [67]. ## Attribute-Based Access Control : In attribute-based access control , an identity management system provides users with token-based attributes or credentials generated either on-chain or off-chain, which they can then use to authenticate themselves and be authorized to call certain account-level operations.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, identity management, token. Contains security framework guidance for authentication systems. Source: Blockchain Networks_ Token Design and Management Overview."}]}
{"id": "nist_01525", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out provide? (Section 70) ll develop a clearinghouse for &lt;organization name&gt; to locate pertinent information about previous incidents, known viruses and worms, known vulnerabilities of systems, and key people to contact. This clearinghouse shall include information about security clearances needed by key computer security and technical personnel at each site. The team shall develop an automated tracking system to track incidents. The Contracting Officer's Technical Representative (COTR) will review the Automated Tracking System and Clearinghouse. At the organizations's discretion, the team shall form cooperative procedures between &lt;organization name&gt; and other federal organizations. Part of the team's task shall be to develop procedures for incident reporting. These procedures define who is contacted during an incident, what kind of information is shared, who performs a particular task, and how subtasks are divided under different types of incidents and conditions. The team shall develop cooperative relationships with vendors to learn of security holes and fixes. The team shall also work with vendors to ensure problems are fixed. The Contractor shall document these cooperative procedures which will be included in the Incident Handling Guidelines, described in Task 5 below. The Contractor shall deliver the Cooperative Procedures Report to the COTR. The team shall develop guidelines for incident handling that both the team and technical personnel at the &lt;organization name&gt; sites can follow. These guidelines shall include managerial as well as technical guidance for event handling and the Cooperative Procedures Report developed in Task 4, The team shall define what an incident is and conditions under which the team becomes involved, These guidelines shall be consistent with the &lt;organization name&gt; policy.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out."}]}
{"id": "nist_01526", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to NIST_SP_800-53r5_Security_Privacy_Controls? Discussion: The plan of action and milestones is a key organizational document and is subject to", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01527", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Evaluating Differential Privacy Guarantees provide? (Section 6) | 3.4.4. | Min/Max Queries . . . . . . . . . . . . . . . . . | 44 | | 3.5. | Machine Learning | . . . . . . . . . . . . . . . . . . . . . | 44 | | 3.6. | . . . . . . | Synthetic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 46 | |----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------| | | 3.7. . . . | Unstructured Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 50 | | 4. Deploying Differential Privacy . . . . . . . . . . . . . . . . . | 4. Deploying Differential Privacy . . . . . . . . . . . . . . . . . | . . . . . . . . . . . . | 51 | | 4.1. | Query . . . . . . | Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 51 | | 4.2. | Trust . . . . . . . | Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 53 | | | 4.2.1. . . | Central Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 55 | | | 4.2.2. . . . | Local Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 56 | | | 4.2.3. | Future Directions: Shuffle and Secure Computation Models . . . | 57 | | 4.3. | Mechanism Challenges | Implementation . . . . . . . . . . . . . . . . . . . . | 58 | | 4.4.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Evaluating Differential Privacy Guarantees."}]}
{"id": "nist_01528", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2012 Annual Report provide? (Section 182) YPH(cmap:df00) strategic CSIRT s, as well as inGLYPH(cmap:df00)ustry knowleGLYPH(cmap:df00)ge repositories. This may incluGLYPH(cmap:df00)e selective use of security automation where applicable. In FY2013, this work will GLYPH(cmap:df00)evelop GLYPH(cmap:df00)raft SP 800-150, Coordinated Computer Security Incident Handling Guidance . Contacts: Mr. Lee BaGLYPH(cmap:df00)ger (301) 975-3176 lee.baGLYPH(cmap:df00)ger@nist.gov Mr. DaviGLYPH(cmap:df00) Waltermire (301) 975-3390 GLYPH(cmap:df00)aviGLYPH(cmap:df00).waltermire@nist.gov The UniteGLYPH(cmap:df00) States Government Configuration Baseline (USGCB) initiative creates security configuration baselines for information technology (IT) products wiGLYPH(cmap:df00)ely GLYPH(cmap:df00)eployeGLYPH(cmap:df00) across the feGLYPH(cmap:df00)eral agencies. The project evolveGLYPH(cmap:df00) from the FeGLYPH(cmap:df00)eral Desktop Core Configuration (FDCC) manGLYPH(cmap:df00)ate originally GLYPH(cmap:df00)escribeGLYPH(cmap:df00) in a March 2007 memoranGLYPH(cmap:df00)um from the U.S. White House Office of Management anGLYPH(cmap:df00) BuGLYPH(cmap:df00)get (MemoranGLYPH(cmap:df00)um M-0711). USGCB helps to improve information security and reduce overall IT operating costs by providing commonly accepteGLYPH(cmap:df00) security configurations for major operating systems. Through the National Checklist Program described in Special Publication (SP) 800-70, National Checklist Program for IT Products: Guidelines for Checklist Users and Developers , a baseline submitter may express interest in submitting a canGLYPH(cmap:df00)iGLYPH(cmap:df00)ate for use in the USGCB program. CSD works with the FeGLYPH(cmap:df00)eral CIO Council's Technology Infrastructure Subcommittee (TIS) to consider the candidate, recommend any changes to the baseline, and coordinate implementation at federal agencies.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_01529", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices provide? (Section 468) Grants involves the allocation of money to States or their subdivisions in accordance with distribution formulas prescribed by law or administrative regulation, for activities of a continuing nature. The recommended provisional security categorization for the formula grants information type is as follows: Security Category = {(confidentiality, Low), (integrity, Low), (availability, Low)} The confidentiality impact level is the effect of unauthorized disclosure of formula grants information on the ability of responsible agencies to allocate money to States or their subdivisions in accordance with distribution formulas prescribed by law or administrative regulation, for activities of a continuing nature. Typically, unauthorized disclosure of most formula grants information will have only a limited adverse effect on agency operations, assets, or individuals. In most cases, information associated with formula grants is public knowledge. Special Factors Affecting Confidentiality Impact Determination : In a few cases, details of programs for which formula grants are awarded may be sensitive (e.g., some Federal/State cooperative programs intended to support Homeland Security operations). This can result in assignment of a moderate or high impact level to such information. Some formula grants information might be classified (hence outside the scope of this guideline). Recommended Confidentiality Impact Level : The provisional confidentiality impact level recommended for formula grants information is low . The integrity impact level is based on the specific mission and the data supporting that mission, not on the time required to detect the modification or destruction of information. Formula grants activities are not generally time-critical and multiple individuals in multiple organizations are usually involved in the grants process. Therefore, the information maintained by all the individuals/agencies is probably necessary to alter a grants decision.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_01530", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Technology Assessment_ Methods for Measuring the Level of Computer Security provide? (Section 91) y built their own evaluation matrices in the process and have incorporated the methodology into their system development method. The study was published by the Institute for Internal Auditors [SMI80]. - 4.1.1.4 Major Strengths And Weaknesses -The methodology's primary strengths are its thoroughness and structure. It conveys an insightful awareness of the complexity and limitations associated with evaluation. It forces and structures thought, providing a focal point for controlled analysis and documentation. No final \"score\" is produced. In fact, major misunderstandings have resulted from the limited quantitative ratings that exist (e.g. via the assumption that a high score means an area is more secure than one with a low score). As a result , in the future the authors will be removing the use of numbers entirely and replacing them with letters to help avoid numeric oversimplification Peat Marwiok Mitchell &amp; Co. has developed a Data Processing Security Evaluation Guideline (DPSE, pronounced Dipsey) . Its development began in 1973 and the firm has used it for \"hundreds\" of clients. It is a proprietary methodology. The firm is considering licensing it to users. DPSE is a partially quantitative, comprehensive, systematic methodology for evaluating security in a data processing environment It consists of an embedded installation profile and a series of questionnaires formatted so as to accommodate a scoring scheme for the answers to each question. These scores are then consolidated into a score for each major security area reviewed. The DPSE \"guidelines and program are intended to aid professional data processing audit and consultant representatives in planning, reviewing, and evaluating (in-depth), the security of data processing installations\" [p. IB-1] . \"Although the review is designed for medium to large-scale data processing environments, the comprehensive topics of data processing security are appropriate to all computer installations\" [p. IB-1].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technology Assessment_ Methods for Measuring the Level of Computer Security."}]}
{"id": "nist_01531", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Recommended Confidentiality Impact Level according to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices? Recommended Confidentiality Impact Level: The provisional confidentiality impact level recommended for travel information is low .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_01532", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Cryptography may be used to provide or support several basic security services according to Recommendation for Key Management_ Part 1 \u2013 General? Cryptography may be used to provide or support several basic security services: confidentiality, identity authentication, integrity authentication, source authentication, authorization, and nonrepudiation. These services may also be required to protect a key and other key information related to that key. In addition, there are other cryptographic and non-cryptographic mechanisms that are used to support these security services. In general, a single cryptographic mechanism may provide more than one service (e.g., the use of digital signatures can provide integrity authentication and source authentication) but not all services.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_01533", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Executive Summary according to NIST Guidelines on Active Content and Mobile Code According to Guidelines on Active Content and Mobile Code, Executive Summary: The private and public sectors depend heavily upon information technology (IT) systems to perform essential, mission-critical functions. As existing technology evolves and new technologies are introduced to provide improved capabilities and advanced features in systems, new technology-related vulnerabilities often arise. Organizations implementing and using advanced technologies must be increasingly on guard. One such category of technologies is active content. Broadly speaking, active content refers to electronic documents that can carry out or trigger actions automatically without an individual directly or knowingly invoking the actions. Exploits based on vulnerabilities in active content technologies can be insidious. The following key guidelines are recommended to organizations for dealing with active content.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Active Content and Mobile Code."}]}
{"id": "nist_01534", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Smart Card Technology_ New Methods for Computer Access Control say about 4.3.2 Cost Factors of the Smart Card? (Part 1) According to Smart Card Technology_ New Methods for Computer Access Control, 4.3.2 Cost Factors of the Smart Card: 4.3.2 Cost Factors of the Smart Card In addition to increasing the risks and costs associated with possible smart card chip breakage, including a magnetic stripe and embossing may increase the cost of the smart card in two other ways. First, it may raise the price of the card itself since more components must be added. Secondly, extra cost due to fraud may be encountered since a merchant may have the option to bill a card-holder by using the embossing, the magnetic stripe, or both, in addition to, or instead of, the smart card IC transaction. For these reasons, including embossing and/or a magnetic stripe on a smart card may be undesirable. On the other hand, businesses currently using extensive embossing and magnetic stripe systems may be reluctant to make an overnight conversion to systems which use only the smart card's IC chip. Unless they are spread out over a period of time, the costs of replacing millions of embossed magnetic stripe cards and their corresponding readers may be prohibitive. Large-scale conversion to smart card systems with advanced security capabilities may be limited by \"the enormous cost of gathering additional cardholder data not currently in the issuer's file, formatting it, encoding it in the [smart] card, and maintaining [such a] widely distributed database.\" [LNDN 86, p. 4] Many foreign countries have succeeded in developing fairly wide-spread smart card systems for banking, telephone services, and other applications. In some cases (such as in France, for example, where smart cards are used in a telephone payment system), no card systems had been previously established; the smart card systems were set up \"from scratch\" without the need to replace existing technologies. In the U.S., the application of smart cards has been more limited, due in part to large corporate investments in embossed magnetic stripe cards. U.S.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Smart Card Technology_ New Methods for Computer Access Control."}]}
{"id": "nist_01535", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events say about 3.5 Technologies? (Part 5) According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events, 3.5 Technologies: | | . | Component | Product | Function | Cybersecurity Frame- work Subcategories | |----------------------------|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| | Mitigation and Containment | Cisco Identity Services Engine (ISE) v2.4 Glasswall FileTrust ATP for Email v6.90.2.5 Semperis DSP v2.7 | \u2022 Provides ability to sandbox files locally. \u2022 Provides ability to enforce policy across the enterprise. \u2022 Provides ability to quarantine devices across the enter- prise. \u2022 Provides ability to sanitize files through file reconstruc- tion. \u2022 Provides ability to revert changes to domain services. | DE.CM-5, RS.RP-1, RS.MI-1, RS.MI-2 | | Reporting | Micro Focus ArcSight ESM v7.0 Patch 2 | \u2022 Provides ability to send security alerts based on organi- zational policy. \u2022 Provides ability to provide reports of enterprise health. \u2022 Provides ability to provide reports of malware detection across the enterprise.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events."}]}
{"id": "nist_01536", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations say about Considerations in Determining Assessment and Monitoring Frequencies? (Part 1) According to Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations, Considerations in Determining Assessment and Monitoring Frequencies: Considerations in Determining Assessment and Monitoring Frequencies . Organizations take the following criteria into consideration when establishing monitoring frequencies for metrics or assessment frequencies for security controls: - Security control volatility . Volatile security controls are assessed more frequently, whether the objective is establishing security control effectiveness or supporting calculation of a metric. 33 Controls in the NIST SP 800-53 Configuration Management (CM) family are a good example of volatile controls. Information system configurations typically experience high rates of change. Unauthorized or unanalyzed changes in the system configuration often render the system vulnerable to exploits. Therefore, corresponding controls such as CM -6, 33 Security control volatility is a measure of how frequently a control is likely to change over time subsequent to its implementation. Configuration Settings, and CM-8, Information System Component Inventory, may require more frequent assessment and monitoring, preferably using automated, SCAP -validated tools that provide alerts and status on demand. Conversely, controls such as PS -2, Position Categorization, or PS-3, Personnel Screening, (from the NIST SP 800 -53 Personnel Security family of controls) are not volatile in most organizational settings. They tend to remain static over long periods and would therefore typically require less frequent assessment. - System categorizations/impact levels . In general, security controls implemented on systems that are categorized as high-impact are monitored more frequently than controls implemented on moderate-impact systems, which are in turn monitored more frequently than controls implemented on low-impact systems. 34 - Security controls or specific assessment objects providing critical functions .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations."}]}
{"id": "nist_01537", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-37r2_Risk_Management_Framework provide? (Section 213) Management or Risk Executive (Function); Senior Agency Information Security Officer; Senior Agency Official for Privacy. System Development Life Cycle Phase: New - Not Applicable. Existing - Disposal. Discussion: When a system is removed from operation, several risk management actions are required. Organizations ensure that controls addressing system disposal are implemented. Examples include media sanitization; configuration management and control; component authenticity; and record retention. Organizational tracking and management systems (including inventory systems) are updated to indicate the system that is being removed from service. Security and privacy posture reports reflect the security and privacy status of the system. Users and application owners hosted on the disposed system are notified as appropriate, and any control inheritance relationships are reviewed and assessed for impact. This task also applies to system elements that are removed from operation. Organizations removing a system from operation update the inventory of information systems to reflect the removal. System owners and security personnel ensure that disposed systems comply with relevant federal laws, regulations, directives, policies, and standards. References: [SP 800-30]; [SP 800-88]; [IR 8062]. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ LAWS, POLICIES, DIRECTIVES, REGULATIONS, STANDARDS, AND GUIDELINES | [32 CFR 2002.4] | Title 32 Code of Federal Regulations, Sec. 2002.4, Definitions . 2018 ed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_01538", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD) provide? (Section 84) P TLV must be enabled on both the Cisco switch and the IoT device. A policy-map configuration and a corresponding template are used to cause media access control (MAC) authentication bypass to happen. This will trigger an access-session attribute that will cause LLDP TLVs (including the MUD URL) to be forwarded in an accounting message to the RADIUS server. Some manual preconfiguration of VLANs on the switch is required. The Cisco MUD manager supports a default policy for IPv4. It implements a static mapping between domain names and IP addresses inside a configuration file. The version of the Cisco MUD manager used in this project is a proof-of-concept implementation that is intended to introduce advanced users and engineers to the MUD concept. It is not a fully automated MUD manager implementation, and some protocol features are not present. These are described in Section 10.1, Findings. 6.2.2 MUD File Server In the absence of a commercial MUD file server for this project, the NCCoE implemented its own MUD file server by using an Apache web server. This file server signs and stores the MUD files along with their corresponding signature files for the IoT devices used in the project. Upon receiving a GET request for the MUD files and signatures, it serves the request to the MUD manager by using https. NIST SP 1800-15B: Securing Small-Business and Home Internet of Things Devices 39 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 This publication is available freeof charge from:https://doi.org/10.6028/NIST.SP.1800-15", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_01539", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices say about E.1 Legislative Mandates? (Part 1) According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, E.1 Legislative Mandates: E.1 Legislative Mandates Some legislatively mandated prohibitions against disclosure of information (other than national security information) are identified in Table 6. The table gives the title or subject of the section in the United States Code (U.S.C.) in which the prohibition occurs, the U.S.C. citation for the prohibition, and the Department, agency, or generic information type to which the law applies, and the legal source. Note that the information contained in the table is intended only as an aid and will not always be current. Independent law searches by analysts will generally be necessary. Table 6: Legal Information Disclosure Prohibitions | Subject/Title of Provision | United States Code Citation | Agency/Activity [Reference] | |-------------------------------------------------|-------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Access to Information; Confidentiality | 22 U.S.C., Chapter 46A, Section 3144 | Foreign Direct Investment in United States [Foreign Direct Investment and International Financial Data Improvements Act of 1990, Public Law 101-533, Sec. 8, Nov. 7, 1990, 104 Stat. 2350] | | Access to Records | 42 U.S.C., Chapter 114, Subchapter I, Part A, Section 10806 | Department of Health and Human Services/Public Health Service [Public Law 99-319, Title I, Sec.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_01540", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Guidelines for Derived Personal Identity Verification (PIV) Credentials? (Part 31) Control PD-12: d PIV Application Command Interface. ## B.1.4.1 Derived PIV Application Key References and Security Conditions of Use Key references are assigned to keys and passwords of the Derived PIV Application. Table 6-1 of [SP80078] and Table 4 of [SP800-73Part1] define the key reference values that shall be used on the Derived PIV Application interfaces with the following mappings: | Derived PIV Key Type | PIV Key Type | |----------------------------------|--------------------------| | Derived PIV Application Password | PIV Card Application PIN | | Password Unblocking Key | PIN Unblocking Key | Table B-2 Mapping of Key Types | Derived PIV Key Type | PIV Key Type | |----------------------------------|----------------------------| | Derived PIV Authentication Key | PIV Authentication Key | | Derived PIV Token Management Key | Card Management Key | | Digital Signature Key | Digital Signature Key | | Key Management Key | Key Management Key | | Retired Key Management Key | Retired Key Management Key | The key reference specifications in Section 5.1 of [SP800-73Part1] are applicable to the corresponding keys included in the Derived PIV Application (mapped per the table above) except for the following: - \uf0b7 References to 'PIV Card Application' are replaced by 'Derived PIV Application' - \uf0b7 References in the 'Security Conditions for Use' column to 'PIN or OCC' are replaced by 'Derived PIV Application Password' ## B.1.4.2 Derived PIV Application Cryptographic Algorithm and Mechanism Identifiers The algorithm identifiers for the cryptographic algorithms that may be recognized on the Derived PIV Application interfaces are the asymmetric and symmetric identifiers specified in Table 6-2 and Table 6-3 of [SP800-78].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, token. Contains security framework guidance for authentication systems. Source: Guidelines for Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_01541", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automation Support for Security Control Assessments_ Volume 1_ Overview say about SP 800-53A states that:? (Part 2) According to Automation Support for Security Control Assessments_ Volume 1_ Overview, SP 800-53A states that:: e capability (e.g., HWAM, SWAM, or Configuration Setting Management) in which the defect check appears. - Local defect checks - Defect checks that a given organization determines whether to implement. Regarding local defect checks, the organization: - -Might not implement a check because the check assesses a security control item that is in a baseline not found within the organization (e.g., the control item is in the highimpact baseline, but the organization has only low- and moderate-impact systems) or within a specific organizational system; - -Might not implement a check because the check assesses a control item that is not implemented at all within the organization or within a specific system (i.e., has been tailored out with appropriate rationale); - -Might implement a check only for specific system assessment objects on which an associated security control is implemented; - -Might implement an alternative version of the local defect check; or - -Might use manual/procedural assessment methods for certain control items. The organization may customize the defect check tables by adjusting the description of defect checks (adding checks, editing checks, clarifying roles, deselecting checks). Table 15: Sample Rows from a Hypothetical Sub-Capability and Defect Checkprovides an example of part of a defect check table. In order to automate security control assessments to the greatest extent possible and to support ongoing authorization, implementation of the applicable foundational and local defect checks defined in this NISTIR is needed for all implemented security control items.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Automation Support for Security Control Assessments_ Volume 1_ Overview."}]}
{"id": "nist_01542", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Formal Description of the SDNS Security Protocol at Layer 4 (SP4) provide? (Section 64) t := kill_me; end; ``` ``` from WFKR to ACTIVE when K.REPLACEresp provided (direction =down_stack) and (status =assoc_ok) (* Key replacement complete; continue building SE TPDU for output to network. *) var encapsulated_data : data_type; build_status : build_status_type; begin output T.cancel; key_replacement_required := false; flow_control := off; hold_local_key_id := local_key_id; hold_peer_key_id := peer_key_id; hold_security_attributes : = security_attributes; build_SE ( hold_user_data, determine_kind(hold_user_data), fsn, hold_local_key_id, hold_peer_key_id, hold_security_attributes, encapsulated_data, build_status); if (build_status = BUILD_OK) then begin output T.start(inactivity); output N.NUDATAreq( hold_local_address, hold_peer_address, hold_QOS_parameter_set, encapsulated_data); end { otherwise discard problem tpdu } else if (build_status = MAC_ERROR) or (build_status = MDC_ERROR) then report_security_event(my_identifier, MAJOR, INTEGRITY_VIOLATION, INTEGRITY_CHECK_FA1LURE, hold_local_address, hold_peer_address) else if (build_status = ENCIPHER_MECH_ERROR) then report_security_event(my_identifier, MAJOR, SECURITY_DOMAIN_VIOLATION, CRYPTO_FACILITY_FAILURE, hold_local_address, hold__peer_address) else if (build_status = KEY_EXPIRED) then report_security_event(my_identifier, MAJOR, SECURITY_DOMAIN_VIOLATION, KEY_MANAGEMENT_FAILURE, hold_local_address, hold_peer_address) else ``` ``` report_security_event(my_identifier, MINOR, OPERATIONAL_VIOLATION, OTHER_FAILURE, hold_local_address, hold_peer_address); end; from WFKR to ACTIVE when K.REPLACEresp provided (direction =up_stack) and (status =assoc_ok) (* Key replacement complete; continue decoding/decapsulation of SE TPDU for output to user.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Formal Description of the SDNS Security Protocol at Layer 4 (SP4)."}]}
{"id": "nist_01543", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.3.3. Human Management-Provided Properties according to NIST Non-Fungible Token Security According to Non-Fungible Token Security, 3.3.3. Human Management-Provided Properties: The human management of the NFT smart contract should provide the properties of unique , authentic , and authorized . These properties are described below.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Non-Fungible Token Security."}]}
{"id": "nist_01544", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings provide? (Section 13) ent common interface could serve as a model. He argued that a unified interface makes things much simpler, and from this standpoint gave an optimistic assessment of PDF signing and encryption support. Anders Rundgren discussed webform signing, which is already used by millions in Europe, largely for citizen-to-government transactions. However, the systems used are proprietary and non-interoperable, so Rundgren is launching the WASP (Web Activated Signature Protocol) standards proposal in cooperation with five groups in Europe. The WASP use cases all stem from efforts to increase usage of e-government. Sandhu discussed prospects for transaction signatures, as vs. document signatures - addressing the many potential applications in which there are many transactions requiring only a modest level of assurance, instead of a few transactions requiring high assurance. One key difference is that where document signatures are generally humanverified, transaction signatures are verified by a computer, \"with possibly human audit and recourse forensics\". Both Rundgren and Sandhu noted the Outlook Express \"Security Warning\" black screen as a particularly egregious example of how not to design a user interface for email security. In the discussion, Rich Guida stressed the importance of asking \"Is it better than the way we do it now?\" Guida suggested that even with their imperfections, any of the signing mechanisms presented in the panel would be better than paper-based signature processes like signing every line of a form. Guida noted that SAFE (http://www.safe-biopharma.org) is working on a universal signing interface. One of the project contractors has developed an approach to verifying historical digital signatures, based on retrieving historical CRLs. This sparked controversy about record-retention issues more generally.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings."}]}
{"id": "nist_01545", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EP-67 in Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)? (Part 101) Control EP-67: \u2022 To assess the degree of industry and vertical market fragmentation. \u2022 To point towards actions that can increase the effectiveness of IoT standardisation, to improve interoperability, and to allow for the building of IoT ecosystems | | | ETSI TR 118 518 V2.0.0 (2016-09) | ETSI | oneM2M; Industrial Domain Enablement (oneM2M TR-0018 version 2.0.0 Release 2) The present document collects the use cases of the industrial domain and the requirements needed to support the use cases collectively. In addition, it identifies the necessary technical work needed to be addressed while enhancing future oneM2M specifications. | Approved Standard | | HITRUST CSF v9 10 September 2017 | HITRUST Alliance | Access Control: Control objective: to control access to information, information assets, and business processes based on business and security requirements. Authorized Access to Information Systems: Control Objective: to ensure authorized user accounts are registered, tracked and periodically validated to prevent unauthorized access to information systems. Network Access Control: Control Objective: to prevent unauthorized access to networking services that they have been specifically authorized to use. Authentication and authorization mechanisms shall be applied for users and equipment.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_01546", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to SSL VPNs? (Part 49) Control ES-1: esource. This makes adding and removing resources to and from a group transparent to the users and reduces policy complexity. In some specific instances, user-level parameters are also set. Table 3-1. Access Control Examples | Method | Example | |--------------|--------------------------------------------------------------------------------------------------------| | Per-user | The CEO may access all intranet servers, email, and the executive folder of the administrative server. | | Per-group | Sales staff may access email, the organization's intranet, and the sales server. | | Per-resource | All users and groups may access the Community Relations server. | Access control can also be integrated with endpoint security controls. SSL VPNs can use host integrity checking to check the status of the SSL VPN client before access is granted. Some SSL VPNs have the capability to perform this checking either before or after authentication to determine the appropriate access controls. Access control in this sense may be as simple as allowing or denying access completely, or more elaborate such as providing restricted access to selected information based on host integrity checks. Access controls may also be configured per-user, per-group, and per-resource in terms of host integrity checking. It is beneficial to have the ability to bypass the endpoint security restrictions for certain circumstances such as disaster response. Bypassing endpoint security for special circumstances may be accomplished through a special access control policy setting or whitelist. Table 3-2 shows some examples of access control policies in conjunction with endpoint security controls. These examples are an extension of the examples in Table 3-1. The first user is the CEO, who is accessing the SSL VPN from home via an organization-issued laptop.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Guide to SSL VPNs."}]}
{"id": "nist_01547", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results provide? (Section 30) high level of risk in that category, as well as a significant confidentiality risk. A particular type of electronic document may have different levels of risk for different categories or applications. For example, purchase orders used for low-dollar-value transactions may be determined to have low authentication risk, while otherwise identical purchase orders used for high-value transactions may carry a greater risk. For establishment of particular protective techniques, the likelihood of occurrence of the several types of exposures must be considered and it must be determined, in a general sense, what expense is reasonable for protection against them. This is the essential requirement of the Computer Security Act of 1987, which assigns to NIST responsibility for developing standards and guidelines needed to assure the cost-effective security and privacy of sensitive information in Federal computer systems. The Act states that implementation of protective techniques shall be \"commensurate with the risk and magnitude of the harm resulting from the loss, misuse, or unauthorized access to or modification of the information ...\" For messages where confidentiality is a major issue, it might be determined that it is worth the expenditure to protect against eavesdropping if that can be done at a reasonable cost and with reasonable administrative simplicity. For messages for which assurance of delivery is an issue, or for which undesired changes in numerical values contained within the message would be seriously detrimental, appropriate protections may be recommended, again using reasonable cost and administrative simplicity as criteria. The kinds of protective techniques associated with documents embodied in paper media must be appropriate to the media, and analogous electronic techniques at the same level of protection must be appropriate to the new medium.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results."}]}
{"id": "nist_01548", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain A failure in control item effectiveness results in a defect in one or more of the following defect checks: according to NIST Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management According to Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management, A failure in control item effectiveness results in a defect in one or more of the following defect checks:: | Determination Statement ID | Defect Check ID | Defect Check Name | Rationale If an [organization-defined measure] for this defect check is above [the organization- defined threshold], then defects in conducting reviews and updates of the {actual state} system component inventory {for devices and device components}\" with the \"organization-defined frequency\" related to this control item might be the cause of ... | |------------------------------|-------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | CM-8(b)(1) | HWAM- Q04 | Low Timeliness Metric | low timeliness of overall ISCM reporting. |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management."}]}
{"id": "nist_01549", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Enhanced Security Requirements for Controlled Unclassified Information say about GLOSSARY? (Part 14) According to Assessing Enhanced Security Requirements for Controlled Unclassified Information, GLOSSARY: ng as intended. Also used to refer to units of related data fields (i.e., groups of data fields that can be accessed by a program and that contain the complete set of information on particular items). | | risk [OMB A-130] | A measure of the extent to which an entity is threatened by a potential circumstance or event, and typically is a function of: (i) the adverse impact, or magnitude of harm, that would arise if the circumstance or event occurs; and (ii) the likelihood of occurrence. | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | risk assessment [SP 800-30] | The process of identifying risks to organizational operations (including mission, functions, image, reputation), organizational assets, individuals, other organizations, and the Nation, resulting from the operation of a system. | |-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | sanitization | Actions taken to render data written on media unrecoverable by both ordinary and, for some forms of sanitization, extraordinary means. Process to remove information from media such that data recovery is not possible. | | security | A condition that results from the establishment and maintenance of protective measures that enable an organization to perform its mission or critical functions despite risks posed by threats to its use of systems.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_01550", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Property Management Systems say about 5.2.6 PR.AC-4: Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties? According to Securing Property Management Systems, 5.2.6 PR.AC-4: Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties: The access control platform, TDi ConsoleWorks 5.2-0u1, and network protection device, CryptoniteNXT Secure Zone 2.9.1, work in combination to limit access in the least allowable fashion to only those authorized entities, users, systems, transactions, and platforms. Connections that are authorized are given the least level of privilege as feasible.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Securing Property Management Systems."}]}
{"id": "nist_01551", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Usage Restrictions according to NIST Secure Data Network Systems (SDNS) Key Management Documents According to Secure Data Network Systems (SDNS) Key Management Documents, Usage Restrictions: Only the initiator of the application association may request the K-EXCH-CRED service, except after a K-TRY-ME or K-NO-KEY service. After a K-TRY-ME or K-NO-KEY service, only the responder of the application association service may request the K-EXCH-CRED. The K- EXCH-CRED service must be (*or must have been) invoked prior to the use of the following services: - 0 K-TEK-ATTRIBUTES - 0 K-IREKEY - 0 K-REQUEST-SREKEY - o K-DELIVER-SREKEY - o K-GET-CRL - 0 K-UPDATE-TEK* - 10.1.3. Disrupted Services The K-EXCH-CRED service does not disrupt any services. - 10.1.4. Disrupting Services 10.2. The A-ABORT and the A-P-ABORT services disrupt the K-EXCH-CRED service. - K-TRY-ME Service Sequencing Information - 10.2.1. Type of Service K-TRY-ME is an unconfirmed service. - 10.2.2. Usage Restrictions Only the initiator of the application association may request the K-TRY-ME service. - 10.2.3. Disrupted Services The K-TRY-ME service does not disrupt any services. - 10.2.4. Disrupting Services 10.3. The A-ABORT and the A-P-ABORT services disrupt the K-TRY-ME service.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_01552", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Engineering Trustworthy Secure Systems say about Authority? According to Engineering Trustworthy Secure Systems, Authority: This 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. \u00a7 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_01553", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to Security and Privacy Controls for Information Systems and Organizations? Discussion: Information is represented internally within systems using abstractions known as", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01554", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Technical Guide to Information Security Testing and Assessment say about 3.2 Log Review? (Part 1) According to Technical Guide to Information Security Testing and Assessment, 3.2 Log Review: 3.2 Log Review 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. 6 This publication discusses reviews strictly from the aspect of assessment. Reviews should also be conducted periodically as part of regular system monitoring and maintenance, such as to identify operational problems, security misconfigurations, malicious activity, and other types of security events. Organizations can choose to use findings from operational reviews for their assessments. 7 NIST SP 800-92, Guide to Security Log Management , provides more information on security log management methods and techniques, including log review. It is available at Examples of log information that may be useful when conducting technical security assessments include: - GLYPH&lt;c=31,font=/DGCOEC+Webdings&gt; Authentication server or system logs may include successful and failed authentication attempts.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Technical Guide to Information Security Testing and Assessment."}]}
{"id": "nist_01555", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-16(01) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control AC-16(01): SECURITY AND PRIVACY ATTRIBUTES | DYNAMIC ATTRIBUTE ASSOCIATION ASSESSMENT OBJECTIVE: Determine if:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01556", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record say about 2.2 Record Type 18 Table of Requirement and Assertions? According to Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record, 2.2 Record Type 18 Table of Requirement and Assertions: In preparation for extending BioCTS for AN-2011 to support conformance testing of AN-2011 Record Type 18, the BioCTS team identified over two-hundred test assertions that are necessary to meet the conformance requirements for this Record Type. The test assertions have been organized into a table of requirements and assertions following the format documented in NIST Special Publication 500-295 [8]. Table B.1, which identifies all requirements and associated test assertions for Type 18, uses the test assertion syntax documented Tables 2.1, 2.2, and 2.3 found in Section 2.3. The tables define the Operator Definitions, Terms, and Operand Definitions respectively and are also specified in NIST SP 500-295, section 5.5 - Test Assertion Syntax. They have been reproduced in their entirety in this document for consistency, although some entries in the tables may not be used in the test assertions for Record Type 18. Table B.1 headings are also defined in NIST SP 500-295, Section 5.6 (Tables of requirements and assertions - Table headers) with the exception of Requirement number. Not all test notes included in NIST SP 500-295 apply to the Record Type 18 Table. The three test notes referred to in table B.1 are included below the table. Test Notes 2 and 6 are the same test notes found in NIST SP 500-295, Section 6.3. Test note 18 applies only to Record Type 18. Conformance test levels are defined in NIST's Special Publication 500-295 Section 5.3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record."}]}
{"id": "nist_01557", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is The local exploit level can be captured using two environmental metrics according to The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities? The local exploit level can be captured using two environmental metrics: Local Vulnerability Prevalence and Perceived Target Value.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities."}]}
{"id": "nist_01558", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure say about 5.2.1. Identity Management, Authentication and Access Control Category? (Part 3) According to Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure, 5.2.1. Identity Management, Authentication and Access Control Category: | Ecosystem: Consider implementing formal procedures and guidelines to issue, manage, and verify identities and credentials. Credential management may be performed by an independent entity. This may include the management of authentication mechanisms (e.g., single-factor, multi-factor) and unique identifiers, such as usernames, passwords, certificates, biometrics, smart cards, and hardware tokens. Implement mechanisms to track, log, approve, and audit access attempts and activities of devices within the ecosystem. Identities/credentials stored within the ecosystem may include manufacturer identities, employee identities, supplier identities, provider identities, device identities, test and validation certificates, software certificates, and system administration credentials. Consider that credentials should be promptly accredited and decommissioned when issued and revoked.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, identity management. Contains security framework guidance for authentication systems. Source: Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure."}]}
{"id": "nist_01559", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain IN SUMMARY according to NIST A Study of Federal Agency Needs for Information Technology Security According to A Study of Federal Agency Needs for Information Technology Security, IN SUMMARY: Those organizations the study team worked with and visited appear to have a deep commitment to securily, despite a number of constraints, limitations, and frustrations. They are looking for a clear statement of what is required and expected of them with regard to security - and they expect these requirements to make sense and to be consistent with their other requirements. While agencies regard NIST as one important source for help, they are by no means standing Idly by. They are actively developing programs that work for them. They are also beginning to coordinate their efforts with other agencies. There is clearly a need for federal agencies to continue to be proactive regarding security and define the role they will assume in their own behalf. In this regard, it is recommended that federal agencies continue to monitor their security needs, communicate these needs to the central agencies, seek sources of help from within the federal community, and be generous in the sharing of their own experiences, efforts, and products. Finally, this study is but one piece of a much larger mosaic. We believe this study is an important element in providing a sound basis for planning future NIST security-related efforts. In addition to NIST and the other central agencies, each agency's staff, including agency security, management, and individual users, are among those who play an integral role in providing comprehensive security for the federal government. In deciding where to apply resources and energies, it is Important to take into account the roles and relationships among all these players. There is an open invitation and welcome for all to join in the search for and development of solutions that serve our community.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of Federal Agency Needs for Information Technology Security."}]}
{"id": "nist_01560", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Dictionary Maintainer according to Common Platform Enumeration_ Dictionary Specification Version 2.3? Dictionary Maintainer: An organization that manages a CPE dictionary and all processes relating to that CPE dictionary. In the majority of cases, the organization that serves as the dictionary creator for a specific CPE dictionary will also serve as the dictionary maintainer. Otherwise, generally the dictionary maintainer is supporting the dictionary on behalf of the dictionary creator.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Platform Enumeration_ Dictionary Specification Version 2.3."}]}
{"id": "nist_01561", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to SSL VPNs provide? (Section 151) n properly when proxying is used, so network extension must be used. - -When users login from public hosts that are not organization-managed, they can access a set of Web-based applications via proxy. - -The set of HR applications are accessible by network extension because some require many interlocking programs and cannot be accessed by other means. Table 7-1 summarizes the organization's access control policy. Table 7-1. Organization's Access Control Policy | Resource | Group | Condition | Access Type | |---------------------------------------------|----------|--------------------------------------------------------------------------------------------------------------------------|-------------------| | Internal resources (except HR applications) | Users | Organization-managed host | Network extension | | Web applications | Users | Any host running a recent version of Windows with critical updates installed and updated antivirus and firewall software | Proxy | | HR applications (only) | HR users | Organization-managed host | Network extension | The organization designs an endpoint security policy to enforce access control. The policy is mainly driven by a prelogin sequence executed by the SSL VPN appliance before a user logs in. This sequence runs host integrity checks that require the host to download and run active content controls. These controls or applets ensure that the host complies with the organization's endpoint security policy.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to SSL VPNs."}]}
{"id": "nist_01562", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Metrics and Methodology for Hardware Security Constructs say about 5. Methodology for Hardware Weakness Threat Analysis? (Part 8) According to Metrics and Methodology for Hardware Security Constructs, 5. Methodology for Hardware Weakness Threat Analysis: Mapping a newly discovered attack technique to an existing generalized class of attacks is a relatively straightforward process. The third step of the methodology involves performing a simple matrix multiplication to identify correlations between the most common hardware weaknesses and standard attack patterns. Table 6T shows the result of multiplying the matrices in Table 4 and Table 5. Table 6.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Metrics and Methodology for Hardware Security Constructs."}]}
{"id": "nist_01563", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Building Secure Microservices-based Applications Using Service-Mesh Architecture provide? (Section 16) 5 of the OSI model) concerns. However, fine-grained authorization may still need to be performed at the microservice level since that is the only entity that has full knowledge of the business logic. Alternatively, the Service Mesh can be defined as 'a distributed computing middleware that optimizes communications between application services [3].' The service-to-service communication is most effectively enabled using a proxy (see Section 1.1). A Service Mesh is typically implemented as an array of lightweight network proxies that are deployed alongside application code without the application needing to be aware [4]. In addition, the Service Mesh can be leveraged to monitor and secure communication. Because it is intercepting and routing all cluster traffic and gathering health metrics, the Service Mesh can learn and intelligently route traffic. Examples of this higher-level functionality include A/B testing, canary deployments, beta channels, automatic retries, circuit breakers, and injecting faults. These features are only possible because the Service Mesh is able to view and learn from the entire cluster's traffic. It is considered economical to deploy Service Mesh when the number of microservices in the application is in the order of hundreds or thousands. However, the Service Mesh is not without some drawbacks. Because each microservice requires its own service proxy, the number of runtime instances and the overall attack surface for the application increases. As the functionality built into a service proxy increases, it may become a communication bottleneck. A Service Mesh consists of two main architectural layers or components: - Data plane - Control plane The interconnected set of proxies in a Service Mesh that control the inter-services communication represents its data plane. The data plane is the data path and provides the ability to forward requests from the applications.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Building Secure Microservices-based Applications Using Service-Mesh Architecture."}]}
{"id": "nist_01564", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events say about Continuous Monitoring? (Part 1) According to Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events, Continuous Monitoring: Continuous Monitoring Maintaining ongoing awareness to support organizational risk decisions SOURCE: NIST SP 800-137 Cybersecurity Prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation SOURCE: CNSSI 4009-2015 (NSPD-54/HSPD-23) Data A subset of information in an electronic format that allows it to be retrieved or transmitted SOURCE: CNSSI-4009 Data Integrity The property that data has not been changed, destroyed, or lost in an unauthorized or accidental manner SOURCE: CNSSI-4009 Information Security The protection of information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide confidentiality, integrity, and availability SOURCE: FIPS 199 (44 U.S.C., Sec. 3542) Information Security Risk The risk to organizational operations (including mission, functions, image, reputation), organizational assets, individuals, other organizations, and the Nation due to the potential for unauthorized access, use, disclosure, disruption, modification, or destruction of information and/or information systems SOURCE: CNSSI 4009-2015 (NIST SP 800-30 Rev. 1) Information System A discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information SOURCE: FIPS 200 (44 U.S.C., Sec. 3502) Insider An entity inside the security perimeter that is authorized to access system resources but uses them in a way not approved by those who granted the authorization SOURCE: NIST SP 800-82 Rev. 2 (RFC 4949) Kerberos An authentication system developed at the Massachusetts Institute of Technology (MIT).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_01565", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Report on Lightweight Cryptography according to NIST Report on Lightweight Cryptography According to Report on Lightweight Cryptography, Report on Lightweight Cryptography: Kerry A. McKay Larry Bassham Meltem S\u00f6nmez Turan Nicky Mouha Computer Security Division Information Technology Laboratory This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8114 March 2017 <!-- image --> U.S. Department of Commerce Wilbur L. Ross, Jr., Secretary", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report on Lightweight Cryptography."}]}
{"id": "nist_01566", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on PDA Forensics say about 1.1 Authority? According to Guidelines on PDA Forensics, 1.1 Authority: The National Institute of Standards and Technology (NIST) developed this guide in furtherance of its statutory responsibilities under the Federal Information Security Management Act (FISMA) of 2002, Public Law 107-347. NIST is responsible for developing standards and guidelines, including minimum requirements, for providing adequate information security for all Federal 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 A130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in A-130, Appendix III. This guide 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 guide 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: Guidelines on PDA Forensics."}]}
{"id": "nist_01567", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is https according to 2016 NIST_ITL Cybersecurity Program Annual Report? https: / /nccoe.nist.gov/projects/use\\_cases/securingsensitive-consumer-data", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01568", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Survey of Remote Monitoring say about Remotely Controlled Software Monitors? (Part 1) According to A Survey of Remote Monitoring, Remotely Controlled Software Monitors: Remotely Controlled Software Monitors A remotely controlled software monitor can be implemented as simply as a system log monitor. The purpose of the monitor is limited only by the ingenuity of the impl ementers , e'g. it may monitor the CPU utilization, inspect resource utilization, etc. In a pure software monitor, the monitor is instigated, for a particular run, by an operator, a system clock, or it is set for cyclic invocation at system initiation time. A remotely controlled software monitor is triggered by a central monitor controller. There are two prominent examples of actual implementations which employ this technique: the first example is the WWMCCS ADP System Security Officer (WASSO) station, 29j42 gp^ ^1^^ second example is a technique used on Control Data computers. ^ ^' The WASSO station potentially could be implemented as a true remotely controlled software monitor, or as a monitor distributed between a software tool and an intelligent terminal; the former case is discussed in this section. Most sites in the WWMCCS are centered around a Honeywell 6000 series computer under the GCOS III operating system. Each site is potentially processing sensitive data in a multiprogramming environment; thus, there is a need for a secure operating policy in the system. Each such site has at least one ADP System Security Officer whose mission is to monitor the physical protocol of the site, as well as the internal operation of the system. The WASSO station is under development to aid the officer in the latter part of his mission by providing a facility to implement collection, reduction, and analysis of information necessary to assess the site's security posture. The current status of the WASSO study is that a prototype system is being built, and this prototype will partially rely on the standard software tools that exist in the operating system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Survey of Remote Monitoring."}]}
{"id": "nist_01569", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Telehealth Remote Patient Monitoring Ecosystem provide? (Section 366) \uf0a7 Ability to prevent external access to the IoT device management interface. \uf0a7 Ability to control the IoT device's logical interface (e.g., locally or remotely). \uf0a7 Ability to detect remote activation attempts. \uf0a7 Ability to detect remote activation of a collaborative computing device/component (e.g., microphone, camera). \uf0a7 Ability to detect remote activation of sensors. \uf0a7 Ability to establish access to the IoT device to perform organizationally defined user actions without identification or authentication. \uf0a7 Ability to assign roles to IoT device user accounts. \uf0a7 Ability to support a hierarchy of logical access privileges for the IoT device based on roles (e.g., admin, emergency, user, local, temporary) o Ability to establish user accounts to support role- based logical access privileges. o Ability to administer user accounts to support role- based logical access privileges. o Ability to use organizationally defined roles to define each user account's access and permitted device actions. | \uf0a7 Providing descriptions of the types of access to the IoT device that the manufacturer will require on an ongoing or regular basis. \uf0a7 Providing detailed instructions for how to implement management and operational controls based on the role of the IoT device user, and not on an individual basis. \uf0a7 Providing documentation and/or other communications describing how to implement management and operational controls to protect data obtained from IoT devices and associated systems from unauthorized access, modification, and deletion. \uf0a7 Providing a detailed description of the other types of devices and systems that will access the IoT device during customer use of the device, and how they will access it. \uf0a7 Providing communications and detailed instructions for implementing a hierarchy of privilege levels to use with the IoT device and/or necessary associated information systems. \uf0a7 Providing communications and documentation detailing how to perform | .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_01570", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Access Control Documents say about 3.3 Layer 7 E-Mail? (Part 3) According to Secure Data Network Systems (SDNS) Access Control Documents, 3.3 Layer 7 E-Mail: eer-to-peer characteristics which are necessary for SDNS components to guarantee enforcement without relying on processing performed within non-SDNS intermediate entities (e.g., mail staging systems). User-level COMPOSITE IDs will contain one of two separate classes of clearance/accreditation information: a first class (USER DATA) specifying the user's clearance information, and a second class (END SYSTEM DATA) reflecting those end system characteristics (e.g., authorized sensitivity levels and other inputs to risk index computations) which are needed in order to constrain dataflows appropriately. If the user moves to an alternate end system, the alternate end system's END SYSTEM DATA, rather than the home end system's END SYSTEM DATA, would become relevant. This implies that the process performed in order to activate a user's ID at an alternate end system must, in effect, associate USER DATA information with the applicable end system's END SYSTEM DATA.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Access Control Documents."}]}
{"id": "nist_01571", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research provide? (Section 74) zeroize the token containing the DPC, MyID will revoke all certificates. In this scenario, using one of MyID's several mechanisms to revoke credentials, an operator can use the Remove Person workflow. The Remove Person workflow will revoke all active credentials and associated certificates immediately. The MyID Operator removes a Subscriber by using the People \uf0e0 Remove Person workflow as shown in Figure 49. Figure 49: MyID Remove Person <!-- image --> The MyID Operator selects the reason for termination as shown in Figure 50. Figure 50: MyID Remove Person Reason Selection <!-- image --> The MyID CMS will revoke all certificates associated with the Subscriber's record. The serial numbers of the certificates will appear in the next DPC PIV CA and DPC LOA-3 CA CRL publications as shown in Figures 51 and 52. <!-- image --> Figure 51: Subscriber's PIV Authentication Certificate and CRL Entry <!-- image --> Figure 52: Subscriber's Derived PIV Authentication Certificate and CRL Entry <!-- image --> Section 4.3 of this report describes the services that the user will be accessing using their DPCs. Microsoft Office 365 'single sign-on' allows customers to use their organization credentials to access Office 365 services. This capability is provided through ADFS or third-party single signon providers. 36 At the time of this report's publication, the various Office 365 services use different protocols. For the user to be prompted for his or her X.509-based credential at time of authentication, the Web Services Federation (WS-Federation) passive requester profile 37 is used. Office 365 Outlook Web Access, SharePoint, and OneDrive use WS-Federation. The ADFS Identity Provider Security Token Service (IdP STS) authenticates the user to AD and generates a SAML token asserting the user's identity. Within this token is the authenticating user's AD UserPrincipalName (UPN) and ObjectGUID, a unique AD object.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token, single sign-on. Contains security framework guidance for authentication systems. Source: Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research."}]}
{"id": "nist_01572", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Key Notarization System for Computer Networks say about 11.3 THE REG EIVER? According to A Key Notarization System for Computer Networks, 11.3 THE REG EIVER: Once user j is active, and has received the encrypted DKij, IV, and data, he may use LDK and LIV to load the receive active storage. He can then decrypt and check the signature to insure that it is correct. Note that the same data key may be used for both encryption and digital signatures. If j wishes he can generate a DKji to communicate securely to i, but communications from j to i will not be encrypted with the same data key as communications from i to j \u00b7", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Key Notarization System for Computer Networks."}]}
{"id": "nist_01573", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Segmentation in a Small Manufacturing Environment say about Why should I implement Security Segmentation?? (Part 1) According to Security Segmentation in a Small Manufacturing Environment, Why should I implement Security Segmentation?: Why should I implement Security Segmentation? Table 1 shows how security segmentation helps address some common cybersecurity weaknesses that most small manufacturing environments face. Table 1. How Security Segmentation Addresses Common Weaknesses | Common Weakness | Security Segmentation | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Segmentation in a Small Manufacturing Environment."}]}
{"id": "nist_01574", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 590) rts, protocols, or services that pose unnecessarily high risks and understand the trade-offs involved in blocking specific ports, protocols, or services or requiring system service providers to do so. Early identification of functions, ports, protocols, and services avoids costly retrofitting of controls after the system, component, or system service has been implemented. SA-9 describes the requirements for external system services. Organizations identify which functions, ports, protocols, and services are provided from external sources. Related Controls: CM-7, SA-9. (10) ACQUISITION PROCESS | USE OF APPROVED PIV PRODUCTS Employ only information technology products on the FIPS 201-approved products list for Personal Identity Verification (PIV) capability implemented within organizational systems. Discussion: Products on the FIPS 201-approved products list meet NIST requirements for Personal Identity Verification (PIV) of Federal Employees and Contractors. PIV cards are used for multi-factor authentication in systems and organizations. Related Controls: IA-2, IA-8, PM-9. (11) ACQUISITION PROCESS | SYSTEM OF RECORDS Include [Assignment: organization-defined Privacy Act requirements] in the acquisition contract for the operation of a system of records on behalf of an organization to accomplish an organizational mission or function. Discussion: When, by contract, an organization provides for the operation of a system of records to accomplish an organizational mission or function, the organization, consistent with its authority, causes the requirements of the [PRIVACT] to be applied to the system of records. Related Controls: PT-6. (12) ACQUISITION PROCESS | DATA OWNERSHIP (a) Include organizational data ownership requirements in the acquisition contract; and (b) Require all data to be removed from the contractor\u2019s system and returned to the organization within [Assignment: organization-defined time frame].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor. Contains security framework guidance for authentication systems. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01575", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Random Bit Generator (RBG) Constructions say about 3.2.2.1. External Conditioning When Full Entropy is Not Required? According to Recommendation for Random Bit Generator (RBG) Constructions, 3.2.2.1. External Conditioning When Full Entropy is Not Required: The Get\\_conditioned\\_input procedure specified below iteratively requests entropy from the Get\\_entropy\\_bitstring process (represented as a Get\\_entropy\\_bitstring procedure; see Sec. 2.8.2 and 3.1) and distributes the entropy in the newly acquired entropy\\_bitstring across the conditioning function's output block. The output of the Get\\_conditioned\\_input procedure is the concatenation of the conditioning function output blocks. The entire output of the 12 Any padding required could be done before submitting the entropy\\_bitstring to the CBC-MAC function. Get\\_conditioned\\_input procedure shall be provided as input to the DRBG mechanism (i.e., the output of the Get\\_conditioned\\_input function shall not be truncated). Let output\\_len be the length of the conditioning function's output block.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Bit Generator (RBG) Constructions."}]}
{"id": "nist_01576", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Automation Support for Security Control Assessments_ Software Asset Management provide? (Section 248) | Determine if the organization: employs integrity verification tools to detect unauthorized changes to [Assignment: an organization-defined subset of software, firmware, and information]. | | Determination Statement ID | Implemented By | Assessment Boundary | Assessment Responsibility | Assessment Methods | Selected | Rationale for Risk Acceptance | Frequency of Assessment | Impact of Not Implementing | |------------------------------|------------------|-----------------------|-----------------------------|----------------------|------------|---------------------------------|---------------------------|------------------------------| | SI-7{1} | ISCM-Ops | ISCM-TN | ISCM-Sys | Test | | | | | A failure in effectiveness of this control item results in a defect in one or more of the following defect checks: | Determination Statement ID | Defect Check ID | Defect Check Name | Rationale If an [organization-defined measure] for this defect check is above [the organization-defined threshold], then defects in employing integrity verification tools to detect unauthorized changes to specified software related to this control item might be the cause of the defect, i.e.,\u2026 | |------------------------------|-------------------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | SI-7{1} | SWAM- F01 | Unauthorized software executes | the execution of unauthorized software.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_01577", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CP-09 in Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations? (Part 61) Control CP-09: . Update risk assessments [ Assignment: organization-defined frequency ]. ## DISCUSSION Establishing the system boundary is a prerequisite to assessing the risk of the unauthorized disclosure of CUI. Risk assessments consider threats, vulnerabilities, likelihood, and adverse impacts to organizational operations and assets based on the operation and use of the system and the unauthorized disclosure of CUI. Risk assessments also consider risks from external parties (e.g., contractors operating systems on behalf of the organization, service providers, individuals accessing systems, and outsourcing entities). Risk assessments can be conducted at the organization level, the mission or business process level, or the system level and at any phase in the system development life cycle. Risk assessments include supply chain-related risks associated with suppliers or contractors and the system, system component, or system service that they provide. ## REFERENCES Source Controls: RA-03, RA-03(01), SR-06 Supporting Publications: SP 800-30 [55], SP 800-161 [33] ## 03.11.02 Vulnerability Monitoring and Scanning - a. Monitor and scan the system for vulnerabilities [ Assignment: organizationdefined frequency ] and when new vulnerabilities affecting the system are identified. - b. Remediate system vulnerabilities within [ Assignment: organization-defined response times ]. - c. Update system vulnerabilities to be scanned [ Assignment: organization-defined frequency ] and when new vulnerabilities are identified and reported. ## DISCUSSION Organizations determine the required vulnerability scanning for system components and ensure that potential sources of vulnerabilities (e.g., networked printers, scanners, and copiers) are not overlooked. Vulnerability analyses for custom software may require additional approaches, such as static analysis, dynamic analysis, or binary analysis.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_01578", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices say about III. Sensitive But Unclassified Information? According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, III. Sensitive But Unclassified Information: In addition to information that could reasonably be expected to assist in the development or use of weapons of mass destruction, which should be classified or reclassified as described in Parts I and II above, departments and agencies maintain and control sensitive information related to America's homeland security that might not meet one or more of the standards for classification set forth in Part 1 of Executive Order 12958. The need to protect such sensitive information from inappropriate disclosure should be carefully considered, on a case-by-case basis, together with the benefits that result from the open and efficient exchange of scientific, technical, and like information. All departments and agencies should ensure that in taking necessary and appropriate actions to safeguard sensitive but unclassified information related to America's homeland security, they process any Freedom of Information Act request for records containing such information in accordance with the Attorney General's FOIA Memorandum of October 12, 2001, by giving full and careful consideration to all applicable FOIA exemptions. See FOIA Post, \"New Attorney General FOIA Memorandum Issued\" (posted 10/15/01) (found at http://www.usdoj.gov/oip/foiapost/2001foiapost19.htm), which discusses and provides electronic links to further guidance on the authority available under Exemption 2 of the FOIA, 5 U.S.C. \u00a7 552(b)(2), for the protection of sensitive critical infrastructure information. In the case of information that is voluntarily submitted to the Government from the private sector, such information may readily fall within the protection of Exemption 4 of the FOIA, 5 U.S.C. \u00a7 552(b)(4).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, sensitive but unclassified. Contains guidance on protecting sensitive government information. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_01579", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to NIST_SP_800-53r5_Security_Privacy_Controls? Discussion: Hardware integrity verification allows organizations to detect unauthorized", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01580", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems provide? (Section 68) or Program [M0942] Limit Software Installation [M1033] | CM1.1 COMP 1.1 | | Guideline 7: Protect Communications Connections | Guideline 7: Protect Communications Connections | Guideline 7: Protect Communications Connections | Guideline 7: Protect Communications Connections | Guideline 7: Protect Communications Connections | Guideline 7: Protect Communications Connections | | PR.IR-01 | 12.2 | Boundary Protection [SC-7] | DS: COM(1) DO: SMP(5h) | Network Segmentation [M0930] | NET 1.1 | The NVD was reviewed in early 2022 to better understand known cybersecurity vulnerabilities that have been identified in smart inverters.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems."}]}
{"id": "nist_01581", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2012 Annual Report provide? (Section 37) :df00) outreach activities with academic institutions, providing information on NIST's security standards and guidelines and exploring new areas of cybersecurity research and development. In FY2012, CSD completeGLYPH(cmap:df00) the following activities: - \u0091\u0091 DevelopeGLYPH(cmap:df00) NIST SP 800-30, Revision 1, Guide for Conducting Risk Assessments ; - \u0091\u0091 DevelopeGLYPH(cmap:df00) GLYPH(cmap:df00)raft SP 800-53, Revision 4, Recommended Security Controls for Federal Information Systems and Organizations ; - \u0091\u0091 Released example security assessment cases for assessment proceGLYPH(cmap:df00)ures in SP 800-53A, Revision 1, Guide for Security Assessment of Federal Information Systems and Organizations: Building Effective Security Assessment Plans ; and - \u0091\u0091 CollaborateGLYPH(cmap:df00) with the ITL Software anGLYPH(cmap:df00) Systems Division and the NIST Standards CoorGLYPH(cmap:df00)ination Office using the International StanGLYPH(cmap:df00)arGLYPH(cmap:df00) ISO/IEC 17020:2008 General criteria for the operation of various types of bodies performing inspections , in support of GSA in establishing a process for qualifying Third Party Assessment Organizations (3PAOs) to conGLYPH(cmap:df00)uct security assessments of Cloud Service Providers (CSPs) information systems consistent with GSA requirements based on NIST standards and guidelines.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_01582", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-2 in Computer Security Division 2004 Annual Report? (Part 58) Control HA-2: uirements to evaluate vendors' operational procedures, review third-party audits and assess operational compliance demonstrations when establishing the initial list of three approved PKI providers. It has been asked why the SSP system is necessary when services are currently available under the Access Certificates for Electronic Services (ACES) program or the GSA smart card contract. The SSP Program does not establish a contract but creates a qualified bidders list. The SSP Subcommittee does not want to limit agencies to one solution. The SSP Subcommittee does want to set a standard for PKI that implements a common policy in the Federal government that ensures a minimum level of security and quality when agencies contract for PKI services. CSD, as part of the SSP Subcommittee, has developed the Shared Service Provider Roadmap. The Shared Service Provider Roadmap is intended to identify the background information, phases and activities related to the selection process for prospective PKI managed service providers. This document identifies the process by which a vendor qualifies for inclusion on the Qualified Bidders List. The document also describes requirements that must be met to maintain qualification, as well as contracting considerations. We are also assisting GSA in the development of an online e-authentication credential validation infrastructure. The GSA e-Authentication Gateway will mediate between government applications and non-government CSPs, permitting applications to accept a variety of identification credentials. For example, individuals may be able to leverage authentication mechanisms, such as passwords, established with their banks to access government applications. The GSA E-Authentication Gateway architecture relies on SAML, TLS and PKI to exchange authentication information with CSPs and government applications.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Computer Security Division 2004 Annual Report."}]}
{"id": "nist_01583", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2016 NIST_ITL Cybersecurity Program Annual Report say about https:/ /doi.org/10.1109/TIFS.2016.2516916? According to 2016 NIST_ITL Cybersecurity Program Annual Report, https:/ /doi.org/10.1109/TIFS.2016.2516916: Network diversity has long been regarded as a security mechanism for improving the resilience of software and networks against various attacks. More recently, this diversity has found new applications in cloud computing security, moving-target defense, and improving the robustness of network routing. However, most existing efforts rely on intuitive and imprecise notions of diversity, and the few existing diversity models are mostly designed for a single system running diverse software replicas or variants. At a higher abstraction level, as a global property of the entire network, network diversity and its effect on security have received limited attention. In this paper, we take the first step toward formally modeling network diversity as a security metric by designing and evaluating a series of diversity metrics. In particular, we first devise a biodiversity-inspired metric based on the effective number of distinct resources. We then propose two complementary diversity metrics, based on the least and the average attacking efforts, respectively. We provide guidelines for instantiating the proposed metrics and present a case study on estimating software diversity. Finally, we evaluate the proposed metrics through simulation.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01584", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Secure Web Services provide? (Section 148) user authentication. Set up an end-to-end user authentication mechanism that reaches from requesters to the mainframe or other backend legacy server. - Establish an end-to-end encrypted data channel. Use encryption from the individual requesters to the Web service interface and from the Web service interface to the legacy backend system. This is done to ensure that sensitive data are not exposed in transit over external and internal networks. If the 55 For further guidance on public key implementation, see NIST SP 800-32, Introduction to Public Key Technology and the Federal PKI Infrastructure and NIST SP 800-44, Guidelines on Securing Public Web Servers, available at http://csrc.nist.gov/publications/nistpubs/. backend system does not natively support encrypted data channels, IPsec or SSL tunneling software can provide an encrypted data channel. - Implement public key security end-to-end. Deploy public key components all the way from the requester to the backend system and integrate them with existing security systems. In addition to certificate-based identification and authentication (I&amp;A), the Web service will also need to perform application-level monitoring and auditing of Web connections, access events, and security violations. In certain high-risk environments, a second factor of authentication, in addition to PKI certificate-based I&amp;A, may be desired. This second factor may include a static password, a dynamic password, or a biometric. In some applications, the user's initial authentication may be via a second-factor mechanism during the authenticated session. Security for the mainframe was not designed with the SOA processing model in mind. Rather, mainframe security was designed for a closed, well-defined, and tightly controlled environment. Key characteristics of such environments include a known and relatively trusted user population, a well-defined set of applications, and firm connectivity boundaries.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services."}]}
{"id": "nist_01585", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Both finger's template records shall be wrapped in a single CBEFF structure AS05.02.01: prior to storage on the PIV card. according to NIST PIV Data Model Test Guidelines According to PIV Data Model Test Guidelines, Both finger's template records shall be wrapped in a single CBEFF structure AS05.02.01: prior to storage on the PIV card.: e is constructed in accordance with this assertion. VE05.02.01.01: The vendor shall specify in its documentation the CBEFF structur TE05.02.01.01: The tester shall parse the biometric data container to verify this assertion. elf is tested in later assertions. Note: The CBEFF structure its", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_01586", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Secure Domain Name System (DNS) Deployment Guide provide? (Section 110) e servers is as follows: ``` acl 'valid_secondary_NS' { 224.10.229.5; 224.10.235.6; 239.10.245.25; }; ``` The allow-transfer substatement can be used in a zone statement and in an options statement. When it is used in a zone statement, it can restrict zone transfer for that zone; when it is used in an options statement, it can restrict zone transfer for all zones in the name server. The allow-transfer substatement at the server level is as follows: ``` options { allow-transfer { 'valid_secondary_NS'; }; }; ``` The allow-transfer substatement at the zone level is as follows: ``` zone 'example.com' { type master; file 'zonedb.example.com'; allow-transfer { 'valid_secondary_NS'; }; }; ``` The foregoing statements apply to primary name servers. In the secondary and stealth secondary name servers, zone transfer should be disabled as shown below: ``` zone 'example.com' { type slave; masters { 224.239.5.1; } ; file 'zonedb_bak.example.com'; allow-transfer { none; }; }; ``` NSD has a similar set of tools to restrict zone transfers to only a chosen set of slave servers. Like BIND, the administrator should learn and use the options available in the NSD configuration file. There is no way to create access control lists (ACLs), but an administrator can list the individual IP address of slave servers in the zone statements in the NSD configuration file. In the configuration file, the provide-xfr statement is used in the zone statement block of the nsd.conf file much like a combined masters statement and allow-transfer statement in BIND configuration files: ``` zone: #allow transfer from subnet provide-xfr: 169.192.85.0/24 #prevent transfer from specific IP address in block provide-xfr: 169.192.85.66 BLOCKED ``` Only one IP address should appear in a provide-xfr statement, but the address can be an entire subnet. The provide-xfr statement allows transfers; all other transfer requests are rejected by default.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Domain Name System (DNS) Deployment Guide."}]}
{"id": "nist_01587", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT) provide? (Section 333) t affect supply chain security. These other aspects should be considered directly, where and when they have an impact on security management, including transporting these goods along the supply chain. | Approved Standard | | 20243- 1:2018 | ISO/IEC | Information Technology -- Open Trusted Technology Provider Standard (O-TTPS) Identifies secure engineering best practices, including secure management of the IT products, components, and their supply chains | Approved Standard Conformity Assessment | | 27036- 1:2014 | ISO/IEC | Information technology - Security techniques - Information security for supplier relationships - Part 1: Overview and concepts | Approved Standard | Supply Chain Risk Management (SCRM): Standards that provide the confidence that organizations will produce and deliver information technology products or services that perform as required and mitigate supply chain-related risks, such as the insertion of counterfeits and malicious software, unauthorized production, tampering, theft, and poor quality products and services.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_01588", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation say about E.3.4.5 Test Case: SIDR-ROV-4.5.1? (Part 2) According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, E.3.4.5 Test Case: SIDR-ROV-4.5.1: 01i-R1-2. The RPKI VC 1 contains all used IP prefixes, but for origin 65509. The RPKI VC 2 contains all used IP prefixes of Traffic A with origin 65511, and IP prefixes of Traffic B with origin 65501. VC 1 should result in invalid for all routes in R1-1, and VC 2 will result in valid for all routes in R1- 2 if validated using the RPKI validation algorithm. All routers are configured to NOT drop invalid . Traffic A is a route originated by AS 65511. Traffic B has three routes: one learned via IBGP network, one via static network, and one via local network. R1-1: Configure the connection to RPKI VC 1 and enable Extended Community String. R1-2: Configure the connection to RPKI VC 2 and enable Extended Community String. The following configuration for Routers AS65501 and AS65501i has been added: | | IPv4 or IPv6? | Both Test Harness or Hardware with Live | |-----------------|--------------------------------------------------------------------------------------------------------------------------| | Procedure | 1. Configure the AS 65511 router to redistribute Traffic A to AS 65501. 2. Configure AS 65501 to redistribute Traffic B. |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_01589", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Personal Identity Verification (PIV) of Federal Employees and Contractors say about Zone 5B? According to Personal Identity Verification (PIV) of Federal Employees and Contractors, Zone 5B: Physical Characteristics of Cardholder When a cardholder attempts to pass through an access control point for a federally controlled facility, a human guard SHALL perform visual identity verification of the cardholder and SHALL determine whether the identified individual should be allowed through the control point. The following steps SHALL be applied in the visual authentication process: - The guard at the access control entry point determines whether the PIV Card appears to be genuine and has not been altered in any way. - The guard compares the cardholder's facial features with the photograph on the card to ensure that they match. - The guard checks the expiration date on the card to ensure that the card has not expired. - The guard compares the cardholder's physical characteristic descriptions to those of the cardholder. (Optional) - The guard collects the cardholder's signature and compares it with the signature on the card. (Optional) - One or more of the other data elements on the card (e.g., name, employee affiliation, agency card serial number, issuer identification, agency name) are used to determine whether the cardholder should be granted access. Some characteristics of the visual authentication mechanism include the following: - human inspection of the card, - does not provide rapid or high-volume access control, - susceptible to human error, - some resistance to the use of an unaltered card by a non-owner, - low resistance to tampering and forgery, and - does not provide protection against the use of a revoked card.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Personal Identity Verification (PIV) of Federal Employees and Contractors."}]}
{"id": "nist_01590", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EP-67 in Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)? (Part 295) Control EP-67: ITU International Telecommunication Union ITU-T International Telecommunication Union - Telecommunication JTC Joint Technical Committee LAN Local Area Network LDAP Lightweight Directory Access Protocol LES Lean Execution System LoRa Alliance Long Range Alliance LTE Long Term Evolution M2M Machine to Machine MAC Message Authentication Code MES Manufacturing Execution System MLE Mesh Link Establishment MQTT Message Queuing Telemetry Transport NATO North Atlantic Treaty Organization NERC North American Electric Reliability Corporation NHTSA National Highway Traffic Safety Administration NOAA National Oceanic and Atmospheric Administration NS/EP National Security and Emergency Preparedness NSC's Cyber IPC National Security Council's Cyber Interagency Policy Committee NSTAC President's National Security Telecommunications Advisory Committee OASIS Organization for the Advancement of Structured Information Standards OCF Open Connectivity Foundation OFB Output Feedback Block OMA Open Mobile Alliance OMG Object Management Group OpenFog RA OpenFog Reference Architecture OSDP Open Supervised Device Protocol OTA Open Travel Alliance O-TTPS Open Trusted Technology Provider Standard PCI Payment Card Industry PHR Personal Health Records PID Proportional Integral Derivative PII Personally Identifiable Information PKCS Public-Key Cryptography Standards PKI Public Key Infrastructure PLC Programmable Logic Controllers PSS Probabilistic Signature Scheme PTK Pairwise Transient Key QMS Quality Management Systems RA Reference Architecture RADIUS Remote Authentication Dial-In User Service RFC Request for", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_01591", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways provide? (Section 70) software and critical software platforms. | Objective 5 : Strengthen the understanding and performance of humans' actions that foster the security of critical software and critical software platforms. | Objective 5 : Strengthen the understanding and performance of humans' actions that foster the security of critical software and critical software platforms. | | SM 5.1: Train all users of critical software, based on their roles and responsibilities, on how to securely use the software and the critical software platforms. | PR.AT-1 | AT-2, AT-3 | | Security Measure (SM) | Cybersecurity Framework Subcategories | SP 800-53 Rev. 5 Controls | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------------------| | SM 5.2: Train all administrators of critical software and critical software platforms, based on their roles and responsibilities, on how to securely administer the software and/or platforms. | PR.AT-2 | AT-3, CP-3 | | SM 5.3: Conduct frequent awareness activities to reinforce the training for all users and administrators of critical software and platforms, and to measure the training's effectiveness for continuous improvement purposes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_01592", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture provide? (Section 4) s 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. high-performance computing; HPC reference architecture; HPC security; HPC security posture; HPC threat analysis; security guidance. 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. NOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture."}]}
{"id": "nist_01593", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does BIOS Protection Guidelines for Servers provide? (Section 36) . - 3-C.i If verification fails, then the system shall initiate a recovery procedure. - 3-C.ii Automatic recovery mechanisms which initiate recovery to a protected, authentic BIOS should be supported. - 3-D Each RTU shall be protected from modifications outside the authenticated update mechanisms. - 3-D.i Protection mechanisms that ensure the integrity of the RTU shall be engaged prior to execution of code outside of the RTU. - 3-D.ii RTU integrity protections shall be enforced by hardware mechanisms that are disengaged only by an authorized mechanism, for example system reset. - 4-A The design of the system and accompanying system components and firmware shall ensure that there are no mechanisms to install and execute unauthenticated BIOS code, except through physical intervention and the secure local update mechanism. - 4-B The authenticated BIOS update mechanism shall be the exclusive mechanism for modifying the RTU absent physical intervention through the secure local update mechanism. - 4-C The design of the system and accompanying system components and firmware shall ensure that there are no mechanisms that allow the host processor or any other system component to bypass the authenticated update mechanism for updating the RTU, except for the secure local update mechanism. - 4-D While a system component may have read access to system flash memory, it shall not be able to directly modify the RTU unless that component serves as an RTU itself. - 5-A Service Processors employed as a Root of Trust to protect BIOS, shall meet the following requirements: - 5-A.i Updates to the SP code, cryptographic keys, and static data stored on the SP flash memory shall be by way of an authenticating update mechanism. - 5-A.ii The SP environment shall be controlled such that only authenticated code can be executed on the SP. - 5-A.iii Authorization should be required for user interaction with the SP.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: BIOS Protection Guidelines for Servers."}]}
{"id": "nist_01594", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Fingerprint Identification and Mobile Handheld Devices_ An Overview and Implementation say about Reports on Computer Systems Technology? According to Fingerprint Identification and Mobile Handheld Devices_ An Overview and Implementation, Reports on Computer Systems Technology: The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL's responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Interagency Report discusses 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 18 pages (2006)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Fingerprint Identification and Mobile Handheld Devices_ An Overview and Implementation."}]}
{"id": "nist_01595", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Foundations of a Security Policy for Use of the National Research and Educational Network say about 2.2.2 Supercomputing Initiative? According to Foundations of a Security Policy for Use of the National Research and Educational Network, 2.2.2 Supercomputing Initiative: With funding from Congress, the National Science Foundation established in 1984 a program intended to improve the availability and use of high performance computing to the science research communities. In 1985-86, NSF selected five sites as National Supercomputing Centers with computing facilities remotely accessible by other researchers through a backbone NSFNET. The selected centers were: San Diego Super Computer Center - located by the University of California at San Diego and operated by General Atomics; National Center for Supercomputing Applications operated by the University of Illinois; Cornell Theory Center - located at Cornell University; Pittsburgh Supercomputing Center - operated jointly by the University of Pittsburgh, Carnegie Mellon University and Westinghouse Electric Corporation; and John von Neumann Supercomputer Center -located in Princeton, New Jersey. Promoted as providing backbone connectivity to supercomputer centers, the network traffic of NSFNET was soon dominated by use of general services such as electronic mail, remote login, and file transfer. With the creation of the Federally funded NSFNET in 1985, ARPANET was eventually phased out and replaced by a new Defense Research Internet (DRI) for unclassified military information that would make use of NSFNET. ARPANET and MILNET became the main constituents of a TCP/IP internet DDN (Defense Data Network) - a subset of the Internet operated by the Department of Defense. Other networks in DDN include DISNET (Defense Integrated Secure Network), SCINET (Sensitive Compartmented Information Network) and WINCS (WWMCCS Intercomputer Command and Control System) of the World Wide Military Command and Control System [QUAR90].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, compartmented. Contains guidance on protecting sensitive government information. Source: Foundations of a Security Policy for Use of the National Research and Educational Network."}]}
{"id": "nist_01596", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS) provide? (Section 164) s them from directly performing those actions (i.e., through untrusted system utility software.) This is a version of the \"who watches the watcher\" problem and is discussed in more detail below. - P8. The responsibility for creating, installing, running, and acting on the results of IVP (consistency checking) software cannot be assigned to the system itself in any general way - it must be done by management. The system can, however, ensure that results that purport to come from an IVP (such as a reconciliation of accounts) cannot be generated by masquerading software if each IVP (or collections of them) , and only an IVP, is installed (by procedures like P5 and P6) as a trusted subject whose a-max label is something like \"account reconciliation.\" Following, very briefly, is an analysis of how each of the 9 requirements of the Clark &amp; Wilson model is met by the above configuration rules or by the inherent properties of a Bl or higher class trusted system. - P8 CI: IVP Certification C2 : TP Certification - P6 El: TP to CDI enforcement - P2 , P4 , P6, and TCSEC security (integrity) policy enforcement - E2: User to TP enforcement - PI, P4 , P6, and TCSEC security (integrity) policy enforcement C3 : Separation of duties - primarily P4 and PI - E3: User identity authentication identification - TCSEC and authentication - P6 - C4; Audit trail and TCSEC audit requirements (for security actions) C5: Valid data P6 - P5, - E4 : Can't change own authorization or affect own transaction - P4 , P7 , and TCSEC security (integrity) policy - enforcement One topic that was somewhat glossed over above is that of what kind of controls should be exercised over those who are entrusted with authority to change the system itself, including authorization information such as the integrity categories given to users or trusted subjects. The following rules, all derived from the separation of duties principle, seem to make sense: - Rl.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)."}]}
{"id": "nist_01597", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control UI-64 in Guidelines for the Secure Deployment of IPv6? (Part 93) Control UI-64: ter Solicitation (RS) . When an interface becomes enabled, hosts may send RSs that request routers to generate RAs immediately rather than at their next scheduled time. - \uf03c Router Advertisement (RA) . Routers advertise their presence together with various link and Internet parameters either periodically or in response to a RS message. RAs contain prefixes used for on-link determination and address configuration, a suggested hop limit value, the Maximum Transmission Unit (MTU) for the link, etc. - \uf03c Neighbor Solicitation (NS) . Nodes send NSs to determine the link-layer address of a neighbor or to verify that a neighbor is still reachable via a cached link-layer address. NSs are also used for Duplicate Address Detection (DAD). - \uf03c Neighbor Advertisement (NA) . A response to a NS message. A node may also send unsolicited NAs to announce a link-layer address change. - \uf03c Redirect Message . Used by routers to inform hosts of a better first hop for a destination. A common use of the NS and NA messages is to resolve IP addresses by discovering the MAC (Media Access Control) addresses of nodes on the same link. A sender must discover the recipient's MAC address to send a data packet. Figure 3-11 illustrates this example of the ND process. Figure 3-11. Example of Neighbor Discovery <!-- image --> For NS, the sending node (Host A) knows the unicast address of the destination node (Host B) is local because of the network prefix. Knowing this, it uses a link-local solicited-node multicast address to send its NS message.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_01598", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does An Analysis of Computer Security Safeguards for Detecting and Preventing Intentional Computer Misuse provide? (Section 34) | | H | | CD | CO | | | | | | woo: | | CO QCcn4-)CQPj4-lCOt-( | | | | | | | | Vj | | | OXJ 03.-iV43a33 | | | | | | | | | | | c^ | | | | | | | | | | | | | | | | ^ | | | | | | | | | in | | | M-l \u2022r4 TJ J-l 4J CO .-I CJ Cfl 44 M-l 0) CO -H 3 o CU -H x: di g O Q H O S Q O H Q \u2022H a!", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: An Analysis of Computer Security Safeguards for Detecting and Preventing Intentional Computer Misuse."}]}
{"id": "nist_01599", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Derived PIV Application and Data Model Test Guidelines provide? (Section 151) eter command data field) or '63 CX' (verification failed, with X indicating the number of further allowed retries (verify the error code supplied matches what is described in vendor documentation). 4. From Step 4, the command returns status word '6A 80' (incorrect parameter in command data field) or '63 CX' (verification failed, | 13 It may be necessary to perform a successful VERIFY command while performing the test scenario in order to keep the Derived PIV Application Password's retry counter from dropping to 0. | | with X indicating the number of further allowed retries) (verify the error code supplied matches what is described in vendor documentation). 5. From Step 5, the command returns status word '6A 80' (incorrect parameter in command data field) or '63 CX' (verification failed, with X indicating the number of further allowed retries) (verify the error code supplied matches what is described in vendor documentation).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_01600", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cryptographic Key Management Workshop Summary -- June 8-9, 2009 say about Matt Fanto, Aegis? According to Cryptographic Key Management Workshop Summary -- June 8-9, 2009, Matt Fanto, Aegis: - The focus of the talk was on KM in the auto industry. Cryptography is being, or will be, used in all aspects of the automotive business, including within the car itself. They are concerned with (1) a single point of failure, where systems are without support for redundancy, so that KM systems or backups are at the risk of a BIG loss (catastrophic); (2) immediate needs versus costs, and a more flexible credentialing system - many manufacturers are locked into the current system with no way to change -Electronic Key Management (EKM) is needed that can leverage existing policies and authentication methods to lower cost and give faster deployment; and (3) an offline availability of keys.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Cryptographic Key Management Workshop Summary -- June 8-9, 2009."}]}
{"id": "nist_01601", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information say about B.1. Establishing Federation Trust? (Part 2) According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information, B.1. Establishing Federation Trust: nd behaves in a reliable, trustworthy way. This type of trust may be formalized in contracts or trust frameworks. Public keys for SAML IdPs and RPs are typically communicated using X.509 certificates. However, in most cases it is not necessary to establish or use a trusted certificate authority to issue certificates for SAML signatures or encryption. When certificates are used to assert the identity of a website or an email address, accepting only certificates from trusted certificate authorities is critical. When establishing a SAML integration, however, trust is explicitly established in a specific signing or encryption key; it is not inherited from a trusted authority. Message switches today do not commonly support SAML for user authentication. Switch vendors may take different approaches to SAML implementation. A SAML assertion could be used to authenticate a user and initiate a session for a defined period during which the user could submit multiple queries. Other designs are possible; for example, the switch might not maintain session state and instead might require a SAML assertion to be sent along with each individual query. The approach may be dependent on the specific vendor technology and implementation. The rest of this appendix covers the following topics: - Challenges in using federation technologies for message switch use cases (Appendix B.2) - Meeting FAL requirements in complex federation scenarios (Appendix B.3) - Options for federated architecture configurations (Appendix B.4) - VPN integration (Appendix B.5)", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, certificate authority. Contains security framework guidance for authentication systems. Source: Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information."}]}
{"id": "nist_01602", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Intrusion Detection and Prevention Systems (IDPS) say about 9.4.2.1 Daily Use? (Part 1) According to Guide to Intrusion Detection and Prevention Systems (IDPS), 9.4.2.1 Daily Use: 9.4.2.1 Daily Use Organizations should consider how the IDPS solution needs to be used on a daily basis for monitoring security events, performing analysis of events of interest, and generating reports. Because these three activities are often intertwined, it is often easiest to assess them together.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Intrusion Detection and Prevention Systems (IDPS)."}]}
{"id": "nist_01603", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Segmentation in a Small Manufacturing Environment provide? (Section 40) esign, which involves the following tasks: - Write policies for the company and for each security zone, including identifying users and permissions required. - Write detailed procedures where needed. Include steps for executing each policy. - Add technical security controls to the network and devices. - o Determine and implement appropriate settings on devices in the environment. - o Select and purchase security solutions as needed to meet security goals. - o Configure security solutions and products. Security segmentation is an approach to mitigate cyber vulnerabilities for small manufacturing environments through use of security zones. Implementing security controls and improving the cybersecurity posture are part of a journey not a one-time task. Each step on that journey makes a facility more secure and less vulnerable to a cyber attack. To facilitate the difficult task of implementing security controls, a limited initial set of security controls are presented as an example to begin the cyber risk mitigation journey. Additional cybersecurity practices can be selected from NISTIR 8183 Rev. 1 [3] as needed by the business. The security architecture design activities presented in this paper are foundational and will prepare the organization for additional security strategies like Zero Trust. - [1] Jeff Winter, What Is Industry 4.0?, https://blog.isa.org/what-is-industry-40 - [2] National Institute of Standards and Technology (2018) Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Cybersecurity White Paper (CSWP) NIST CSWP 6. https://doi.org/10.6028/NIST.CSWP.6 - [3] Stouffer KA, Zimmerman T, Tang C, Pease M, Lubell J, Cichonski J, McCarthy J (2020) Cybersecurity Framework Version 1.1 Manufacturing Profile. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Internal Report (IR) 8183 Rev.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Security Segmentation in a Small Manufacturing Environment."}]}
{"id": "nist_01604", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Secure Domain Name System (DNS) Deployment Guide provide? (Section 166) between 1 - 15 octets would be acceptable for the majority of cases. Note that for zones that are dynamically resigned as needed may not be able to change the salt for NSEC3 RR's as an atomic process. In these cases, the salt rollover procedure is similar to the key algorithm rollover procedure in that the NSEC3 RR chain with the new salt is generated first (ending with the NSEC3PARAM RR) before removing the old (outgoing) NSEC3 chain. The iterations value depends on factors that are largely beyond the control of DNS administrators. The iterations value is included to increase the amount of work an attacker must complete when conducting a brute force attack offline against a known hashed name from the zone. The goal is to set this value so the amount of work is equal to the time needed to conduct a brute force attack against the server itself (including network lag, etc.). So choosing a value for the iterations requires a good estimate of the computational power available to an attacker and the time required to perform a brute force dictionary attack against an online DNS server. However, setting the value too high would result more work being done by the server and valid clients that may result in slow response time for end users and may be a possible Denial of Service (DoS) vector for servers and clients. The iterations value should be reviewed annually and changed if conditions warrant. Since the average DNS query response time is in the range of 25 to 200 ms, the iterations value should be chose to reflect the number of hash calculations the average processor could do in that time period. However, in practice the value should be lower to account for client processing power and to speed response for valid clients. Basic empirical work has shown that the ideal iteration value when using SHA-1 should be between 1 and 500, with values 1-200 recommended for average zones.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Domain Name System (DNS) Deployment Guide."}]}
{"id": "nist_01605", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Computer Security Log Management? (Part 106) Control ES-1: ould provide a stronger assurance of a successful attack than either log source would alone, and it would also likely contain more data on the attack than either individual source would have recorded. Another example of using correlation as a factor for prioritization is using information on known vulnerabilities in the 59 As described in Section 3.1, filtering does not alter the content of the original logs-it simply restricts which log entries are used for analysis. The filtered entries in the original log data might be needed for any number of reasons, including providing context for other entries and identifying long-term security problems through trend analysis. organization's installed operating systems and applications to assign a higher priority to log entries that are related to these vulnerabilities. ## 5.2.3 Comparing System-Level and Infrastructure-Level Analysis Analysis is typically very similar for system-level and infrastructure administrators. The main difference is that for infrastructure administrators, log analysis is often a primary responsibility, whereas for systemlevel administrators it is often a secondary responsibility, particularly if the infrastructure administrators are reviewing the most important log entries from systems. In such an arrangement, infrastructure administrators typically perform log analysis on an ongoing basis each day, and system-level administrators perform periodic reviews (e.g., daily, weekly) commensurate with the criticality of each system and its information. Also, infrastructure administrators might have access to more sophisticated tools than system-level administrators do because it is cost-prohibitive to have them available for all systems.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Computer Security Log Management."}]}
{"id": "nist_01606", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector? (Part 88) Control AM-1: | |-------------------------------------------------------------------------------------------------------------------------------| ## 6.1.7 Test Case: PACS-6 | Parent Requirement | (CR-3) Enterprise Domain and Identity Management-Access Control (CR-6) Data Security | |--------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Testable Requirement | (CR-3.b) User Authentication, (CR-3.c) Device and System Authentication, (CR-6.a) In-Transit Encryption | | Description | Show how to securely review archived medical images.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, identity management. Contains security framework guidance for authentication systems. Source: Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector."}]}
{"id": "nist_01607", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium say about Conclusion? According to Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium, Conclusion: High-end AM printers are expensive, highly calibrated machines, increasingly complex, and generally not 'plug-and-play' systems. With respect to the system discussed in this presentation, there has been a great deal of ongoing support from the OEM in order to optimize printer operational performance. This type of support requires remote connectivity to the system. When the manufacturer is a foreign entity, this situation compounds security challenges and complicates protocols due to the need to comply with International Traffic in Arms (ITAR) regulations that may prohibit collaborations. At a minimum, many security assessment protocols and mitigation procedures implemented typically for enterprise business systems should be applied or adapted for implementation and operation of DDM systems.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium."}]}
{"id": "nist_01608", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management provide? (Section 253) Y The organization establishes and retains unique identification of [Assignment: organization-defined supply chain elements, processes, and actors] for the system, system component, or system service. | | SA-12-z-15-z | SA-12 (15) | (15) SUPPLY CHAIN PROTECTION | PROCESSES TO ADDRESS WEAKNESSES OR DEFICIENCIES The organization establishes a process to address weaknesses or deficiencies in supply chain elements identified during independent or organizational assessments of such elements. | | SA-18 | SA-18 | SA-18 TAMPER RESISTANCE AND DETECTION Control: The organization implements a tamper protection program for the system, system component, or system service. | | SA-18-z-01-z | SA-18 (1) | (1) TAMPER RESISTANCE AND DETECTION | MULTIPLE PHASES OF SDLC The organization employs anti-tamper technologies and techniques during multiple phases in the system development life cycle including design, development, integration, operations, and maintenance. | | SA-18-z-02-z | SA-18 (2) | (2) TAMPER RESISTANCE AND DETECTION | INSPECTION OF SYSTEMS, COMPONENTS, OR DEVICES The organization inspects [Assignment: organization-defined systems, system components, or devices] [Selection (one or more): at random; at [Assignment: organization-defined frequency], upon [Assignment: organization-defined indications of need for inspection]] to detect tampering. | | SA-19-a | SA-19 | SA-19 COMPONENT AUTHENTICITY Control: The organization: a.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management."}]}
{"id": "nist_01609", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain https://doi.org/10.6028/NIST.SP.800-88r1 according to NIST Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide, https://doi.org/10.6028/NIST.SP.800-88r1 - [SP\\_800-171] Ross RS, Pillitteri VY, Dempsey KL, Riddle M, Guissanie G (2020) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-171, Rev. 2, Includes updates as of January 28, 2021. https://doi.org/10.6028/NIST.SP.800-171r2", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide."}]}
{"id": "nist_01610", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Small Business Information Security_ The Fundamentals provide? (Section 40) owing your policies. Train employees on the following: - What they are allowed to use business computers and mobile devices for, such as if they are allowed to use them to check their personal email. - How they are expected to treat customer or business information, for example whether or not they can take that information home with them. - What to do in case of an emergency or security incident (see Section 3.4). - Basic practices as contained in Section 4 of this document. You may be able to obtain training from various organizations, such as your local Small Business Development Center (SBDC), SCORE Chapter, community college, technical college, or commercial training vendors. In addition, the Small Business Administration (SBA) and Federal Trade Commission (FTC) produce videos and topic-specific tips and information which can be used for training [SBA LC] [FTC]. Continually reinforce the training in everyday conversations or meetings. Monthly or quarterly training, meetings, or newsletters on a specific subject can help reinforce the importance of security and develop a culture of security in your employees and in your business. The activities under the Detect Function enable timely discovery of information security or cybersecurity events. Malware (short for Malicious Software or Malicious Code) is computer code written to steal or harm 10 . It includes viruses, spyware, and ransomware. Sometimes malware only uses up computing resources (e.g. memory), but other times it can record your actions or send your personal and sensitive information to cyber criminals. Install, use, and regularly update anti-virus and anti-spyware software on every device used in your business (including computers, smart phones, and tablets). It may be useful to set the anti-virus and anti-spyware software to automatically check for updates at least daily (or in 'real-time', if available), and then set it to run a complete scan soon afterwards.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Small Business Information Security_ The Fundamentals."}]}
{"id": "nist_01611", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to Security and Privacy Controls for Information Systems and Organizations? Discussion: Trusted sources include software and data from write-once, read-only media or", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01612", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices provide? (Section 551) 31, 1974; amended by Public Law 94-183, Sec. 2(2), Dec. 31, 1975, 89 Stat. 1057; Debt Collection Act of 1982, Public Law 97-365, Sec. 2, Oct. 25, 1982, 96 Stat. 1749; Congressional Reports Elimination Act of 1982, Public Law 97-375, Title II, Sec. 201(a), (b), Dec. 21, 1982, 96 Stat. 1821; Public Law 97-452, Sec. 2(a)(1), Jan. 12, 1983, 96 Stat. 2478; Central Intelligence Agency Information Act, Public Law 98- 477, Sec. 2(c), Oct. 15, 1984, 98 Stat. 2211; National Archives and Records Administration Act of 1984, Public Law 98-497, Title I, Sec. 107(g), Oct. 19, 1984, 98 Stat. 2292; Computer Matching and Privacy Protection Act of 1988, Public Law 100-503, Sec. 2-6(a), 7, 8, Oct. 18, 1988, 102 Stat. 2507- 2514; Omnibus Budget Reconciliation Act of 1990, Public Law 101-508, Title VII, Sec. 7201(b)(1), Nov. 5, 1990, 104 Stat. 1388-334; Omnibus Budget Reconciliation Act of 1993, Public Law 103-66, Title XIII, Sec. 13581(c), Aug. 10, 1993, 107 Stat. 611; Personal Responsibility and Work Opportunity Recon-ciliation Act of 1996, Public Law 104-193, Title I, Sec. 110(w), Aug. 22, 1996, 110 Stat. 2175; Social Security- Medicare and Medicaid Coverage Data Bank Repeal, Public Law 104- 226, Sec. 1(b) (3), Oct. 2, 1996, 110 Stat. 3033; General Accounting Office Act of 1996, Public Law 104-316, Title I, Sec. 115(g)(2)(B), Oct. 19, 1996, 110 Stat. 3835; Taxpayer Re-lief Act of 1997, Public Law 105-34, Title X, Sec. 1026(b) (2), Aug. 5, 1997, 111 Stat. 925; Federal Reports Elimina- tion Act, Public Law 105-362, Title XIII, Sec. 1301(d), Nov. 10, 1998, 112 Stat. 3293; Tax Relief Extension Act of 1999, Public Law 106-170, Title IV, Sec. 402(a)(2), Dec. 17, 1999, 113 Stat.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_01613", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation say about Appendix G References? (Part 2) According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, Appendix G References: lable: https://arstechnica.com/information-technology/2010/11/how-china- swallowed-15-of-net-traffic-for-18-minutes/. | | [NANOG69] | M. Adalier, K. Sriram, O. Borchert, K. Lee, and D. Montgomery, 'High Performance BGP Security: Algorithms and Architectures,' North American Network Operators Group (NANOG69) , February 2017. Available: | | [NIST BGP-SRx] | BGP Secure Routing Extension (BGP SRx) Prototype , National Institute of Standards and Technology, [website]. Available: secure-routing-extension-bgp-srx-prototype. | | [NIST SP 800-130] | E. Barker, M. Smid, D. Branstad, and S. Chokhani, A Framework for Designing Cryptographic Key Management Systems , NIST SP 800-130, National Institute of Standards and Technology, August 2013. Available: | | [NIST SP 800-152] | E. Barker, M. Smid, and D. Branstad, A Profile for U.S. Federal Cryptographic Key Management Systems, NIST SP 800-152, National Institute of Standards and Technology, October 2015. Available: | |-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [NIST SP 800-160] | Systems Security Engineering: An Integrated Approach to Building Trustworthy Resilient Systems , NIST SP 800-160 Second Public Draft, National Institute of Standards and Technology, November 2016. Available: https://doi.org/10.6028/NIST.SP.800-160 | | [NIST SP 800-30] | Guide for Conducting Risk Assessments , NIST SP 800-30 Revision 1, National Institute of Standards and Technology, September 2012.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_01614", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 653) PROTECTION | IDENTITY AND TRACEABILITY [Withdrawn: Moved to SR-4(1) and SR-4(2).] (15) SUPPLY CHAIN PROTECTION | PROCESSES TO ADDRESS WEAKNESSES OR DEFICIENCIES [Withdrawn: Incorporated into SR-3.] SA-13 TRUSTWORTHINESS [Withdrawn: Incorporated into SA-8.] CHAPTER THREE PAGE 280 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01615", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974 provide? (Section 137) erefore, to take a doomsday approach and claim that security is impossible to attain is as short sighted as to ignore the very real problems of network vulnerability. Good security is possible, today. But there are some very important conditions, most of them uivolving human and sociological issues, not technical ones. The custodians of data banks and the owners of data, as well as users and subjects, should have a large voice in determining what safeguards are present. This session, and the previous one last November addressed the question of legislation. As a concerned professional and private citizen, I welcome legislation in this area. Dr. Willis Ware's report to the Secretary. Health, Education and W^elfare presented a reasoned exposition of legislative needs. Beyond this step, I believe there are two very important actions that need to be addressed by you, me and other concerned people on a national basis. If action is started now, we should go a long way toward insuring that systems are designed with security in mind and that they are capable of safeguardmg individual and corporate rights of confidentiality that are so urgently needed. Specifications for RFP's -To date, very few Requests for Proposal have included definitive requirements for security and integrity. Certainly, if we as users don't care about the subject, it becomes very difficult for the manufacturers to include it in the design of their systems. If we do care about the subject, it is about time we put our money where our mouth is. Therefore, in a spirit of User's Lib, I am presenting an outline of a model set of specifications for requesting secure computer services or systems: Management and Operating Guidelines -Every data processing/data communications environment is sufficiently different in scope, breath, purpose and size so as to make rigid rules of security very difficult to enforce. However, there are sufficient guidelines and practices that have stood the test of time.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974."}]}
{"id": "nist_01616", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Federal and Commercial Information Security Needs provide? (Section 32) wnership within their computer systems. In addition, the ability to list group membership before granting access privileges to that group was considered by some as a necessary part of this capability. The most common approach to implementing DAC is through access control lists (ACLs) . The TCSEC encouraged ACLs as appropriate for usercontrolled access rights. However, when centrally administered, ACLs can become clumsy and difficult to maintain. In centrally administrating DAC, the system administrator assumes responsibility for ownership of all resources, determining what resources and modes of access are needed for the performance of each user's function within the organization. For each new user or every change in responsibility, the central administrator establishes the appropriate access rights within the system. Additionally, when a person leaves the organization, the central administrator deletes the person from all ACLs within the system. Many of the organizations felt ACLs were difficult for the central control and management of access rights. Many organizations preferred a centrally administered, non-discretionary set of controls to meet their security policies and objectives. During the course of this study, organizational policies and objectives have included maintaining and enforcing the rules and ethics associated with a judge's chambers, and the laws and respect for privacy of diagnosing ailments, treating of disease, and administering of medicine within a VA hospital. To support such policies, a capability to centrally control and maintain access rights is needed. The security administrator is responsible for enforcing policy and represents the organization as the \"owner\" of system objects. Access control decisions were found to be based on the roles individual users take on as part of an organization. This includes the specification of duties, responsibilities, obligations, and qualifications.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Assessing Federal and Commercial Information Security Needs."}]}
{"id": "nist_01617", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Related Controls according to NIST_SP_800-53r5_Security_Privacy_Controls? Related Controls: AC-20, CA-5, CA-6, CA-7, PM-9, RA-5, RA-10, SA-11, SC-38, SI-3, SI-12, SR-2, SR-", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01618", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case say about Installation Instructions and Configurations? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case, Installation Instructions and Configurations: Details of the solution implemented: | Name | Version | Hardware Details | |--------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Graylog Enterprise | 2.4.6 | Hyper-V Virtual Machine (Generation 1): \u2022 Processors: 2 virtual cores \u2022 Memory: 6 GB \u2022 Disk space: 400 GB Total (i) Root volume as allocated by the Virtual Appliance file provided by the vendor. (ii) 350+ GB Data volume for log storage \u2022 Network: 1 network adapter \u2022 OS: Ubuntu 14 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case."}]}
{"id": "nist_01619", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Recovering from Ransomware and Other Destructive Events say about Executive Summary? According to Data Integrity_ Recovering from Ransomware and Other Destructive Events, Executive Summary: - \uf0a7 Data integrity attacks have compromised corporate information including emails, employee records, financial records, and customer data. - \uf0a7 Destructive malware, ransomware, malicious insider activity, and even honest mistakes all set the stage for why organizations need to quickly recover from an event that alters or destroys data. Businesses must be confident that recovered data is accurate and safe. - \uf0a7 The National Cybersecurity Center of Excellence (NCCoE) at NIST built a laboratory environment to explore methods to effectively recover from a data corruption event in various Information Technology (IT) enterprise environments. NCCoE also explored auditing and reporting IT system use issues to support incident recovery and investigations. - \uf0a7 This NIST Cybersecurity Practice Guide demonstrates how organizations can develop and implement appropriate actions following a detected cybersecurity event. The solutions outlined in this guide encourage monitoring and detecting data corruption in commodity componentsas well as custom applications and data composed of open-source and commercially available components. - \uf0a7 Thorough quantitative and qualitative data collection is important to organizations of all types and sizes. It can impact all aspects of a business including decision making, transactions, research, performance, and profitability, to name a few.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Recovering from Ransomware and Other Destructive Events."}]}
{"id": "nist_01620", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations say about DISCUSSION? According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, DISCUSSION: Organizations test incident response capabilities to determine their effectiveness and identify potential weaknesses or deficiencies. Incident response testing includes the use of checklists, walk-through or tabletop exercises, and simulations. Incident response testing can include a determination of the effects of incident response on organizational operations, organizational assets, and individuals. Qualitative and quantitative data can help determine the effectiveness of incident response processes.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_01621", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches provide? (Section 113) entify the products that will best integrate with your existing tools and IT system infrastructure. We hope that you will seek products that are congruent with applicable standards and best practices. Section 3.6 Technologies, lists the products that we used and maps them to the cybersecurity controls provided by this reference solution. A NIST Cybersecurity Practice Guide does not describe 'the' solution but a possible solution. Comments, suggestions, and success stories will improve subsequent versions of this guide. Please contribute your thoughts to ds-nccoe@nist.gov . The NCCoE built a hybrid virtual-physical laboratory environment to explore methods to effectively identify sensitive data and protect against a loss of data confidentiality in various Information Technology (IT) enterprise environments. This work also highlights standards and technologies that are useful for a variety of organizations defending against this threat. The servers in the virtual environment were built to the hardware specifications of their specific software components. The NCCoE worked with members of the Data Confidentiality Community of Interest to develop a diverse (but non-comprehensive) set of security scenarios against which to test the reference implementation. These are detailed in Volume B, Section 5.2. The following table presents typographic conventions used in this volume.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches."}]}
{"id": "nist_01622", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio provide? (Section 53) -level measures 9 have been standardized, like the estimated likelihood and impact of a particular vulnerability being exploited. However, for many aspects of ICT risk, there are no standard measures. Without consistent measures, there is little basis for analyzing risk or expressing risk in comparable ways across digital assets and the systems composed of those assets. 9 NIST typically uses the term 'measures' instead of 'metrics.' For more information on the distinction, see https://www.nist.gov/itl/ssd/software-quality-group/metrics-and-measures . Risk analysis for ICT tends to be inconsistent compared to many other forms of risk. Even where guidance is provided, such as in NIST publications, the resulting risk assessment reports from agencies differ significantly. Moreover, foundational inputs for likelihood and impact calculations generally lack a standardized methodology or are at the discretion of vendors who provide a scoring system. Decisions are often made based on an individual's instinct, experience, and knowledge of conventional wisdom and typical practices. In addition, there is usually little analysis performed after controls are deployed to determine whether risks have been reduced to a level deemed acceptable (i.e., within the established risk tolerance parameters). The management of ICT risk is conducted in different ways at various levels, including at the system, organization, and enterprise levels. A common practice is for individual system-level teams to be responsible for tracking relevant risks. While system reporting to the organizational level may occur, there is typically no mechanism in place to consolidate the risk data for systems to the organization level, much less to the enterprise level. When organization or enterprise managers receive system risk data, it is often a vague risk map or at such a volume as to be impractical.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio."}]}
{"id": "nist_01623", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Common Biometric Exchange Formats Framework (CBEFF) provide? (Section 20) ag-Length-Value An application that transforms a CBEFF Basic Data Structure from one Patron Format into another Patron Format. This can include processing of the content of the BDB, but need not. CBEFF defines rules for migrating the values in Standard Biometric Header fields. CBEFF provides the required information to uniquely identify the format and the originator of every biometric data substructure within a CBEFF-compliant structure. The combination of Format Owner, Format Type, Creator and the PID fields described in Clause 5.2.1 meets this objective. CBEFF provides the capability for CBEFF-compliant data structures to be either Basic or Nested. In order to achieve this, CBEFF describes a nested data structure that can be made as complex as the originator of the biometric data structure requires. An example of a nested structure is given in Clause 5.3 . A nested structure could represent biometric data from the same biometric type (e.g., two finger templates) or different biometric data types (e.g., a finger template and a face template) while each substructure would uniquely identify the Format Owner/Format Type, the Creator and PID of each specific biometric data structure. A standard biometric format that may be embedded in a CBEFF data structure is identified by the Format Owner. Upon request by this organization the CBEFF registration Authority, the International Biometric Industry Association (IBIA) in consultation with the CBEFF Technical Development Team, will assign a Format Owner value that will identify that biometric data format. IBIA provides these values to standards organizations free of charge. It is expected that the data conforming to the biometric data format specified in that standard will be used in the CBEFF Biometric Data Block (BDB). Non-standard (proprietary) formats also need a Format Owner to be used within a CBEFF structure.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Biometric Exchange Formats Framework (CBEFF)."}]}
{"id": "nist_01624", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Considerations for Identity Management in Public Safety Mobile Networks provide? (Section 106) o generate an authentication vector (AUTN). To compute an AUTN, the HSS/AuC needs to choose a random nonce (RAND), the secret key K , and a Sequence Number (SQN) as inputs to a cryptographic function. This function produces two cryptographic parameters used in the derivation of future cryptographic keys, alongside the expected result (XRES) and authentication token (AUTN). This authentication vector is passed back to the MME for storage. In addition, the MME provides the AUTN and RAND to the UE, which is then passed to the USIM application. The USIM sends AUTN, RAND, the secret key K , and its SQN through the same cryptographic function used by the HSS/AuC. The result is labeled as RES, which is sent back to the MME. If the XRES value is equal to the RES value, authentication is successful and the UE is granted access to the network. 15 Informally known as a 'SIM card.' 16 Temporary identifiers are useful to protect users from entities maliciously eavesdropping to traffic passing over the air interface. These temporary identifiers prevent eavesdroppers from learning the permanent identity (i.e., IMSI) associated with a cellular subscriber, preventing user's mobile device from being uniquely identified. Temporary identifiers do not defend against false basestation attacks. The following diagram provides shows the LTE AKA authentication process. <!-- image --> The authentication provided by LTE authenticates the UICC to the network. The capabilities of LTE do not support public safety's need for user authentication as neither the user nor the UE are authenticated. To support user authentication, additions to the LTE family of standards or a separate authentication framework built on top of LTE would be required. The following provides additional context around the identifiers provided by LTE and their applicability to public safety.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, identity management, token. Contains security framework guidance for authentication systems. Source: Considerations for Identity Management in Public Safety Mobile Networks."}]}
{"id": "nist_01625", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.7 Chaining Blocks according to NIST Blockchain Technology Overview According to Blockchain Technology Overview, 3.7 Chaining Blocks: Blocks are chained together through each block containing the hash digest of the previous block's header, thus forming the blockchain . If a previously published block were changed, it would have a different hash. This in turn would cause all subsequent blocks to also have different hashes since they include the hash of the previous block. This makes it possible to easily detect and reject altered blocks. Figure 3 shows a generic chain of blocks. Figure 3: Generic Chain of Blocks <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain Technology Overview."}]}
{"id": "nist_01626", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Enhancement Supplemental Guidance according to Contingency Planning Guide for Federal Information Systems? Enhancement Supplemental Guidance: Examples of related plans include Business Continuity Plan, Disaster Recovery Plan, Continuity of Operations Plan, Crisis Communications Plan, Critical Infrastructure Plan, Cyber Incident Response Plan, and Occupant Emergency Plan.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Contingency Planning Guide for Federal Information Systems."}]}
{"id": "nist_01627", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is References according to Security and Privacy Controls for Information Systems and Organizations? References: [SP 800-160-1], [SP 800-160-2].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01628", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management provide? (Section 104) Communications <!-- image --> Once these expectations have been defined and communicated, practitioners can use various methods to ensure that risk is managed to stay within the limits articulated. They do this by identifying potential risks (as described in Section 2.2), estimating the probability that an impactful event will occur, calculating the potential harm to the enterprise after such an event, and analyzing the actual risk exposure (the product of likelihood and impact). Industry practitioners have demonstrated that applying risk analysis techniques like those described in Section 2.3 can be helpful for identifying, responding to, and monitoring enterprise cybersecurity risk. While statistical analysis has been available for hundreds of years, many within the CSRM community have only recently recognized the value of applying a more quantitative approach to risk estimation. It seems likely that those in the CSRM domain will continue to develop and improve statistical methods to estimate risk and include guidance regarding the application of various statistical distribution models. Responses to previous requests for information have indicated that enterprise risk managers desire increased rigor in the manner in which risk identification, analysis, and reporting are performed. This publication is designed to provide guidance and to further conversations regarding ways to improve CSRM and the coordination of CSRM with ERM. Subsequent publications in this series will describe improvements to the manner in which risk scenarios are prioritized, treated, and reported. Through the NISTIR 8286 series publications, NIST will continue to collaborate with public- and private-sector communities to address methods for improving the integration and coordination of ERM and CSRM. - [1] Stine K, Quinn S, Witte G, Gardner RK (2020) Integrating Cybersecurity and Enterprise Risk Management (ERM).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management."}]}
{"id": "nist_01629", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Connectivity and Retrieval according to Cell Phone Forensic Tools_ an Overview and Analysis Update? Connectivity and Retrieval: The password-protected device contents were successfully acquired with or without the SIM present. Basic subscriber information (i.e. IMEI) was found and reported. Memory size is not reported. (Meet)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis Update."}]}
{"id": "nist_01630", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Derived Personal Identity Verification (PIV) Credentials provide? (Section 17) Datacard.........................................................................................................23 | Entrust Datacard.........................................................................................................23 | | 3.6.2 | Intel Authenticate.......................................................................................................24 | Intel Authenticate.......................................................................................................24 | | 3.6.3 | Intercede.....................................................................................................................24 | Intercede.....................................................................................................................24 | | 3.6.4 | MobileIron ..................................................................................................................25 | MobileIron ..................................................................................................................25 | | 3.6.5 | Verizon Shared Service Provider.................................................................................25 | Verizon Shared Service Provider.................................................................................25 | | 3.6.6 | Mobile Endpoints........................................................................................................26 | Mobile Endpoints........................................................................................................26 | | 3.6.7 | Technology Mapping...................................................................................................26 | Technology Mapping...................................................................................................26 | | 5.2.1 | Managed | Architecture Build Testing ..........................................................................35 | | | 5.2.1.1 | Initial Issuance ............................................................................................35 | | | 5.2.1.2 | Maintenance...............................................................................................42 | | | 5.2.1.3 | Termination ................................................................................................42 | | | 5.2.1.4 | Derived PIV Authentication Certificate Management................................43 | | 5.2.2 | Hybrid Architecture Build Testing...............................................................................44 | Hybrid Architecture Build Testing...............................................................................44 | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | | 5.2.2.1 | Initial Issuance ............................................................................................44 | |-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | 5.2.2.2 | Maintenance............................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_01631", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 769) services. Ultimately cybersecurity, as applied to the information exchange standards, should be described as profiles of technologies and procedures which can include both \u201cpower system\u201d methods (e.g. redundant equipment, analysis of power system data, and validation of power system states) and information technology (IT) methods (e.g., encryption, role-based access control, and intrusion detection). There also can be a relationship between certain communication standards and correlated cybersecurity technologies. For instance, if Transmission Control Protocol (TCP)/Internet Protocol (IP) is being used at the transport layer and if authentication, data integrity, and/or confidentiality are important, then transport layer security (TLS) should be used. In the following discussions of information exchange standard being reviewed, these caveats should be taken into account. 9.3.2 Correlation of Cybersecurity Requirements with Physical Security Requirements Correlating cybersecurity requirements with specific physical security requirements is very complex since they generally address very different aspects of a system. Although both cyber and physical security requirements seek to prevent or deter deliberate or inadvertent adversaries from accessing a protected facility, resource, or information, physical security solutions and procedures are vastly different from cybersecurity solutions and procedures, and involve very different expertise. Each may be used to help protect the other, while compromises of one can definitely compromise the other. Physical and environmental security that encompasses protection of physical assets from damage is addressed by this document only at a high level. Therefore, assessments of standards that cover these non-cyber issues must necessarily also be at a general level.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01632", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SA-14 in Criticality Analysis Process Model_ Prioritizing Systems and Components? (Part 80) Control SA-14: | |---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Inputs | Listing of components and subcomponents matched to workflow paths from D.3; Function Diagram with Workflow Paths | | Outputs | Description of operating states to pass to D.5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Criticality Analysis Process Model_ Prioritizing Systems and Components."}]}
{"id": "nist_01633", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cell Phone Forensic Tools_ an Overview and Analysis say about Scenarios? (Part 7) According to Cell Phone Forensic Tools_ an Overview and Analysis, Scenarios: s of the device, find and display selected filenames and file contents. \u2022 Expect that text, images, and other information contained in the compressed archive formatted files can be found and reported. | | Scenario | Description | |-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Misnamed Files | Determine whether the tool can recognize file types by header information instead of file extension, and find common text and graphics formatted files that have been misnamed with a misleading extension. \u2022 Load the device (via email and device synchronization protocols) with various types of common text (e.g., . txt ) and graphics files (e.g., . bmp , . jpg , . gif , and .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_01634", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Validity according to NIST Test Personal Identity Verification (PIV) Cards Version 2? Validity: Not Before: Sep 25 23:18:12 2007 GMT, Not After: Sep 25 23:18:12 2010 GMT", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_01635", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector say about 2.3.1.1 Create PKI Certificate for Hyland Acuo VNA? According to Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector, 2.3.1.1 Create PKI Certificate for Hyland Acuo VNA: 1. Use the DigiCert Certificate Utility for Windows to generate a certificate signing request (CSR) for Hyland Acuo VNA. Information needed for requesting the certificate for Hyland Acuo VAN is below: 2. \uf0a7 Common Name: Hyland-VNA.pacs.hclab 3. \uf0a7 Subject Alternative Name: Hyland-VNA.pacs.hclab 4. \uf0a7 Organization: NIST 5. \uf0a7 Department: NCCoE 6. \uf0a7 City: Rockville 7. \uf0a7 State: Maryland 8. \uf0a7 Country: USA 9. \uf0a7 Key Size: 2048 2. Submit the created CSR to DigiCert portal for certificate signing. 3. Download and save the signed certificate along with its root certificate authority (CA) certificate in the .pem file format. 4. Import the saved certificate to DigiCert Certificate Utility for Windows, then export the certificate with its private key in the .pfx format. 5. The certificate is ready for installation.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, certificate authority. Contains security framework guidance for authentication systems. Source: Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector."}]}
{"id": "nist_01636", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is https according to Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms? https: //doi.org/10.6028/NIST.SP.800-38A", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms."}]}
{"id": "nist_01637", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Securing Web Transactions_ TLS Server Certificate Management? (Part 449) Control HA-1: TPP. 2. Certificate: These objects hold configuration data for certificates managed by Venafi TPP, including certificate authority (CA), key length, certificate owner, approver, and other information. A certificate object can have one or more applications objects-each indicating a location where the certificate is installed. 3. Device: These objects hold configuration information about the systems where certificates are deployed, including the network address and port, authentication credentials, and other information for the system. 4. Application: These objects hold information about the specific application (e.g., Apache, F5, Java, etc.) that uses a certificate on a device. Each device may have one or more applications that use certificates. The attributes and information stored in an application object depends on the type of application. For example, an F5 application object stores information such as the SSL profile, virtual server, and partition for the associated certificate on the F5 device. 5. Workflow: Workflow objects store the rules that are enforced for workflow gates within Venafi TPP. They include the stage of the certificate lifecycle where approval is needed, the required approvers, and even actions that may be automatically perform when the workflow gate is triggered. 6. CA Template: These objects store information about CAs from which Venafi TPP requests certificates and the specific certificate templates that the CAs will use. 7. Credential: These objects hold credential information that Venafi TPP uses to authenticate to other systems, including CAs, systems where certificates are managed via agentless management, etc. Passwords and private keys used in credentials are stored in encrypted form in the Venafi TPP database. ## C.2 Certificate Metadata in Venafi TPP Certificates are stored in Venafi TPP in binary form (i.e., the DER encoded version of the certificate).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, certificate authority, sso. Contains security framework guidance for authentication systems. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_01638", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is The current official CCE list is available at http according to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2? The current official CCE list is available at http: //cce.mitre.org/lists/cce\\_list.html and new CCEs can be requested from the CCE Content Team. Submitters should review the information provided at", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2."}]}
{"id": "nist_01639", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Domain Name System (DNS) Deployment Guide say about 9.8 Additional Protection Measures for DNS Query/Response? (Part 2) According to Secure Domain Name System (DNS) Deployment Guide, 9.8 Additional Protection Measures for DNS Query/Response: emented for protecting zone transfer and dynamic update transactions). Alternatively, the enterprise can provide this capability through other network security mechanisms, such as IP Security (IPsec). Guidance on how to set up IPsec protected connections between clients and a recursive caching server is beyond the scope of this document. Whatever mechanism is used for channel security of the last hop (resolving name server to stub resolver), this capability should be present in DNSSEC-aware nonvalidating stub resolvers as well, in addition to non-DNSSEC aware stub resolvers. A DNSSEC-aware nonvalidating stub resolver can leverage this trusted path to examine the setting of the AD bit in the message header of a response message it receives. These types of stub resolvers can then use this flag bit as a hint to find out whether the resolving name server was able to successfully validate the signatures for all of the data in the Answer and Authority sections of the response. In some situations, establishing a trusted path between stub resolvers and the resolving name servers that provide DNS service for them is not feasible. An example is where the resolving name server is not under the administrative domain of the enterprise but is run by an ISP. In this situation, the end-to-end protection for DNS query/response can be ensured only by having a DNSSEC-aware stub resolver or a stub resolver that can use message authentication (TSIG or SIG(0)) to communicate with a trusted caching server. A DNSSEC-aware stub resolver can indicate to the local resolving name server that it wants to perform its own signature validation by setting the checking disabled (CD) bit in its query messages. Or a stub resolver must be manually configured to use a specific resolving name server and use TSIG/SIG(0) to provide message authentication.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Domain Name System (DNS) Deployment Guide."}]}
{"id": "nist_01640", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-14 in Security and Privacy Controls for Information Systems and Organizations? Control CM-14: SIGNED COMPONENTS Control: Prevent the installation of [Assignment: organization-defined software and firmware components] without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization. Discussion: Software and firmware components prevented from installation unless signed with recognized and approved certificates include software and firmware version updates, patches, service packs, device drivers, and basic input/output system updates. Organizations can identify applicable software and firmware components by type, by specific items, or a combination of both. Digital signatures and organizational verification of such signatures is a method of code authentication. Related Controls: CM-7, SC-12, SC-13, SI-7. References: [IR 8062]. CHAPTER THREE PAGE 114 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ 3.6 CONTINGENCY PLANNING Quick link to Contingency Planning Summary Table", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01641", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 430) s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ Discussion: Organizations can document the media downgrading process by providing information, such as the downgrading technique employed, the identification number of the downgraded media, and the identity of the individual that authorized and/or performed the downgrading action. Related Controls: None. (2) MEDIA DOWNGRADING | EQUIPMENT TESTING Test downgrading equipment and procedures [Assignment: organization-defined frequency] to ensure that downgrading actions are being achieved. Discussion: None. Related Controls: None. (3) MEDIA DOWNGRADING | CONTROLLED UNCLASSIFIED INFORMATION Downgrade system media containing controlled unclassified information prior to public release. Discussion: The downgrading of controlled unclassified information uses approved sanitization tools, techniques, and procedures. Related Controls: None. (4) MEDIA DOWNGRADING | CLASSIFIED INFORMATION Downgrade system media containing classified information prior to release to individuals without required access authorizations. Discussion: Downgrading of classified information uses approved sanitization tools, techniques, and procedures to transfer information confirmed to be unclassified from classified systems to unclassified media. Related Controls: None. References: [32 CFR 2002], [NSA MEDIA]. CHAPTER THREE PAGE 178 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01642", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cell Phone Forensic Tools_ an Overview and Analysis provide? (Section 138) ls translate data to a format and structure that is understandable by the examiner and can be effectively used to identify and recover evidence. However, tools may contain some degree of inaccuracies. For example, the tool's implementation may contain a programming error; a specification used by the tool to translate encoded bits into data comprehensible by the examiner may be inaccurate or out of date; or the protocol structure generated by the cellular device as input may be incorrect, causing the tool to function improperly. In addition, a knowledgeable suspect may tamper with device information to foil the workings of a tool or apply a wiping tool to remove or eliminate data. Over time, experience with a tool provides an understanding of its limitations, allowing an examiner to compensate where possible for any shortcomings or to turn to other means of recovery. While the tools discussed in this paper generally performed well and have adequate functionality, new versions are expected to improve and better meet investigative requirements. For instance, during the course of preparing this report, a new version for nearly every tool was issued, which included support for additional phones and enhanced functionality. The following criteria highlight some items to consider when choosing among available tools: - Usability - the ability to present data in a form that is useful to an investigator. - Comprehensive - the ability to present all data to an investigator so that evidence pertaining to an investigation can be identified. - Accuracy - the quality that the output of the tool has been verified and a margin of error ascertained. - Deterministic - the ability for the tool to produce the same output when given the same set of instructions and input data. - Verifiable - the ability to ensure accuracy of the output by having access to intermediate translation and presentation results.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_01643", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control BA-123 in Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio? (Part 14) Control BA-123: ponsibility, and accountability that enables managers to acceptably manage risk. In this regard, there can be multiple participants in the governance process, depending on context and enterprise type. Larger entities might implement risk governance mechanisms across the enterprise with more specific governance mechanisms at the organization (e.g., division, portfolio, or bureau) and apply that strategy to systems or programs. Table 2 illustrates some notional roles and responsibilities at each level. Table 2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio."}]}
{"id": "nist_01644", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-1 in Domain Name System-Based Electronic Mail Security? (Part 110) Control AC-1: Table 2.3 Test Sequence 3 | Sequence 3 | NCCoE Lab | NCCoE Lab | NCCoE Lab | Remote Sites | Certificate on Receiver Side | |--------------|-------------|-------------|------------------|----------------------------------------------------------------------------------------------|--------------------------------| | Event | MUA | MTA | DNS Service | Secure64 and NLnet Labs | Certificate on Receiver Side | | 13 | Outlook | Exchange | Active Directory | Thunderbird on MacBook, Postfix/ Dovecot, DNS Authority/ Cache/Signer Local CA issued (CU=2) | Local CA (CU=1) | | Sequence 3 | NCCoE Lab | NCCoE Lab | NCCoE Lab | Remote Sites | Certificate on Receiver Side | |--------------|------------------------|------------------|-----------------------------|-------------------------|--------------------------------| | Event | MUA | MTA | DNS Service | Secure64 and NLnet Labs | Certificate on Receiver Side | | 14 | Thunderbird | Postfix/ Dovecot | NSD4/Unbound/ Open DNSSEC | Same as 13 | Local CA issued (CU=1) | | 15 | Thunderbird on MacBook | Postfix/ Dovecot | DNS Authority/ Cache/Signer | Same as 13 | Local CA issued (CU=1) | | 16 | Outlook | Exchange | Active Directory | Same as 13 | Self-signed Cert (CU=3) | | 17 | Thunderbird | Postfix/ Dovecot | NSD4/Unbound/ Open DNSSEC | Same as 13 | Self-signed Cert (CU=3) | | 18", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_01645", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Developing Trust Frameworks to Support Identity Federations say about What are Compliance Marks?? According to Developing Trust Frameworks to Support Identity Federations, What are Compliance Marks?: Often used to augment a registry listing to make marketing and discovery of compliant services more effective, a compliance mark is a visually recognizable mark that can be placed on the web properties and communication materials of compliant framework participants. These can-and in most cases should-be further supported by electronic verification capabilities.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Trust Frameworks to Support Identity Federations."}]}
{"id": "nist_01646", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is http according to Guidelines for Smart Grid Cybersecurity? http: //www.hhs.gov/ocr/privacy/hipaa/administrative/privacyrule/privruletxt.txt [accessed 8/11/2014]. There may also be", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01647", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Securing Public Web Servers say about Appendix B-Glossary? (Part 3) According to Guidelines on Securing Public Web Servers, Appendix B-Glossary: ded to manage and track the installation of patches. PharmingUsing technical means to redirect users into accessing a fake Web site masquerading as a legitimate one and divulging personal information. PhishingUsing social engineering techniques to trick users into accessing a fake Web site and divulging personal information. ProxyA proxy is an application that 'breaks' the connection between client and server. The proxy accepts certain types of traffic entering or leaving a network, processes it, and forwards it. This effectively closes the straight path between the internal and external networks, making it more difficult for an attacker to obtain internal addresses and other details of the organization's internal network. Proxy servers are available for common Internet services; for example, a Hypertext Transfer Protocol (HTTP) proxy used for Web access and a Simple Mail Transfer Protocol (SMTP) proxy used for e-mail. Service PackMicrosoft's term for a collection of patches integrated into a single large update. SOCKS Protocol -An Internet protocol to allow client applications to form a circuit-level gateway to a network firewall via a proxy service. System AdministratorA person who manages a computer system, including its operating system and applications. A system administrator's responsibilities are similar to that of a network administrator. VirtualizationThe use of an abstraction layer to simulate computing hardware so that multiple operating systems can run on a single computer. VulnerabilityA security exposure in an operating system or other system software or application software component. A variety of organizations maintain publicly accessible databases of vulnerabilities based on the version numbers of software. Each vulnerability can potentially compromise the system or network if exploited. Web ServerA computer that provides World Wide Web (WWW) services on the Internet.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Guidelines on Securing Public Web Servers."}]}
{"id": "nist_01648", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automation Support for Security Control Assessments_ Software Asset Management say about Defect Check Rationale Table? According to Automation Support for Security Control Assessments_ Software Asset Management, Defect Check Rationale Table: A failure in effectiveness of this control item results in a defect in one or more of the following defect checks: | Determination Statement ID | Defect Check ID | Defect Check Name | Rationale If an [organization-defined measure] for this defect check is above [the organization- defined threshold], then defects in maintaining an adequate number of prior software baseline versions to support rollback related to this control item might be the cause of the defect, i.e.,\u2026 | |------------------------------|-------------------|-----------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | CM-2(3){1} | SWAM- L05 | Number of prior versions of installed software inadequate | lack of prior versions of installed software to enable rollback and recovery. |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_01649", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Telehealth Remote Patient Monitoring Ecosystem say about Appendix D Problematic Data Actions and Risks? According to Securing Telehealth Remote Patient Monitoring Ecosystem, Appendix D Problematic Data Actions and Risks: While the project team was writing this practice guide, the National Institute of Standards and Technology (NIST) published the NIST Privacy Framework, Version 1.0 [5]. Privacy concerns should be addressed particularly in healthcare environments. The project team examined the NIST Privacy Framework and included approaches that lead toward better understanding and managing the privacy risks that may be present in remote patient monitoring (RPM) deployments. Structurally, the NIST Privacy Framework is like the NIST Cybersecurity Framework. Both frameworks should be applied when evaluating enterprise programs and developing mitigation strategies. Applying the Privacy Framework does not supersede the NIST Cybersecurity Framework. Rather, the Privacy Framework provides organizations with information to understand privacy-specific risks. For more information about the NIST Privacy Framework , healthcare delivery organizations (HDOs) should review NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0 [5].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_01650", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.2 Message Authentication Code (MAC) Algorithm according to NIST Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography, 5.2 Message Authentication Code (MAC) Algorithm: A Message Authentication Code (MAC) algorithm defines a family of cryptographic functions that is parameterized by a symmetric key. It is computationally infeasible to determine the MAC of a (newly formed) MacData value without knowledge of the MacKey value (even if one has seen the MACs corresponding to other MacData values that were computed using that same MacKey value). The input to a MAC algorithm includes a symmetric key, called MacKey and a binary data string called MacData that serves as the 'message.' That is, a MAC computation is represented as MAC( MacKey , MacData ). In this Recommendation, a MAC algorithm is used if key confirmation is performed during key establishment (see Section 5.9); a (possibly different) MAC algorithm may be used for the required key-derivation process (see Section 5.8 and SP 800-56C). Key confirmation requires the use of an approved MAC algorithm, i.e., HMAC, AESCMAC or KMAC. HMAC is specified in FIPS 198 and requires the use of an approved hash function. AES-CMAC is specified in SP 800-38B for the AES block cipher algorithm specified in FIPS 197. KMAC is specified in SP 800-185. When used for key confirmation, an entity is required to compute a MAC tag on received or derived data using a MAC algorithm with a MacKey that is derived from a shared secret. The MAC tag is sent to the other entity participating in the key-establishment scheme in order to provide assurance that the shared secret or derived keying material was correctly computed. MAC-tag computation and verification are defined in Sections 5.2.1 and 5.2.2. If a MAC algorithm is employed in key derivation, an approved MAC algorithm shall be selected and used in accordance with SP 800-56C.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}]}
{"id": "nist_01651", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE) provide? (Section 124) the Security of Mobile Applications [50] - \uf0a7 NIST SP 800-171 Revision 2, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations [60] - \uf0a7 NIST SP 800-181, National Initiative for Cybersecurity Education (NICE) Cybersecurity Workforce Framework [7] - \uf0a7 Center for Internet Security [46] - \uf0a7 Executive Office of the President, Bring Your Own Device Toolkit [68] - \uf0a7 Federal Chief Information Officers (CIO) Council and Department of Homeland Security (DHS) Mobile Security Reference Architecture, Version 1.0 [69] - \uf0a7 Digital Services Advisory Group and Federal Chief Information Officers Council, Government Use of Mobile Technology Barriers, Opportunities, and Gap Analysis [70] - \uf0a7 International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) 27001:2013, Information technology-Security techniques-Information security management systems-Requirements [45] - \uf0a7 Mobile Computing Decision Example Case Study [71] - \uf0a7 Mobile Services Category Team (MSCT) Advanced Technology Academic Research Center (ATARC), Mobility Strategy Development Guidelines Working Group Document [72] - \uf0a7 MSCT ATARC, Mobile Threat Protection App Vetting and App Security Working Group Document [73] - \uf0a7 MSCT, Device Procurement and Management Guidance [74] - \uf0a7 MSCT, Mobile Device Management (MDM), MDM Working Group Document [75] - \uf0a7 MSCT, Mobile Services Roadmap, MSCT Strategic Approach [76] - \uf0a7", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_01652", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Study of OSI Key Management provide? (Section 204) . Here are some suggestions on diagnostic information. It is up to the local security policy to decide whether it can be sent. The concern is that to much information would be provided to an intruder. | Type | Reason | |--------|---------------------------------------------------| | 0 | Proposed Confidentiality Algorithms not supported | | 1 | r*roposed Integrity Algorithms not supported | | 2 | Proposed Key Exchange Methods not supported | The diagnostic parameters are defined in the algorithm dependent section. Type Reason 0 PDU could not be correctly decrypted There are algorithm dependent diagnostic parameters, these parameters begin with the value 100. There are also security protocol dependent diagnostic parameters, they begin with the value 200. One problem encountered in the service specification was whether some specific parameters should be provided or not For example, should the certification path be included in the New Key service primitive? The motive for not including the certification path is that it might be desirable to have the certification path cached in its transfer syntax form, thereby avoiding unnecessary retranslations. Encryption and decryption procedures are performed on the transfer syntax representation of the data, therefore the Diffie-Hellman public key provided in the New Key request cannot be sent signed. The service primitives issued, as previously described, can been seen as issued from the part of the key management application process that resides outside the key management application entity. Where should the \"intelligence\" be built in? In the part of the application process that is outside the application entity or in the application entity? For example, should the authentication procedure be employed in the application process or application entity?", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: A Study of OSI Key Management."}]}
{"id": "nist_01653", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.5.3.2 SAML Statements according to NIST Guide to Secure Web Services According to Guide to Secure Web Services, 3.5.3.2 SAML Statements: SAML defines three types of statements-authentication, attribute, and authorization-allowing SAML assertions to provide a wealth of information about individual subjects. SAML authentication statements indicate that a subject was authenticated and provide specific details, such as what authentication method was used, when the authentication occurred, and who the authenticating entity was. Different techniques for establishing identity are supported, ranging from use of a password to use of hardware tokens and personal physical attributes (biometrics). SAML allows assertions to specify any type of authentication mechanism used and provides a vocabulary for a number of commonly used mechanisms. Figure 3-8 shows a sample authentication statement. A SAML authorization decision statement may be used to assert that a request by a subject to access a specified resource has resulted in the specified decision and may optionally include evidence to support the decision. SAML attribute statements provide information about a particular subject that may be useful or necessary for determining whether or not access should be granted. In an RBAC environment, a SAML attribute statement can provide information about the subject's roles; similarly, in an ABAC environment, a SAML attribute statement can provide the attributes required by the policy.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, token. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services."}]}
{"id": "nist_01654", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management say about 3.2 HWAM Sub-Capabilities and Defect Check Tables and Templates? (Part 1) According to Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management, 3.2 HWAM Sub-Capabilities and Defect Check Tables and Templates: 3.2 HWAM Sub-Capabilities and Defect Check Tables and Templates This section documents the specific test templates that are proposed and considered adequate to assess the control items that support HWAM. See Section 5 of Volume 1 of this NISTIR for an overview of defect checks, and see Section 4.1 of Volume 1 for an overview of the actual state and desired state specifications discussed in the Assessment Criteria Notes for each defect check. Sections 3.2.1 and 3.2.2 of this document describe the foundational and local defect checks, respectively. The Supporting Control Item(s) data in sections 3.2.1 and 3.2.2 document which controls might cause any of the checks to fail, i.e., documenting why the check (test) might be needed. Refer to Section 3.1 on how to adapt the defect checks (and roles specified therein) to the organization. Data found in Section 3.2 can be used in both defect check selection and root cause analysis, as described there. Section 3.2.3 documents how each sub-capability (tested by a defect check) serves to support the overall capability by addressing certain example attack steps and/or data quality issues. The Defect Check Templates are organized around four-part tables, as follows: - (1) Part 1 of the table is preceded by the text, 'The purpose of this sub-capability is defined as follows:' and contains the following columns: - a. Sub-Capability Name . - b. Sub-Capability Purpose . This is a description of the sub-capability purpose. Note that how sub-capabilities block or delay attack steps is described in Section 3.2.3.) - (2) Part 2 of the table is preceded by the text, 'The defect check to assess whether this subcapability is operating effectively is defined as follows:' and contains the following columns: - a. Defect Check ID . Defect check identifier. - b. Defect Check Name . - c. Assessment Criteria Summary . Short description of what is checked. - d. Assessment Criteria Notes .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management."}]}
{"id": "nist_01655", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Review of the Advanced Encryption Standard provide? (Section 12) depends on the algorithmic description of the AES algorithm but also on the way the algorithm is implemented and on how its inputs (plaintexts/ciphertexts, and keys) are generated by the application. When a cryptographic application is vulnerable to a practical attack, this approach allows for the identification of the underlying cause and an evaluation of the vulnerability's impact.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Review of the Advanced Encryption Standard."}]}
{"id": "nist_01656", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automation Support for Security Control Assessments_ Volume 1_ Overview say about 7.2.2 Root Cause Analysis How-to: Defect Types? (Part 1) According to Automation Support for Security Control Assessments_ Volume 1_ Overview, 7.2.2 Root Cause Analysis How-to: Defect Types: 7.2.2 Root Cause Analysis How-to: Defect Types Three levels of root cause analysis are needed for defect check failures: - (1) Determine case-specific causes. - (2) Determine which control failed. - (3) Determine systemic causes. LEVEL 1: Determine the case-specific causes . This typically involves affirming whether the desired specification or the actual state is in error. - a. Was the desired state specification wrong? - b. Was the actual state wrong? In coordination with the system owner (SO) and SSO, designated operational staff looks at each specific case to decide whether option (a) or (b) applies to the defect. It is equally important to consider what caused (a) or (b) to be the defect. Example 1: Perhaps a system administrator has connected multiple devices to the production network without first adding them to the authorized inventory, configuring them correctly, and patching them. Determining that this is the root cause indicates that option (b), actual state error, is the issue because the actual state (unpatched, misconfigured devices on the network and not in the inventory) is the defect. In this case, the solution is not just to get the devices authorized, configured, and patched, but also to make sure the system administrator understands the importance of following operational procedures. For Example 1, note that the failure includes one or more of the controls/control items related to managing the actual state. Example 2: Perhaps a system administrator has connected multiple devices to the production network after getting them authorized and correctly configuring and patching them. However, the administrator forgot to put them in the authorized system component inventory first. Determining that this is the root cause indicates that option (a), desired state specification error, is the issue because the desired state specification (failure to include a correctly authorized device in the inventory) is the defect.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Volume 1_ Overview."}]}
{"id": "nist_01657", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Validating the Integrity of Computing Devices say about 4.2.1.1 IBM QRadar? According to Validating the Integrity of Computing Devices, 4.2.1.1 IBM QRadar: We demonstrate the capabilities described above with IBM QRadar -a SIEM platform which supports the collection of security events and automated processing of events by way of rules that align with an organization's risk posture. We leverage two of its core capabilities, the log manager and the SIEM. The log manager is the component that collects, analyzes, stores, and reports on security event logs from Dell and HP Inc. laptop endpoints. The SIEM consolidates data gathered by the log manager and executes our custom ruleset which detects potential platform integrity events. This results in identifying offenses, events that security operations personnel may need to take remediation action on, which can be consumed by other enterprise systems (such as Dashboards) via the QRadar Representational State Transfer (REST) application programming interface (API).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validating the Integrity of Computing Devices."}]}
{"id": "nist_01658", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 1 \u2013 General say about 9.2.1 Key Inventories? (Part 1) According to Recommendation for Key Management_ Part 1 \u2013 General, 9.2.1 Key Inventories: 9.2.1 Key Inventories A key inventory shall include information about each key (e.g., all or part of the metadata associated with the key); unless the inventory is also used for key backup or archiving, the inventory shall not include secret or private keys but shall include a reference to the key (e.g., a key identifier or pointer to the location of the key). The information in the inventory should indicate who/what owns or shares the key, the key type, the algorithm with which the key is to be used, the key length, how it is used (e.g., the application), and its expiration date. Key inventories should be maintained in a central repository or network of mutually trusted repositories and operated in accordance with a Key-Inventory Policy. See SP 800-57, Part 2 for additional information. If a key is compromised, the owners or sponsors associated with the compromised key need to be notified so that remedial actions can be taken, including revoking the key, performing an analysis of the effects of the compromise, and replacing the key when appropriate. The information in the inventory can be used to identify who is to be notified and how to contact them. If an owner is no longer authorized to use a key (e.g., the owner is a human who left the organization or a device that is removed from the system), other entities need to be notified so that further interaction using that key is terminated. If the key is a symmetric key, the information in the inventory can be used to identify other entities that need to be notified and how to contact them. If the key is an asymmetric key and PKI certificates are used, notification is usually accomplished using CRLs. If the cryptoperiod for a key expires or is about to expire, the key needs to be replaced if interactions between the entities using that key are to continue (i.e., using a replacement key).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_01659", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Report_ Authentication Diary Study provide? (Section 102) r nine hours or however many hours you're doing and then you think of something of home, it definitely is less likely that you're going to get online to actually do that thing that you're thinking of. You're just going to wait until the next day.' (P11) Study participants reported avoiding entering authentication elements in two key situations: time-outs on systems or networks, and when they perceived authenticating as more of a 'hassle' than it was worth for the task they needed to do. One common reason for having to re-authenticate was because the desktop or laptop computer the person was using had locked after 15 minutes of inactivity (as described in Sec. 2.7 ). Participants addressed this inconvenience by doing something to prevent the computer from timing out, such as jiggling the mouse, or carrying their laptop with them - although as the participant quoted at the end of Sec. 6.2.1 pointed out, this solution was far from ideal and did little to reduce the friction and disruption caused by timed lockouts. One participant also mentioned (in jest) that software that makes the computer think the mouse is moving often enough to prevent the screen from locking or a 'drinking bird' could be employed to periodically tap a key on the computer and prevent timeouts. Another participant said that despite the appeal of 'cheating' the lockout, he/she did not plan to do so: 'Well you have two choices. Either you can beat the system - I mean there are little devices that you can buy that you plug into USB that imitates the mouse being moved every so often, right? [\u2026] And they're very cheap. They're like five dollars or something. But I prefer not to try and beat the system, although that's tempting.' (P23) In certain situations, participants elected to perform long tasks without the computer because doing so was more efficient than logging in, being locked out, having to log in again, and so on.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report_ Authentication Diary Study."}]}
{"id": "nist_01660", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Available at https according to Digital Identity Guidelines? Available at https: //www.govinfo.gov/content/pkg/USCODE-2018-title5/pdf/USCODE-", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Digital Identity Guidelines."}]}
{"id": "nist_01661", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Module-Lattice-Based Key-Encapsulation Mechanism Standard provide? (Section 61) indication if random bit generation failed 4: end if 5: 6: (\ud835\udc3e,\ud835\udc50) \u2190 ML-KEM . Encaps _ internal ( ek , \ud835\udc5a) return (\ud835\udc3e,\ud835\udc50) \u25b7 run internal encapsulation algorithm ``` The decapsulation algorithm ML-KEM . Decaps of ML-KEM (Algorithm 21) accepts a decapsulation key and an ML-KEM ciphertext as input, does not use any randomness, and outputs a shared secret. This algorithm requires input checking, as specified below. Decapsulation input check. To check a candidate decapsulation key dk and ciphertext \ud835\udc50 , perform the following checks: 1. (Ciphertext type check) If \ud835\udc50 is not a byte array of length 32(\ud835\udc51 \ud835\udc62 \ud835\udc58 + \ud835\udc51 \ud835\udc63 ) for the values of \ud835\udc51 \ud835\udc62 , \ud835\udc51 \ud835\udc63 , and \ud835\udc58 specified by the relevant parameter set, then input checking has failed. 2. (Decapsulation key type check) If dk is not a byte array of length 768\ud835\udc58 + 96 for the value of \ud835\udc58 specified by the relevant parameter set, then input checking has failed. 3. (Hash check) Perform the computation <!-- formula-not-decoded --> If test \u2260 dk [768\ud835\udc58 + 32 \u2236 768\ud835\udc58 + 64] , then input checking has failed. If all of the above checks pass, then ML-KEM . Decaps can be run with inputs dk \u2236= dk and \ud835\udc50 \u2236= \ud835\udc50 . It is important to note that this checking process does not guarantee that dk is a properly produced output of ML-KEM . KeyGen , nor that \ud835\udc50 is a properly produced output of ML-KEM . Encaps . ML-KEM . Decaps shall not be run with a decapsulation key or a ciphertext unless both have been checked. However, checking of the decapsulation key need not be performed by the decapsulating party, nor with every execution of ML-KEM . Decaps . Instead, assurance that this check has been performed can be acquired through other means (see SP 800-227 [1]). Ciphertext checking shall be performed with every execution of ML-KEM . Decaps . Uses the decapsulation key to produce a shared secret key from a ciphertext. Checked input : decapsulation key dk \u2208 \ud835\udd39 768\ud835\udc58+96 . Checked input : ciphertext \ud835\udc50 \u2208 \ud835\udd39 32(\ud835\udc51 \ud835\udc62 \ud835\udc58+\ud835\udc51 \ud835\udc63 ) . Output : shared secret key \ud835\udc3e \u2208 \ud835\udd39 32 . 1: \ud835\udc3e \u2032 \u2190 ML-KEM .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Module-Lattice-Based Key-Encapsulation Mechanism Standard."}]}
{"id": "nist_01662", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Interview according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, Interview: [SELECT FROM: personnel with identifier management responsibilities; personnel with information security responsibilities; system developers; system administrators]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_01663", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Active Content and Mobile Code say about 2.2 Server Anatomy? (Part 3) According to Guidelines on Active Content and Mobile Code, 2.2 Server Anatomy: application executes as an integral part of the Web server within the same address space as the server code and can remain in memory or be removed from memory dynamically to conserve system resources. Server-side processing methods also have been developed that take advantage of these more efficient interfaces and are easier to program; for example, Microsoft ASP.NET for use with Internet Information Services (IIS) servers, Java Server Pages supported by Sun and Netscape, and the freeware PHP Hypertext Preprocessor (PHP) supported by most major Web platforms, including Apache and IIS. In general, the techniques for dynamically generating content and improving Web server capabilities tend to be proprietary and used by software manufacturers to differentiate their product from others in the marketplace. Further details of common content generating technologies, including Server Side Includes (SSI), Active Server Pages (ASP), Java Server Pages (JSP), and PHP, are discussed in Section 4. Web Scripting - Client vs. Server: It is important to distinguish scripts run by the browser (i.e., client-side scripting) from those run by the Web server (i.e., server-side scripting). Clientside scripting and server-side scripting are distinct concepts that serve different purposes. For example, since a server does not interact directly with a user, server-side scripting requires no human-to-computer interface capability. Furthermore, the Web browser and server each supply their own unique environment for executing scripts. Client-side scripting is used to make Web pages more interactive and functional after they have been sent to the browser. For example, client-side scripts might involve validating data entry fields on an HTML form so the user gets immediate feedback when a mistake occurs, or integrating an ActiveX control or Java applet with another component on the page so that they interact.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Active Content and Mobile Code."}]}
{"id": "nist_01664", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography say about 6.2.1.5 Incorporating Key Confirmation into a C(1e, 2s) Scheme? According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography, 6.2.1.5 Incorporating Key Confirmation into a C(1e, 2s) Scheme: The subsections that follow illustrate how to incorporate key confirmation (as described in Section 5.9) into the C(1e, 2s) key-agreement schemes described above. Note that party V cannot act as a key-confirmation recipient unless a nonce ( NonceV ) is provided by party V to party U and is used (in addition to the shared secret Z ) as input to the key-derivation method employed by the scheme. This would be accomplished by including (a copy of) NonceV in the OtherInput provided to the KDM, as part of the FixedInfo (see Section 5.8), in addition to using (a copy of) NonceV as the EphemDataV employed in the MacTag computations for key confirmation. The flow depictions separate the key-establishment flow from the key-confirmation flow. The depictions and accompanying discussions presume that the assumptions of the scheme have been satisfied, that the key-agreement transaction has proceeded successfully through key derivation, and that the received MacTags are successfully verified as specified in Section 5.2.2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}]}
{"id": "nist_01665", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Examine according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, Examine: [SELECT FROM: system and information integrity policy and procedures; configuration management policy and procedures; procedures for malicious code protection; records of malicious code protection updates; system design documentation; system configuration settings; scan results from malicious code protection mechanisms; record of actions initiated by malicious code protection mechanisms in response to malicious code detection; system audit records; system security plan; other relevant documents or records]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_01666", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Category according to Guidelines for Smart Grid Cybersecurity? Category: Common Governance, Risk, and Compliance (GRC) Requirements", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01667", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain C.2.8.1 Central Fiscal Operations Information Type according to NIST Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, C.2.8.1 Central Fiscal Operations Information Type: Central Fiscal Operations includes the fiscal operations that the Department of Treasury performs on behalf of the Government. 14 [Note: Tax-related functions are associated with the Taxation Management information type.] Impacts to some information and information systems associated with central fiscal operations may affect the security of the critical banking and finance infrastructure. In most cases, the effect on public welfare of a loss of central fiscal operations functionality can be expected to be delayed rather than immediate. The potential for consequent loss of human life or of major national assets is low. . The provisional security categorization recommended for the central fiscal operations information type is as follows: Security Category = {(confidentiality, Moderate), (integrity, Low), (availability, Low)}", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_01668", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements say about Appendix D-References? (Part 4) According to Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements, Appendix D-References: anagement and Budget (OMB) Memorandum M-08-22, Guidance on the Federal Desktop Core Configuration (FDCC) , August 11, 2008. | | [RFC 2119] | Internet Engineering Task Force (IETF) Request for Comment (RFC) 2119, Key words for use in RFCs to Indicate Requirement Levels , March 1997. https://doi.org/10.17487/RFC2119 | | [SWID] | ISO/IEC 19770-2:2015, Information technology - Software asset management - Part 2: Software identification tag , October 2015 (corrected March 2017). http://www.iso.org/iso/catalogue_detail.htm?csnumber=65666. | | [XMLS] | World Wide Web Consortium (W3C) Recommendation, XML Schema [XML Schema 1.1], October 28, 2004. http://www.w3.org/XML/Schema.html. |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements."}]}
{"id": "nist_01669", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for the Secure Deployment of IPv6 say about Table of Contents? (Part 11) According to Guidelines for the Secure Deployment of IPv6, Table of Contents: | Comparing IPv6 and IPv4 Addressing...................................................... | 3-11 | | 3.2 | IPv6 Address Allocations......................................................................................3-12 | IPv6 Address Allocations......................................................................................3-12 | | | | 3.2.1 IPv6 Address Assignments ...................................................................... | 3.2.1 IPv6 Address Assignments ...................................................................... | 3-12 | | | 3.2.2 Obtaining Globally Routable IPv6 Address Space.................................... | 3.2.2 Obtaining Globally Routable IPv6 Address Space....................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_01670", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE) say about iii. In the Address dialogue:? According to Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE), iii. In the Address dialogue:: - 1) For the Name field, enter a unique name to identify this address. - 2) For the Description field, enter a meaningful description of the purpose of this address. - 3) In the unnamed field following the Type drop-down menu, enter the IPv4 address that this interface will use in Classless Inter-Domain Routing notation. This example uses 10.6.1.2/24 for the WAN interface in our lab environment. - 4) Click OK. Figure 2-38 WAN Interface IP Address Configuration <!-- image --> - e. The address should now appear as an item in the IP list box; select OK; the Address dialogue closes. 4. Click OK. 5. Repeat Steps 2 and 3 for each of the additional Ethernet/Layer3 interfaces. Figure 2-39 Completed WAN Interface Configuration <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_01671", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Framework Profile for Liquefied Natural Gas provide? (Section 17) | Category........................................................................................................................................23 | | Table 22. CSF Subcategory Priorities for the Identify Function's Business Environment (ID.BE) Category........................................................................................................................................23 | | | Table 23. CSF Subcategory Priorities for the Identify Function's Governance (ID.GV) Category. .......................................................................................................................................................24 | | | Table 24. CSF Subcategory Priorities for the Identify Function's Risk Assessment (ID.RA) Category........................................................................................................................................24 | | | Table 25. CSF Subcategory Priorities for the Identify Function's Risk Management Strategy (ID.RM) | Category..........................................................................................................................25 | | Table 26. CSF Subcategory Priorities for the Identify Function's Supply Chain Management (ID.SC) Category.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, csf, fips. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Liquefied Natural Gas."}]}
{"id": "nist_01672", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Threat Analysis on UOCAVA Voting Systems say about 7 Security Controls? (Part 1) According to A Threat Analysis on UOCAVA Voting Systems, 7 Security Controls: 7 Security Controls The threat analysis conducted and documented in Section 6 includes references to security controls. These controls provide procedural and technical countermeasures to protect the confidentiality, integrity and availability of systems from threats. Whenever possible, specific controls are referenced for each threat identified in the analysis. These controls fully or partially mitigate the associated threat. In some cases the controls are preventative. That is, the controls prevent a security violation from taking place. In other cases the controls are reactive, in that they help recover from an attack or other security violation without further loss of confidentiality, integrity or availability. Preventative controls are preferable, but not always possible or realistic. This section summarizes the security controls identified to mitigate threats to each transmission option. These controls point to specific controls listed in NIST SP 800-53, Recommended Security Controls for Federal Information Systems [3] . NIST SP 800-53 is a catalog of highlevel security controls, written primarily for federal computer systems. This report references the controls documented in NIST SP 800-53 by the Control Number. As the controls are highlevel, and not geared for election systems, this report includes discussion on how these controls could be implemented in UOCAVA election systems. The particular security controls referenced in this report mitigate specific threats identified to each transmission option. Furthermore, threats are identified for the high-level characterizations of election systems outlined in Section 4. Most jurisdictions will use a variation of one or more of the systems identified in this paper. As such, specific voting systems may be vulnerable to different threats, requiring a different set of security controls. This report does not suggest that the following controls adequately mitigate the threats faced by each system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: A Threat Analysis on UOCAVA Voting Systems."}]}
{"id": "nist_01673", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities provide? (Section 33) em files that the system cannot operate without. Another example is disabling a service that is needed to boot the system. | The threat posed by a security configuration issue may change over time. The base metrics are limited to the characteristics of a security configuration issue that are constant over time and across user environments. To incorporate the time-variant aspect of threats, the temporal metrics produce a scaling factor that is applied to the Exploitability components of the base metric. Temporal metrics describe the characteristics of security configuration issues that can change over time but remain constant across user environments. The two components of CMSS temporal metrics are the General Exploit Level and the General Remediation Level. Since temporal metrics are optional, each includes a default metric value that has no effect on the score. This value is used when the scoring analyst wishes to ignore a particular metric because it does not apply or the analyst does not have sufficient data to determine the appropriate metric value. The General Exploit Level metric measures the prevalence of attacks against a security configuration issue-how often any vulnerable system is likely to come under attack. If a security configuration issue could be exploited more widely with the use of exploit code, the prevalence of attacks may be related to the current state of exploit techniques or exploit code availability. Public availability of easy-to-use exploit code increases the number of potential attackers by including those who are unskilled, thereby increasing the severity of the vulnerability. The availability of automated exploit code also increases the number of attacks each attacker can launch. However, note that attacks may not require exploit code. For example, consider a security configuration issue that can be attacked by sending a user an email with instructions to perform actions that result in an exploit.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities."}]}
{"id": "nist_01674", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IA-3 in NIST_SP_800-53r5_Security_Privacy_Controls? (Part 1) Control IA-3: DEVICE IDENTIFICATION AND AUTHENTICATION Control: Uniquely identify and authenticate [Assignment: organization-defined devices and/or types of devices] before establishing a [Selection (one or more): local; remote; network] connection. Discussion: Devices that require unique device-to-device identification and authentication are defined by type, device, or a combination of type and device. Organization-defined device types include devices that are not owned by the organization. Systems use shared known information (e.g., Media Access Control [MAC], Transmission Control Protocol/Internet Protocol [TCP/IP] addresses) for device identification or organizational authentication solutions (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.1x and Extensible Authentication Protocol [EAP], RADIUS server with EAP-Transport Layer Security [TLS] authentication, Kerberos) to identify and authenticate devices on local and wide area networks. Organizations determine the required strength of authentication mechanisms based on the security categories of systems and mission or business requirements. Because of the challenges of implementing device authentication on a large scale, organizations can restrict the application of the control to a limited number/type of devices based on mission or business needs. Related Controls: AC-17, AC-18, AC-19, AU-6, CA-3, CA-9, IA-4, IA-5, IA-9, IA-11, SI-4. Control Enhancements: (1) DEVICE IDENTIFICATION AND AUTHENTICATION | CRYPTOGRAPHIC BIDIRECTIONAL AUTHENTICATION Authenticate [Assignment: organization-defined devices and/or types of devices] before establishing [Selection (one or more): local; remote; network] connection using bidirectional authentication that is cryptographically based. Discussion: A local connection is a connection with a device that communicates without the use of a network. A network connection is a connection with a device that communicates through a network.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01675", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Symmetric Key Injection onto Smart Cards provide? (Section 11) d holder connects to the PACS over a two-way authenticated Transport Layer Security (TLS) session [6] in which client authentication is performed using the PIV Authentication key from the PIV Card. 2. The PACS uses information provided by the card holder in addition to information available from the Backend Attribute Exchange [1] to determine whether to provision the PIV Card with a symmetric physical access key. The PACS also uses the Backend Attribute Exchange to find the Universal Resource Identifier (URI) for the PIV Card's CMS. 3. If the PACS wishes to provision the PIV Card with a symmetric physical access key then the PACS directs the card holder to the PIV Card's CMS by providing the card holder with a URI that points to the card holder's CMS. The URI includes an identifier for the PACS (e.g., ). 4. The card holder follows the URI, which results in the establishment of a two-way authenticated TLS session with the PIV Card's CMS. Client authentication is performed using the PIV Authentication key from the PIV Card. 5. The CMS makes a decision as to whether to load the PACS's key onto the PIV Card, and proceeds with the remainder of the protocol only if the key is to be loaded. The decision process must include verifying that the identifier specified in the URI corresponds to a legitimate PACS. If the identified PACS is legitimate, but no empty slots remain on the PIV Card, then the CMS may ask the card holder to determine which, if any, PACS's key should be deleted in order to allow the new key to be loaded. 6. The CMS uses the Backend Attribute Exchange to obtain the symmetric physical access key for the PIV Card, KPHYS , from the PACS. The communication between the CMS and the PACS is performed over a two-way authenticated TLS session using a cipher suite that provides both confidentiality and integrity protection for the data transmitted between the CMS and the PACS.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Symmetric Key Injection onto Smart Cards."}]}
{"id": "nist_01676", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Considerations for Code Signing say about Feedback? According to Security Considerations for Code Signing, Feedback: Feedback on this publication is welcome, and can be sent to: code-signing@nist.gov.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Code Signing."}]}
{"id": "nist_01677", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications say about Block Size? According to A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications, Block Size: Block sizes are dependent on the individual statistical test. In the case of Maurer's Universal Statistical test, block sizes range from 1 to 16. However, for each specific block size, a minimum sequence length should be used. If the block size were fixed at 16, a sequence of more than a billion bits would be required. For some users, that may not be feasible. Intuitively, it would seem that the larger the block size, the more information could be gained from the parsing of a sequence, such as in the Approximate Entropy test. However, a block size that is too large should not be selected either, for otherwise the empirical results may be misleading and incorrect because the test statistic is better approximated by a distinct probability distribution. In practice, NIST advises selecting a block size no larger than \uf8f0 log 2 n \uf8fb , where n is the sequence length. However, certain exceptions hold, and thus NIST suggests choosing a smaller block size.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications."}]}
{"id": "nist_01678", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Device Security_ Bring Your Own Device (BYOD) say about Appendix C References? (Part 2) According to Mobile Device Security_ Bring Your Own Device (BYOD), Appendix C References: s://csrc.nist.gov/publications/detail/sp/800-30/rev-1/final. - [9] NIST. NIST Privacy Risk Assessment Methodology. Jan. 16, 2020. [Online]. Available: - [10] Joint Task Force, Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy, NIST SP 800-37 Revision 2, NIST, Gaithersburg, Md., Dec. 2018. Available: - [11] Open Web Application Security Project (OWASP). ' OWASP Mobile Top 10, ' [Online]. Available: https://owasp.org/www-project-mobile-top-10/. - [12] NIST. Privacy Engineering Program: Privacy Risk Assessment Methodology, Catalog of Problematic Data Actions and Problems. [Online]. Available: - [13] Qualcomm. 'Mobile Security Solutions.' [Online] . Available: https://www.qualcomm.com/products/features/mobile-security-solutions. - [14] National Information Assurance Partnership (NIAP). U.S. Government Approved Protection Profile -Extended Package for Mobile Device Management Agents Version 3.0. Nov. 21, 2016. [Online]. Available: https://www.niap-ccevs.org/MMO/PP/ep\\_mdm\\_agent\\_v3.0.pdf. - [15] International Business Machines (IBM). About enterprise app wrapping. Aug. 09, 2022 last updated. [Online]. Available: https://www.ibm.com/docs/en/maas360?topic=overview-aboutenterprise-app-wrapping. - [16] NIAP. U.S. Government Approved Protection Profile -Module for Virtual Private Network (VPN) Gateways 1.1. July 01, 2020. [Online]. Available: - [17] NIAP. U.S. Government Approved Protection Profile -collaborative Protection Profile for Network Devices Version 2.2e. Mar. 27, 2020. Available: - [18] NIAP. Approved Protection Profiles. [Online].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, risk management framework, fips. General security reference material without sensitive content. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_01679", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does BIOS Protection Guidelines for Servers say about 2.4 Threats to the System BIOS? According to BIOS Protection Guidelines for Servers, 2.4 Threats to the System BIOS: A server is susceptible to the same forms of attack that threaten a client system. Execution of operating system-level malware on servers could precede a BIOS attack. Server BIOS updates that are executed without being authenticated as coming from a trusted source are vulnerable to attacks. Since servers may have multiple BIOS update mechanisms, each mechanism has a risk of vulnerability. The interaction between update mechanisms potentially can also introduce vulnerabilities. The Service Processor in servers has elevated privileges to perform system management, which may include modifying BIOS. While the Service Processor might be controlled through an isolated communication channel, unauthorized access to this channel exposes great risk to the server. While many security practices focus on the data network, the management network might be less vetted and less protected without special efforts. If insufficiently protected, BIOS image backups on servers (often maintained for recovery features) are vulnerable to rewrite attacks even while the primary BIOS is protected from modification. Subsequent to successful subversion of a BIOS backup, an adversary could employ other means to cause the server to reboot with the infected backup image.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, malware, adversary. Contains technical security guidance that could inform defensive posture. Source: BIOS Protection Guidelines for Servers."}]}
{"id": "nist_01680", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AN-2011 in ANSI_NIST-ITL 1-2011 Requirements and Conformance Test Assertions? (Part 143) Control AN-2011: 7, Table 66, 7.4.4 Table 66 See section 7.4.4 for details. Reserved for future useonly by ANSI/NIST-ITL. Table 66, Table 6, 8.13.19 The first information item shall be the friction ridge code/ FRC. See Section 7.7.7 for a description of the remaining three information items. - 13.018, 13.019- Reserved O 13.020- COM Value - 13.021, 13.023- Reserved O 13.024- LQM Value <See Requirement ID: \u201cField: Type13- CondCode>. <See Requirement ID: \u201cField: Comment>. <See Requirement ID: \u201cField: Type13- CondCode>. <See Requirement IDs: \u201cField: Sample Quality Subfield 1\u201d, \u201cField: Sample Quality Subfield 2\u201d, \u201cField: Sample Quality Subfield 3\u201d, \u201cField: Sample Quality Additional Subfield\u201d>. Table 66 Reserved for future useonly by ANSI/NIST-ITL. Table 66 User Defined Fields Table 66 Reserved for future useonly by ANSI/NIST-ITL. - - - 13.025, 13.199- Reserved 13.200 to 13.900- User Defined 13.901- Reserved <See Requirement ID: \u201cField: Type13- CondCode>. TRUE <See Requirement ID: \u201cField: Type13- CondCode>. 8.13.21, This is an optional field, listing the O 13.902- <See Requirement ID: \u201cField: xx.902-ANN\u201d >. 111 t-2 t-2 t-2 t-2 t-2 t-2 t-2 t-2 t-2 B 13.902- Annotated Information Value Field: 13.903- Device Unique Identifier Value Field: 13.904- Make/Mode l/Serial Number Value Field: 13.905, 13.994- Reserved Field: 13.995- Associated Context Value Field: 13.996- Hash Value Field: 13.997- Source Representati on Value Field: 13.998- Geographic Sample Acquisition Location Value Field: 13.999- Image Data Valid Table 66 8.13.22, Table 66 operations performed on the original source in order to prepare it for inclusion in a biometric record type. See Section 7.4.1. This is an optional field. See Section 7.7.1.1. ANN-Value O 13.903-DUI <See Requirement ID: \u201cField: Device ID\u201d >. t-2 Value 8.13.23, Table 66 This is an optional field. See Section 7.7.1.2. O 13.904- MMS Value <See Requirement ID: \u201cField: Make Model\u201d >.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: ANSI_NIST-ITL 1-2011 Requirements and Conformance Test Assertions."}]}
{"id": "nist_01681", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2009 Annual Report provide? (Section 70) s and innovative voting system architectures. NIST will be holding an end-to-end (E2E) voting system workshop to investigate the viability of using these novel voting systems for largescale elections. In addition, we will support the NIST National Voluntary Laboratory Accreditation Program (NVLAP) efforts to accredit voting system test laboratories and host the TGDC plenary meetings. We plan to engage voting system manufacturers, voting system test laboratories, state election officials, and the academic community in exploring ways to increase voting system security and transparency. http://vote.nist.gov/ Contacts: Dr. Nelson Hastings (301) 975-5237 nelson.hastings@nist.gov Mr. Andrew Regenscheid (301) 975-5155 andrew.regenscheid@nist.gov FIPS 140-3 (draft), Security Requirements for Cryptographic Modules , provides four increasing qualitative levels of security that are in- tended to cover a wide range of potential applications and environments. The security requirements cover areas related to the secure design and implementation of a cryptographic module. These areas include cryptographic module specification; cryptographic module physical ports and logical interfaces; roles, authentication, and services; software security; operational environment; physical security; physical security - non-invasive attacks; sensitive security parameter management; self-tests; life-cycle assurance; and mitigation of other attacks. The standard provides users with a specification of security features that are required at each of four security levels, flexibility in choosing security requirements, a guide to ensuring that the cryptographic modules incorporate necessary security features, and the assurance that the modules are compliant with cryptography-based standards. The FIPS 140-3 draft is a result of the reexamination and reaffirmation of the current standard, FIPS 140-2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2009 Annual Report."}]}
{"id": "nist_01682", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Domain Name System-Based Electronic Mail Security say about 3.1.2.1 Configuration of OpenSSL to act as a Local Certificate Authority (CA)? According to Domain Name System-Based Electronic Mail Security, 3.1.2.1 Configuration of OpenSSL to act as a Local Certificate Authority (CA): OpenSSL can be used to generate certificates and act as a local enterprise Certificate Authority (CA). This is not always advisable as it is very basic set of tools. Enterprises using OpenSSL as their CA must take great care to ensure that the root certificate (i.e. the CA certificate that signs all the end-entity certificates) is adequately protected. Compromise of the root certificate private key would allow an attacker to generate arbitrary certificates for spoofed hosts and services. How this root certificate private key is protected is beyond the scope of this document but should include adequate physical, access, and logical controls. OpenSSL can be used via the openssl command line tool to generate key pairs, and certificates for those key pairs. This certificate generation can be done by adding the certificate data on the command line, or using a configuration file for (organizational) default values. For example, if the organizational policy is for all certificates to have a lifetime of one year (365 days), that value can be set in a configuration file and does not need to be set using command line options unless there is a need to override the default for a specially generated certificate. The general order in setting up OpenSSL to operate an enterprise local CA (or to generate self-signed certificates) is to: Generate and set up configuration files, generate the root certificate, and finally, generate and sign end entity certificates.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_01683", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Third-Round Report of the SHA-3 Cryptographic Hash Algorithm Competition provide? (Section 138) ps://www.cosic.esat.kuleuven.be/ecrypt/courses/tenerife09/index.shtml - [21] ECRYPT II Hash Workshop, Tallinn, Estonia, May 19-20, 2011, - [22] Quo Vadis Cryptology? SHA-3 Contest - 7 th International Workshop on the State of the Art in Cryptology and New Challenges Ahead, Warsaw, Poland, May 23-24, 2011, http://cryptography.gmu.edu/quovadis/ - [23] Hash Workshop on SHA3 Finalists, Kolkata, India, December 9-10, 2011, - [24] ECRYPT SHA-3 Zoo, - [25] D. Bernstein and T. Lange (editors), eBASH: ECRYPT Benchmarking of All Submitted Hashes, http://bench.cr.yp.to/ebash.html - [26] External Benchmarking Extension (XBX), http://xbx.das-labor.org/trac - [27] C. Rechberger, T. Bj\u00f8rstad, J. Daemen, C. De Canni\u00e8re, P. Gauravaram, D. Khovratovich, W. Meier, T. Nad, I. Nikoli\u0107, M. Robshaw, M. Schl\u00e4ffer, S. Thomsen, E. Tischhauser, D. Toz, G. Van Assche, K. Var\u0131c\u0131, ' ECRYPT II SHA-3 Design and Cryptanalysis Report ,' August 2010, - [28] P. Gauravaram, F. Mendel, M. Naya-Plasencia, V. Rijmen, D.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Third-Round Report of the SHA-3 Cryptographic Hash Algorithm Competition."}]}
{"id": "nist_01684", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007 say about Record-Level Requirements and Assertions? (Part 120) According to Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007, Record-Level Requirements and Assertions: } | | | | | frequency (pixel density). | 2 | M | 13.008-JP2L-SLC | No Implementation | 4 | | | | | 2 | M | 13.008-PNG-SLC | IF Present(PHYS Chunk) THEN IF {13.008} EQ 1 OR 2 THEN {Sampling Units} EQ 1, ELSE IF {13.008} EQ 0 THEN {Sampling Units} EQ 0 | 3 | | 13.009-HPS | 18.1.9 | Field 13.010 shall specify the integer pixel density used in the horizontal direction of the transmitted image if the SLC field contains a 1 or 2. Otherwise, it | 2 | M | 13.009-JPEGL-HPS | IF {13.008} EQ '1' OR '2', THEN IF Present(JFIF Header) THEN {13.009} EQ {Horizontal Density} | 3 | | | | | 2 | M | 13.009-JP2L-HPS | No Implementation | 4 | | | | indicates the horizontal component of the pixel aspect ratio.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007."}]}
{"id": "nist_01685", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Secure Web Services say about F.8 Online Documents? (Part 5) According to Guide to Secure Web Services, F.8 Online Documents: s/nwesp2005\u00ad federated-security.pdf | | Neal Leavitt: 'Are Web Services Finally Ready to Deliver?' ( IEEE Computer, Nov. 2004) | To purchase from IEEE Computer Society: 004.199 | | Takeshi Imamura, Michiaki Tatsubori, and Yuichi Nakamura, IBM/Tokyo Research Lab., and Christopher Giblin, IBM/Zurich Research Lab.: 'Web Services Security Configuration in a Service-Oriented Architecture' ( Proceedings of WWW2005 ) | | | Academic Theses | | | Thomas Schepers, University of Tilburg (Netherlands): A View on Web Service Security: Can Current Security Standards Adequately Secure Web Services?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Secure Web Services."}]}
{"id": "nist_01686", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cryptographic Algorithms and Key Sizes for Personal Identity Verification say about Keywords? According to Cryptographic Algorithms and Key Sizes for Personal Identity Verification, Keywords: cryptographic algorithm; FIPS 201; identity credential; Personal Identity Verification (PIV); smart cards.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cryptographic Algorithms and Key Sizes for Personal Identity Verification."}]}
{"id": "nist_01687", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Usability and Security Considerations for Public Safety Mobile Authentication provide? (Section 17) | 5.10 Proximity Token............................................................................................ | 24 | | 5.11 | Fingerprints................................................................................................... | 24 | | 5.12 | Facial Recognition ........................................................................................ | 25 | | 5.13 | Iris Recognition ............................................................................................. | 26 | | | 5.14 Speaker Recognition.....................................................................................", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Usability and Security Considerations for Public Safety Mobile Authentication."}]}
{"id": "nist_01688", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Common Biometric Exchange Formats Framework (CBEFF) provide? (Section 14) Podio 1 , Jeffrey S. Dunn 2 , Lawrence Reinert 2 , Catherine Tilton 3 , Bruno Struif 4 , Fred Herr 5, Jim Russell 6 , M. Paul Collier 5 , Mark Jerde 7 , Lawrence O'Gorman 6 , Brigitte Wirtz 9 The Common Biometric Exchange Formats Framework (CBEFF) describes a set of data elements necessary to support biometric technologies in a common way. These data elements can be placed in a single file used to exchange biometric information between different system components or between systems. The result promotes interoperability of biometric-based application programs and systems developed by different vendors by allowing biometric data interchange. This specification is a revised (and augmented) version of the original CBEFF, the Common Biometric Exchange File Format, published as NISTIR 6529. In addition to the name change, which reflects more accurately the scope of the specification, NISTIR 6529-A incorporates new features such as a CBEFF nested structure in order to support multiple biometric data types (e.g., finger, face and voice) and/or multiple biometric data blocks of the same biometric type (e.g., finger biometric data blocks from more than one finger) within a CBEFF data structure, a Biometric Feature to further define the type of biometric data being placed in the file, a Validity Period for that data, an expanded definition of the Creator field which now specifies a Product Identifier, and Index Field associated with a specific instance of biometric reference data, a Challenge-Response field and a Payload field. NISTIR 6529-A also defines two new CBEFF Formats, biometric data objects for use within smart cards and other tokens and a simple root header for use in domains where more than one Patron Format, simple or nested, may be encountered. CBEFF provides forward compatibility accommodating for technology improvements and allows for new formats to be created. CBEFF implementations simplify integration of software and hardware provided by different vendors.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: token, sso. Contains security framework guidance for authentication systems. Source: Common Biometric Exchange Formats Framework (CBEFF)."}]}
{"id": "nist_01689", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations say about 5 CKMS Security Policy? (Part 1) According to Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations, 5 CKMS Security Policy: 5 CKMS Security Policy An organization often creates and supports layered security policies, with high-level policies addressing the management of its information and lower-level policies specifying the rules for protecting the information. - An organization's Information Management Policy governs the collection, processing, and use of an organization's information and should specify, at a high level, what information is to be collected or created, and how it is to be managed. - The organization's Information Security Policy is created to support and enforce portions of the organization's Information Management Policy by specifying in more detail what information is to be protected from anticipated threats. and how that protection is to be attained. A Federal organization may have different Information Security Policies covering different applications of categories of information. A CKMS Security Policy 84 (SP) is a high-level document that describes the authorization and protection objectives and constraints that apply to the generation, establishment, accounting, storage, use, and destruction of cryptographic keying material. It is intended to support an Information Security Policy by protecting the cryptographic keys and metadata used by a CKMS and to enforce restrictions associated with their use. A CKMS SP includes an identification of all cryptographic mechanisms and cryptographic protocols that can be used by the CKMS. A CKMS SP 85 also includes a set of rules that are established to describe the goals, responsibilities, and overall requirements for the management of cryptographic keying material throughout the entire key lifecycle, including when they are operational, stored, transported and used.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations."}]}
{"id": "nist_01690", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guidelines on Electronic Mail Security? (Part 135) Control ES-1: s (e.g., Windows, Linux, Unix). This arrangement introduces an added layer of complexity because that general-purpose operating system must also be secured in addition to the firewall software itself. Application layer firewalls are increasingly being deployed as appliance-based devices, which may use specialized operating systems. Routers and stateful inspection firewalls also typically run on specialized operating systems. To successfully protect a mail server using a firewall, ensure that the firewall is patched to the latest or most secure level (application and underlying operating system) and is both capable of and configured to support the following items: - GLYPH&lt;c=31,font=/HABHKN+Webdings&gt; Control all traffic between the Internet and the mail server - GLYPH&lt;c=31,font=/HABHKN+Webdings&gt; Block all inbound traffic to the mail server except that traffic which is required, such as TCP port 25 (SMTP).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_01691", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways say about 3.5.2 Security Control Map? (Part 8) According to Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways, 3.5.2 Security Control Map: orts. Table 3-2 lists the Cybersecurity Framework Subcategories and SP 800-53 Revision 5 security controls that are needed to support the example solution-to mitigate the risks of the solution itself. Table 3-2: Mapping Security Characteristics of the Example Solution for Scenario 6 | Cybersecurity Framework Category | Cybersecurity Framework Subcategory | SP 800-53 Revision 5 Controls | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, identity management. Contains security framework guidance for authentication systems. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_01692", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications provide? (Section 69) equence to produce the next bit (the 5 th bit). The examination proceeded as follows: 5 Defined in The Handbook of Applied Cryptography ; A. Menezes, P. Van Oorschot and S. Vanstone; CRC Press, 1997. | | Bit 1 | Bit 2 | Bit 3 | Bit 4 | Bit 5 | |---------------------------------------------|---------|---------|---------|---------|---------| | The first 4 bits and the resulting 5 th bit | 1 | 1 | 0 | 1 | 0 | | Bits 2-5 and the resulting 6 th bit | 1 | 0 | 1 | 0 | 1 | | Bits 3-6 and the resulting 7 th bit | 0 | 1 | 0 | 1 | 1 | | Bits 4-7 and the resulting 8 th bit | 1 | 0 | 1 | 1 | 1 | | Bits 5-8 and the resulting 9 th bit | 0 | 1 | 1 | 1 | 1 | | Bits 6-9 and the resulting 10 th bit | 1 | 1 | 1 | 1 | 0 | | Bits 7-10 and the resulting 11 th bit | 1 | 1 | 1 | 0 | 0 | | Bits 8-11 and the resulting 12 th bit | 1 | 1 | 0 | 0 | 0 | | Bits 9-12 and the resulting 13 th bit | 1 | 0 | 0 | 0 | 1 | For this block, the trial feedback algorithm works. If this were not the case, other feedback algorithms would be attempted for the block (e.g., adding bits 1 and 3 to produce bit 5, or adding bits 1, 2 and 3 to produce bit 6, etc.). - (1) Under an assumption of randomness, calculate the theoretical mean \u00b5 : <!-- formula-not-decoded --> + 13 ( 9 + ( -1 ) 13 + 1 ) ( 13 3 2 9 ) For the example in this section, \u00b5 = + -2 13 = 6.777222. 2 36 - (4) M For each substring, calculate a value of Ti , where T = ( -1 ) \u00b7 ( L -\u00b5 )+ 2 9 .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications."}]}
{"id": "nist_01693", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.2.4 Validate the TPM/TXT is enabled according to NIST Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments According to Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments, 5.2.4 Validate the TPM/TXT is enabled: 1. SSH into the ESX host as root and run the following command: ``` zcat /var/log/boot.gz | grep -I tpm ``` This should show if the TPM library was loaded. 2. Other commands to check are: 3. As a root user, run the following command: ``` vmkload_mod -l | grep tpm grep -i tpm /var/log/hostd.log | less -S ``` ``` esxcli hardware trustedboot get ``` It should show two answers, and both should be true .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments."}]}
{"id": "nist_01694", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Module-Lattice-Based Digital Signature Standard say about Algorithm 46 AddVectorNTT (\ud835\udc2f, \u0302 \ud835\udc30) \u0302? According to Module-Lattice-Based Digital Signature Standard, Algorithm 46 AddVectorNTT (\ud835\udc2f, \u0302 \ud835\udc30) \u0302: \u0302 \u0302 ``` Computes the sum \ud835\udc2f + \ud835\udc30 of two vectors \ud835\udc2f, \ud835\udc30 over \ud835\udc47 \ud835\udc5e Input : \u2113 \u2208 \u2115, \ud835\udc5e , \ud835\udc5e . \ud835\udc2f \u2208 \ud835\udc47 \u2113 \ud835\udc30 \u2208 \ud835\udc47 \u2113 Output : \ud835\udc5e . \ud835\udc2e \u2208 \ud835\udc47 \u2113 1: for \ud835\udc56 from 0 to \u2113 - 1 do 2: \ud835\udc2e[\ud835\udc56] \u2190 AddNTT (\ud835\udc2f[\ud835\udc56], \ud835\udc30[\ud835\udc56]) 3: end for 4: return \ud835\udc2e\u0302 ``` \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 \u0302 .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Module-Lattice-Based Digital Signature Standard."}]}
{"id": "nist_01695", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Introduction to Cybersecurity for Commercial Satellite Operations provide? (Section 53) | AU1, 2, 3, 6, 7, 12, 13, 14, 16 | | | 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 | | Functions | Subcategories | Informative | Reference | |-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|------------------------------------------------------------------------------------------------| | | | SP 800-53, Rev. 4 | SP 800-53, Rev. 5 | | | 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 | | | 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 | | Detect | DE.AE-3: Event data are collected and correlated from multiple sources and sensors.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Introduction to Cybersecurity for Commercial Satellite Operations."}]}
{"id": "nist_01696", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Data Action according to Securing Telehealth Remote Patient Monitoring Ecosystem? Data Action: Patients are provided one or more biometric devices that monitor biometric data and send that data to their healthcare providers to help assess the physical health condition of the patient between visits with the provider.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_01697", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Third-Round Report of the SHA-3 Cryptographic Hash Algorithm Competition provide? (Section 49) , but also the depth and maturity of the analysis and the tools used to cryptanalyze the algorithm. The 'depth of cryptanalysis' measure is described in somewhat more detail in Section 4.1.5. Table 5. Security Margins for the Five Finalists Based on Collision-type Attacks | Algorithm | Best Attack | Security Margin | Work | Depth of Analysis | |--------------------------------|---------------|-------------------|-------------|---------------------| | Semi-free-start near collision | 71% | Practical | High | BLAKE | | Semi-free-start collision | 40% | Impractical | Very High 8 | Gr\u00f8stl | | Semi-free-start near collision | 38% | Impractical | Low | JH | | Near collision | 79% | Practical | Medium | Keccak | | Semi-free-start near collision | 56% | Impractical | High 8 | Skein | | Collision | 62% | Practical | Medium | SHA-2 | This way of looking at the cryptanalysis results is quite unfavorable to JH, which received relatively limited cryptanalysis, and still seems to have a rather small security margin. It is relatively favorable to BLAKE and Keccak (with large security margins, despite a reasonable depth of analysis), and also to Skein (with a relatively large security margin, despite a reasonable depth of analysis, and a best attack with an impractically high amount of work required). The picture for Gr\u00f8stl is less clear; Gr\u00f8stl has a relatively low security margin, but is the most deeply analyzed finalist, and its best attack requires an impractically high amount of work and applies only to its compression function.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Third-Round Report of the SHA-3 Cryptographic Hash Algorithm Competition."}]}
{"id": "nist_01698", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Prioritizing Cybersecurity Risk for Enterprise Risk Management say about 2.2. Prioritizing Cybersecurity Risks? (Part 1) According to Prioritizing Cybersecurity Risk for Enterprise Risk Management, 2.2. Prioritizing Cybersecurity Risks: 2.2. Prioritizing Cybersecurity Risks After having calculated the risk exposure resulting from each risk in the CSRR, as detailed in NIST IR 8286A, 4 the next step in the process is to determine their relative priority. Because the priority reflects an order of precedence, the highest priority risks may not always be those with the greatest exposure value. Since risk response has not yet been determined, priority is not necessarily a reflection of the chronological order in which risk should be mitigated. Ultimately, the relative priority of various types of risk must be decided upon by those with appropriate authority, usually through guidance provided through the risk management strategy. That strategy and the resulting internal guidance are interpreted at each level (such as by application at the system level in the CSRR) and may then be adjusted as risk management activities are reported and monitored (as illustrated in Fig. 2). In this way, those in the enterprise who are accountable for cybersecurity oversight (e.g., a Chief Information Security Officer) establish priorities for cybersecurity risks and collaborate with other enterprise executive colleagues regarding how risk will be managed in the context of other enterprise risks. 4 These values are described in NIST IR 8286A and may be based upon risk analysis methods, various sources of impact information (e.g., a traditional business impact analysis [BIA]), and other enterprise information such as from previous iterations of the cybersecurity risk management cycle. The formula for calculating risk exposure is described in NIST IR 8286A, Section 2.4, and represents the total loss if the risk occurs multiplied by the probability that the risk will happen. The priority column describes the relative importance of each risk (usually ordered from most important to least important) based on the enterprise's risk management guidance.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Prioritizing Cybersecurity Risk for Enterprise Risk Management."}]}
{"id": "nist_01699", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings say about 5.7 Interfacing a VA? (Part 1) According to 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings, 5.7 Interfacing a VA: 5.7 Interfacing a VA For the interface between an RP and a VA, today's standard validation protocol, OCSP [21], clearly has too limited functionality. The successor, SCVP, has been severely delayed, and support for the protocol seems to be low. A better approach, in our opinion, is to provide VA services as Web Services. The XKISS part of XKMS [12] is a good starting point for the VA interface. The XML documents exchanged with the VA may in the future be subject to standardisation. In any case, a VA should publish its XML specifications in order to enable integration software produced by 'anyone'. The desired level of standardisation may be limited by the heterogeneity of different VA services, and by the possibility of tailoring VA services to specific customers. For performance, a VA must optimise gathering of information from CAs (and possibly other sources for auxiliary information) and answer requests as far as possible based on information cached locally. The preferred option is CRL download, with OCSP requests to the CA as a fallback alternative. CRL download must be configurable and be done by a separate process. A polling strategy may be used in order to catch CRLs issued out of or before schedule. Delta-CRLs and CRL push mechanisms should be exploited wherever available. All interfaces to and from a VA must be secured. The communication links should be protected by use of SSL (or similar means), and it must be possible to sign requests and responses between the RP and the VA and between the VA and CAs. Authentication of the RPs (and the VA towards the CAs) is done either when the SSL channel is established or through signatures on requests. The RPs may be authenticated by certificates issued by their preferred CA.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, sso. Contains security framework guidance for authentication systems. Source: 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings."}]}
{"id": "nist_01700", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is References according to Guidelines for Securing Wireless Local Area Networks (WLANs)? References: FIPS Publication 199; NIST Special Publications 800-41, 800-77", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Guidelines for Securing Wireless Local Area Networks (WLANs)."}]}
{"id": "nist_01701", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Purpose and Objectives according to NIST Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services, Purpose and Objectives: The PNT Profile is designed to be used as part of a risk management program in order to help organizations manage risks to systems, networks, and assets that use PNT services. The PNT Profile provides guidance for establishing risk management approaches to achieve the desired outcomes commensurate with acceptable and responsible levels of risk that result from the disruption or manipulation of PNT data. The PNT Profile is not intended to serve as a solution or compliance checklist that would guarantee the responsible use of PNT services. Use of the PNT Profile will help organizations: - Identify systems that use PNT services and determine their operating and performance requirements; - Identify sources of PNT data; - Identify known and anticipated threats to PNT services, equipment, and data; - Protect systems that are dependent on PNT services by adhering to basic principles of responsible use; - Detect disruptions and manipulation of PNT services and data; - Address risk in the management and use of PNT services and data; - Respond to PNT service or data anomalies in a timely, effective, and resilient manner; and, - Recover from PNT service or data anomalies in a timely, effective, and resilient manner.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_01702", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RA-1 in Guide to Operational Technology (OT) Security? Control RA-1: POLICY AND PROCEDURES CNTL NO. CONTROL NAME Control Enhancement Name CONTROL BASELINES LOW MOD HIGH", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_01703", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines on Electronic Mail Security provide? (Section 180) | Completed | Action | |-------------|-----------------------------------------------------------------------------------------------------------------------| | | Logging | | | Log IP stack setup errors | | | Log resolver configuration problems (e.g., DNS, NIS) | | | Log mail server configuration errors (e.g., mismatch with DNS, local configuration error, out-of-date alias database) | | | Log lack of system resources (e.g., disk space, memory, CPU) | | | Log alias database rebuilds | | | Log logins (failed, and also successful if adequate space is available) | | | Log security problems (e.g., spamming) | | | Log lost communications (network problems) | | | Log protocol failures | | | Log connection timeouts | | | Log connection rejections | | | Log use of VRFY and EXPN commands | | | Log send on behalf of | | | Log send as | | | Log malformed addresses | | | Log message collection statistics | | | Log creation of error messages | | | Log delivery failures (permanent errors) | | | Log messages being deferred (transient errors) | | | Store logs on a separate logging server | | | Backup and archive logs according to organizational requirements | | | Review", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_01704", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to NIST_SP_800-53r5_Security_Privacy_Controls? Discussion: Personally identifiable information processing and transparency policy and", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01705", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Derived PIV Application and Data Model Test Guidelines provide? (Section 239) m field obtained in Step 3 using Table 3-6 of [SP800-78]. 8. Match the digest algorithm obtained from Step 7 to an entry of Table 3-2 of [SP800-78] based on the public key algorithm and size (Step 6). | |--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Expected Result(s) | 1. From Step 1, the command returns the application property template with the status word '90 00'. 2. From Step 2, the command the requested data object along with the returns status word '90 00'. 3. From Step 8, the digestAlgorithm field value of the SignerInfo is in accordance with Tables 3-6 and 3-2 of [SP800-78] and it matches the value present in the digestAlgorithms field of the SignedData.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_01706", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Recommendation for Key Management_ Part 1 \u2013 General? (Part 117) Control HA-3: were destroyed (see transition 5). A private and public key-transport key pair transitions to the deactivated state when the notAfter date is reached on the last certificate issued for the public key. The transition shall be recorded (see SP 800-152). ## 7.3 Suspended State The use of a key or key pair may be suspended for several possible reasons. (Note that in the case of asymmetric key pairs, both the public and private keys shall be suspended at the same time.) One reason for a suspension might be a possible key compromise; in this case, the suspension might be issued to allow for time to investigate the situation. Another reason might be that the entity that owns a digital signature key pair is not available (e.g., is on an extended leave of absence); signatures purportedly signed during the suspension time would be invalid. Depending on the reason for the suspension, a suspended key or key pair may be restored to an active, deactivated, or destroyed state or may transition to the compromised state. A suspended key shall not be used to apply cryptographic protection (e.g., encrypt plaintext or generate a digital signature). This includes all key types listed in Section 5.1.1 except those types that are never used to apply cryptographic protection (i.e., a public signature-verification key, a public authentication key, a private key-transport key, and a public authorization key). Depending on the reason for the suspension, a suspended key could be used to process information for which cryptographic protection was applied before the suspension period. This includes the use of a public-verification key to verify a digital signature, a symmetric data-encryption key to decrypt encrypted information, and a symmetric key-wrapping key to unwrap keying material.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_01707", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 73) targeted assessment resulting from changes affecting specific controls or where controls were previously assessed and the results accepted in the reciprocity process), or a common control assessment. For partial assessments, system owners and common control providers collaborate with organizational officials with an interest in the assessment (e.g., senior information security officers, senior agency officials for privacy/chief privacy officers, mission/information owners, Inspectors General, and authorizing officials) to determine which controls are to be assessed. The determination of the controls to be assessed depends on the purpose of the assessment. For example, during the initial phases of the system development life cycle, specific controls may be selected for assessment to promote the early detection of weakness and deficiencies and a more cost-effective approach to risk response. After the initial authorization to operate has been granted, targeted assessments may be necessary when changes are made to the system, specific security or privacy controls, common controls, or the environment of operation. In such cases, the focus of the assessment is on the controls that may have been affected by the change. 3.2.2 SELECT PROCEDURES TO ASSESS THE SECURITY AND PRIVACY CONTROLS SP 800-53A provides assessment procedures for each security and privacy control and control enhancement in [SP 800-53]. For each control in the security plan and privacy plan to be included in the assessment, assessors select the corresponding assessment procedure from Chapter 4. The selected assessment procedures can vary from assessment to assessment based on the current content of the security plans and privacy plans and the purpose of the assessment (e.g., complete assessment, partial assessment, common control assessment).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01708", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Operational Technology (OT) Security provide? (Section 18) orts ............................................................. 201 D.3.4. CISA ICS Training Courses ................................................................................... 201 D.3.5. MITRE ATT&CK for ICS ........................................................................................ 201 D.3.6. NIST Cybersecurity Framework ............................................................................. 201 D.3.7. SANS ICS Security Courses.................................................................................. 202 D.4. Sector-Specific Resources....................................................................................... 202 D.4.1. Chemical ............................................................................................................... 202 viii NIST SP 800-82r3 September 2023 Guide to Operational Technology (OT) Security D.4.2. Communications .................................................................................................... 203 D.4.3. Critical Manufacturing ............................................................................................ 203 D.4.4. Dams ..................................................................................................................... 203 D.4.5. Energy ................................................................................................................... 203 D.4.6. Food and Agriculture ............................................................................................. 203 D.4.7. Healthcare and Public Health ................................................................................ 204 D.4.8. Nuclear Reactors, Materials, and Waste................................................................ 204 D.4.9. Transportation Systems ......................................................................................... 204 D.4.10.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_01709", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Potential Inputs according to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy? Potential Inputs: Impact levels determined for each information type and for each security objective (confidentiality, integrity, availability); security categorization based on high-water mark of information type impact levels; list of high value assets for the organization.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, fips, security control. General security reference material without sensitive content. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_01710", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance say about 1.2 Background? (Part 2) According to Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance, 1.2 Background: ments for managing cybersecurity risks associated with such devices.' The NISTIR 8259 series and SP 800-213 represent a significant portion of NIST's activities to address the requirements of the Act. After the draft documents were published, NIST began a series of stakeholder engagement activities. The April 2021 workshop was an open event to engage stakeholders in focused discussions on two of the draft documents: NIST SP 800-213 and NISTIR 8259D, which are the core documents defining federal requirements and processes for IoT device cybersecurity.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance."}]}
{"id": "nist_01711", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Derivation Using Pseudorandom Functions provide? (Section 5) | Scope and Purpose.......................................................................................................... 2 | Scope and Purpose.......................................................................................................... 2 | | | Pseudorandom Function (PRF)....................................................................................... 3 | Pseudorandom Function (PRF)....................................................................................... 3 | | | Key-Derivation Function (KDF)........................................................................................ 4 | Key-Derivation Function (KDF)........................................................................................ 4 | | | KDF in Counter Mode................................................................................................. 6 | KDF in Counter Mode................................................................................................. 6 | | | KDF in Feedback Mode..............................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key Derivation Using Pseudorandom Functions."}]}
{"id": "nist_01712", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.4.2 SQL Interface to Physical Database according to NIST Security of SQL-Based Implementations of Product Data Exchange Using STEP According to Security of SQL-Based Implementations of Product Data Exchange Using STEP, 2.4.2 SQL Interface to Physical Database: The OS provides the basic services that enable the SQL processor to store, retrieve, and modify data on the system. The OS is responsible for guaranteeing the integrity of the data and preventing denial of service. The OS must also prevent data from being accessed outside the SQL processor. Such action can result in loss of integrity (improper modification) or confidentiality (by circumventing SQL's internal access controls).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Security of SQL-Based Implementations of Product Data Exchange Using STEP."}]}
{"id": "nist_01713", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2013 Annual Report? (Part 18) Control HA-3: ion, CSD conducted outreach activities with academic institutions, providing information on NIST's security standards and guidelines, and exploring new areas of cybersecurity research and development. In FY 2013, CSD completed the following outreach activities: - \u0097 Finalized SP 800-53, Revision 4 - \u0097 Collaborated with the ITL Software and Systems Division and the NIST Standards Coordination Office using the International Standard ISO/IEC 17020:2008, Conformity Assessment - Requirements for the operation of various types of bodies performing inspection, in support of GSA in establishing a process for qualifying 3PAOs to conduct security assessments of CSPs information systems consistent with GSA requirements based on NIST standards and guidelines - \u0097 Developed a preliminary draft of SP 800-53A, Revision 4, Guide for Assessing the Security and Privacy Controls in Federal Information Systems and Organizations - \u0097 Developed a preliminary draft of SP 800-18, Revision 2, Guide for Developing Security Plans for Federal Information Systems and Organizations In FY 2014, CSD intends to: - \u0097 Finalize SP 800-53A, Revision 4, Guide for Assessing the Security and Privacy Controls in Federal Information Systems and Organizations - \u0097 Finalize SP 800-60 Revision 2, Guide for Mapping Types of Information and Information Systems to Security Categories - \u0097 Finalize SP 800-18 Revision 2, Guide for Developing Security Plans for Federal Information Systems and Organizations - \u0097 Expand cybersecurity outreach to include additional state, local, and tribal governments, as well as private sector organizations and academic institutions - \u0097 Continue to support federal agencies in effective implementation of the NIST Risk Management Framework. ## Contacts: Dr. Ron Ross (301) 975-5390 ron.ross@nist.gov Mr. Arnold Johnson (301) 975-3247 arnold.johnson@nist.gov Ms.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2013 Annual Report."}]}
{"id": "nist_01714", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1.3 RELATED PUBLICATIONS according to NIST Guide for Conducting Risk Assessments According to Guide for Conducting Risk Assessments, 1.3 RELATED PUBLICATIONS: The risk assessment approach described in this publication is supported by a series of security standards and guidelines necessary for managing information security risk. In addition to this publication, the Special Publications developed by the Joint Task Force Transformation Initiative supporting the unified information security framework for the federal government include: - Special Publication 800-39, Managing Information Security Risk: Organization, Mission, and Information System View ; 11 - Special Publication 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach ; - Special Publication 800-53, Recommended Security Controls for Federal Information Systems and Organizations ; and - Special Publication 800-53A, Guide for Assessing the Security Controls in Federal Information Systems and Organizations: Building Effective Security Assessment Plans . The concepts and principles associated with the risk assessment processes and approaches contained in this publication are intended to be similar to and consistent with the processes and approaches described in International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC) standards. Extending the concepts and principles of these international standards for the federal government and its contractors and promoting the reuse of risk assessment results, reduces the burden on organizations that must conform to ISO/IEC and NIST standards.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, fips, security control. General security reference material without sensitive content. Source: Guide for Conducting Risk Assessments."}]}
{"id": "nist_01715", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2006 Annual Report say about National Vulnerability Database? According to Computer Security Division 2006 Annual Report, National Vulnerability Database: NIST maintains the National Vulnerability Database (NVD). NVD is sponsored by the Department of Homeland Security's National Cyber Security Division and is designed to complement their current suite of vulnerability management products. This publicly available resource is being accessed at a rate of 30 million times a year by the information technology security community. NVD is a comprehensive cyber security vulnerability database that is updated daily with the latest vulnerabilities. Using a single search engine, one can find all publicly available U.S. Government vulnerability resources and references to industry resources. It contains over 20,000 analyzed vulnerabilities advisories with 20 new vulnerabilities added daily. In fiscal year 2006, over 6500 new vulnerabilities were add to the database. NVD is a general-purpose tool that can be used for a variety of purposes. Recommended uses include- - Viewing all publicly available U.S. Government vulnerability mitigation information; - Learning how to mitigate vulnerabilities referenced within security products (e.g., intrusion detection systems); - Keeping abreast of the latest vulnerabilities; - Researching the vulnerability history of a product; - Researching what vulnerabilities might exist on a computer that may not be detected by vulnerability scanners (e.g., vulnerabilities in obscure products); and - Viewing statistics on vulnerability discovery. NVD is built completely upon the Common Vulnerabilities and Exposures (CVE) naming standard and provides CVE with a fine-grained search engine and database. CVE is used by over 300 security products and services to uniquely identify vulnerabilities. http://nvd.nist.gov Contact: Mr. Peter Mell (301) 975-5572 mell@nist.gov", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Computer Security Division 2006 Annual Report."}]}
{"id": "nist_01716", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management provide? (Section 214) )(b)(1) | Determine if the organization: prevents the unauthorized removal of maintenance equipment containing organizational information by: (b) Sanitizing or destroying the equipment. | | Determination Statement ID | Implemented By | Assessment Boundary | Assessment Responsibility | Assessment Methods | Selected | Rationale for Risk Acceptance | Frequency of Assessment | Impact of not implementing | |------------------------------|------------------|-----------------------|-----------------------------|----------------------|------------|---------------------------------|---------------------------|------------------------------| | MA-3(3)(b)(1) | DM | ISCM-TN | ISCM-Sys | Test | | | | | | Determination Statement ID | Defect Check ID | Defect Check Name | Rationale If an [organization-defined measure] for this defect check is above [the organization- defined threshold], then defects in maintenance equipment {devices and device subcomponents} being sanitized or destroyed before removal related to this control item might be the cause of ... | |------------------------------|-------------------|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | MA-3(3)(b)(1) | HWAM- L01 | Devices moving into/out of the assessment boundary | devices not being adequately prepared for movement into or out of the assessment boundary.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management."}]}
{"id": "nist_01717", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity of Genomic Data say about References? (Part 11) According to Cybersecurity of Genomic Data, References: of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 1800-15. https://doi.org/10.6028/NIST.SP.1800-15 - [74] The MITRE Corporation (2019) Vulnerability Details: CVE-2017-6526. Available at - [75] Zorz Z (2019) Web-based DNA sequencers getting compromised through old, unpatched flaw. Available at - [76] U.S. Department of Defense (DoD) Cyber Exchange Public (2023) STIGs Document Library . Available at - [77] Center for Internet Security (2023) CIS Benchmarks . Available at https://www.cisecurity.org/cis-benchmarks/ - [78] Fagan M, Megas K, Scarfone K, Smith M (2020) Foundational Cybersecurity Activities for IoT Device Manufacturers (National Institute of Standards and Technology, Gaithersburg, MD), NIST Internal Report (IR) 8259. - [79] National Institute of Standards and Technology (2020) Cyber-Physical Systems/Internet of Things Testbed. Available: - [80] National Institutes of Health (2023) iDASH Privacy &amp; Security Workshop 2023 - secure genome analysis competition. Available at http://www.humangenomeprivacy.org/2023/ - [81] Shi X, Wu X (2016) An overview of human genetic privacy. Annals of the New York Academy of Sciences 1387(1):61-72. - [82] Rieke N, Hancox J, Li W, Milletar\u00ec F, Roth HR, Albarqouni S, Bakas S, Galtier MN, Landman BA, Maier-Hein K, Ourselin S, Sheller M, Summers R, Trask A, Xu D, Baust M, Cardoso MJ (2020) The future of digital health with federated learning. npj Digital Medicine 3(119). https://doi.org/10.1038/s41746-020-00323-1 - [83] Aziz MA, Anjum M, Mohammed N, Jiang X (2022) Generalized genomic data sharing for differentially private federated learning. Journal of Biomedical Informatics 132.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, cve-. Contains technical security guidance that could inform defensive posture. Source: Cybersecurity of Genomic Data."}]}
{"id": "nist_01718", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TR-1 in Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1? (Part 2) Control TR-1: anization'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. | | 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. | | 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. | | 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. | | 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1."}]}
{"id": "nist_01719", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NSTIC Pilots_ Catalyzing the Identity Ecosystem provide? (Section 61) techniques. This may include requirements for the currency and validity of the information used in the proofing or the development of the KBA questions; and - 2) report failure rates of KBA systems. In addition to standardizing validity criteria for data and processes used in the proofing process or KBA question development, this standard will establish reporting requirements for false acceptance, false rejections, and failure to enroll. This standard would have a positive impact on the existing identity and access management market by providing a common understanding of KBA and remote proofing standards, improving confidence in solutions, and improving risk-based decision making. Additionally, this standard would improve access to services across multiple markets (health care, financial services, online services that fall under the FTC Children's Online Privacy Protection Act, etc.) that require identity proofing to provide services that require high assurance identity solutions. No existing standards relating to performance metrics for Knowledge Based Authentication for remote proofing of identity have been identified. The closest related work discovered is a report by the IDPV Identity Resolution Project on 'Establishment of Core Identity Attributes Sets and Supplemental Identity Attributes' (Document No. NASPO-IDPV-060) which analyzed a large database of identity attributes to determine sets of attributes that could be used to resolve individuals from that database. Thus, the NASPO paper's principle purpose was to determine attribute sets for identity resolution, rather than to consider attribute verification for identity proofing. However, to the extent that certain attributes that may be used for KBA were not available within an attribute set (creating what was classified as a 'null identity' in the paper), the paper may inform a standard that is developed based on this proposal by identifying one reason for failure in a KBA system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NSTIC Pilots_ Catalyzing the Identity Ecosystem."}]}
{"id": "nist_01720", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guidelines for Securing Radio Frequency Identification (RFID) Systems? (Part 92) Control ES-1: rson while appearing legitimate to personnel who visually check the badge. 31 Environmental threats to tags include extreme heat, cold, moisture, vibration, shock, and radiation (including sunlight). Any risk assessment of environmental threats should also consider the impact of these conditions to the material to which the tag is attached and the glue or other mechanism that attaches the tag to the item. Impacts of harsh environmental conditions include degradation of tag performance, destruction of the tag, and separation of the tag from its associated item. Organizations need to assess the likelihood of these threats in their environment and set requirements for their RFID technology accordingly. In general, human threats are more likely to be realized if outsiders (e.g., customers or members of the general public) have physical access to the tags and therefore the means to engage in malicious behavior. Human threats are also more likely if people have an incentive to perform the attack, such as some form of financial gain or access to a restricted resource. ## 3.5 RFID Economics Cost-benefit tests can be applied to any technology project, but the RF subsystem of an RFID system has differentiating characteristics, especially regarding security. Table 3-2 examines the key factors to consider. Table 3-2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_01721", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Conformance Test for FDDI Medium Access Control (MAC) say about FDDI MAC Conformance Test C Language Test Generated by the TTCN Translator? (Part 27) According to A Conformance Test for FDDI Medium Access Control (MAC), FDDI MAC Conformance Test C Language Test Generated by the TTCN Translator: dict (FAIL) return (TRUE) } } /* end of level [5] */ ) /* line 1217 \"FDDI.MP\" [4]? OTHERWISE */ if (_buffer) { _level +-1; SetfVerdict (FAIL) ; return (TRUE) } /* line 1220 \"FDDI.MP if (Timeout (\"TRT. \") _level +-1; SetfVerdict (FAIL) return (TRUE) } } } } } _level -_lastlevel; return (FALSE); -[4]? TIMEOUT */ /* end of level [4] */ /* end of level [3] */ /* end of level [2] */ /* end of level [1] */ /* * LateToken - Testing MAC Timed Token Rotation Protocol (TTRP) 2: Tester * receives Late Token */ int LateToken () { int _lastlevel; _time -0; _level ' 1; strcpy(R, \"NONE\") Result -NONE; _timername -(char *) 0; _bufferlen --1; /* line 1228 \"FDDI.MP\" [1]+ */ /* Initializing Connection */ _lastlevel -_level; if (INITCONNECT 0 return (TRUE) else if (_level > _lastlevel) ( _level +' 1; while (TRUE) { I* line 1231 \"FDDI.MP\" --[2]! ECH0_Req */ ``` ``` /* Tester sends SMT ECHO Request frame, */ pECHO_Req -ECHO_Req_Tl () Send_PDD_ECHO_Req (pECHO_Req) _level +\u00b7 1; while (TRUE) { /* line 1235 \"FDDI.MP\" [3]? TIMEOUT */ if (Timeout (\"TRT. ') ) { __level +-1; while (TRUE) { /* line 1237 ''FDDI.MP\" [4] */ Start_timer (\"TRT. \", (long) TTRT 1000); _level += 1; while (TRUE) { /* line 1239 \"FDDI.MP\" [5]! TOKEN */ /* and issues Late To)cen when TTRT<TRT<2xTTRT . */ pTOKEN -TOKEN_Tl(); Send_PDU_TOKEN (pTOKEN) _level +* 1; _timername * \"TRT.\"; while (TRUE) { /* line 1243 \"FDDI.MP\" [6]? TOKEN */ /* IDT returns Token. */ pTOKEN -= TOKEN_Rl () ; _buffer ' Receive_PDD (_timername) if (I s_PDD_TOKEN (pTOKEN, _buffer) ) { Start_timer (\"TRT. \", (long) TTRT 1000); _level 1; while (TRUE) { /* line 1247 \"FDDI.MP\" [7]! ECH0_Req */ /* Tester sends SMT ECHO Request frame again, */ pECHO_Req -ECHO_Req_Tl () Send_PDU_ECHO_Req (pECH0_Req) _level +' 1; while (TRUE) { /* line 1251 \"FDDI.MP\" --[8]? TIMEOUT */ if (Timeout (\"TRT. \") ) { _level +' 1; while (TRUE) { /* line 1253 \"FDDI.MP\" [9] */ Start_timer (\"TRT. \", (long) TTRT 1000); _level +\u00bb 1; while (TRUE) { /* line 1255 \"FDDI.MP\" [10]!", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, token. Contains security framework guidance for authentication systems. Source: A Conformance Test for FDDI Medium Access Control (MAC)."}]}
{"id": "nist_01722", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SC-40(2) in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Control SC-40(2): T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 1 6 0 v 2 r 1 . I Notes: The Initial Access tactic in ATT&CK for ICS reflects elements of ATT&CK for Enterprise under multiple tactics. Data Historian Compromise (T0810) and Engineering Workstation Compromise (T0818) are examples of Lateral Movement. The adversary already has a presence in the IT environment and compromises a data historian or engineering workstation to gain a foothold in the control system environment. Drive-by Compromise (T0817) is similar to the corresponding ATT&CK for Enterprise technique since it involves an attack on the IT network. Other ATT&CK for ICS techniques with corresponding ATT&CK for Enterprise techniques of the same name include Exploit Public-Facing Application (T0819) with T1190, Exploitation of Remote Services (T0866) with T1210, External Remote Services (T0822) with T1133, Remote Services (T0886) with T1021, Replication Through Removable Media (T0847) with T1091, and Supply Chain Compromise (T0862) with T1195. Spearphishing Attachment (T0865) corresponds to a sub-technique under Phishing for Information (T1598) and Phishing (T1566). No ATT&CK for Enterprise technique corresponds to Internet Accessible Device (T0883), Rogue Master (T0848), or Wireless Compromise (T0860). TABLE G-2: POTENTIAL EFFECTS OF CYBER RESILIENCY ON EXECUTION TECHNIQUES ATT&CK Technique Mitigation or Candidate Mitigation Cyber Resiliency Implementation Approaches Potential Effects Cyber Resiliency Controls Change Operating Mode (T0858) Authorization Enforcement (M0800) Attribute-Based Usage Restriction Negate, Degrade, Exert", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, adversary. Contains technical security guidance that could inform defensive posture. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_01723", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessment of Access Control Systems say about Workflow? (Part 1) According to Assessment of Access Control Systems, Workflow: Workflow Based on the definition provided by the Workflow Management Coalition (WFMC), an international organization of workflow vendors, users, and research groups, a workflow is a representation of an organizational or business process in which '\u2026documents, information, or tasks are passed from one participant to another in a way that is governed by rules or procedures.' A workflow separates the various activities of a given organizational process into a set of well-defined tasks. Hence, typically, a workflow (often synonymous with a process) is specified as a set of tasks and a set of dependencies among the tasks, and the sequencing of these tasks is important. The various tasks in a workflow are usually carried out by several users in accordance with organizational rules relevant to the process represented by the workflow. The representation of a business process using a workflow involves a number of organizational rules or policies. An important class of organization policies is the organization's security policies. Within the realm of security policies, access control policies play a key role, and hence defining and enforcing access control requirements becomes a key function of a Workflow Management System (WFMS). Figure 1 presents a schematic diagram of the overall architecture of a WFMS, which consist of two main components: design-time and run-time. The design-time component consists of a set of tools (called the process definition tools) that are used for defining and modeling the business processes and their constituent tasks. A process definition consists of a process name (e.g., purchase order process), the definition of various tasks within the process (e.g., purchase order approval task), and a set of business rules associated with the process (e.g., task sequence or data flow among tasks).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Assessment of Access Control Systems."}]}
{"id": "nist_01724", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control MP-4 in Control Baselines for Information Systems and Organizations? (Part 134) Control MP-4: | | PE-13(4) | INSPECTIONS | | | | | | PE-14 | Environmental Controls | | x | x | x | | PE-14(1) | AUTOMATIC CONTROLS | | | | | | PE-14(2) | MONITORING WITH ALARMS AND NOTIFICATIONS | | | | | | PE-15 | Water Damage Protection | | x | x | x | | PE-15(1) | AUTOMATION SUPPORT | | | | x | | PE-16 | Delivery and Removal | | x | x | x | | PE-17 | Alternate Work Site | | | x | x | | PE-18 | Location of System Components | | | | x | | PE-18(1) | FACILITY SITE | W: Moved to PE-23.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Control Baselines for Information Systems and Organizations."}]}
{"id": "nist_01725", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook say about 2. NATURE OF REQUEST? According to National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook, 2. NATURE OF REQUEST: - Hardware to be accessed - Specific computer system(s). - Specific terminal location(s) [Complete address, street, city, state, and dial-in access telephone number].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook."}]}
{"id": "nist_01726", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Manufacturing Industrial Control Systems_ Behavioral Anomaly Detection say about C.2.3. Enabling Self-Learning Analytics? According to Securing Manufacturing Industrial Control Systems_ Behavioral Anomaly Detection, C.2.3. Enabling Self-Learning Analytics: The CyberX platform has five different self-learning analytics engines that are used to detect various types of behavioral anomalies within the network. The following steps describe the process to enable individual analytics engines: 1. Select System Settings from the navigation menu on the CyberX console 2. Click the Enabled / Disabled button next to each engine to enable or disable the engine. If an engine is enabled, then the button will indicate Enabled and will be illuminated with a green background color. An example with all five engines enabled is shown in Figure C-4 Figure C-4 Example Screenshot with All Five Self-Learning Analytics Enabled <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Manufacturing Industrial Control Systems_ Behavioral Anomaly Detection."}]}
{"id": "nist_01727", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Operational Technology (OT) Security provide? (Section 42) to existing physical systems, often replacing or supplementing physical control mechanisms. For example, embedded digital controls replaced analog mechanical controls in rotating machines and engines. Improvements in cost and performance have encouraged this evolution and resulted in many of today\u2019s \u201csmart\u201d technologies, such as the smart electric grid, smart transportation, smart buildings, smart manufacturing, and the Internet of Things. While this increases the connectivity and criticality of these systems, it also creates a greater need for their adaptability, resilience, safety, and security. Engineering OT continues to provide new capabilities while maintaining the typical long life cycles of these systems. The introduction of IT capabilities into physical systems presents emergent behavior with security implications. Engineering models and analysis are evolving to address these emergent properties, including safety, security, privacy, and environmental impact interdependencies. 3 See 8 NIST SP 800-82r3 September 2023 Guide to Operational Technology (OT) Security OT-Based Systems and Their Interdependencies OT is used in many industries and infrastructures, including those identified by the Cybersecurity and Infrastructure Security Agency (CISA) as critical infrastructure sectors listed below. OT can be found in all critical infrastructures and is more prevalent in the sectors that are in bold.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_01728", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2005 Annual Report say about FEDERAL INFORMATION SYSTEMS SECURITY EDUCATORS' ASSOCIATION? (Part 3) According to Computer Security Division 2005 Annual Report, FEDERAL INFORMATION SYSTEMS SECURITY EDUCATORS' ASSOCIATION: vendor exhibition. Further information regarding the conference is available on the FISSEA web site. Contacts: Mr. Mark Wilson (301) 975-3870 mark.wilson@nist.gov Ms. Peggy Himes (301) 975-2489 peggy.himes@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2005 Annual Report."}]}
{"id": "nist_01729", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Digital Identity Guidelines_ Federation and Assertions say about 3.4.1.1. General Requirements? According to Digital Identity Guidelines_ Federation and Assertions, 3.4.1.1. General Requirements: When using pairwise pseudonymous identifiers within the assertions generated by the IdP for the RP, the IdP SHALL generate a different federated identifier for each RP (see Sec. 3.4.1.2) or set of RPs (see Sec. 3.4.1.3). Some identity attributes such as names, physical addresses, phone numbers, email addresses, and others can be used to identify a subscriber outside of a federation transaction. When PPIs are used alongside these kinds of identifying attributes, it may still be possible for multiple colluding RPs to re-identify a subscriber by correlation across systems. For example, if two independent RPs each see the same subscriber identified with a different PPI, the RPs could still determine that the subscriber is the same person by comparing the name, email address, physical address, or other identifying attributes carried alongside the PPI in the respective assertions. If PPIs are used alongside identifying attributes, RPs SHALL establish privacy policies, processes, and procedures to prevent the correlation of subscriber data consistent with applicable legal and regulatory requirements. In a proxied federation model (see Sec. 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. In such situations, the PPI is generally established between the IdP and the federation proxy. Acting as an IdP, the proxy can provide a PPI to the downstream RP. Depending on the protocol, the federation proxy may need to map the PPI back to the associated identifiers from upstream IdPs in order to allow the identity protocol to function. In such cases, the proxy will be able to track and determine which PPIs represent the same subscriber at different RPs. The mapping of a PPI to other identifiers is considered subscriber information and SHALL be treated in accordance with the requirements in Sec. 3.10.1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Digital Identity Guidelines_ Federation and Assertions."}]}
{"id": "nist_01730", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.1.2 Terminology Conventions according to NIST Recommended Criteria for Cybersecurity Labeling of Consumer Software According to Recommended Criteria for Cybersecurity Labeling of Consumer Software, 2.1.2 Terminology Conventions: The Descriptive Claims group defines two terms, Claimant and Label Scope: A Claimant is defined in broad terms to encompass organizations of varying sizes and functions. This allows for individual developers, developer organizations, publishers, and others to act as the entity making the claims represented in a label and allows for flexibility on the part of the scheme owner. The Label Scope refers to what a label is describing. This allows a claimant to distinguish among software that is either included or excluded from the claims backed by the label (e.g., a mobile app versus a back-end server). This is especially important to the consumer, as it is often difficult to determine where these systems begin and end - their boundaries. For brevity, the criteria in this document frequently use the term 'software' and should be understood as referring to 'software within the label scope.'", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommended Criteria for Cybersecurity Labeling of Consumer Software."}]}
{"id": "nist_01731", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Integrating Forensic Techniques into Incident Response provide? (Section 46) n incorrect network configuration, resolving a functional problem with an application, and recording and reviewing the current OS and application configuration settings for a host. - ! Log Monitoring. Various tools and techniques can assist in log monitoring, such as analyzing log entries and correlating log entries across multiple systems. This can assist in incident handling, identifying policy violations, auditing, and other efforts. - ! Data Recovery. There are dozens of tools that can recover lost data from systems, including data that has been accidentally or purposely deleted or otherwise modified. The amount of data that can be recovered varies on a case-by-case basis. - ! Data Acquisition. Some organizations use forensics tools to acquire data from hosts that are being redeployed or retired. For example, when a user leaves an organization, the data from the userGLYPH&lt;146&gt;s workstation can be acquired and stored in case it is needed in the future. The workstationGLYPH&lt;146&gt;s media can then be sanitized to remove all of the original userGLYPH&lt;146&gt;s data. - ! Due Diligence/Regulatory Compliance. Existing and emerging regulations require many organizations to protect sensitive information and maintain certain records for audit purposes. Also, when protected information is exposed to other parties, organizations may be required to notify other agencies or impacted individuals. Forensics can help organizations exercise due diligence and comply with such requirements. Regardless of the situation, the forensic process comprises the following basic phases: 4 - ! Collection. The first phase in the process is to identify, label, record, and acquire data from the possible sources of relevant data, while following guidelines and procedures that preserve the integrity of the data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Integrating Forensic Techniques into Incident Response."}]}
{"id": "nist_01732", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Authority Key Identifier : according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Authority Key Identifier :: 36:DC:7B:64:B8:56:FB:0E:BF:AA:06:A6:F8:93:27:99:47:B6:B3:8A", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_01733", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Securing Radio Frequency Identification (RFID) Systems provide? (Section 104) ccess to that information if proper controls are not in place. This risk is distinct from the business process risk because it can be realized even when business processes are functioning as intended. A competitor or adversary can gain information from the RFID system in a number of ways, including eavesdropping on RF links between readers and tags, performing independent queries on tags to obtain relevant data, and obtaining unauthorized access to a back-end database storing information about tagged items. Supply chain applications may be particularly vulnerable to this risk because a variety of external entities may have read access to the tags or related databases. The risk of unauthorized access is realized when the entity engaging in the unauthorized behavior does something harmful with that information. In some cases, the information may trigger an immediate response. For example, someone might use a reader to determine whether a shipping container holds expensive electronic equipment, and then break into the container when it gets a positive reading. This scenario is an example of targeting . In other cases, data might also be aggregated over time to provide intelligence regarding an organization's operations, business strategy, or proprietary methods. For instance, an organization could monitor the number of tags entering a facility to provide a reasonable indication of its business growth or operating practices. In this case, if someone determined that a warehouse recently received a number of very large 32 Researchers from the Johns Hopkins University and RSA Laboratories cloned tags used as vehicle immobilizers and electronic payment tokens. Source: S. Bono, M. Green, A. Stubblefield, A. Juels, A. Rubin, and M. Szydlo, \"Security analysis of a cryptographically-enabled RFID device,\" in the Fourteenth USENIX Security Symposium , 2005, pp. 1-16. 33 A University of Waterloo student cloned a proximity card used for access control. Source: S.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, pki, token. Contains security framework guidance for authentication systems. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_01734", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control OA-3 in Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research? (Part 47) Control OA-3: ee main security principles: - Non-exportability: Since all private information on the VSC is encrypted by using the host machine's TPM, it cannot be used on a different machine with a different TPM. Additionally, TPMs are designed to be tamper-resistant and non-exportable themselves, so an adversary cannot reverse engineer an identical TPM or install the same one on a different machine. - Isolated cryptography: TPMs provide the same properties of isolated cryptography offered by conventional smart cards, and this is utilized by VSCs. When used, unencrypted copies of private keys are loaded only within the TPM and never into memory accessible by the OS. All cryptographic operations with these private keys occur inside the TPM. - Anti-hammering: If a user enters a PIN incorrectly, the VSC responds by using the antihammering logic of the TPM, which rejects further attempts for a period of time instead of blocking the card. This is also known as lockout. ADCS supports TPM attestation, 30 which provides the ability for the issuing CA to confirm that the key in the certificate request is protected by a known TPM. There are three methods of TPM attestation: 29 http://www.microsoft.com/en-us/download/details.aspx?id=29076 30 https://technet.microsoft.com/en-us/library/dn581921.aspx - User credential: The CA trusts the user-provided EKPub (the public key of the TPM endorsement key) as part of the certificate request, and no validation is performed other than the requester's domain credentials. - EKCert: The CA validates the EKCert (the certificate associated with the TPM EKPub key) chain that is provided as part of the certificate request and is a member of a list of allowed EKCert chains. - EKPub: The CA validates that the EKPub provided as part of the certificate request is a member of a list of allowed EKPubs. TPMs implement anti-hammering functionality to reduce the threat of brute force PIN guessing attacks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research."}]}
{"id": "nist_01735", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RA-1 in Guide to Operational Technology (OT) Security? (Part 159) Control RA-1: lnerability management procedures should include flexibility for interim alternative mitigations. Out-of-date OSs and applications may contain newly discovered vulnerabilities that could be exploited. Security patch support may not be available for legacy OT, so vulnerability management procedures should include contingency plans for mitigating vulnerabilities where patches may never be available or replacement plans. Vulnerabilities not considered by the organization could result in exploitation. Vulnerability management procedures should be in place to determine a plan of action or inaction upon the discovery of a vulnerability. Some OT considerations are: availability concerns may push patching until the next planned operational downtime; security patch support may not be available for OT systems that use outdated OSs; isolated systems may not require immediate patching; and OT exposed to the internet may need to be prioritized for patching. Modifications to hardware, firmware, and software deployed without testing could compromise normal operation of the OT. Documented procedures should be developed for testing all changes for security impacts. The live operational systems should never be used for testing. The testing of system modifications may need to be coordinated with system vendors and integrators. There are many reasons why an OT may need to be remotely accessed, including vendors and system integrators performing system maintenance functions or OT engineers accessing geographically remote system components. The concept of least privilege should be applied to remote access controls. Remote access capabilities must be adequately controlled to prevent unauthorized individuals from gaining access or authorized individuals from gaining excessive access to the OT. Improperly configured systems may leave unnecessary ports and protocols open. These unnecessary functions may contain vulnerabilities that increase the overall risk to the system.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_01736", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT) say about Identity and Access Management: Standards that enable the use of secure, interoperable digital identities and attributes of entities to be used across security domains and organizational boundaries.? (Part 4) According to Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT), Identity and Access Management: Standards that enable the use of secure, interoperable digital identities and attributes of entities to be used across security domains and organizational boundaries.: entities, the LwM2M protocol required that all communication between LwM2M Clients and LwM2M Servers as well as LwM2M Clients and LwM2M Bootstrap-Servers are authenticated using mutual authentication. Page 68, Section 7.3.1 | Approved Standard Guidance Available |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_01737", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST_SP_800-37r2_Risk_Management_Framework say about SYSTEM USER? According to NIST_SP_800-37r2_Risk_Management_Framework, SYSTEM USER: The system user is an individual or (system) process acting on behalf of an individual that is authorized to access information and information systems to perform assigned duties. System user responsibilities include, but are not limited to, adhering to organizational policies that govern acceptable use of organizational systems; using the organization-provided information technology resources for defined purposes only; and reporting anomalous or suspicious system behavior.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_01738", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Identifying and Categorizing Data Types for Public Safety Mobile Applications_ Workshop Report say about Sample Information Types:? According to Identifying and Categorizing Data Types for Public Safety Mobile Applications_ Workshop Report, Sample Information Types:: - Tanker contents. - Vehicle telematics (speed, number of occupants, make/model, etc.). - Miscellaneous assets (tow trucks, flat-bed trucks, MCI bus, etc.).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Identifying and Categorizing Data Types for Public Safety Mobile Applications_ Workshop Report."}]}
{"id": "nist_01739", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Device Security_ Cloud and Hybrid Builds provide? (Section 104) mobile malware or PHAs, particularly repackaged versions of legitimate applications \u2022 Exploitation of vulnerabilities in a third- party library (e.g., advertisement library) embedded in an application | | Device Integrity | Application whitelisting/blacklisting | Microsoft Intune/SCCM: can additionally specify a whitelist or blacklist of specific applications and prohibit unsigned applications from being installed | \u2022 Installation of vulnerable applications, which increases the probability of application and device compromise | | Security Characteristic | Security Capability and Capability Description | Implementation Note | Example Mitigated Threats | |---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | | | \u2022 Installation of untrusted applications, which handle sensitive data in an insecure manner | | Device Integrity | Boot validation: validation that the device is in a known working state and unmodified at boot (e.g., basic input-output system integrity checks) | \u2022 Android: optional Verified Boot capability with device-specific availability.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, malware. Contains technical security guidance that could inform defensive posture. Source: Mobile Device Security_ Cloud and Hybrid Builds."}]}
{"id": "nist_01740", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Proceedings of the Workshop of the Federal Criteria for Information Technology Security provide? (Section 24) luated in unusable configurations, thereby defeating the whole purpose of the evaluation process. This might be done via constraints cmi the vetting of profiles and the evaluation of security targets. One light hearted suggestion was for the government to copyright profile names, requiring that they not be misused, just as the Ada Joint Program Office copyrighted the use of 'Ada.' Rating Maintenance Phase (RAMP): There was a concern that the RAMP process was not addressed in the Federal Criteria. Global Issues CHAPTER 4 Based on analysis of the comments to the Functional Requirements the following set of issues were presented for discussion. Whenever possible, people who made insightful comments were invited to present their positions. - Precision in Tenninology - Identification and Authentication - Access Control - Availability &amp; Fault Tolerance - Policy Neutral Criteria - TCB &amp; Reference Monitor Focus - Integrity - Open-Ended Criteria - Issues from the attendees The ground rules for discussion were to focus on philosophy &amp; high-level issues. Wordsmithing was to be handled by the written comments. The objective of the workshop was to seek guidance and direction. Multiple options were considered useful, especially if statistical indicators such as distribution of (pinions and variance were captured. Martha Branstad ofTrusted Information Systems presented issues concerning precision in tenninology. She emphasized that the Federal Criteria must be meaningful and understandable. Her focus was on arriving at a definition of security. She quoted Dan Sterne's definition of a security policy objective as **A statement of intent to protect an identified resource from unauthorized use** and emphasized that security is not synonymous with correcmess. The ensuing discussion surfaced several inccxnpatible positions concerning definitions of information security.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Proceedings of the Workshop of the Federal Criteria for Information Technology Security."}]}
{"id": "nist_01741", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IA-32 in Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases? (Part 86) Control IA-32: | | Chain of Trust (CoT) | A method for maintaining valid trust boundaries by applying a principle of transitive trust, where each software module in a system boot process is required to measure the next module before transitioning control. | | Confidential Computing | Hardware-enabled features that isolate and process encrypted data in memory so that the data is at less risk of exposure and compromise from concurrent workloads or the underlying system and platform. | | Cryptographic Accelerator | A specialized separate coprocessor chip from the main processing unit where cryptographic tasks are offloaded to for performance benefits. | | Hardware-Enabled Security | Security with its basis in the hardware platform. | | Platform Trust | An assurance in the integrity of the underlying platform configuration, including hardware, firmware, and software. | | Root of Trust (RoT) | A starting point that is implicitly trusted. | | Shadow Stack | A parallel hardware stack that applications can utilize to store a copy of return addresses that are checked against the normal program stack on return operations. | | Trusted Execution Environment (TEE) | An area or enclave protected by a system processor. |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases."}]}
{"id": "nist_01742", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Secure Web Services provide? (Section 196) njection Test: Involves data perturbation (i.e., alteration of the type of data the execution environment components pass to the application, or that the application's components pass to one another). Fault injection can reveal the effects of security defects on the behavior of the components themselves and on the application as a whole. [12] Security-Oriented Code Review: A code review, or audit, investigates the coding practices used in the application. The main objective of such reviews is to discover security defects and potentially identify solutions. [12] Security Service: A processing or communication service that is provided by a system to give a specific kind of protection to resources, where said resources may reside with said system or reside with other systems, for example, an authentication service or a PKI-based document attribution and authentication service. A security service is a superset of AAA services. Security services typically implement portions of security policies and are implemented via security mechanisms. [1] Service: A software component participating in a service-oriented architecture that provides functionality or participates in realizing one or more capabilities. [14] Service Composition: Aggregation of multiple small services into larger services. [14] Service Description: A set of documents that describe the interface to and semantics of a service. [1] Service Interface: The abstract boundary that a service exposes. It defines the types of messages and the message exchange patterns that are involved in interacting with the service, together with any conditions implied by those messages. [1] Service-Oriented Architecture (SOA): A collection of services. These services communicate with each other. The communication can involve either simple data passing or it could involve two or more services coordinating some activity.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services."}]}
{"id": "nist_01743", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992 say about 7 Session on Security Management in Distributed Networks? According to Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992, 7 Session on Security Management in Distributed Networks: Session Leader: Vint Cerf, Corporation for National Research Initiatives", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992."}]}
{"id": "nist_01744", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Intrusion Detection and Prevention Systems (IDPS) provide? (Section 161) uilding profiles of typical activity and identifying significant deviations. - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Searching application content for keywords (e.g., 'confidential', 'proprietary'). This makes it more valuable for network forensics and less valuable for intrusion detection and prevention than a typical network-based IDPS. 48 Although syslog has been in use for many years, it has not been standardized formally. Request for Comments (RFC) 3164, The BSD Syslog Protocol , was published in August 2001, and it is an informational RFC that describes commonly used syslog message formats based on existing implementations. It is available at By default, syslog's transport mechanism is trivially simple; RFC 3164 states that '\u2026the payload of any IP packet destined to UDP port 514 MUST be considered to be a valid syslog message'. RFC 3195, Reliable Delivery for Syslog , was published in November 2001, and it defines multiple transport mechanisms for syslog. It is available at 49 Additional information on complementary tools is available from NIST SP 800-86, Guide to Integrating Forensic Techniques into Incident Response , which is available at http://csrc.nist.gov/publications/nistpubs/. Ways in which NFAT software complements IDPSs include the following: - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; NFAT software is often more valuable for network forensics than IDPS software because of its extensive packet logging. - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Having NFAT software perform packet logging can reduce the load on network-based IDPS sensors. - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; NFAT software might be better-suited to customization, especially for content searches (e.g., keywords), than some IDPS technologies.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: intrusion detection, incident response. Contains technical security guidance that could inform defensive posture. Source: Guide to Intrusion Detection and Prevention Systems (IDPS)."}]}
{"id": "nist_01745", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective say about A. Level of Effort? (Part 2) According to Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective, A. Level of Effort: ractors , (2005) and the Registered Traveler Interoperability Consortium (RTIC) Specification (2006) are examples of high levels of effort that resulted in standards being developed within six months. Such timing was possible because of the resources dedicated to the work and the fact that both of these standards profiled already available base standards. Example: The U.S. High Definition Television (HDTV) standard was developed quickly by industry in the early 1990s. The impetus for this rapid standards development was the declaration by the Federal Communications Commission (FCC) that industry had a specific deadline to produce such a standard and demonstrate its viability or the FCC would develop the standard. Industry quickly collaborated to develop the digital specification, established a testing facility, and demonstrated interoperable digital technology.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective."}]}
{"id": "nist_01746", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Secure Domain Name System (DNS) Deployment Guide provide? (Section 124) ey for dynamic updates: ``` zone 'example.com' { type master; file 'zonedb.example.com'; allow-update { key dhcp-server.example.com.; }; }; ``` Note that although the string dhcp-server.example.com. looks like a FQDN, it actually denotes the name of the TSIG key. The implication of the configuration statement example is that any host that possess the key named dhcp-server.example.com. can submit dynamic update requests (adding, deleting, or modifying RRs) to the zone file (for the zone example.com) that resides in the primary authoritative name server. To use SIG(0) to authenticate dynamic update messages, the key used must first have its public component stored in the DNS, so a validating client can obtain it 10 . See section 9.5 on publishing keys. The previous steps above need to be performed to control access (if desired). After that is done, the updating name server (i.e., primary authoritative name server) should be able to obtain the key and process the dynamic update request (if the name server supports SIG(0) with dynamic update). Dynamic updates are allowed on the copy of the zone file in the primary authoritative name server only because that is the only 'writable' copy. This does not automatically imply that the primary authoritative name server is the only one allowed to accept dynamic update requests. In fact, BIND 9.1.0 and later versions allow secondary name servers to accept dynamic update requests and forward them to the primary authoritative name server. In this scenario, if there are no restrictions on the basis of the identity of hosts from whom the secondary name server can forward such dynamic update requests, it is equivalent to circumventing the dynamic update restrictions specified in the primary name server because the request can literally originate from any host to the secondary name server and be forwarded to the primary name server.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Domain Name System (DNS) Deployment Guide."}]}
{"id": "nist_01747", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain e. GUIDANCE FOR CALCUUATINQ SOFTWARE AND DATA REPLACEMENT COSTS: according to NIST U.S. Department of Energy Risk Assessment Methodology According to U.S. Department of Energy Risk Assessment Methodology, e. GUIDANCE FOR CALCUUATINQ SOFTWARE AND DATA REPLACEMENT COSTS:: - For \"Off-the-shelf\" Software Prices: - For Software and Data Development Costs: - -Consult computer catalogs and advertisements, as well as government price schedules and local vendor price lists available from your organization's computer support group or Procurement Office - Consult contract labor cost rates available from the Procurement Office or the contract's COTR OR - -Develop the total cost by multiplying approx, hours spent times average labor cost per hour. Accepted labor costs for your use are provided: - \u00b7 Clerclal: $5-10/hr. - \u00b7 Junior Professional or Programmer: .. Senior Professional or Programmer: - Approximate No. of work hours per: - (Holidays and weekends are not - Included) - 1 Year: 2,080 6 Months: 1,040 1 Month: 170 - . Personnel Management - . Manufacturing/Control - . Mathematics/Statistical - . Security - . Training $1 5-20/hr. $20-30/hr.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: U.S. Department of Energy Risk Assessment Methodology."}]}
{"id": "nist_01748", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain The organization prevents the unauthorized exfiltration of information across managed interfaces. according to NIST Trustworthy Email According to Trustworthy Email, The organization prevents the unauthorized exfiltration of information across managed interfaces.: Supplemental Guidance: Safeguards implemented by organizations to prevent unauthorized exfiltration of information from information systems include, for example: (i) strict adherence to protocol formats; (ii) monitoring for beaconing from information syste ms; (iii) monitoring for steganography; (iv) disconnecting external network interfaces except when explicitly needed; (v) disassembling and reassembling packet headers; and (vi) employing traffic profile analysis to detect deviations from the volume/types of traffic expected within organizations or call backs to command and control centers. Devices enforcing strict adherence to protocol formats include, for example, deep packet inspection firewalls and XML gateways. These devices verify adherence to protocol formats and specification at the application layer and serve to identify vulnerabilities that cannot be detected by devices operating at the network or transport layers. This control enhancement is closely associated with cross-domain solutions and system guards enforcing information flow requirements.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Trustworthy Email."}]}
{"id": "nist_01749", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Implementing a Zero Trust Architecture_ High-Level Document provide? (Section 56) semanaged endpoint. - \uf0a7 Scenario C-8: Stolen credential using BYOD - a legitimate user's federated ID credential is stolen and is used to request access to an enterprise resource from a BYOD endpoint. Use Case D demonstrates a subject with an Other-ID (i.e., an ID that is issued and maintained by another enterprise but known or registered by the first enterprise) requesting access to a resource. Its scenarios are: - \uf0a7 Scenario D-1: Full/limited resource access using an enterprise endpoint - the subject is granted full, limited, or no access to the requested resource as determined by its authentication status and endpoint compliance status. - \uf0a7 Scenario D-2: Full/limited internet access using an enterprise endpoint - the subject is granted full, limited, or no access to the requested internet domain as determined by enterprise policy. - \uf0a7 Scenario D-3: Stolen credential using BYOD or enterprise endpoint - a legitimate user's Other-ID credential is stolen and is used to request access to an enterprise resource from either an enterprise-managed endpoint or a BYOD. - \uf0a7 Scenario D-4: Full/limited resource access using BYOD - a subject using a bring-your-own device (BYOD) is granted full or limited access to the requested resource as determined by authentication status and enterprise policy. - \uf0a7 Scenario D-5: Full/limited internet access using BYOD - the subject is granted or denied access to an internet domain as determined by enterprise policy. - \uf0a7 Scenario D-6: Stolen credential using BYOD - a legitimate user's Other-ID credential is stolen and is used to request access to an enterprise resource from a BYOD endpoint. - \uf0a7 Scenario D-7: Just-in-Time Access Privileges - An enterprise provisions access privileges to a resource based on a single business process flow. Temporary privileges are granted to perform a portion of the business process and then revoked when the process is complete.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Implementing a Zero Trust Architecture_ High-Level Document."}]}
{"id": "nist_01750", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RS-232 in Validating the Correctness of Hardware Implementations of the NBS Data Encryption Standard? (Part 15) Control RS-232: Appendix B: The DES Test Set ## IP AND E TEST ## PLAIN 95F8A5E5DD31D900 DD7F121CA5015619 2E8653104F3834EA 4BD388FF6CD81D4F 20B9E767B2FB1456 55579380D77138EF 6CC5DEFAAF04512F 0D9F279BA5D87260 D9031B0271BD5A0A 424250B37C3DD951 B8061B7ECD9A21E5 F15D0F286B65BD28 ADD0CC8D6E5DEBA1 E6D5F82752AD63D1 ECBFE3BD3F591A5E F356834379D165CD 2B9F982F20037FA9 889DE068A16F0BE6 E19E275D846A1298 329A8ED523D71AEC E7FCE22557D23C97 12A9F5817FF2D65D A484C3AD38DC9C19 FBE00A8A1EF8AD72 750D079407521363 64FEED9C724C2FAF F02B263B328E2B60 9D64555A9A10B852 D106FF0BED5255D7 E1652C6B138C64A5 E428581186EC8F46 AEB5F5EDE22D1A36 E943D7568AEC0C5C DF98C8276F54B04B B160E4680F6C696F FA0752B07D9C4AB8 CA3A2B036DBC8502 5E0905517BB59BCF 814EEB3B91D90726 4D49DB1532919C9F ## CIPHER 8000000000000000 4000000000000000 2000000000000000 1000000000000000 0800000000000000 0400000000000000 0200000000000000 0100000000000000 0080000000000000 0040000000000000 0020000000000000 0010000000000000 0008000000000000 0004000000000000 0002000000000000 0001000000000000 0000800000000000 0000400000000000 0000200000000000 0000100000000000 0000080000000000 0000040000000000 0000020000000000 0000010000000000 0000008000000000 0000004000000000 0000002000000000 0000001000000000 0000000800000000 0000000040000000 0000000200000000 0000000100000000 0000000080000000 0000000040000000 0000000020000000 0000000010,000000 0000000008000000 0000000004000000 0000000002000000 0000000001000000 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 0101010101010101 25EB5FC3F8CF0621 AB6A20C0620D1C6F 79E90DBC98F92CCA 866ECEDD8072BB0E 8B54536F2F3E64A8 EA51D3975595B86B CAFFC6AC454 2DE31 8DD45A2DDF90796C 1029D55E880EC2D0 5D86CB23639DBEA9 1D1CA853AE7C0C5F CE332329248F3228 8405D1ABE24FB942 E643D78090CA4207 48221B9937748A23 DD7C0BBD61FAFD54 2FBC291A570DB5C4 E07C30D7E4E26E12 0953E2258E8E90A1 5B711BC4CEEBF2EE CC083F1E6D9E85F6 D2FD8867D50D2DFE 06E7EA22CE92708F 166B40B44ABA4BD6 0000000000800000 0000000000400000 0000000000200000 0000000000100000 0000000000080000 0000000000040000 0000000000020000 0000000000010000 0000000000008000 0000000000004000 0000000000002000 0000000000001000 0000000000000800 0000000000000400 0000000000000200 0000000000000100 0000000000000080 0000000000000040 0000000000000020 0000000000000010 0000000000000008 0000000000000004 0000000000000002 0000000000000001 !", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validating the Correctness of Hardware Implementations of the NBS Data Encryption Standard."}]}
{"id": "nist_01751", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-200901022 in Assessing Enhanced Security Requirements for Controlled Unclassified Information? (Part 25) Control PD-200901022: Included in the definition of each assessment method are types of objects to which the method can be applied. The application of each method is described in terms of the attributes of depth and coverage, progressing from basic to focused to comprehensive. The attribute values correlate to the assurance requirements specified by the organization. T The depth attribute addresses the rigor and level of detail of the assessment. For the depth attribute, the focused attribute value includes and builds upon the assessment rigor and level of detail defined for the basic attribute value; the comprehensive attribute value includes and builds upon the assessment rigor and level of detail defined for the focused attribute value. The coverage attribute addresses the scope or breadth of the assessment. For the coverage attribute, the focused attribute value includes and builds upon the number and type of assessment objects defined for the basic attribute value; the comprehensive attribute value includes and builds upon the number and type of assessment objects defined for the focused attribute value. Tables C-1 through C-3 provide complete descriptions of the examine , interview , and test assessment methods. The use of bolded text in the assessment method description indicates the content that was added to and appears for the first time in the description, signifying greater rigor and level of detail for the attribute value. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ TABLE C-1: EXAMINE ASSESSMENT METHOD | Method | EXAMINE The process of checking, inspecting, reviewing, observing, studying, or analyzing one or more assessment objects to facilitate understanding, achieve clarification, or obtain evidence.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_01752", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Test Personal Identity Verification (PIV) Cards Version 2 say about Authority Information Access :? According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Authority Information Access :: CA Issuers - CA Issuers - ldap://smime2.nist.gov/cn=Test%20ECC%20P- 256%20CA%20for%20Test%20PIV%20Cards%20v2,ou=Test%20CA,o=Test%20Certific ates%202020,c=US?cACertificate;binary,crossCertificatePair;binary OCSP - ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_01753", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N say about Table of Contents? (Part 14) According to A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N, Table of Contents: | 44 | | 5.5 | Administrative Review and Resource Discovery........................................... | Administrative Review and Resource Discovery...........................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N."}]}
{"id": "nist_01754", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers provide? (Section 75) ble 7-7 contains test case requirements, associated test cases, and descriptions of the test scenarios for the e-commerce platform system administrator MFA capabilities of the example implementations. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Table 7-7 Test Case MFA-5 (System Administrator MFA) | Test Case Field | Description | |--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Parent Requirement | (CR 5) The MFA example implementations shall strongly authenticate e-commerce platform administrators before the administrators perform administration activities. | | Testable Requirement | (CR 5.a) Magento and TokenOne | | Description | Show that the MFA example implementation requires the e-commerce platform administrator to authenticate with TokenOne before logging in and performing administration.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, mfa, token. Contains security framework guidance for authentication systems. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_01755", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Reference control parameter P1 according to NIST Government Smart Card Interoperability Specification, Version 2.1 According to Government Smart Card Interoperability Specification, Version 2.1, Reference control parameter P1: The reference control parameter P1 shall be used to indicate the type of requested ACR properties information. The following P1 values are possible: 0x00: All ACR table entries are to be extracted. 0x01: Only one entry of the ACR table is extracted based on ACRID. 0x10: All Applet/Object ACR table entries are to be extracted. 0x11: Only the entries of the Applet/Object ACR table for one applet are extracted based on applet AID. 0x12: Only one entry of the Applet/Object ACR table for an object is extracted based on object ID. 0x20: The Access Method Provider table is extracted. 0x21: The Service Applet table is extracted.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_01756", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Interfaces for Personal Identity Verification_ Part 2 \u2013 PIV Card Application Card Command Interface provide? (Section 91) me the key and algorithm. Table 23 shows the GENERAL AUTHENTICATE card commands sent to the PIV Card Application to realize mutual authentication using AES - ECB (algorithm identifier '08'). Table 23. Mutual authentication of client application and PIV Card Application | Command | Response | Comment | |----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | '00 87 08 9B 04 7C 02 80 00 00' | | The client application requests a witness from the PIV Card Application.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interfaces for Personal Identity Verification_ Part 2 \u2013 PIV Card Application Card Command Interface."}]}
{"id": "nist_01757", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cell Phone Forensic Tools_ an Overview and Analysis say about Supported Phones? According to Cell Phone Forensic Tools_ an Overview and Analysis, Supported Phones: The make, model, and type of CDMA phone determine what data BitPIM can acquire. Some common data fields that BitPIM can recover are: Phonebook, Wallpapers (Graphic files present on the phone), Ringers (sound bytes), Calendar entries, and Memo entries. BitPIM also captures a dump of the filesystem, where data related to Incoming/Outgoing/Missed/Attempted calls and SMS/MMS messages can be found. Figure 52 shows a screen shot of the phones listed in the Settings window under a menu item that allows selection of the specific make and model of the device for acquisition. The Read Only box should always be checked to avoid writing to the phone. Figure 52: Supported Phone Selection <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_01758", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does ANSI_NIST-ITL 1-2011 Requirements and Conformance Test Assertions provide? (Section 128) pe(Record) EQ 20) t-2 t-2 90 B* B* B* B B B* B B* B* Source Type- 20 Field: 10.024- Subject Quality Scores Type- 20 Field: 10.025- Subject Pose Angles Value included in the transaction. 8.10.22, Table 53, 7.7.7 <Table 53 lists the value constraints for SQS.> D 10.024-SQS <See Requirement ID: \u201cField: Sample Quality Subfield 1\u201d and \u201cField: Sample Quality Subfield 2\u201d and \u201cField: Sample Quality Subfield 3\u201d.> t-2 8.10.23, Table 53 <Table 53 lists the value constraints for SPA.> 1 M \u21d1 1 M \u21d1 1 M \u21d1 1 O \u21d1 10.025- SPA- Value Subfield 1 10.025- SPA- Value Subfield 2 10.025- SPA- Value Subfield 3 10.025- SPA- Value Subfield 4 to 6 {US_Subfield:1 in 10.025} GTE -180 AND LTE 180 {US_Subfield:2 in 10.025} GTE -90 AND LTE 90 {US_Subfield:3 in 10.025)} GTE -180 AND LTE 180 {US_Subfields:4 to 6 in 10.025)} GTE 0 AND LTE 90 Field: 10.026- Subject Facial Description Value Field: 10.027- Subject Eye Color Value Field: 10.028- Subject Hair Color Value 8.10.24, Table 53, Table 58 8.10.25, Table 53, Table 14 8.10.26, Table 53, Table 59 8.10.27, Table 53 Field: 10.029- 2D Facial Feature Points Value The value should be selected from the \u201cAttribute code\u201d column of Table 58. D 10.026-SXS <Cannot check for values because the standard allows user-defined Alphabetic Text. See Requirement ID: \u201cField: Type10-Subfield CharType\u201d and \u201cField: Type10-Subfield CharCount\u201d> t-2 <Table 53 lists the value constraints for SEC.> D 10.027-SEC <See Requirement ID: \u201cField: Image ECL Value\u201d>. t-2 <Table 53 lists the value constraints for SHC.> When the subject is predominantly bald, but hair color is discernible, then the appropriate hair color attribute code shall follow \u201cBAL\u201d in a second entry. For streaked hair, use \u201cSTR\u201d in the first entry; use the second entry to describe the principal color of the hair. <Table 53 lists the value constraints for FFP.> The first information item, feature point type / FPT is a one character value.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: ANSI_NIST-ITL 1-2011 Requirements and Conformance Test Assertions."}]}
{"id": "nist_01759", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does An Overview of Mobile Application Vetting Services for Public Safety say about 5 Mobile Application Vetting Service Feature Descriptions? According to An Overview of Mobile Application Vetting Services for Public Safety, 5 Mobile Application Vetting Service Feature Descriptions: The goal of this exercise is to gain understanding of the features offered by services in the mobile application vetting space. The following list of features was derived from the analysis of the mobile application vetting services mentioned in the previous section. Features were established according to common characteristics found within each mobile application vetting service. This section describes each feature and provides details on how the information may be beneficial to public safety.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: An Overview of Mobile Application Vetting Services for Public Safety."}]}
{"id": "nist_01760", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide for Security-Focused Configuration Management of Information Systems? (Part 31) Control ES-1: , databases, etc.) used to build the system. For example, a secure configuration for selected IT products used within the system or organization could incorporate the principle of least functionality. Least functionality helps to minimize the potential for introduction of security vulnerabilities and includes, but is not limited to, disabling or uninstalling unused/unnecessary operating system (OS) functionality, protocols, ports, and services, and limiting the software that can be installed and the functionality of that software. Implementing secure configurations is part of the Identifying and Implementing Configurations phase of SecCM and supports the implementation of NIST [SP 800-53] controls CM-6 Configuration Settings and CM-7 Least Functionality. ## 2.3.7 BASELINE CONFIGURATION A baseline configuration is a set of specifications for a system, or Configuration Item (CI) within a system, that has been formally reviewed and agreed on at a given point in time, and which can be changed only through change control procedures. The baseline configuration is used as a basis for future builds, releases, and/or changes. The baseline configuration of a system may evolve over time depending on the stage of the system development life cycle (SDLC). Early in the SDLC when a system is being initiated and acquired, the baseline may be a set of functional requirements. As the system is developed and implemented, the baseline may expand to include additional configuration items such as the technical design, the software load, the architecture, and configurations of the system and its individual components. A baseline configuration may also represent different information computing environments such as development, test, and production. When a new baseline configuration is established, the implication is that all of the changes from the last baseline have been approved.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_01761", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 18. Recipient denies receiving information (Repudiate\\_Receive) according to NIST IT Security for Industrial Control Systems According to IT Security for Industrial Control Systems, 18. Recipient denies receiving information (Repudiate\\_Receive): The recipient of a message denies receiving the message, to avoid accountability for receiving the message or to avoid obligations incurred as a result of receiving the message.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IT Security for Industrial Control Systems."}]}
{"id": "nist_01762", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-4009 in NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3? (Part 62) Control SI-4009: See Security Label.' | | SLA for Privacy | | TBD | | | Signed data (applied to privacy) | CNSSI-4009 | | | | Privacy Spillage | CNSSI-4009 | | 'Security incident that results in the transfer of classified or CUI information onto an information system not accredited (i.e., authorized) for the appropriate security level.' | | Status (for privacy components) monitoring | NIST SP 800-137 | Person or s/w agent | 'Monitoring the information security metrics defined by the organization in the information security ISCM strategy.' | | Term | Sources | Security and Privacy Fabric | Comments | |----------------------------------------------------------------------------|---------------------------------------------------------|------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Suppression measure (applied to privacy) | CNSSI-4009 | | 'Action, procedure, modification, or device that reduces the level of, or inhibits the generation of, compromising emanations in an information system.' | | Privacy Integrity | NIST SP 800-27 | | Adapt from System Integrity?", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, cui. Contains guidance on protecting sensitive government information. Source: NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3."}]}
{"id": "nist_01763", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data say about 3.2 Classifying Vulnerabilities Based on Hypervisor Functionality? (Part 4) According to A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data, 3.2 Classifying Vulnerabilities Based on Hypervisor Functionality: Interrupt Controller (APIC). It was discovered in Xen 4.8.x through 4.10.x. This vulnerability allows an x86 PVH guest OS user to cause a DoS attack (a NULL pointer dereference and hypervisor crash). | | Hypercalls | An example of hypercall vulnerability is CVE-2017-8903, which is reported through Xen 4.8.x on 64-bit platforms that might allow a PV guest OS user to execute arbitrary code on the host OS by mishandling page tables after an IRET hypercall. | | VMExit | The exploit of a VMExit-handling code usually leads to a DoS attack. An example of a VMExit vulnerability is CVE-2017-2596, in which the 'nested_vmx_check_vmptr' function in arch/x86/kvm/vmx.c in the Linux kernel through 4.9.8 improperly emulates the VMXONinstruction that puts the processor in Virtual Machine Extensions (VMX) root mode. This then | | Hypervisor Functionality | Sample Vulnerability | |----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | allows a KVM L1 guest OS user to cause a DoS attack (the host OS memory consumption) by leveraging the mishandling of page references.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit, cve-. Contains technical security guidance that could inform defensive posture. Source: A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data."}]}
{"id": "nist_01764", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Electronic Mail Security say about Appendix B-Email-Related RFCs? (Part 1) According to Guidelines on Electronic Mail Security, Appendix B-Email-Related RFCs: Appendix B-Email-Related RFCs This appendix contains lists of IETF RFCs that are related to email and email security. The first list contains an extensive list of RFCs, sorted by RFC number. The subsequent lists contain subsets of the first list, focused on particular protocols such as IMAP4, POP, SMTP, and MIME. Email-Related RFCs by RFC Number | RFC No. | RFC Cat.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_01765", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 193) successful logon a\ue001empts, or both is de\ufb01ned; AC-09(02) the user is no\ue000\ufb01ed, upon successful logon, of the number of <AC-09(02)_ODP[01] SELECTED PARAMETER VALUE> during <AC-09(02)_ODP[02] \ue000me period>. POTENTIAL ASSESSMENT METHODS AND OBJECTS: AC-09(02)-Examine [SELECT FROM: Access control policy; procedures addressing previous logon no\ue000\ufb01ca\ue000on; system design documenta\ue000on; system con\ufb01gura\ue000on se\ue001ngs and associated documenta\ue000on; system audit records; system security plan; other relevant documents or records]. AC-09(02)-Interview [SELECT FROM: System/network administrators; organiza\ue000onal personnel with informa\ue000on security responsibili\ue000es; system developers]. AC-09(02)-Test [SELECT FROM: Mechanisms implemen\ue000ng access control policy for previous logon no\ue000\ufb01ca\ue000on]. AC-09(03) PREVIOUS LOGON NOTIFICATION | NOTIFICATION OF ACCOUNT CHANGES ASSESSMENT OBJECTIVE: Determine if: AC-09(03)_ODP[01] changes to security-related characteris\ue000cs or parameters of the user\u2019s account that require no\ue000\ufb01ca\ue000on are de\ufb01ned; AC-09(03)_ODP[02] the \ue000me period for which the system no\ue000\ufb01es the user of changes to security- related characteris\ue000cs or parameters of the user\u2019s account is de\ufb01ned; AC-09(03) the user is no\ue000\ufb01ed, upon successful logon, of changes to <AC-09(03)_ODP[01] security-related characteris\ue000cs or parameters> during <AC-09(03)_ODP[02] \ue000me period>. POTENTIAL ASSESSMENT METHODS AND OBJECTS: AC-09(03)-Examine [SELECT FROM: Access control policy; procedures addressing previous logon no\ue000\ufb01ca\ue000on; system design documenta\ue000on; system con\ufb01gura\ue000on se\ue001ngs and associated documenta\ue000on; system audit records; system security plan; other relevant documents or records]. AC-09(03)-Interview [SELECT FROM: System/network administrators; organiza\ue000onal personnel with informa\ue000on security responsibili\ue000es; system developers].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01766", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Special Factors Affecting Integrity Impact Determination according to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices? Special Factors Affecting Integrity Impact Determination: Impacts to some population health management and consumer safety information and supporting information systems associated with quality assurance of food, animal, plant and pharmaceuticals may affect the security of critical agriculture and food and public health infrastructures. Additionally, unauthorized modification or destruction of information affecting external communications (e.g., web pages, electronic mail) may adversely affect operations and public confidence in the agency and the agency mission. In such cases, unauthorized modification or destruction of information can result in loss of human life. This can result in assignment of a high impact level to such information.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_01767", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Available at https according to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations? Available at https: //www.cnss.gov/CNSS/issuances/Instructions.cfm", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_01768", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Random Bit Generator (RBG) Constructions say about 2.5. RBG Security Boundaries? (Part 2) According to Recommendation for Random Bit Generator (RBG) Constructions, 2.5. RBG Security Boundaries: BG3 constructions in Sec. 5 and 6, respectively, use this model. Fig. 2. Example of an RBG security boundary within a cryptographic module <!-- image --> In the case of the RBG1 construction in Sec. 4, the security boundary containing the DRBG does not include a randomness source (shown as an entropy source in Fig. 2). For an RBGC construction, the security boundary is the computing platform on which the tree of DRBGs is used. A cryptographic primitive (e.g., an approved hash function or block cipher) used by an RBG may be used by other applications within the same cryptographic module. However, these other applications shall not modify or reveal the RBG's output, intermediate values, or internal state.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Bit Generator (RBG) Constructions."}]}
{"id": "nist_01769", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Integrity according to NIST Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Integrity: The integrity impact level is based on the specific mission and the data supporting that mission, not on the time required to detect the modification or destruction of information. Judicial hearings activities are not typically time-critical. Modification or destruction of court records can result in disruption or jeopardy to legal proceedings. In most cases, the adverse effects of unauthorized modification or destruction of judicial hearings information on agency mission functions and/or public confidence in the agency will be limited. Recommended Integrity Impact Level: The provisional integrity impact level recommended for judicial hearings information is low .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_01770", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.4.3 Follow-Up Interviews according to NIST Report_ Authentication Diary Study According to Report_ Authentication Diary Study, 3.4.3 Follow-Up Interviews: Within one month after the 'diary day,' we met with each participant to interview them about their experiences with authentication. During this time, basic demographic information, including profession, gender, and age range, was collected from each participant. The interview focused on retrospectively reviewing diary events to ensure the researchers understood the data collected, as well as the context for problem events. Because of the retrospective nature of the interview, participant diaries were used in combination with a list of open-ended questions (see Sec. 3.2 ), to set the framework for the exchange. Initially, participants were asked what they thought the big insights were from their 'diary day,' what surprises they encountered, and what questions they had. The rest of the interview investigated: - The number and frequency of authentications throughout the day, and how participants felt about these measures. - How much control and autonomy participants felt they had in authentication and where they exercised it, e.g., whether they could do certain things to control how often they authenticated. - Where participants encountered frustration, and what were the factors contributing to that frustration, i.e., what participants found frustrating and why. - When participants authenticated during the day and why. - How participants felt about the effectiveness of authentication, including perceived tradeoffs of security versus usability and convenience. - How participants decided on their coping strategies, if used. - How typical the timing of recorded authentication events was. - What participants considered the major impediments related to authentication. Participants' responses to these inquiries are related in Sec. 4 and Sec. 6 . Appendix C provides a catalog of participants' direct quotes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report_ Authentication Diary Study."}]}
{"id": "nist_01771", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain ERRATA according to NIST Metrics and Key Performance Indicators for Robotic Cybersecurity Performance Analysis According to Metrics and Key Performance Indicators for Robotic Cybersecurity Performance Analysis, ERRATA: ERRATA This table contains changes that have been incorporated into NISTIR 8177. Errata updates can include corrections, clarifications, or other minor changes in the publication that are either editorial or substantive in nature. | Date | Type | Change | Page | |------------|-------------|-------------------------------------------------------------------------------------------------------------------------|--------| | 04-24-2019 | Editorial | General formatting. | All | | 04-24-2019 | Substantive | Updated description for KPI 4.1 ( Actuation Latency ) in Table 4. | 9 | | 04-24-2019 | Substantive | Added new KPI 4.6 ( Job Execution Time ) in Table 4. | 9 | | 04-24-2019 | Substantive | Incorporated the original notes for Throughput Rate (KPI 2.3) into the general formulas and fixed a mathematical error. | 15 | | 04-24-2019 | Substantive | Fixed variable terms for KPI 3.2 ( Joint Setpoint ). | 18 | | 04-24-2019 | Substantive | Updated the description, formula, and notes for KPI 4.1 ( Actuation Latency ). | 19 | | 04-24-2019 | Substantive | Updated the formula and notes for KPI 4.2 ( Pose Travel Time ). | 20 | | 04-24-2019 | Editorial | Restructured formula layout for KPI 4.3 ( Position Accuracy ). | 20 | | 04-24-2019 | Substantive | Added new KPI 4.6 ( Job Execution Time ). | 22 | | 04-24-2019 | Substantive | Added bar accent to formula for KPI 6.6 to denote the calculation produces an average value. | 26 | | 04-24-2019 | Substantive | Added bar accent to formula for KPI 6.7 to denote the calculation produces an average value. | 27 | | 04-24-2019 | Substantive | Fixed error in formula for KPI 8.2 ( CPU Utilization Distribution) . | 29 | | 04-24-2019 | Editorial | Fixed formatting error, separating tables for KPI 8.2 and KPI 9.1. | 30 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Metrics and Key Performance Indicators for Robotic Cybersecurity Performance Analysis."}]}
{"id": "nist_01772", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 242) Instead, the interface characteristics between the systems (e.g., how the information is being exchanged. how the information is protected) are described in the respective security and privacy plans. If the systems that exchange information have different authorizing officials within the same organization, the organizations can develop agreements or provide the same information that would be provided in the appropriate agreement type from CA-3a in the respective security and privacy plans for the systems. Organizations may incorporate agreement information into formal contracts, especially for information exchanges established between federal agencies and nonfederal organizations (including service providers, contractors, system developers, and system integrators). Risk considerations include systems that share the same networks. Related Controls: AC-4, AC-20, AU-16, CA-6, IA-3, IR-4, PL-2, PT-7, RA-3, SA-9, SC-7, SI-12. Control Enhancements: (1) SYSTEM CONNECTIONS | UNCLASSIFIED NATIONAL SECURITY SYSTEM CONNECTIONS [Withdrawn: Moved to SC-7(25).] (2) SYSTEM CONNECTIONS | CLASSIFIED NATIONAL SECURITY SYSTEM CONNECTIONS [Withdrawn: Moved to SC-7(26).] (3) SYSTEM CONNECTIONS | UNCLASSIFIED NON-NATIONAL SECURITY SYSTEM CONNECTIONS [Withdrawn: Moved to SC-7(27).] (4) SYSTEM CONNECTIONS | CONNECTIONS TO PUBLIC NETWORKS [Withdrawn: Moved to SC-7(28).] (5) SYSTEM CONNECTIONS | RESTRICTIONS ON EXTERNAL SYSTEM CONNECTIONS CHAPTER THREE PAGE 87 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, national security. Contains guidance on protecting sensitive government information. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01773", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to NIST_SP_800-53r5_Security_Privacy_Controls? Discussion: Although policies to control for authorized use can be applied to information", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01774", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3. The guest OS networking information on the VM's was set as follows: according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case, 3. The guest OS networking information on the VM's was set as follows:: Virtual Machine: GTB-Inspector Network interface:eth0 IP address: 10.100.0.175 Gateway: 10.100.0.1 Subnet Mask: 255.255.255.0 DNS:10.100.0.17 Network interface:eth2-&gt; connected to Monitor Port1 of a Network Aggregator device Network interface:eth3-&gt; connected to WAN interface of our Cisco-ASA firewall. Virtual Machine: GTB-Central Network interface:eth0 IP address: 10.100.0.176 Gateway: 10.100.0.1 Subnet Mask: 255.255.255.0 DNS:10.100.0.17", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case."}]}
{"id": "nist_01775", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Maintenance Testing for the Data Encryption Standard say about 1. INTRODUCTION? According to Maintenance Testing for the Data Encryption Standard, 1. INTRODUCTION: The Federal Information Processing Data Encryption Standard (DES) is the standard cryptographic algorithm for use within the Federal Government for protecting nonclassified transmission and storage of computer data. The DES algorithm is normally implemented in hardware and commercial DES devices are presently available from eight different sources. The National Bureau of Standards has validated the designs of the various hardware implementations with a validation test, i. e., a collection of input-keyoutput triplets which, when applied as a test to a device, and if successfully executed, insures that the device being tested in fact correctly executes the DES algorithm. A Monte-Carlo test using random data is also a part of this test [8], A small maintenance test, residing in read only memory and executed by the same microprocessor that controls the DES device provides a means of testing the operation of the DES hardware in the field. Since one criterion for a field test is that it be economical, the tests are designed so that only a partial test may be needed in a given application. The test is so designed that a full functional test can be executed if it is convenient and desirable to do so. The maintenance test provides results which are a combination of the validation test and of the Monte-Carlo test described in [8]. The maintenance test uses an initial fixed input-key pair and the resulting ciphertext is then fed back as input or as key, as in the Monte-Carlo test, and this cycling process is repeated. By simply checking the output of this process against four known results the test determines if the DES algorithm is properly functioning. A maximum of 192 cycles has been determined to test completely the DES device but three earlier check points are defined which result in specific partial tests. In all, four categories of tests have been defined. They range from a simple test for stuck-faults of the 54 output bits of the DES to a complete functional test.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Maintenance Testing for the Data Encryption Standard."}]}
{"id": "nist_01776", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is https according to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services? https: //www.afrl.af.mil/News/Article/2874807/afrls-pnt-agilepod-achieves-flight-testobjectives/https://doi.org/10.21236/ADA290597 or ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_01777", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Timing Channels according to NIST Guidelines for Evaluating Differential Privacy Guarantees According to Guidelines for Evaluating Differential Privacy Guarantees, Timing Channels: In some cases, the time it takes to run a query may reveal something about the underlying data. This risk is especially pronounced if untrusted analysts are allowed to write their own queries and measure how long it takes to receive the answer. For example, it might be possible to write a program whose running time reveals whether or not Joe is a part of the data with 100% certainty: ``` Example: Timing Channel Attack. if Joe in Data: return slowQuery() else: return fastQuery() ``` In many settings, timing is not an issue because analysts are not allowed to design and submit their own queries, or they are not able to observe how long those queries take to run. If analysts can submit their own queries and measure running time, careful implementations must be used to hide the information revealed by the running time.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Evaluating Differential Privacy Guarantees."}]}
{"id": "nist_01778", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Fiscal Year 2021 Cybersecurity and Privacy Annual Report say about ABSTRACT? According to Fiscal Year 2021 Cybersecurity and Privacy Annual Report, ABSTRACT: During Fiscal Year 2021 (FY 2021) - from October 1, 2020, through September 30, 2021 - the NIST Information Technology Laboratory (ITL) Cybersecurity and Privacy Program successfully responded to numerous challenges and opportunities in security and privacy. This annual report highlights the FY 2021 research agenda and activities for the ITL Cybersecurity and Privacy Program, including the ongoing participation and development of international standards; the enhancement of privacy and security risk management models, including those for the protection of controlled unclassified information (CUI), systems engineering and cyber resiliency, supply chains, and mobile technologies; the continued advancement of cryptographic technologies, including updates to Federal Information Processing Standard (FIPS) Publication 140-3, Security Requirements for Cryptographic Modules, and preparation for post-quantum cryptographic methods; and improved infrastructure protection in areas such as zero trust architectures and advanced networking security. NIST maintained a strong focus on supporting small and medium-sized businesses (SMBs), including updates to the Small Business Cybersecurity Corner website to make resources easier to find and use and drawing on contributed cybersecurity resources and feedback received from federal partners and the public.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Fiscal Year 2021 Cybersecurity and Privacy Annual Report."}]}
{"id": "nist_01779", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Trust Model for Security Automation Data 1.0 (TMSAD) say about 7. Processing Requirements? According to Trust Model for Security Automation Data 1.0 (TMSAD), 7. Processing Requirements: All implementations MUST implement the processing requirements specified in [XMLDSIG]. This section describes additional general processing requirements that implementations of the trust model MUST follow to correctly process the trust model.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Trust Model for Security Automation Data 1.0 (TMSAD)."}]}
{"id": "nist_01780", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.2.1 Base Equation according to NIST The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities According to The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities, 3.2.1 Base Equation: The base equation is the foundation of CCSS scoring. The CCSS base equation is identical to the CVSS base equation: ``` BaseScore = round_to_1_decimal(((0.6 * Impact) + (0.4 * Exploitability) - 1.5) * f(Impact)) Impact = 10.41 * (1 - (1 - ConfImpact) * (1 - IntegImpact) * (1 - AvailImpact)) Exploitability = 20 * AccessVector * Authentication * AccessComplexity f(Impact) = 0 if Impact = 0, 1.176 otherwise AccessVector = case AccessVector of requires local access: 0.395 adjacent network accessible: 0.646 network accessible: 1.0 Authentication = case Authentication of requires multiple instances of authentication: 0.45 ``` ``` requires single instance of authentication: 0.56 requires no authentication: 0.704 AccessComplexity = case AccessComplexity of high: 0.35 medium: 0.61 low: 0.71 ConfImpact = case ConfidentialityImpact of none: 0.0 partial: 0.275 complete: 0.660 IntegImpact = case IntegrityImpact of none: 0.0 partial: 0.275 complete: 0.660 AvailImpact = case AvailabilityImpact of none: 0.0 partial: 0.275 complete: 0.660 ``` The base equation does not include two of the base metrics: Exploitability Method and Privilege Level. Exploitability Method is used in the definitions for some of the base metrics, so it is used in choosing the associated values. Privilege Level is used by analysts when calculating certain environmental metrics.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities."}]}
{"id": "nist_01781", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.4 SECCM ROLES AND RESPONSIBILITIES according to NIST Guide for Security-Focused Configuration Management of Information Systems According to Guide for Security-Focused Configuration Management of Information Systems, 2.4 SECCM ROLES AND RESPONSIBILITIES: The set of roles (at the organization, mission/business process, and system level) that are relevant to the SecCM program are defined along with the responsibilities. The responsibilities are in the context of SecCM only and are not inclusive of other non-SecCM responsibilities the roles may also have. Typically, SecCM roles and responsibilities include:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_01782", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Section 2.3 The Four-Party Model according to NIST A Credential Reliability and Revocation Model for Federated Identities According to A Credential Reliability and Revocation Model for Federated Identities, Section 2.3 The Four-Party Model: Recommendation 8: The types of attributes accepted by the federation are usually defined by the service providers of the federation. Attributes can be assigned by the identity provider to its users as either self-asserted or verified attributes. Where attributes serve a critical part in the roles or the functions a user is permitted to perform, it is important for attributes to be verified and upto-date. The identity provider, therefore, should check the authoritative source(s) for attribute updates (e.g., changes in the attribute qualification, revocation, suspension). Recommendation 9: As a benefit of using the same credential, and taking into account service provider feedback mechanisms, the authentication decisions by the attribute provider and identity provider should be based on the same status of the credential.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Credential Reliability and Revocation Model for Federated Identities."}]}
{"id": "nist_01783", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does National Online Informative References (OLIR) Program_ Submission Guidance for OLIR Developers say about Supportive Relationship Mapping OLIR? According to National Online Informative References (OLIR) Program_ Submission Guidance for OLIR Developers, Supportive Relationship Mapping OLIR: An OLIR that indicates how a supporting concept can or does help achieve a supported concept, with one of the concepts being a Focal Document Element and the other a Reference Document Element.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: National Online Informative References (OLIR) Program_ Submission Guidance for OLIR Developers."}]}
{"id": "nist_01784", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives provide? (Section 164) n the other hand, attractiveness of an intermediary function (by requirement holders, i.e., government) reference central authority. - o 'Decentralized' is quite overloaded in meaning and application. - Traceability Consideration - o Free and open-source software plays into the prime's deliveries (end deliveries to government and acceptance from suppliers). - o Is a supply chain traceability solution for software products a complete risk reduction solution? Knowing that software hasn't changed and where it came from may only cover a portion of risks specific to software products. - Company/Business Drivers - o Business Driver: rising incidence of counterfeit parts, resulting in increased support costs and brand reputation losses, among other things - o Focused on Identity and works out from it: central to broader array of traceability solutions - o Physical identity: gap in assurance between physical item and data about the physical item. - Supply Chain Risk Management - o Addresses risk associated with asserting genuineness and maintaining physical and digital data connections - o NIST 800-171 given as a reference for cyber security guidance in securing information and access. - Marketplace Positioning Model (Lens and Diffusion) - o Innovator tackling traditionally hard problem of object identification (as in serialized parts) and partnering with blockchain developers (e.g., Manufacturer X). - o Traditional solutions (serial numbers, stickers, barcodes, etc.) are not secure and are separable from objects, leaving them a mystery, and some parts are not subjectable to markings. - Win/Win and Production Possibility - o In addition to aiding a generalized security and sharing win/win by providing a way to uniquely identify objects, this technology moves the PPF by enabling ecosystem participants to maintain and share all their data, and also protect their IP by having a detailed and agile permissioning approach for the data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist 800, fips, security control. General security reference material without sensitive content. Source: Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives."}]}
{"id": "nist_01785", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways say about 3.4.5 Scenario 4: Emergency mitigation (and backout if needed)? According to Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways, 3.4.5 Scenario 4: Emergency mitigation (and backout if needed): This is the emergency procedure in a crisis situation to temporarily mitigate risk for vulnerabilities prior to a vendor releasing a patch. It is typically required when the vulnerability is being actively exploited in the wild. The mitigation can vary and may or may not need to be rolled back afterward. The scope of targets is the same as Scenario 1. Organizations need to be prepared to quickly implement a wide variety of emergency mitigations to protect vulnerable devices. Without processes, procedures, and tools in place to implement emergency mitigations, too much time may be lost and vulnerable devices may be compromised before mitigations are in place. This may require disabling system functionality, having automated mechanisms to apply these changes, and having capabilities to revert back these changes when a permanent and approved patch is released.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_01786", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Design Alternatives for Computer Network Security provide? (Section 58) , based on network topology, geographic distribution, or administrative boundries.* Such subdivisions would form the individual domains for the various Security Controllers as indicated in Figure 3-1. ' S ' ' ;' One other entity that would be needed if a network were to be interconnected with other dissimilar networks is also shown in Figure 3-1. This internetwork interface will be referred to as a \"gateway\" and would be needed due to differences between two nets in one or more protocol levels. These differences would be mediated by the gateway via transformations of the message * For purposes of discussion, we will typically consider the subdivision to be on the basis of topological structure, i.e., one SC per local subnet, but there is no inherent need for physical subsetting. For excimple, an ARPA-like network could be arbitrarily divided into subsets of HOST'S, with each subset forming the domain for one Security Controller. This flexibility is due to the way in which an entity is \"attached\" to an SC, namely by providing that SC (and only j that SC) with the value of a private code (key) that is associated with that entity. I I leaders, formats, etc. with the gateway appearing in an intermediate destination HOST (to limit the affected protocol levels to those of a HOST) . If such transformations are feasible for the two nets, the gateway would effectively reflect a foreign HOST as a pseudo-HOST at the local subnet. The gateway will be considered further in Section 3.3.4. The primary concern of this chapter will be with the specification of the Security Controller. Other entities such as users at terminals, HOST's, etc. will be considered as they affect the SC, but will not be our concern per se. The next lower level entities, the Intelligent Cryptographic Devices, will be mentioned as needed to define the interface and the requirements that are passed down by the SC, but will otherwise be deferred to Section 4.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Design Alternatives for Computer Network Security."}]}
{"id": "nist_01787", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST_SP_800-37r2_Risk_Management_Framework say about ONGOING AUTHORIZATION? (Part 3) According to NIST_SP_800-37r2_Risk_Management_Framework, ONGOING AUTHORIZATION: or organizational policies. The authorizing official conveys updated risk determination and acceptance results to the senior accountable official for risk management or the risk executive (function). The use of automated support tools to capture, organize, quantify, visually display, and maintain security and privacy posture information promotes near real-time risk management regarding the risk posture of the organization. The use of metrics and dashboards increases an organization's capability to make riskbased decisions by consolidating data in an automated fashion and providing the data to decision makers at different levels within the organization in an easy-to-understand format. References: [SP 800-30]; [SP 800-39] (Organization, Mission/Business Process, and System Levels); [SP 800-55]; [SP 800-160 v1] (Risk Management Process); [IR 8011 v1]; [IR 8062].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_01788", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance) provide? (Section 166) s power. 2. Tester brings the PIV Card back into range of the contactless reader. 3. Set sharedConnection := true 4. Set connectionDescription := <<valid connection>> 5. Create cardHandle reference 6. Call pivConnect with \u2022 (IN) sharedConnection \u2022 (INOUT) connectionDescription \u2022 (INOUT) CDLength \u2022 (OUT) cardHandle 7. Call pivSelect with (AID of the PIV Card) \u2022 (IN) cardHandle \u2022 (IN) applicationAID \u2022 (IN) AIDLength \u2022 (OUT) applicationProperties \u2022 (INOUT) APLength 8. Call pivGetData with (OID of the X.509 Certificate for Card Authentication) \u2022 (IN) cardHandle \u2022 (IN) OID \u2022 (IN) oidLength | | Expected Result(s) | \u2022 (INOUT) DataLength 1. Step 6 returns with status_word of PIV_OK and initialized cardHandle . 2. Step 7 returns PIV_OK and the initialized application properties reference. 3. Step 8 returns PIV_SM_FAILED . | | Postcondition(s) | Secure Messaging is not established | This appendix specifies the tests that shall be performed on PIV Card Applications. Unless otherwise specified: - Tests within a subsection titled 'Contact Interface' shall be performed over the contact interface of the PIV Card without the use of secure messaging. These tests shall be performed for all PIV Card Applications being tested.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)."}]}
{"id": "nist_01789", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security_ Selected Articles say about security? According to Computer Security_ Selected Articles, security: support of an attempted theft. Thus, it is inappropriate that the DP staff be put in the position of defining the controls through which such problems can be identified and minimized.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security_ Selected Articles."}]}
{"id": "nist_01790", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1 say about 4. SCAP Processing Requirements and Recommendations? According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1, 4. SCAP Processing Requirements and Recommendations: This section defines the processing requirements that tools MUST follow in order to correctly process SCAP 1.1 content. This section also provides recommendations that are not mandatory; organizations are encouraged to adopt them to promote stronger interoperability and greater consistency. The topics covered in this section are legacy support, SCAP content validation, the &lt;xccdf:Profile&gt; element, and check system usage. The end of the section covers result-related topics: SCAP result data streams, XCCDF results, OVAL results, and OCIL results.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1."}]}
{"id": "nist_01791", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain hash function according to NIST Recommendation for Random Bit Generator (RBG) Constructions According to Recommendation for Random Bit Generator (RBG) Constructions, hash function: A (mathematical) function that maps values from a large (possibly very large) domain into a smaller range. The function satisfies the following properties: 1. (One-way) It is computationally infeasible to find any input that maps to any pre-specified output. 2. (Collision-free) It is computationally infeasible to find any two distinct inputs that map to the same output.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Bit Generator (RBG) Constructions."}]}
{"id": "nist_01792", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Situational Awareness for Electric Utilities provide? (Section 181) ovides a description of the risk analysis we performed. - Section 3.4.2, Security Control Map, maps the security characteristics of this example solution to cybersecurity standards and best practices. You might share the Executive Summary, NIST SP 1800-7A, with your leadership team members to help them understand the importance of adopting a standards-based situational awareness solution. IT professionals who want to implement an approach like this will find this whole practice guide useful. You can use the How-To portion of the guide, NIST SP 1800-7C, to replicate all or parts of the build created in our lab. The How-To guide provides specific product installation, configuration, and integration instructions for implementing the example solution. We do not recreate the product manufacturers' documentation, which is generally widely available. Rather, we show how we incorporated the products together in our environment to create an example solution. This guide assumes that IT professionals have experience implementing security products within the enterprise. While we have used a suite of commercial products to address this challenge, this guide does not endorse these particular products. Your organization can adopt this solution or one that adheres to these guidelines in whole, or you can use this guide as a starting point for tailoring and implementing parts of a solution that includes physical access control systems (PACS) operational technology (OT), IT systems, and business processes . Your organization's security experts should identify the products that will best integrate with your existing tools and IT system infrastructure. We hope that you will seek products that are congruent with applicable standards and best practices. Volume B, Section 3.5, Technologies, lists the products that we used and maps them to the cybersecurity controls provided by this reference solution.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Situational Awareness for Electric Utilities."}]}
{"id": "nist_01793", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Automation Support for Security Control Assessments_ Software Vulnerability Management provide? (Section 9) mary focus of the VUL capability is on known vulnerabilities (e.g., CVEs), risk associated with unknown vulnerabilities is also addressed by the focus on common sources of software flaws (e.g., CWEs). NISTIR 8011, Volume 4 outlines detailed, step-by-step processes to automate the assessment of security controls that support vulnerability management implemented for a given assessment boundary (target network) and to apply the results to the assessment of all authorization boundaries within that network. A process is also provided to implement the assessment (diagnosis) and response to a discovered vulnerability. Automated testing related to the controls for the VUL capability, as outlined herein, is consistent with other NIST guidance. NISTIR 8011, Volume 4 documents a detailed assessment plan to evaluate the effectiveness of controls related to vulnerability management. Included are specific tests that form the basis for such a plan, how the tests apply to specific controls, and the resources needed to operate and use the assessment to mitigate defects found. For the VUL capability, it can be shown that the assessment of 87.5 % 2 of determination statements for controls in the NIST SP 800-53 Low- 2 Derived from the Control Allocation Tables (CAT) in this volume. With respect to security controls selected in the NIST SP 800-53 [SP800-53] Low-Medium-High baselines that support the VUL capability, 42 of 48 determination statements (87.5 %) can be fully or partially automated. Medium-High baselines can be fully or partially automated. The methods outlined here are designed to provide objective, timely, and complete identification of defects in the effectiveness of security controls supporting the VUL capability, facilitating risk management at a lower cost than manual assessment methods. Using security control defect information can drive the most efficient and effective responses to the security defects found.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Automation Support for Security Control Assessments_ Software Vulnerability Management."}]}
{"id": "nist_01794", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to Security and Privacy Controls for Information Systems and Organizations? Discussion: Security marking refers to the application or use of human-readable security", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01795", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-512 in Computer Security Division 2009 Annual Report? (Part 12) Control HA-512: s used in their small businesses. The draft of NISTIR 7621 was released for public comment in September 2009 and is planned for release as a final document in the first quarter of FY2010. Contact: Mr. Richard Kissel (301) 975-5017 richard.kissel@nist.gov ## Cryptographic Technology Group ## STRATEGIC GOAL Develop and improve mechanisms to protect the integrity, confidentiality, and authentic ity of federal agency information by developing security mechanisms, standards, testing methods, and supporting infrastructure requirements and procedures. ## Overview The Cryptographic Technology (CT) Group continues to make an impact in cryptography within and outside the federal government. Strong cryptography can be used to improve the security of systems and the information they process. IT users enjoy the enhanced availability of secure applications in the marketplace that is made possible by the appropriate use of cryptography. Our main work in this area addresses topics such as hash algorithms, symmetric and asymmetric cryptography techniques, key management and transport, authentication, cryptographic protocols, Internet security services, security applications, biometrics, and smart tokens. A few examples of the impact of our work are changes to how users authenticate their identities for online government services and new methods for authentication and key management of wireless applications. This work also supports the NIST's Personal Identity Verification (PIV) project in response to the Homeland Security Presidential Directive 12 (HSPD-12). The CT Group collaborates with national and international agencies, academic and research organizations, and standards bodies to develop interoperable security standards and guidelines.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, token. Contains security framework guidance for authentication systems. Source: Computer Security Division 2009 Annual Report."}]}
{"id": "nist_01796", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet provide? (Section 189) | | T | | Req. # - ID | Ref. in Base Std. | Requirement Summary | L e v e l | Assertion ID | Test Assertion | N o t e s | Imp. Required | Imp. Support | Supporte d Range | Test Result | E n c .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet."}]}
{"id": "nist_01797", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Quarantine decision and enforcement according to Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways? Quarantine decision and enforcement: 6) The vulnerability management system shares the device patch level with the network access management system to be used for network access control. 7) The network access management system applies one of the following two enforcement actions: 7a) If the network device does not exceed the organizational patch threshold, the device is given network access and does not need to go through the remainder of the diagram. 7b) If the network device exceeds the organizational patch threshold, the network access management system performs quarantine actions on the endpoint and restricts network access. 8) The network access management system shares the missing patch information with the software and configuration management system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_01798", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings provide? (Section 84) ; while ri = 1 means 'granted'. The set C is the crucial authorization decisions in R , which means any element rj in the set C must be 'granted', in order that the access be authorized. The above process can be generalized as [0,1] \u2208 i r and 0 \u2265 s F , when the provider is not so sure about his decision. In XPOLA-enabled Web services, when a user makes a remote call from the client side, the client program first performs a preliminary authorization check by matching the capability policy with the SOAP body content and the user's identity. If nothing violates the policy, it inserts the appropriate tokens into the SOAP header, including the signatures; otherwise, the client is refrained from invoking the request. Figure 6 The Processing Stack on the Service Side <!-- image --> On the resource side, when the Web service receives a remote call through a SOAP message, the processing node first authenticates it by checking the validity of the user's signature against the whole message. If nothing is wrong, the authorization processing node verifies the signature of the embedded capability token. It then does a series of matching operations, such as the capability issuer's DN and the actual resource provider's DN, the actual caller's DN and the allowed users' DNs, the operations specified in the capability and the ones in the SOAP body. It also checks whether the capability has expired against the time. At last, it peels off the capability token and passes the rest of the SOAP message on to the next processing node. The detailed diagram is showed in Figure 6. The client side policy checking prevents those unauthorized requests from reaching services and is able to prompt appropriate error information immediately to the users. Services thus need not waste their resources on processing these requests.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, pki, token. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_01799", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessment of Access Control Systems provide? (Section 79) nforcing separation, consider the capabilities of a cashier and a cashier supervisor, where the capability to void erroneous cashier transactions is assigned to the cashier supervisors. Clearly, a user's ability to execute the capabilities of both cashier and cashier supervisor within a single subject would constitute a conflict of interest (i.e., a user acting as cashier would be able to void his or her own transactions). One prescribed approach to this security issue is to restrict any user from simultaneously obtaining membership to both cashier and cashier supervisor. However, such an approach could impose unacceptable operational restrictions (i.e., the users authorized for the role and capabilities of cashier supervisor would never be able to perform the functions of the cashier). Examples of SSOD policies are RBAC and RuBAC (Sections 3.4 and 3.5). SOD constraints may require that two roles be mutually exclusive, because no user should have the privileges from both roles. This might be done, for example, to deny any user the ability to both enter and authorize an order for disbursement of funds. However, permission 'escalation,' violating SOD requirements, may occur if a third role is assigned the requisite permissions without being included in SOD constraints. A user might have one of the mutually exclusive roles, yet acquire this third role and thereby gain the ability to violate the requirement that no individual can both enter and authorize funds disbursement. In an environment where there are numerous users, attributes, objects, and relations, safety needs to be carefully considered. Separation of duties can be enforced dynamically (i.e., at access time), and the decision to grant access refers to the past access history.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Assessment of Access Control Systems."}]}
{"id": "nist_01800", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CA-3 in Security and Privacy Controls for Information Systems and Organizations? (Part 2) Control CA-3: onsider the risk related to new or increased threats that may be introduced when systems exchange information with other systems that may have different security and privacy requirements and controls. This includes systems within the same organization and systems that are external to the organization. A joint authorization of the systems exchanging information, as described in CA-6(1) or CA-6(2), may help to communicate and reduce risk. Authorizing officials determine the risk associated with system information exchange and the controls needed for appropriate risk mitigation. The types of agreements selected are based on factors such as the impact level of the information being exchanged, the relationship between the organizations exchanging information (e.g., government to government, government to business, business to business, government or business to service provider, government or business to individual), or the level of access to the organizational system by users of the other system. If systems that exchange information have the same authorizing official, organizations need not develop agreements. Instead, the interface characteristics between the systems (e.g., how the information is being exchanged. how the information is protected) are described in the respective security and privacy plans. If the systems that exchange information have different authorizing officials within the same organization, the organizations can develop agreements or provide the same information that would be provided in the appropriate agreement type from", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01801", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Derived PIV Application and Data Model Test Guidelines say about 9.3.1.3 Public Key Size? (Part 1) According to Derived PIV Application and Data Model Test Guidelines, 9.3.1.3 Public Key Size: 9.3.1.3 Public Key Size | Test Assertion | TA-09.03.01.03 | |----------------------|-----------------------------------------------------------------------------------------| | Purpose | Verifies that the key size requirements are in accordance with Table 3-1 of [SP800-78]. | | DTR(s) | \u2022 DTR-07.03.01.12 | | Issuer Documentation | None. | | Precondition(s) | \u2022 A token with the Derived PIV Application is inserted into an appropriate token reader. \u2022 Suitable drivers have been loaded between the test system and an instance of the reader. \u2022 A Derived PIV Authentication certificate is present within the Derived PIV Application. | |--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Test Scenario | 1. Send the SELECT command with \u2022 AID == 'A0 00 00 03 08 00 00 20 00 01 00' 2. Send GET DATA command with \u2022 Data field of the command containing the tag ('5FC105') of the X.509 Certificate for Derived PIV Authentication data object 3. Extract subjectPublicKeyInfo->algorithm->algorithm field value. 4. Extract the subjectPublicKeyInfo->subjectPublicKey from the certificate 5. Match the key size to Table 3-1 of [SP800-78]. | | Expected Result(s) | 1. From Step 1, the command returns the application property template with the status word '90 00'. 2. From Step 2, the command returns the requested data object along with the status word '90 00'. 3.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_01802", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SC-03(02) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control SC-03(02): SECURITY FUNCTION ISOLATION | ACCESS AND FLOW CONTROL FUNCTIONS", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01803", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RC-725 in A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems? (Part 8) Control RC-725: nt support is needed after the distribution as all of the activity comes from the subject side. A credential is private by default, and a subject can redeem it only if they want to use or transfer it. However, the list of all the identifiers the Merkle airdrop was issued to must be available to the subjects to redeem their NFT (both the private key and the list of all the identifiers included in the Merkle airdrop are needed to build the Merkle proof and mint the NFT). In Merkle airdrops, tokens must be pulled by the users while for traditional airdrops tokens are pushed to them without any approval needed. ## 4.4.2.2 Offchain Object In this architecture, a credential takes the form of an offchain object that acts as a self-contained vehicle for transmitting information directly between parties. This can go hand in hand with the bring-your-own blockchain address architecture (discussed in Section 4.4.1.2) to establish a lightweight identity management system that can operate at scale. It best matches use cases where the lifecycle of a credential is predetermined. However, verification of a credential (see Lifecycle Determination at Origination in Section 4.2.1) may require chain access (see Efficiency and Cost in Section 4.3). In particular, if revocability is permitted, onchain artifacts are required for one to check the credential revocation status, such as credential revocation registries (see Offchain Objects Coupled with Global Credentials Registry in Section 4.4.3). It can provide a high level of control and autonomy to the subjects as they can manage the storage of their own credentials offchain. It ensures privacy by default and need not be constrained to a specific blockchain. This architecture may use, for example, the JWT format (see Section 3.4 on Building Blocks ), as in Blockstack [49]. ## 4.4.3 Combination Patterns It is possible to combine the architectures for identifiers, credentials, or both.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: identity management, token. Contains security framework guidance for authentication systems. Source: A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems."}]}
{"id": "nist_01804", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Information Security Handbook_ A Guide for Managers? (Part 115) Control PD-12: in Phase 3. The steps to develop a business case are based on industry practices and mandated guidance, including Office of Management and Budget (OMB) Circular A-11, the Clinger-Cohen Act, and GPRA. The results of the prior three phases will be included in the business case as supporting evidence. NIST SP 800-55 provides guidance on security practitioners' inputs into the CPIC process and on their role in core development. Each agency should follow agency-specific business case guidance during this phase. Typically, the components and analysis of the business facilitate the completion of internal and external budget requests. A thorough examination of the business case will support and facilitate the obtaining resources process. 48 Also see Chapter 10, Risk Management, and Chapter 11, Certification, Accreditation, and Security Assessments, of this guide for additional guidance on prioritizing corrective actions. ## 7.4.5 Apply Corrective Actions Phase 6 of the process, Apply Corrective Actions, involves implementing corrective actions as determined through data analysis and as defined in an applicable business case or a POA&amp;M. After corrective actions are applied, the cycle completes itself and restarts with subsequent data collection and analysis. Iterative data collection, analysis, and reporting will track the progress of corrective actions through the POA&amp;M, among others, measure improvement, and identify areas for further improvement to be included in tactical plans, Program Management Plans, or other agency planning mechanisms. The iterative nature of the cycle ensures that the progress is monitored, and the corrective actions are affecting system security control implementation in an intended way.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_01805", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain SOLUTION according to NIST Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, SOLUTION: The NCCoE Secure InterDomain Routing (SIDR) Project is improving internet security by demonstrating how to use ROV to protect against route hijacks. The SIDR Project has produced a proof -of-concept example that demonstrates the use of BGP ROV in realistic deployment scenarios, has developed detailed deployment guidance, has addressed implementation and use issues, and has generated best practices and lessons le arned. Project results are presented in this publicly available NIST Cybersecurity Practice Guide. This guide describes the following concepts : - security objectives that are supported by implementing BGP ROV that uses Resource Public Key Infrastructure (RPKI) mechanisms - an example solution of methods and tools that demonstrate and enable a practical implementation of BGP ROV - how to protect your own internet addresses from route hijacking by registering them with trusted sources, thereby gaining assurance that traffic intended for your organization will not be hijacked when it is forwarded by entities that perform BGP ROV - how to perform BGP ROV on received BGP route updates to validate, if possible, whether the entity that originated the route is in fact authorized to do so - how to more precisely express your routing security requirements and/or service offerings While the NCCoE used a suite of available products to address this challenge, this guide does not endorse these particular products, nor does it guara ntee compliance with any regulatory initiatives. Your organization's information security experts should identify the products that will best integrate with your existing tools and information technology (IT) system infrastructure. Your organization can adopt this solution or one that adheres to these guidelines in whole, or you can use this guide as a starting point for tailoring and implementing parts of a solution.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, sso. Contains security framework guidance for authentication systems. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_01806", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Conformance Test for FDDI Medium Access Control (MAC) provide? (Section 180) \") flush_queue () ; PHInvalidRSOb () ; DL_POSTAMBLE ( ) print_verdict (\"End test case PHInvalidRSOb \") Output_trace (\"\\n\\nStarting test case DetectTokenEDl \"); flush_queue () ; DetectTokenEDl () DL_POSTAMBLE ( ) print_verdict (\"End test case DetectTokenEDl \"); Output_trace (\"\\n\\nStarting test case DetectTokenED2 \"); flush_queue () ; DetectTokenED2 () DL_POSTAMBLE ( ) print_verdict (\"End test case DetectTokenED2 \"); exit ( ) ``` ``` /* NIST TTCN Translator Version 1.0 4/89 */ include <stdio.h> include \"sysdef.h\" typedef unsigned char BYTE; typedef struct { union { long v; char *ptr; } value; char tag; } CONSTARG; extern int _level, _time.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, token. Contains security framework guidance for authentication systems. Source: A Conformance Test for FDDI Medium Access Control (MAC)."}]}
{"id": "nist_01807", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is DES according to A Study of OSI Key Management? DES: Data Encryption Standard.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of OSI Key Management."}]}
{"id": "nist_01808", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices provide? (Section 587) HE ESTABLISHMENT OF THE DEPARTMENT OF HOMELAND SECURITY [See http://www.state.gov/documents/organization/22978.doc.] Section 19. Functions of Certain Officials in the Department of Homeland Security. The Secretary of Homeland Security, the Deputy Secretary of Homeland Security, the Under Secretary for Information Analysis and Infrastructure Protection, Department of Homeland Security, and the Assistant Secretary for Information Analysis, Department of Homeland Security, each shall be considered a 'Senior Official of the Intelligence Community' for purposes of Executive Order 12333, and all other relevant authorities, and shall: (a) recognize and give effect to all current clearances for access to classified information held by those who become employees of the Department of Homeland Security by operation of law pursuant to the Homeland Security Act of 2002 or by Presidential appointment; (b) recognize and give effect to all current clearances for access to classified information held by those in the private sector with whom employees of the Department of Homeland Security may seek to interact in the discharge of their homeland security-related responsibilities; (c) make all clearance and access determinations pursuant to Executive Order 12968 of August 2, 1995, or any successor Executive Order, as to employees of, and applicants for employment in, the Department of Homeland Security who do not then hold a current clearance for access to classified information; and (d) ensure all clearance and access determinations for those in the private sector with whom employees of the Department of Homeland Security may seek to interact in the discharge of their homeland security- related responsibilities are made in accordance with Executive Order 12829 of January 6, 1993.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, secret. Contains guidance on protecting sensitive government information. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_01809", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Risk Management Framework Development, Implementation, and Assessment according to NIST 3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report According to 3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report, Risk Management Framework Development, Implementation, and Assessment: The Risk Management Framework (RMF) Development, Implementation, and Assessment Panel featured panelists from federal agencies, national laboratories, and academia, all of whom extensively utilize HPC to support operational research missions. The goal of the panel was to discuss how the NIST RMF supports their HPC cybersecurity programs and share valuable insights, best practices, future challenges and opportunities, and lessons learned. Two panelists presented their work on developing a security framework for scientific HPC facilities and supporting the implementation of RMF, and a moderated discussion to exchange ideas followed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, rmf, fips. General security reference material without sensitive content. Source: 3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report."}]}
{"id": "nist_01810", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cloud Computing Synopsis and Recommendations provide? (Section 95) jack a consumer's cloud resources. These risks apply to non-cloud environments as well; however in cloud computing, the reliance upon safe, end-user, client applications and networking may be greater. By relying on a consumer's browser for software application interfaces, the SaaS approach also raises a risk that, if a consumer visits a malicious Web site and the browser becomes contaminated, subsequent access to a SaaS application might compromise the consumer's data. Another risk is that data from different SaaS applications might be inadvertently mixed on consumer systems within consumer Web browsers. In Figure 9, for example, client C1 is concurrently running applications B and C. Depending on the data processed by B and C, it may be important to keep them separated. Additionally, although Figure 9 depicts applications B and C as being served by the same provider, in other scenarios they may originate from different organizations and require careful separation. Prominent Web browsers provide features, such as sandboxes to separate Web pages (and the interactive code that they contain) from one another, but sandboxing relies on Web browsers' robust resistance to attack. Unfortunately, as is evidenced by numerous competitions [Por10, Mar09], Web browsers are often vulnerable to malicious Web sites. One work-around to this issue is for consumers to use multiple browsers and to dedicate specific browsers to important SaaS applications and not to perform general-purpose Web surfing that may expose them to attack. Another work-around is for consumers to use a virtual desktop when connecting to cloud-hosted applications, which provides a secure, fully functional work platform that is governed by strict policies for limiting what can or cannot be accessed elsewhere, while connected to a cloud. The availability of a SaaS application depends on a reliable and continuously available network.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cloud Computing Synopsis and Recommendations."}]}
{"id": "nist_01811", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does PIV Data Model Test Guidelines say about 11.2.2.3 Verify expira tion dates consistency? (Part 2) According to PIV Data Model Test Guidelines, 11.2.2.3 Verify expira tion dates consistency: field value from (2.16.840.1.103.3.7.2.48.0)>> h the following parameters andle (2.16.840.1.10 \u2022 (IN) c \u2022 (OUT) data 4. Extract validity->notAfter->ut the certificate 5. Set OID := << CHUID ata wit 6. Call pivGetD \u2022 (IN) cardH \u2022 (IN) OID \u2022 (OUT) data | |--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Expected Result(s) | The expiration date of the digital signature certificate is not beyond the ration date of the CHUID i.e. the PIV card expi . |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_01812", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity of Genomic Data say about 4.1.1. U.S. Government Resources? (Part 1) According to Cybersecurity of Genomic Data, 4.1.1. U.S. Government Resources: 4.1.1. U.S. Government Resources For the U.S. Federal government, the Federal Information Security Management Act (FISMA 2002) served as the initial driver for cybersecurity risk management programs. The Office of Management and Budget (OMB) Circular A-130, 'Managing Federal Information as a Strategic Resource' requires executive agencies to leverage NIST guidance. The NIST RMF and the Federal Risk and Authorization Management Program (FedRAMP) are examples of risk management processes used by federal agencies. FISMA requires each federal agency to develop, document, and implement an agency-wide program to provide information security for the information and systems that support the operations and assets of the agency, including those provided or managed by another agency, contractor, or other sources. The Federal Information Security Modernization Act (FISMA 2014) [40] includes updates to address evolving cybersecurity concerns, reduce reporting burdens, strengthen continuous monitoring in systems, and reporting incidents. OMB Circular A-130 requires executive agencies within the federal government to plan for security, ensure that appropriate officials are assigned security responsibility, periodically review the security safeguards in their systems, and authorize system processing prior to operations and periodically, based on risk. The NIST RMF (defined in NIST SP 800-37 Revision 2) [37] provides a structured, yet flexible, process for managing cybersecurity and privacy risk that includes steps for preparation, system categorization, control selection, control implementation, control assessment, system authorization, and continuous monitoring. Risk management involves more than complying with regulations or technical controls and should be tailored to each organization's mission, regulatory environment, and risk tolerance. Table 1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, rmf, fips. General security reference material without sensitive content. Source: Cybersecurity of Genomic Data."}]}
{"id": "nist_01813", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography say about 5.8.2.2 Two-step Key-Derivation (Extraction-then-Expansion)? According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography, 5.8.2.2 Two-step Key-Derivation (Extraction-then-Expansion): For the two-step key-derivation method specified in SP 800-56C, FixedInfo is a bit string that contains component data fields such as a Label , Context information, and [ L ]2, where: - Label is a binary string that identifies the purpose of the derived keying material. The encoding method for the label is defined in a larger context, for example, in a protocol using the key-derivation method. - Context is a binary string containing information relating to the derived keying material. Section 5.8.2 provides a list of context-specific information that may be appropriate for the inclusion in this string. - [ L ]2 is a binary string that specifies the length (in bits) of the keying material to be derived. Different orderings of the component data fields of FixedInfo may be used, and one or more of the data fields may be combined (or omitted under certain circumstances). See Section 5 in SP 800-56C, and Sections 5, 7.4, 7.5 and 7.6 in SP 800-108 for details", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}]}
{"id": "nist_01814", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Framework for Multi-mode Authentication_ Overview and Implementation Guide say about Table of Contents? (Part 5) According to A Framework for Multi-mode Authentication_ Overview and Implementation Guide, Table of Contents: | | Appendix A - Handler Library..................................................................................................... | 26 | | Types......................................................................................................................................... | 26 | | Functions................................................................................................................................... | 26 | | Appendix B - Mandatory Access Control Settings ...................................................................... | 28 | | Hardware Related...................................................................................................................... | 28 | | Software Related....................................................................................................................... | 29 | | Appendix C - MAMGlobal Variables.........................................................................................", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: A Framework for Multi-mode Authentication_ Overview and Implementation Guide."}]}
{"id": "nist_01815", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for the Use of PIV Credentials in Facility Access provide? (Section 47) usion areas. It also ensures that credential validation is done in either case. Notes (4) and (5) add some flexibility in the case of discretionary access control among areas at the same impact level. The previous version of this document 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 both VIS and CHUID provide 'LITTLE or NO' confidence in the identity of the cardholder. Other authentication mechanisms other than the CHUID authentication mechanisms must be implemented. Newly purchased systems must support other authentication mechanisms (e.g., PKI-CAK) besides the CHUID mechanism. PIV authentication mechanisms can be mapped to perimeter crossings in many ways, provided that the requirements of this section are met. Figure 4-2 below provides some examples of mapping PIV authentication mechanisms to the perimeter crossings within a facility. Figure 4-2: Examples of Mapping PIV Authentication Mechanisms <!-- image --> Figure 4-2 illustrates five different examples. Other sequences of authentication mechanisms are possible. Refer to Appendix B for a complete list of possible combinations of PIV authentication mechanisms that could be used in federal agency facility environments. Each example below is labeled with a number and is described as follows: 1. The PKI-CAK, SYM-CAK and BIO authentication mechanisms provide one-factor authentication and can be used to cross from Unrestricted to Controlled areas. 2. The BIO-A, PKI-AUTH and OCC-AUTH authentication mechanisms provide two-factor authentication and can be used to cross into Limited areas. The example shows these authentication mechanisms to cross from Controlled to Limited areas. 3. Authentication in context can be leveraged if the 'Controlled, Limited, Exclusion' areas are nested.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, pki. Contains security framework guidance for authentication systems. Source: Guidelines for the Use of PIV Credentials in Facility Access."}]}
{"id": "nist_01816", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Technical Guide to Information Security Testing and Assessment? (Part 87) Control ES-1: t provides a snapshot of security at a given point in time, organizations may choose to require more frequent assessments. Important technical considerations can also help determine testing frequency. For example, if a system is believed to have several weaknesses, testing might be conducted sooner to confirm the presence of the weaknesses-or delayed until the weaknesses have been mitigated, to confirm they have been resolved. The timing used depends on the testing objective. Another consideration is whether any system or network activities required by the testing may impact the functionality or security of the environmentfor example, if a major upgrade is about to be conducted, testing might be delayed until the upgrade has been completed. Another example of a technical consideration is when an organization wants to identify rogue devices on wired networks. This could be accomplished using one or more techniques, such as performing network discovery through passive sniffing or active scanning, or reviewing data collected by network management software, network intrusion detection sensors, or other devices that routinely monitor network activity. If these monitoring devices are able to generate alerts as soon as a new, potentially rogue device is observed on the network, there may be little or no need to perform periodic testing for rogue devices because effective testing is continuously being performed. Organizations also need to carefully consider resource availability. Resources should first be identified for high-priority systems, after which lower-priority systems may be tested with less frequency and in descending order. If a gap exists between required and available resources, the organization may need to allocate additional resources and consider reducing the scope of its planned assessments.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technical Guide to Information Security Testing and Assessment."}]}
{"id": "nist_01817", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Domain Name System-Based Electronic Mail Security say about 3 Device Configuration and Operating Recommendations? According to Domain Name System-Based Electronic Mail Security, 3 Device Configuration and Operating Recommendations: This section provides additional information regarding for installing, configuring and operating Email and DNS security applications. Section 3.1 provides specific recommendations regarding certificate generation. Section 3.2 describes cryptographic operation and management by users on Outlook and Thunderbird. Section 3.3 describes setting up Exchange and Postfix MTAs to provide server-to-server encryption of email. Section 3.4 provides links to some tools and utilities that are useful in installing, configuring, provisioning, and maintaining DNS-based email security software. It is recommended that the installation, configuration, and operation of DNS servers be conducted in conformance to NIST SP 800-81-2, the Secure Domain Name System (DNS) Deployment Guide . Appendix D provides a checklist for management of secure DNSs. Installation, configuration, and operation of email applications should follow the recommendations of SP 800-177, Trustworthy Email .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_01818", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Use of ISO_IEC 24727 say about C O M P U T E R S E C U R I T Y? According to Use of ISO_IEC 24727, C O M P U T E R S E C U R I T Y: Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 August 2009 <!-- image --> U.S. Department of Commerce Gary Locke, Secretary National Institute of Standards and Technology Dr. Patrick D. Gallagher, Deputy Director", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Use of ISO_IEC 24727."}]}
{"id": "nist_01819", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Audience according to NIST Workshop Summary Report for \u201cCybersecurity Risks in Consumer Home Internet of Things (IoT) Products\u201d Virtual Workshop According to Workshop Summary Report for \u201cCybersecurity Risks in Consumer Home Internet of Things (IoT) Products\u201d Virtual Workshop, Audience: The main audiences for this publication are IoT device manufacturers, consumer organizations, and other stakeholders in the consumer home IoT market. 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Workshop Summary Report for \u201cCybersecurity Risks in Consumer Home Internet of Things (IoT) Products\u201d Virtual Workshop."}]}
{"id": "nist_01820", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Technical Guide to Information Security Testing and Assessment say about Executive Summary? (Part 1) According to Technical Guide to Information Security Testing and Assessment, Executive Summary: Executive Summary An information security assessment is the process of determining how effectively an entity being assessed (e.g., host, system, network, procedure, person-known as the assessment object ) meets specific security objectives. Three types of assessment methods can be used to accomplish this-testing, examination, and interviewing. Testing is the process of exercising one or more assessment objects under specified conditions to compare actual and expected behaviors. Examination is the process of checking, inspecting, reviewing, observing, studying, or analyzing one or more assessment objects to facilitate understanding, achieve clarification, or obtain evidence. Interviewing is the process of conducting discussions with individuals or groups within an organization to facilitate understanding, achieve clarification, or identify the location of evidence. Assessment results are used to support the determination of security control effectiveness over time. This document is a guide to the basic technical aspects of conducting information security assessments. It presents technical testing and examination methods and techniques that an organization might use as part of an assessment, and offers insights to assessors on their execution and the potential impact they may have on systems and networks. For an assessment to be successful and have a positive impact on the security posture of a system (and ultimately the entire organization), elements beyond the execution of testing and examination must support the technical process. Suggestions for these activities-including a robust planning process, root cause analysis, and tailored reporting-are also presented in this guide.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technical Guide to Information Security Testing and Assessment."}]}
{"id": "nist_01821", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report) say about APPENDIX H APPLICABLE GUIDANCE AS REPORTED BY CSPPs? (Part 7) 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), APPENDIX H APPLICABLE GUIDANCE AS REPORTED BY CSPPs: s IAW FIPS PUBS IBM Manuals IEEE 802.3 IG AUDITS INTERNATIONAL MOU'S IRM P 2100.5 IRS CODE (AS AMENDED) SECTS. 6103(1)01), 6103(P)(4), &amp; 6402(C) I TAR Immigration and Naturalization Act Info Tech. Security Manual National Finance Center provided guidance Info Resources Management Manual InteCom and VMX Manuals Internal Control Review Directive Internal Management Decision JANAP 128, Fed Personnel Manual 732 JDC -Congressional mandate executed by JDC JPL Computer &amp; Network Security G/LS/Handbook JPL SPI 4-19 JPL Software Management Std D-4000 JSC AIS Handbook &amp; AIS Security Plan JSC AISSP JSC Equipment Management Manual JSCM 1600C Security Manual KMI 2410. 4A LIMS Acceptance Test Plan l TU\u00a7 RFP LMI 2410.3A &amp; LMI 2410.9 LOCAL REGS FOR BUILDING Low Observables Security Classification Guide M204 STD MANUAL OF OPS &amp; ADMIN (MOA SECT 2, CHAPT 900) MASS Program Devel Plan D-5179 MCCC Devel Section Standard Practice D 1816-15 Mission OPS &amp; Data Sys Directorate Sys Mgmt Policy Document MMI 2410.6 MP-6 MSFC FORM 2683 OCT. 1982 MSFC Source Evaluation Board Guide Management of Fed Info Resources Memo 1/12/87 from AAAG for Adnin. Re Natl. Policy on Protection Mission Operations CorrpuSec Training Model Framework for Mgt. Control over AIS NAS10-10600, S.W.O., WB.B.S 1.4.1, BOC STD &amp; Procedures NASA ADP Risk Analysis G/L/NASA Conn Div Sec Proc Manual NASA AIS Program Handbook NASA Financial Management Manual NASA G/LS for certifying sensitive applications NASA G/LS for contingency planning NASA Handbook 1620.3B. NASA Info Resource Handbook 2410.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)."}]}
{"id": "nist_01822", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Personal Identity Verification (PIV) of Federal Employees and Contractors provide? (Section 49) y agency policy. Reissuance is the process by which a new PIV Card is issued to a cardholder without the need to repeat the entire identity proofing and registration process. The reissuance process may be used to replace a PIV Card that is nearing expiration, in the event of an employee status or attribute change, or to replace a PIV Card that has been compromised, lost, stolen, or damaged. The cardholder may also apply for reissuance of a PIV Card 15 A reasonable basis to believe occurs when a disinterested observer with knowledge of the same facts and circumstances would reasonably reach the same conclusion. if one or more logical credentials have been compromised. The identity proofing, registration, and issuance processes, as described in Section 2.7 and Section 2.8, SHALL be repeated if the issuer does not maintain a PIV enrollment record that includes biometric data records for the cardholder. If the expiration date of the new PIV Card is later than the expiration date of the old card, or if any data about the cardholder is being changed, the card issuer SHALL ensure that an adjudicative entity has authorized the issuance of the new PIV Card. The issuer SHALL ensure that the adjudicative entity has verified that there is a PIV eligibility determination in an authoritative record, such as the agency's IDMS or the Central Verification System (or successor). The issuer SHALL perform a biometric verification of the applicant to the biometric data records of the PIV enrollment record or to the biometric data records of the PIV Card using the BIO-A or OCC-AUTH authentication mechanisms. Minimum accuracy requirements for the biometric verification are specified in [SP 800-76].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Personal Identity Verification (PIV) of Federal Employees and Contractors."}]}
{"id": "nist_01823", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-20(02) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control AC-20(02): the use of organiza\ue000on-controlled portable storage devices by authorized individuals is restricted on external systems using <AC-20(02)_ODP restric\ue000ons>. POTENTIAL ASSESSMENT METHODS AND OBJECTS:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01824", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security of Personal Computer Systems_ A Management Guide say about 1.2.3. NATURE OF DATA BEING HANDLED? According to Security of Personal Computer Systems_ A Management Guide, 1.2.3. NATURE OF DATA BEING HANDLED: The information processed and stored on personal computer systems often can be more sensitive and accessible than that found on larger, multi-user systems. This is due primarily to the fact that the information on a given machine is often associated with one person or a well-defined group. This information is likely to be in the form of memoranda, reports, spreadsheets, or simple lists which are readily accessible using software tools familiar to all personal computer users. Finally, such data will tend to be in relatively \"final\" form, rather than being a mass of unanalyzed or unprocessed raw data. Al 1 of this may make the job of searching for specific information much easier than on a large systems with thousands of users and data files. The personal computer has been called the electronic equivalent of the desk or file cabinet. This is a useful analogy, since users of personal computers should have an inherent understanding of the nature and need to protect items in their desks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security of Personal Computer Systems_ A Management Guide."}]}
{"id": "nist_01825", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways provide? (Section 164) the public internet, a NAT rule needs to be created to allow the public IP address for the firewall to be used for external network traffic from internal network endpoints using private IP addresses. To create a NAT policy, perform the following steps: 1. Select Devices &gt; NAT. 2. Click New Policy &gt; Threat Defense NAT to create a new policy. Give the policy a name, optionally assign devices to it, and click Save . 3. Click Edit ( ) to edit the Threat Defense NAT policy. 4. Click Add Rule , then select Auto NAT Rule . 5. Under Interface Objects , leave any under Source Interface Objects , and place Outside\\_Zone under Destination Interface Objects . <!-- image --> 6. Under the Translation tab, select IPv4-Private-10.0.0.0-8 under Original Source , and under Translated Source select Destination Interface IP . 7. Click Ok , then click Save. 8. Click Deploy &gt; Select Device &gt; Deploy to deploy the NAT policy. <!-- image --> Cisco ISE is a network administration product that allows for enforcement of administrator-created security and access control policies. Cisco ISE captures attributes about devices, such as IP address, MAC address, and OS in order to enforce custom policies. Cisco ISE can be deployed as a standalone system or as a primary and secondary node for high-availability deployments. Our build utilized a single ISE VM node set in standalone deployment. The installation process for deploying a virtualized version of Cisco ISE requires you to download the OVA from and deploy it using VMware. Note that you will need a Cisco account to be able to download software from Cisco. Follow the steps here for deploying the Cisco ISE OVA template. After deploying the ISE OVA, launch the VM console from VMware. At the Cisco ISE CLI, type setup to start the ISE setup wizard. Use it to configure hostname and IP address information and to create admin credentials for the Web Admin portal.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_01826", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CP-09 in Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations? (Part 6) Control CP-09: 800-192 [24], IR 7874 [25], IR 7966 [26] ## 03.01.03 Information Flow Enforcement Enforce approved authorizations for controlling the flow of CUI within the system and between connected systems. ## DISCUSSION Information flow control regulates where CUI can transit within a system and between systems (in contrast to who is allowed to access the information) and without regard to subsequent accesses to that information. Flow control restrictions include keeping CUI from being transmitted in the clear to the internet, blocking external communications traffic that claims to be sourced from within the organization, restricting requests to the internet that are not from the internal web proxy server, and limiting CUI transfers between organizations based on data structures and content. Transferring CUI between organizations may require an agreement that specifies how the information flow is enforced (see 03.12.05). Transferring CUI between systems that represent different security domains with different security policies introduces the risk that such transfers violate one or more domain security policies. In such situations, information owners or stewards provide guidance at designated policy enforcement points between interconnected systems. Organizations consider mandating specific architectural solutions when required to enforce specific security policies. Enforcement includes prohibiting CUI transfers between interconnected systems (i.e., allowing information access only), employing hardware mechanisms to enforce one-way information flows, and implementing trustworthy regrading mechanisms to reassign security attributes and security labels. Organizations commonly use information flow control policies and enforcement mechanisms to control the flow of CUI between designated sources and destinations (e.g., networks, individuals, and devices) within systems and between interconnected systems.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_01827", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report on Lightweight Cryptography say about 2.3.1 Lightweight Block Ciphers? (Part 2) According to Report on Lightweight Cryptography, 2.3.1 Lightweight Block Ciphers: g around 2 32 blocks for some of the approved modes of operations. Depending on the algorithm, this may lead to attacks such as plaintext recovery or key recovery or with non-negligible probabilities. - -Smaller key sizes: Some lightweight block ciphers use small key sizes (less than 96 bits) for efficiency (e.g., 80-bit PRESENT). At the time of this writing, the minimum key size required by NIST is 112 bits [4]. - -Simpler rounds: The components and operations used in lightweight block ciphers are typically simpler than those of conventional block ciphers. In lightweight designs using Sboxes, 4-bit S-boxes are preferred over 8-bit S-boxes. This reduction in size results in significant area savings. For example, the 4-bit S-box used in PRESENT required 28 GEs, whereas the AES S-box required 395 GEs in [21]. For hardware-oriented designs, bit permutations (such as those used in PRESENT), or recursive MDS matrices (as in PHOTON [24] and LED [25]) may be preferred over complex linear layers. When rounds are simpler, they may need to be iterated more times to achieve security. - -Simpler key schedules: Complex key schedules increase the memory, latency and the power consumption of implementations; therefore, most of the lightweight block ciphers use simple key schedules that can generate sub-keys on the fly. This may enable attacks using related keys, weak keys, known keys or even chosen keys. Using a secure key derivation function (KDF) can prevent some of these attacks (for examples, see [11, 12, 15, 64]). - -Minimal implementations: There are several modes of operation and protocols that require only the encryption function of a block cipher. Some applications may require a device to only support one of the encryption or decryption operations. Implementing only the necessary functions of a cipher may require fewer resources than implementing the full cipher.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report on Lightweight Cryptography."}]}
{"id": "nist_01828", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cell Phone Forensic Tools_ an Overview and Analysis Update say about Motorola V300? (Part 1) According to Cell Phone Forensic Tools_ an Overview and Analysis Update, Motorola V300: Motorola V300 The following scenarios were conducted on an unlocked Motorola V300 GSM phone. Connectivity was established using Susteen's Motorola 2 Penguin cable. Connectivity and Retrieval: Proper authentication had to be provided to the password-protected device and the SIM card had to be inserted before contents were successfully acquired. Basic subscriber information (i.e. IMEI/ESN) was found and reported. Memory size is not reported. (Meet) PIM Applications: All active phone book entries were found and reported. Active calendar entries were found. Deleted PIM data was not found. (Below) Dialed/Received Phone Calls: Dialed/received phone calls were not found. (Miss) SMS/MMS Messaging: All active incoming and outgoing SMS messages were found and reported. Deleted SMS and MMS message data (i.e., images, sound bytes) were not found. (Below) Internet Messaging: No data was found. (Miss) Web Applications: Visited URLs, search queries performed, textual Web content and graphical images of visited sites were not found. (Miss) Text File Formats: Data content associated with text files (e.g., . txt , . doc , . pdf ) was not found. (Miss) Graphics Files Format: A connection could not be established allowing the transfer of graphic files (e.g., . bmp , . jpg , . gif . png , . tif ) to the Motorola V300. Images were created by using the picture camera. Active data was found and reported. (Meet). Compressed File Archive Formats: N.A. - The Motorola V300 does not support compressed archive files (e.g., . zip , . rar , . exe , . tgz ). (NA) Misnamed Files: N.A. - The Motorola V300 does not support misnamed files (e.g., . txt file renamed with a . dll extension). (NA) Peripheral Memory Cards: N.A. - The Motorola V300 does not allow for removable media. (NA) Acquisition Consistency: N.A. - SecureView does not provide an internal hashing algorithm for individual files or overall phone acquisition.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Cell Phone Forensic Tools_ an Overview and Analysis Update."}]}
{"id": "nist_01829", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Technical Guide to Information Security Testing and Assessment say about Appendix E-Resources? (Part 2) According to Technical Guide to Information Security Testing and Assessment, Appendix E-Resources: ation. Table E-1 contains a list of NIST documents that complement this guide, and Table E-2 provides a list of online resources that organizations may reference for additional information. Table E-1. Related NIST Documents 48 | NIST Document | URL | |------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| | SP 800-30, Risk Management Guide for Information Technology Systems | | | SP 800-40 Version 2.0, Creating a Patch and Vulnerability Management Program | | | SP 800-53 Revision 2, Recommended Security Controls for Federal Information Systems | final.pdf | | SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems | sz.pdf | | SP 800-64 Revision 1, Security Considerations in the Information System Development Life Cycle | | | SP 800-84, Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities | http://csrc.nist.gov/publications/nistpubs/800-84/SP800-84.pdf | | SP 800-92, Guide to Computer Security Log Management | http://csrc.nist.gov/publications/nistpubs/800-92/SP800-92.pdf | | SP 800-94, Guide to Intrusion Detection and Prevention Systems (IDPS) | http://csrc.nist.gov/publications/nistpubs/800-94/SP800-94.pdf | Table E-2.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Technical Guide to Information Security Testing and Assessment."}]}
{"id": "nist_01830", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Service Mesh Proxy Models for Cloud-Native Applications provide? (Section 33) gated based on the degree of isolation of the host (i.e., container versus micro-VM versus VM). The likelihood of exploiting a shared L7 ingress or egress gateway is the same across all architectures. Threat Description : Client libraries are not updated frequently or consistently across the estate of microservices, leading to potential vulnerabilities and weaknesses that can be exploited. Proxy Function Impacted : The proxy's infrastructure code is decoupled from its application code. Impact Score = 1 : The mesh infrastructure is separate from the application itself and, therefore, not directly impacted by application vulnerabilities. Instead, a compromised application would use the functioning mesh to hijack the application's identity. Some application vulnerabilities can be mitigated via policies enforced by the mesh (e.g., mesh-enforced web application firewall (WAF) policy can help mitigate an application vulnerability like Log4j while the organization is patching applications). Likelihood Score = 1 : The likelihood is the same, regardless of architecture. Threat Description : There is a conventional DoS threat. Proxy Function Impacted : Because the proxy is a per app instance, a DoS needs to be executed per app. Because the proxy shares resources with the application, a DoS on the mesh data plane directly competes for resources with the app instance itself. The overall blast radius of the DoS is as strong as the underlying isolation mechanism that protects workloads (i.e., pods) from each other (e.g., VMs, micro-VMs, containers). Impact Score = 1 : There is a single instance of a single application. Likelihood Score = 1 : L4 and L7 code may be exploited. However, the attack must be executed across each instance of the target. There is not a central resource to target to achieve a DoS other than a shared ingress gateway that is identical across all architectures under discussion.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Service Mesh Proxy Models for Cloud-Native Applications."}]}
{"id": "nist_01831", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Derived Personal Identity Verification (PIV) Credentials provide? (Section 12) Technical Requirements....................................................................................................................10 | | | 3.1 | CERTIFICATE POLICIES ............................................................................................................................10 | CERTIFICATE POLICIES ............................................................................................................................10 | | | 3.2 | CRYPTOGRAPHIC SPECIFICATIONS ...........................................................................................................10 | CRYPTOGRAPHIC SPECIFICATIONS ...........................................................................................................10 | | | 3.3 | CRYPTOGRAPHIC TOKEN TYPES ..............................................................................................................10 | CRYPTOGRAPHIC TOKEN TYPES ..............................................................................................................10 | | | | 3.3.1 3.3.2 | Removable (Non-Embedded) Hardware Cryptographic Tokens ..............................................11 | | | 3.4 | Embedded Cryptographic Tokens.............................................................................................12 ACTIVATION DATA ..................................................................................................................................13 | Embedded Cryptographic Tokens.............................................................................................12 ACTIVATION DATA ..................................................................................................................................13 | | | List of Appendices | List of Appendices | List of Appendices | List of Appendices | | Appendix A-Digital Signature and Key Management Keys (Informative)......................................15 | Appendix A-Digital Signature and Key Management Keys (Informative)......................................15 | Appendix A-Digital Signature and Key Management Keys (Informative)......................................15 | | | Appendix B-Data Model and Interfaces for Removable (Non-Embedded) Hardware | Appendix B-Data Model and Interfaces for Removable (Non-Embedded) Hardware | Appendix B-Data Model and Interfaces for Removable (Non-Embedded) Hardware | Appendix B-Data Model and Interfaces for Removable (Non-Embedded) Hardware | | Cryptographic | Tokens (Normative)........................................................................................................16 | Tokens (Normative)........................................................................................................16 | ........................................................16 | | B.1 DERIVED | B.1.1 | PIV APPLICATION DATA MODEL AND REPRESENTATION Derived PIV Application Identifier...........................................................................................16 | | | | B.1.2 | Derived PIV Application Data Model Elements.......................................................................16 |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, token. Contains security framework guidance for authentication systems. Source: Guidelines for Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_01832", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does The Common Vulnerability Scoring System (CVSS) and its Applicability to Federal Agency Systems say about 2.2 Temporal Metrics? According to The Common Vulnerability Scoring System (CVSS) and its Applicability to Federal Agency Systems, 2.2 Temporal Metrics: The threat posed by a vulnerability may change over time. Three such factors that CVSS captures are: confirmation of the technical details of a vulnerability, the remediation status of the vulnerability, and the availability of exploit code or techniques. Since temporal metrics are optional they each include a metric value that has no effect on the score. This value is used when the user feels the particular metric does not apply and wishes to 'skip over' it.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: The Common Vulnerability Scoring System (CVSS) and its Applicability to Federal Agency Systems."}]}
{"id": "nist_01833", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control MA-04 in Assessing Security and Privacy Controls in Information Systems and Organizations? Control MA-04: NONLOCAL MAINTENANCE ASSESSMENT OBJECTIVE: Determine if:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01834", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Service Mesh Proxy Models for Cloud-Native Applications say about 5.1.6. Outdated Client Libraries in Applications (TR-6)? According to Service Mesh Proxy Models for Cloud-Native Applications, 5.1.6. Outdated Client Libraries in Applications (TR-6): Threat Description : Client libraries are not updated frequently or consistently across the estate of microservices, leading to potential vulnerabilities and weaknesses that can be exploited. Proxy Function Impacted : The proxy's infrastructure code is decoupled from its application code. Impact Score = 1 : The mesh infrastructure is separate from the application itself and, therefore, not directly impacted by application vulnerabilities. Instead, a compromised application would use the functioning mesh to hijack the application's identity. Some application vulnerabilities can be mitigated via policies enforced by the mesh (e.g., mesh-enforced web application firewall (WAF) policy can help mitigate an application vulnerability like Log4j while the organization is patching applications). Likelihood Score = 1 : The likelihood is the same, regardless of architecture.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Service Mesh Proxy Models for Cloud-Native Applications."}]}
{"id": "nist_01835", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2006 Annual Report say about Overview? (Part 2) According to Computer Security Division 2006 Annual Report, Overview: and outreach programs. Activities in this area have historically, and continue to, involve large amounts of collaboration and the facilitation of relationships with other entities. Federal agencies that have collaborated recently with these activities are the Department of State, the Department of Commerce, the Department of Defense, the General Services Administration, the National Aeronautics and Space Administration, the National Security Agency, the Department of Energy, the U.S. Office of Management and Budget, the Social Security Administration, the United States Postal Service, the Department of Veterans Affairs, the Federal Aviation Administration, and NIST's National Voluntary Laboratory Accreditation Program. The list of industry entities that have worked with us in this area is long and includes the American National Standards Institute (ANSI), Oracle, Cisco Systems, Lucent Technologies, Microsoft Corporation, International Business Machines (IBM), VISA, MasterCard, Computer Associates, RSA Security, Research in Motion, Sun Microsystems, Network Associates, Entrust, and Fortress Technologies. The Division also has collaborated at the global level with Canada, the United Kingdom, France, Germany, India, Japan, and Korea in this area.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2006 Annual Report."}]}
{"id": "nist_01836", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Information Security Handbook_ A Guide for Managers provide? (Section 1) NIST Special Publication 800-100 <!-- image --> Recommendations of the National Institute of Standards and Technology Pauline Bowen Joan Hash Mark Wilson Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 <!-- image --> Carlos M. Gutierrez, Secretary Robert Cresanti, Under Secretary of Commerce for Technology William Jeffrey, Director The 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. This document has been developed by the National Institute of Standards and Technology (NIST) in furtherance of its statutory responsibilities under the Federal Information Security Management Act (FISMA) of 2002, Public Law 107-347. NIST is responsible for developing standards and guidelines, including minimum requirements, and for providing adequate information security for all agency operations and assets, but such standards and guidelines shall not apply to national security systems.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_01837", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Key Notarization System for Computer Networks provide? (Section 12) to every encrypted password stored in system memory. Each user is expected to manage the encrypted keys which belong to him, but he will not know any clear keys. Yet, key encryption is not sufficient. A method is required to protect against key substitution and to insure that each user correctly identifies the user with whom he is communicating. The KNF contains a DES encryption device. It will have a control microprocessor and memory to implement commands and data transfers. The KNF must also store the unencrypted interchange keys and the states of active users. An active state consists of a user identifier along with an initialization vector and an unencrypted data key for both transmitting and receiving data. A user is act ive as soon as his identifier is loaded into active user memory in the KNF. He may then proceed to load the rest of his state. The KNF contains a key generator which is capable of generating unpredictable keys. At any time a user should be able to predict the next key to be generated with only a 1/ (2**56) probability of success where 2**56 is two raised to the 56'th power. One possible key generator is proposed in the Appendix. Once the 56-bit keys are generated the proper parity Is determined and the entire 64-bit key is encrypted before it is returned to the host. Thus, no clear keys are known outside the KNF . The key generator is also used to generate 64-bit initialization vectors which initialize the DBS cryptoal gor i thm . Since the KNF contains clear keys, the encryption algorithm, the commands program, and the key generator, it must be physically protected. Cryptographic facilities containing a single master key are used in Ehrsam, et al [4] to perform encryption and execute key management commands. Our key notarization facilities hold several keys and the key generator. They employ a different key hierarchy, a different set of commands, and are the enforcers of key notarization.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: A Key Notarization System for Computer Networks."}]}
{"id": "nist_01838", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.1.6 Retrieval Time according to NIST PIV Card to Reader Interoperability Guidelines According to PIV Card to Reader Interoperability Guidelines, 2.1.6 Retrieval Time: Retrieval time 1 for 12.5 kilobytes (KB) of data through the contact interface of the reader shall not exceed 2.0 seconds.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Card to Reader Interoperability Guidelines."}]}
{"id": "nist_01839", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Primary Responsibility according to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy? Primary Responsibility: System Owner; Common Control Provider; Senior Agency Information Security Officer; Senior Agency Official for Privacy.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, fips, security control. General security reference material without sensitive content. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_01840", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain \u00b7 Safeguard sensitive information from disclosure to otfiers. according to NIST Computer Users' Guide to the Protection of Information Resources According to Computer Users' Guide to the Protection of Information Resources, \u00b7 Safeguard sensitive information from disclosure to otfiers.: People often forget to lock up sensitive reports and computer media containing sensitive data when they leave their work areas. Information carelessly left on top of desks and in unlocked storage can be casually observed, or deliberately stolen. Every employee who works with sensitive information should have lockable space available for storage when information is not in use. If you aren't sure what infor- mation should be locked up or what locked storage is available, ask your manager. While working, be aware of the visibility of data on your personal computer or terminal display screen. You may need to reposition equipment or furniture to eliminate over-the-shoulder viewing. Be especially careful near windows and in public areas. Label all sensitive diskettes and other computer media to alert other employees of the need to be especially careful. When no longer needed, sensitive information should be deleted or discarded in such a way that unauthorized individuals cannot recover the data. Printed reports should be finely shredded, while data on magnetic media should be overwritten. Files that are merely deleted are not really erased and Ccui still be recovered.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Users' Guide to the Protection of Information Resources."}]}
{"id": "nist_01841", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DS-2 in Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)? (Part 66) Control DS-2: i): [mud@localhost ~]$ wget 192.168.20.222 --2019-07-24 15:30:01-- / Connecting to 192.168.20.222:80... connected. HTTP request sent, awaiting response... 200 OK Length: 10701 (10K) [text/html] Saving to: \u2018index.html\u2019 100%[======================================>] 10,701 --.-K/s in 0s 2019-07-24 15:30:01 (139 MB/s) - \u2018index.html\u2019 saved [10701/10701] Procedure 3 (from pi to laptop): (unapproved): --2019-07-10 17:37:09-- Connecting to 192.168.20.238:80... failed: Connection refused. Procedure 4 (from pi to local hosts): (approved): --2019-07-10 19:02:34-- Connecting to 192.168.20.110:443... connected. HTTP request sent, awaiting response... 200 OK Length: 10701 (10K) [text/html] Saving to: \u2018index.html.28\u2019 0K .......... 100% 11.2M=0.001s NIST SP 1800-15D: Securing Small-Business and Home Internet of Things Devices 159 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Test Case Field Description 2019-07-10 19:02:34 (11.2 MB/s) - \u2018index.html.28\u2019 saved [10701/10701] (approved): --2019-07-10 19:00:10-- Connecting to 192.168.20.232:80... connected. HTTP request sent, awaiting response... 200 OK Length: 277 Saving to: \u2018index.html.14\u2019 0K 100% 10.9M=0s 2019-07-10 19:00:10 (10.9 MB/s) - \u2018index.html.14\u2019 saved [277/277] (approved): --2019-07-10 18:59:40-- Connecting to 192.168.20.117:80... connected. HTTP request sent, awaiting response... 200 OK Length: 10701 (10K) [text/html] Saving to: \u2018index.html.12\u2019 0K ..........", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_01842", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-1 in Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers? (Part 124) Control CM-1: ctions document the software, hardware, and network requirements for Magento Open Source 2.1.X. ## 2.2.2.1 Software Requirements For this implementation, Magento was installed on a CentOS 7.0 server. Magento Open Source developer's documentation states that Magento can operate on Linux operating systems, such as these: - \uf0a7 Red Hat Enterprise Linux - \uf0a7 CentOS - \uf0a7 Ubuntu - \uf0a7 Debian Magento Open Source 2.1.X requires the following installations: - \uf0a7 Web Server: Apache 2.2 or 2.4 or NGINX 1.X - \uf0a7 Database: MySQL 5.6, MariaDB, Percona, or other binary-compatible MySQL technologies - \uf0a7 Hypertext Preprocessor (PHP): 7.0.2, 7.0.4, 7.0.6-7.0.X, or 7.1.X - \uf0a7 Secure Sockets Layer (SSL) - \uf0a7 Mail Server: Redis 3.0, Varnish 3.5, memcached See Magento's developer's documentation for additional details and download links: https://devdocs.magento.com/guides/v2.1/install-gde/system-requirements-tech.html. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ ## 2.2.2.2 Hardware Requirements Magento requires installing Magento Open Source on a server with at least 2 GB of RAM. ## 2.2.3 Magento Preinstallation Magento requires the Linux, Apache, MySQL, PHP (LAMP) software stack. This section describes the process of installing and configuring the LAMP software stack that uses versions compatible with Magento. 1. Open a terminal window, and enter the following command to log in as root: sudo su - a. After entering the command, you will be prompted to enter the password for the current user. 2. To install wget from the terminal, enter the following command: <!-- image --> yum install wget \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ <!-- image --> 3.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_01843", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Guidance for First Responder Mobile and Wearable Devices provide? (Section 89) ing by remotely logging into the DUT. Most mobile devices do not allow authenticated scans without root account access, which is often restricted or prohibited by the manufacturer or service provider. Like Test 6, all network ports should be analyzed to determine a device's integrity. Guidance: Like guidance in Test 6, devices under a common administration should be routinely scanned over a managed local network using for potential network vulnerabilities. An MDM solution and mobile management policy should be implemented to ensure periotic scanning. Only applications required for mission-critical operations should be present on the device. Nonessential applications should be removed to ensure no external network connections can be made to the device. Authenticated scans are typically performed on devices running an MDM and an associated scanner plugin. The scanner application works in conjunction with the MDM application to provide detailed analysis of device applications and patches. Devices that cannot be scanned or are scanned using unauthenticated methods should have an MTD installed and scheduled to run daily. For more information on MDM implementation, consult NIST SPECIAL PUBLICATION 1800-4, 'Mobile Device Security Cloud and Hybrid Builds.' This publication includes detailed procedures on how to architect enterprise-class protection for mobile devices accessing corporate resources. [27] Benefits: External vulnerability scans allow the user to determine if the mobile device is exploitable. When possible, the scanning software will attempt to determine OS type, hardware platform, exploitable applications, services and exploit unpatched systems. Security Objective(s) : Mobile device confidentiality Test Description: Device confidentiality and autonomy can be maintained using MAC address randomization.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Security Guidance for First Responder Mobile and Wearable Devices."}]}
{"id": "nist_01844", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations say about PM-13 SECURITY AND PRIVACY WORKFORCE? According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, PM-13 SECURITY AND PRIVACY WORKFORCE: Supplemental C-SCRM Guidance: Security and privacy workforce development and improvement should ensure that relevant C-SCRM topics are integrated into the content and initiatives produced by the program. Section 2 provides information on C-SCRM roles and responsibilities. NIST SP 800-161 can be used as a source of topics and activities to include in the security and privacy workforce program. Level(s): 1, 2", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_01845", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2008 Annual Report provide? (Section 56) We expect to issue an additional publication, SP 800-56B, Recommendation for Pair-Wise Key Establishment Schemes Using Integer Factorization Cryptography (e.g., RSA) for public review in FY2009. Wireless Local Area Network (LAN) and Metropolitan Area Network (MAN) technologies are being widely adopted by government agencies. While wireless technologies can provide connections for mobile users, wireless devices and networks are also vulnerable to various attacks. The Institute of Electrical and Electronics Engineers (IEEE), the Internet Engineering Task Force (IETF), and other industry standards bodies have developed security protocols for wireless networks and communications. A new feature for many wireless services is a fast 'handoff' or transition between different access points. Fast handoff poses a new challenge for cryptographic key management. To make the handoff truly fast, cryptographic keys are derived and distributed among different access points so that whenever a mobile station is roaming to a different access point, the keys are ready for a secure connection. A key hierarchy is derived from a master key for the fast handoff. The primary security concerns relate to key establishment among multiple key holders. This is further complicated because, unlike a cellular system, a mobile LAN or MAN station determines when to make a transition from one access point to another. This makes it more difficult for the network to coordinate key establishment among multiple parties in a secure manner. In 2008, we completed draft NIST SP 800-108, Recommendation for Key Derivation Using Pseudorandom Functions, and requested public comments on the draft. The draft of SP 800-108 specifies three families of key derivation functions using pseudorandom functions. They incorporate the most commonly used key derivation functions in wireless applications. We expect to publish SP 800-108 in FY2009 after the public comments are resolved.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2008 Annual Report."}]}
{"id": "nist_01846", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is https according to Guide to Operational Technology (OT) Security? https: //www.cisa.gov/resources-tools/resources/emergency-services-sector-cybersecurity-", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_01847", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2004 Annual Report say about AUTHORIZATION MANAGEMENT AND ADVANCED ACCESS CONTROL MODELS? (Part 2) According to Computer Security Division 2004 Annual Report, AUTHORIZATION MANAGEMENT AND ADVANCED ACCESS CONTROL MODELS: cess control policies directly impacts its ability to execute its mission - by determining the degree to which its volumes of resources may be protected and shared among its user community. Whether in regard to the Government's war on terror or a company's formation of a strategic partnership, the focus on sharing information is becoming increasingly acute. Unfortunately, when it comes to access control mechanisms, one size does not fit all. At the request and support of the Department of Homeland Security (DHS), CSD has initiated a project in pursuit of a standardized access control mechanism that is general enough to configure and enforce any attribute-based access control policy, referred to as the Policy Machine (PM). A core feature is the PM's ability to configure and enforce arbitrary attribute-based access control policies and its ability to protect resources under multiple instances of these policies. It is not our intent to devise a completely new access control mechanism, but instead to redefine, implement and transfer to industry an access control mechanism that we believe includes abstractions, properties and functions common to most if not all access control mechanisms. If successful, we believe that the PM will benefit organizations in a number of ways including: - Increased user productivity through the increased sharing of resources - Decreased insider crime through the ability to enforce organization-specific access control policies - Increased administrator productivity through better interfaces in configuring access control policy - Increased cooperation among organizations through the potential for the coordination and exchange of interoperability of access control data Development of the PM has been ongoing during the last year and will continue in the coming year. Contact: Mr. David Ferraiolo (301) 975-3046 david.ferraiolo@nist.gov", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Computer Security Division 2004 Annual Report."}]}
{"id": "nist_01848", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.2 provide? (Section 98) r a benchmark. While a benchmark can be tailored in place by setting properties of various elements, &lt;xccdf:Profile&gt; elements allow one benchmark document to hold several independent tailorings. The &lt;xccdf:select&gt; element children of the &lt;xccdf:Profile&gt; affect which &lt;xccdf:Group&gt; and &lt;xccdf:Rule&gt; elements are selected for processing when the &lt;xccdf:Profile&gt; is in effect. The &lt;xccdf:refine-rule&gt; element allows modification of properties in &lt;xccdf:Group&gt; and &lt;xccdf:Rule&gt; elements, while the &lt;xccdf:refine-value&gt; element allows modification of &lt;xccdf:Value&gt; properties, including selection of the effective value. Finally, &lt;xccdf:set-value&gt; and &lt;xccdf:setcomplex-value&gt; allow an &lt;xccdf:Value&gt; element's value to be set directly to a simple or complex setting, respectively. The example below shows a simple &lt;xccdf:Profile&gt; . ``` <xccdf:Profile id=\"xccdf_org.example_profile_strict\" prohibitChanges=\"1\" extends=\"xccdf_org.example_profile_lenient\" note-tag=\"strict-tag\"> <xccdf:title>Strict Security Settings</xccdf:title> <xccdf:description> Strict lockdown rules and values, for hosts deployed to high-risk environments. </xccdf:description> <xccdf:set-value idref=\"xccdf_org.example_value_password-len\">10</xccdf:set-value> <xccdf:refine-value idref=\"xccdf_org.example_value_session-timeout\" selector=\"quick\"/> <xccdf:refine-rule idref=\"xccdf_org.example_value_session-auth-rule\" selector=\"harsh\"/> <xccdf:select idref=\"xccdf_org.example_value_password-len-rule\" selected=\"1\"/> <xccdf:select idref=\"xccdf_org.example_value_audit-cluster\" selected=\"1\"/> <xccdf:select idref=\"xccdf_org.example_value_telnet-disabled-rule\" selected=\"1\"/> <xccdf:select idref=\"xccdf_org.example_value_telnet-settings-cluster\" selected=\"0\"/> </xccdf:Profile> ``` An &lt;xccdf:Profile&gt; MAY extend another &lt;xccdf:Profile&gt; in the same benchmark by using the @extends attribute.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.2."}]}
{"id": "nist_01849", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-2 in Computer Security Division 2004 Annual Report? (Part 17) Control HA-2: tity Verification (PIV) for Federal Employees and Contractors . FIPS 201 will be signed by the Secretary of Commerce by February 25, 2005, in order to comply with the deadlines set out in HSPD-12. This standard will define the technical requirements for an identity credential that will be: - Issued based on sound criteria for verifying an individual employee's identity - Resistant to identity fraud, tampering, counterfeiting and terrorist exploitation - Rapidly authenticated electronically - Issued only by providers whose reliability has been established by an official accreditation process - Applicable to all government organizations and contractors - Used to grant access to Federally-controlled facilities and information systems - Flexible enough for agencies to select the appropriate security level for each application by providing graduated criteria from least secure to most secure - Not applicable to identification associated with national security systems - Implemented in a manner that protects citizens' privacy The FIPS 201 standard will establish requirements for the following processes and the supporting infrastructure: - Identity Token (ID card) Application by Person - this establishes the requirements for an application for the standardized identification. - Identity Source Document Request by Organization - every Federal organization is different but its security needs can be grouped into one of four assurance levels. Depending on which assurance level is needed, a given agency will require specific forms of documentation in order to verify the identity of the potential grantee of the ID Card. - Identity Registration and ID Card Issuance by Issuer - after a person's legal identity has been authenticated that person needs to be registered with the PIV system and that person's card needs to be issued. The PIV standard provides specifications for this process.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: Computer Security Division 2004 Annual Report."}]}
{"id": "nist_01850", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control provide? (Section 173) | https://www.swpc.noaa.gov/ Presidential Policy Directive 21 (PPD-21) (2013) Presidential Policy Directive - Critical Infrastructure Security and Resilience. (The White House, Washington, DC). Available at office/2013/02/12/presidential-policy-directive-critical-infrastructure- security-and-resil | | [RB-2012] | Rodriguez Bejarano JM, Yun A, De La Cuesta B (2012) 'Security in IP satellite networks: COMSEC and TRANSEC integration aspects.' 2012 6th Advanced Satellite Multimedia Systems Conference (ASMS) and 12th Signal Processing for Space Communications Workshop (SPSC), pp. 281- 288. Available at https://ieeexplore.ieee.org/document/6333089 | Satellite Ground Segment: Applying the CSF to Satellite Command and Control | [RTCA-DO-235] | Radio Technical Commission for Aeronautics (2008) RTCA DO-235A Assessment of Radio Frequency Interference Relevant to the GNSS L1 Frequency Band . (RTCA, Washington, DC). Available at | |----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [Space-ISAC] [SPD-5] | https://s-isac.org/ Space Policy Directive 5 (SPD-5) (2020) Memorandum on Space Policy Directive-5-Cybersecurity Principles for Space Systems. (The White House, Washington, DC), September 4, 2020.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, csf, fips. General security reference material without sensitive content. Source: Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control."}]}
{"id": "nist_01851", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Study of OSI Key Management say about B1.2 SECURITY REGISTER MODULES? According to A Study of OSI Key Management, B1.2 SECURITY REGISTER MODULES: ``` SecurityRegister {iso organisation security(I) modules(I) securityRegisier(I)} DEHNinONS ::= BEGIN EXPORTS keyExchMethods, integrityAlgs, confidentialityAlgs, securityLevels, securityLabels, signatureAlgs, rekeyingMethods; - Dummy definition. IMPORTS security FROM Register {iso organisation security(1) modules(l)}; keyExchMethods integrityAlgs confidentialityAlgs securityLevels securityLabels signatureAlgs rekeyingMethods OBJECT IDENTIFIER OBJECT IDENTIFIER OBJECT IDENTIFIER OBJECT IDENTIFIER OBJECT IDENTIFIER OBJECT IDENTIFIER OBJECT IDENTIFIER = {security 1} = (security 2} = (security 3} = (security 4} = ( security 5 = (security 6} = ( security 7 ``` END - of SecurityRegister", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of OSI Key Management."}]}
{"id": "nist_01852", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-224 in Secure Hash Standard (SHS)? (Part 6) Control HA-224: | | | | | | FUNCTIONS AND CONSTANTS...................................................................................................................10 | FUNCTIONS AND CONSTANTS...................................................................................................................10 | | | | 4.1 | 4.1 | | | | FUNCTIONS ......................................................................................................................................10 | FUNCTIONS ......................................................................................................................................10 | | | | 4.1.1 | SHA-1 Functions ................................................................................................................10 | | | | 4.1.2 | SHA-224 and SHA-256 Functions......................................................................................10 | | | | 4.1.3 | SHA-384, SHA-512, SHA-512/224 and SHA-512/256 Functions.......................................11 | | | | 4.2 | CONSTANTS .....................................................................................................................................11 | | | | 4.2.1 | SHA-1 Constants ................................................................................................................11 | | | | 4.2.2 | SHA-224 and SHA-256 Constants......................................................................................11 | | | | 4.2.3 | SHA-384, SHA-512, SHA-512/224 and SHA-512/256 Constants.......................................12 | | | 5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Hash Standard (SHS)."}]}
{"id": "nist_01853", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain \u8b1d\u8f9e according to NIST Application Container Security Guide According to Application Container Security Guide, \u8b1d\u8f9e: \u8457\u8005\u306f\u3001\u672c\u6587\u66f8\u306e\u30c9\u30e9\u30d5\u30c8\u7248\u3092\u30ec\u30d3\u30e5\u30fc\u3057\u3001\u7b56\u5b9a\u4e2d\u306b\u6280\u8853\u7684\u306a\u5185\u5bb9\u306b\u8ca2\u732e\u3057\u3066\u304f\u308c\u305f\u540c\u50da\u3001\u7279\u306b Intel Corporation \u306e Raghuram Yeluri \u6c0f\u3001 Cisco Systems, Inc. \u306e Paul Cichonski \u6c0f\u3001 NIST \u306e Michael Bartock \u6c0f\u3068 Jeffrey Cichonski \u6c0f\u3001 Edward Siewick \u6c0f\u306b\u611f\u8b1d\u306e\u610f\u3092\u8868\u3059\u308b\u3002\u307e\u305f\u3001 Docker \u3001 Motorola Solutions \u3001 StackRox \u3001\u7c73\u56fd\u79fb\u6c11\u5c40\uff08 USCIS \uff09 \u3001\u7c73 \u56fd\u9678\u8ecd\u306a\u3069\u3001\u30d1\u30d6\u30ea\u30c3\u30af\u30b3\u30e1\u30f3\u30c8\u671f\u9593\u4e2d\u306b\u30d5\u30a3\u30fc\u30c9\u30d0\u30c3\u30af\u3092\u63d0\u4f9b\u3057\u3066\u304f\u308c\u305f\u7d44\u7e54\u306b\u3082\u611f\u8b1d\u3092\u8868\u3059\u308b\u3002", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Application Container Security Guide."}]}
{"id": "nist_01854", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992 say about Recommendations on Configuration Control? According to Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992, Recommendations on Configuration Control: Configuration control/management consists of a potpourri of activities, some of which may be system specific. In addition to general password management and file protection, it might include such activities as initializing newly installed systems by immediately setting a root password, checking for proper settings of file access to various system files, closing off some functions like ftp or rlogin, closing down some logical ports, closing known security holes, etc. This area was considered to be of high importance to overall security. Without it, as previously noted, it may be impossible to accomplish many of the other things. Automatic aids are available in support packages such as COPS and Security Profile Inspector (SPI) and their use is strongly recommended. Based on security configuration specifications, the latter package goes through a check of the system and constructs scripts that can be used as produced or can be modified to make the necessary configuration changes. These tools should be used by principal investigators and system administrators.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992."}]}
{"id": "nist_01855", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007 say about Record-Level Requirements and Assertions? (Part 152) According to Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007, Record-Level Requirements and Assertions: Otherwise, it | 2 | M | 14.010-JPEGB- JPEGL-VPS | IF {14.008} EQ '1' OR '2', THEN IF Present(JFIF Header) THEN {14.010} EQ {Vertical Density} | 3 | | | | indicates the vertical component of the | 2 | M | 14.010-JP2-JP2L- VPS | No Implementation | 4 | | | | pixel aspect ratio.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007."}]}
{"id": "nist_01856", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Framework for Designing Cryptographic Key Management Systems say about Appendix B: Glossary of Terms? (Part 12) According to A Framework for Designing Cryptographic Key Management Systems, Appendix B: Glossary of Terms: eceives and transmits data packets or establishes logical connections among a diverse set of communicating entities (usually supports both hardwired and wireless communication devices simultaneously). | |-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Scalability | The ability of a system to handle a growing amount of work in a capable manner or its ability to be enlarged to accommodate that growth. | | Scheme | An unambiguous specification of a set of transformations that is capable of providing a (cryptographic) service when properly implemented and maintained. A scheme is a higher-level construct than a primitive and a lower level construct than a protocol. | | Sector | A group of organizations (e.g., Federal agencies, private organizations, international consortia) that have common goals, standards, and requirements for a product, system, or service. | | Security Domain | A collection of entities, including their CKMS, in which each CKMS operates under the same security policy - known as the Domain Security Policy. | | Security Policy | The rules and requirements established by an organization that governs the acceptable use of its information and services, and the level and means for protecting the confidentiality, integrity, and availability of its information. | | Security Strength | A number associated with the amount of work (that is, the base 2 logarithm of the minimum number of operations) that is required to cryptanalyze a cryptographic algorithm or system. | | Semantics | The intended meaning of acceptable sentences of a language.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_01857", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case say about Data? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case, Data: 1. Access to sensitive data must be authorized by the Director of Operations. 2. Data must not be shared informally. When access to sensitive information is required, personnel can request access from the Director of Operations and should take all necessary steps to prevent unauthorized access. 3. The Director of Operations must immediately be notified in the event a device is lost containing sensitive data (e.g. mobiles, laptops, USB devices). 4. Encrypted portable media or secure protocols must be used while transporting or transferring sensitive company data. 5. Extra precautions must be taken by remotely-operating employees to ensure sensitive data is appropriately protected. 6. Physical copies of data should be stored in a secure location when not in use. 7. Personnel should ensure physical copies of sensitive data are not left unattended (e.g., on a printer or a desk). 8. Physical copies of sensitive data should be shredded or disposed in a secure manner when no longer required. Data types considered sensitive, proprietary, or containing trade secrets | Description | Digital Files | Physical Copies | Databases | |-------------------------------------|-----------------|-------------------|-------------| | PLC program code | \u2713 | | | | Chemical formulas | \u2713 | \u2713 | | | Quality Assurance Procedures | \u2713 | \u2713 | | | Operating manuals and documentation | \u2713 | \u2713 | | | Electrical diagrams | \u2713 | \u2713 | | | Network diagrams | \u2713 | \u2713 | | | Historical production data | \u2713 | | \u2713 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case."}]}
{"id": "nist_01858", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-002 in Guidelines for Smart Grid Cybersecurity? (Part 143) Control IP-002: information system component needs to be documented, listing the date, time, reason for removal, estimated date of reinstallation, and name personnel removing components. Requirement Enhancements 1. The organization maintains maintenance records for the smart grid information system that include: a. The date and time of maintenance; b. Name of the individual performing the maintenance; c. Name of escort, if necessary; d. A description of the maintenance performed; and e. A list of equipment removed or replaced (including identification numbers, if applicable). Additional Considerations A1. The organization employs automated mechanisms to schedule and document maintenance and repairs as required, producing up-to-date, accurate, complete, and available records of all maintenance and repair actions needed, in process, and completed. Impact Level Allocation Low: SG.MA-3 Moderate: SG.MA-3 High: SG.MA-3 (1) SG.MA-4 Maintenance Tools Category: Common Governance, Risk, and Compliance (GRC) Requirements Requirement The organization approves and monitors the use of smart grid information system maintenance tools. Supplemental Guidance The requirement addresses security-related issues when the hardware, firmware, and software are brought into the smart grid information system for diagnostic and repair actions. Requirement Enhancements None. Additional Considerations A1. A2. The organization requires approval from a management authority explicitly authorizing removal of equipment from the facility; The organization inspects all maintenance tools carried into a facility by maintenance personnel for obvious improper modifications; 155 A3. A4. The organization checks all media containing diagnostic and test programs for malicious code before the media are used in the smart grid information system; and The organization employs automated mechanisms to restrict the use of maintenance tools to authorized personnel only.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01859", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Test according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, Test: [SELECT FROM: mechanisms for implementing system auditing of auditable events; system audit capability]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_01860", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2013 Annual Report provide? (Section 72) es gained a greater understanding of the Risk Management Framework (RMF) and its practical application. Dr. Ron Ross discussed SP 800-53 Revision 4 and the fundamentals of continuous monitoring. Two afternoon panels discussed case studies regarding RMF and 'ongoing authorization.' The Forum plays a valuable role in helping NIST and other federal agencies to develop and maintain a strong, proactive stance in the identification and resolution of new strategic and tactical IT security issues as they emerge. The number of members on the email list has grown steadily and provides a valuable resource for federal security program managers. To join, email your name, affiliation, address, phone number, title, and confirmation that you are a federal employee to sec-forum@nist.gov. Mr. Kevin Stine Chair (301) 975-4483 kevin.stine@nist.gov <!-- image --> Ms. Peggy Himes Administration (301) 975-2489 peggy.himes@nist.gov The Federal Information Systems Security Educators' Association (FISSEA), founded in 1987, is an organization run by and for information systems security professionals to assist federal agencies in meeting their information systems security awareness, training, and education responsibilities. FISSEA strives to elevate the general level of information systems security knowledge for the Federal Government and the federal workforce. It also seeks to assist the professional development of its members. FISSEA membership is open to information systems security professionals, professional trainers and educators, and managers responsible for information systems security training programs in federal agencies, as well as contractors of these agencies and faculty members of accredited educational institutions who are involved in information security training and education.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Computer Security Division 2013 Annual Report."}]}
{"id": "nist_01861", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers say about CHALLENGE? According to Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers, CHALLENGE: Smart chip credit cards and terminals work together to protect in-store payments. The in-store security advances were introduced in 2015, and those have pushed malicious actors who possess stolen credit card data to perform payment card fraud online. This guide describes implementing stronger userauthentication techniques to reduce the risk of e-commerce fraud. The guide documents a system in which risk determines when to trigger MFA challenges to existing customers.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, mfa. Contains security framework guidance for authentication systems. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_01862", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Random Number Generation Using Deterministic Random Bit Generators provide? (Section 99) in Section 9.1: The instantiation of Hash\\_DRBG requires a call to the Instantiate\\_function specified in Section 9.1. Process step 9 of that function calls the instantiate algorithm in this section. The values of highest\\_supported\\_security\\_strength and min\\_length are provided in Table 2 of Section 10.1. The contents of the internal state are provided in Section 10.1.1.1. The instantiate algorithm: Let Hash\\_df be the hash derivation function specified in Section 10.3.1 using the selected hash function. The output block length ( outlen ), seed length ( seedlen ) and appropriate security\\_strengths for the implemented hash function are provided in Table 2 of Section 10.1. The following process or its equivalent shall be used as the instantiate algorithm for this DRBG mechanism (see step 9 of the instantiate process in Section 9.1). Hash\\_DRBG\\_Instantiate\\_algorithm ( entropy\\_input, nonce, personalization\\_string, security\\_strength ): 1. entropy\\_input : The string of bits obtained from the randomness source. 2. nonce : A string of bits as specified in Section 8.6.7. 3. personalization\\_string : The personalization string received from the consuming application. Note that the length of the personalization\\_string may be zero. 4. security\\_strength : The security strength for the instantiation. This parameter is optional for Hash\\_DRBG , since it is not used. 1. initial \\_ working\\_state : The initial values for V , C , and reseed\\_counter (see Section 10.1.1.1). 1. seed\\_material = entropy\\_input || nonce || personalization\\_string . 2. seed = Hash\\_df ( seed\\_material , seedlen ). 3. V = seed . 4. C = Hash\\_df ((0x00 || V ), seedlen ). Comment: Precede V with a byte of zeros. 5. reseed\\_counter = 1. 6. Return ( V , C , reseed\\_counter ). Notes for the reseed function specified in Section 9.2: The reseeding of a Hash\\_DRBG instantiation requires a call to the Reseed\\_function specified in Section 9.2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Number Generation Using Deterministic Random Bit Generators."}]}
{"id": "nist_01863", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Managing Information Security Risk_ Organization, Mission, and Information System View provide? (Section 126) n establishing such connections. Organizations may also determine that implementing effective safeguards and countermeasures (e.g., cross-domain solutions) is not practical in the given circumstances. Thus, the organizations decide to avoid the risk by eliminating the electronic or networked connections and employing an 'air gap' with a manual connection processes (e.g., data transfers by secondary storage devices). Risk mitigation, or risk reduction, is the appropriate risk response for that portion of risk that cannot be accepted, avoided, shared, or transferred. The alternatives to mitigate risk depend on: (i) the risk management tier and the scope \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ of risk response decisions assigned or delegated to organizational officials at that tier (defined by the organizational governance structures); and (ii) the organizational risk management strategy and associated risk response strategies. The means used by organizations to mitigate risk can involve a combination of risk response measures across the three tiers. For example, risk mitigation can include common security controls at Tier 1, process re-engineering at Tier 2, and/or new or enhanced management, operational, or technical safeguards or countermeasures (or some combination of all three) at Tier 3. Another example of a potential risk requiring mitigation can be illustrated when adversaries gain access to mobile devices (e.g., laptop computers or personal digital assistants) while users are traveling. Possible risk mitigation measures include, for example, organizational policies prohibiting transport of mobile devices to certain areas of the world or procedures for users to obtain a clean mobile device that is never allowed to connect to the organizational networks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Managing Information Security Risk_ Organization, Mission, and Information System View."}]}
{"id": "nist_01864", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-06(02) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control SI-06(02): SECURITY AND PRIVACY FUNCTION VERIFICATION | AUTOMATION SUPPORT FOR DISTRIBUTED TESTING ASSESSMENT OBJECTIVE: Determine if:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01865", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Quick Start Guide for Populating Mobile Test Devices say about 6 Text Messages? According to Quick Start Guide for Populating Mobile Test Devices, 6 Text Messages: Populating mobile devices with text messages requires two mobile devices. A sending device, and a target device. Text messages may be categorized as either Short Messages Service (SMS) or Enhanced Message Service (EMS) messages. SMS messages are solely textual based messages containing less than 160 characters. EMS messages are an extension of SMS and support text messages of 160 or more characters. Incoming messages are populated onto the target device by sending the message from a sending device. Outgoing messages are populated by sending a message from the target device to a secondary device. In addition to the text message, document phone numbers, date/time, and the status (i.e., read, unread, deleted). Note: Text messages are categorized with a status of either: Read, Unread, or Deleted. To establish messages with a status of read, open and observe the message on the screen. Messages with a status of Unread are accomplished by not reading/opening the message. Messages with a status of Deleted are accomplished by deleting a specific message after the phone has been entirely populated. Document Text Messages in Appendix B.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Quick Start Guide for Populating Mobile Test Devices."}]}
{"id": "nist_01866", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Introduction to Cybersecurity for Commercial Satellite Operations say about Conclusion? According to Introduction to Cybersecurity for Commercial Satellite Operations, Conclusion: NIST has provided this example to show how an organization could apply the steps of the Cybersecurity Framework to evaluate and address possible security risks. NIST recommends that organizations use the steps that best apply to their threat models, business cases, and risk tolerance. As the industry expands, NIST will continue to support the community through research products.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Introduction to Cybersecurity for Commercial Satellite Operations."}]}
{"id": "nist_01867", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Profile of the IoT Core Baseline for Consumer IoT Products provide? (Section 40) for the sector. Safety and privacy considerations are dynamic for consumer IoT products, though, owing to the fact that even in this specific sector, use cases for IoT products may vary significantly. There may be clear safety implications to a product and its operation, but this is not always the case. The same goes for privacy. This is exacerbated by the fact that different use cases may share broad safety and/or privacy considerations, but the specifics on their impacts and/or mitigations can be very different. This all means that the consumer profile's cybersecurity capabilities must broadly support a variety of use cases while taking care to not hinder these areas. 4. Cybersecurity practices of the customers (i.e., home consumers) that would be managing consumer IoT products will vary in definition and maturity. The unpredictable and ad hoc nature of customer risk mitigation for consumer IoT products highlight the need for broadly useful and generally recommended cybersecurity practices be reflected in the profile. 5. Additionally, an important cybersecurity need for this sector is usable cybersecurity capabilities that are implemented to require minimal/efficient customer set-up and interaction for use, since these customers will not have deep knowledge or resources to leverage if capabilities are not usable to them. 6. Finally, specific standards, solutions, implementations, or mitigations should be used as appropriate for an IoT product's functionality and use case. This means no single set of specific requirements can be applicable to all consumer IoT products. Therefore, the consumer profile describes IoT product-level cybersecurity guidelines in terms of outcomes to be achieved and supported by the product as a whole but may not apply to all IoT product components the same way. Some components may not be able, or need, to support all criteria.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Profile of the IoT Core Baseline for Consumer IoT Products."}]}
{"id": "nist_01868", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Engineering Trustworthy Secure Systems say about Table of Contents? (Part 7) According to Engineering Trustworthy Secure Systems, Table of Contents: | ............................................................................................65 | | C.3. | Distinguishing Requirements, Policy, and Mechanisms | ..........................................68 | | Appendix | D. Trustworthy Secure Design....................................................................70 | | | D.1. Design Approach for Trustworthy Systems | D.1. Design Approach for Trustworthy Systems | .............................................................70 | | D.2. | Design Considering Emergence..............................................................................73 | | |--------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| | D.3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_01869", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.4 Common Configuration Enumeration (CCE) according to NIST Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements According to Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements, 2.4 Common Configuration Enumeration (CCE): Definition: CCE is a format for describing system configuration issues to facilitate correlation of configuration data across multiple information sources and tools. 6 http://nvd.nist.gov 7 Version: 5 Specification: http://cce.mitre.org/ Dictionary: ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements."}]}
{"id": "nist_01870", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about Assessing Security Requirements for Controlled Unclassified Information? According to Assessing Security Requirements for Controlled Unclassified Information, Assessing Security Requirements for Controlled Unclassified Information: Ron Ross Victoria Pillitteri This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-171Ar3 <!-- image -->", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_01871", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.3.2 Key-Establishment Schemes according to NIST Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms According to Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms, 3.3.2 Key-Establishment Schemes: Asymmetric key-establishment schemes are used to set up keys to be used between communicating entities. A scheme is a set of transformations (i.e., cryptographic operations) that provide a cryptographic service -a key-establishment service, in this case; a scheme is used in a protocol that actually performs the communication needed for the key-establishment process. Two classes of asymmetric schemes have been approved that are based on hard mathematical problems: discrete-log-based schemes and integer factorization schemes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms."}]}
{"id": "nist_01872", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Conducting Risk Assessments say about Comments on this publication may be submitted to:? According to Guide for Conducting Risk Assessments, Comments on this publication may be submitted to:: National Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930 Electronic mail: sec-cert@nist.gov \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guide for Conducting Risk Assessments."}]}
{"id": "nist_01873", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity say about 5 Security Characteristic Analysis? According to Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity, 5 Security Characteristic Analysis: This section discusses the results of a security evaluation of the reference architecture shown in Figure 4-2 and how it supports the Cybersecurity Framework Subcategories that we identified and mapped in Table 3-1. The purpose of the security characteristic analysis is to understand the extent to which the project example solution meets its objective of demonstrating that information exchanges among DERs and electric distribution grid operations can be monitored and protected from certain cybersecurity compromises. In addition, it seeks to understand the security benefits and drawbacks of the example solution.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity."}]}
{"id": "nist_01874", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security in ISDN provide? (Section 90) error burst to one in 2^^, for most purposes a negligibly small number. The CRC-32 widely used in LANs, which allow longer packets, increasing the probability of two random errors in the same packet. LAPB is limited to an information field of only 260 bytes, and the CRC-16 is used with both LAPB and LAPD. Figure 26 - DES K-bit Output Feedback (OFB) Mode. <!-- image --> in 2^^ of a 64 bit error burst not being detected by the FCS. The nominal ISDN B channel bit error rate is 10'^. At this rate, with 2,000 bit packets, about 3 packets in 10^ transmitted packets wiU falsely pass the FCS check. Forward error correction could be applied to the ciphertext to single bit errors at the expense of some channel bandwidth. Error correction applied to the plaintext would have to be capable of correcting 64-bit bursts, a formidable requirement. The Output Feedback (OFB), illustrated in figure 26, is similar, except that it is the output of the DES that is fed back rather than the cipher text. Now there effectively are two free running (in the sense of the transmitted cipher text) pseudorandom number generators, whose outputs are exclusive-ored with the plaintext to create the cipher text and exclusive-ored with the cipher text to recover the plaintext. Transmission bit errors are not expanded, but synchronism becomes the problem. Both DES algorithms must be seeded with the same IV and key, must start in synchronism, must maintain synchronism and must recognize the loss of synchronism and recover from it. Since ISDN provides a byte synchronized service, bit errors do not affect synchronism. With ISDN B channels, OFB synchronism, once achieved, is normally easily maintained, however \"byte slips,\" which may normally occur on an ISDN circuit within the continental United States on the order is once a day, will cause the loss of synchronism. It is therefore necessary to recognize loss of synchronism and resynchronize the encryption.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security in ISDN."}]}
{"id": "nist_01875", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Status Report on the Second Round of the NIST Lightweight Cryptography Standardization Process say about References? (Part 12) According to Status Report on the Second Round of the NIST Lightweight Cryptography Standardization Process, References: andidates. - [62] Banik S, Bogdanov A, Peyrin T, Sasaki Y, Sim SM, Tischhauser E, Todo Y (2019) SUNDAE-GIFT v1.0, Submission to the NIST Lightweight Cryptography Standardization Process. lightweight-cryptography/ round-2-candidates. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ - [63] Wu H, Huang T (2019) TinyJAMBU: A Family of Lightweight Authenticated Encryption Algorithms, Submission to the NIST Lightweight Cryptography Standardization Process. lightweight-cryptography/ round-2-candidates. - [64] Aagaard M, AlTawy R, Gong G, Mandal K, Rohit R, Zidaric N (2019) WAGE: An Authenticated Cipher, Submission to the NIST Lightweight Cryptography Standardization Process. lightweight-cryptography/ round-2-candidates. - [65] Daemen J, Hoffert S, Peeters M, Assche GV, Keer RV (2019) Xoodyak: A Lightweight Cryptographic Scheme, Submission to the NIST Lightweight Cryptography Standardization Process. lightweight-cryptography/round-2-candidates. - [66] Chakraborti A, Datta N, Jha A, Nandi M (2020) Structural Classification of Authenticated Encryption Schemes, NIST Lightweight Cryptography Workshop 2020. Events/lightweight-cryptography-workshop-2020/documents/papers/ structural-classification-lwc2020.pdf. - [67] Bovy E (2020) Comparison of the Second Round Candidates of the NIST Lightweight Cryptography Competition, Bachelor thesis Computing Science, Radboud University. https://www.cs.ru.nl/bachelors-theses/. - [68] Bertoni G, Daemen J, Peeters M, Assche GV (2008) On the Indifferentiability of the Sponge Construction.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Second Round of the NIST Lightweight Cryptography Standardization Process."}]}
{"id": "nist_01876", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium say about 1 INTRODUCTION? (Part 2) According to Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium, 1 INTRODUCTION: s in a timely way and develop standards, systems and processes for security before such wide scale adoption of the technology limits, or prohibits, the deployment of protection mechanisms. The negative impacts of failure to include security protocols at start-up can be seen within the power and energy sector, which has large deployments of programmable logic controllers (PLC) and supervisory control and data acquisition (SCADA) systems. At the time of design and deployment, these systems were not equipped with adequate security mechanisms to contend with the threats of the connected world in the current environment. Now these systems are so tightly woven into the fabric of the power grid, retrofitting security is a much larger task than if it had been tackled in the beginning.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium."}]}
{"id": "nist_01877", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-2 in Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions? (Part 22) Control HA-2: ct a tag length less than 64 bits after a careful risk analysis is performed. The tag length shall be the same across the lifespan of the key. - R5. Limit on the maximum number of decryption failures. When the tag bit length \ud835\udf06 satisfies 64 \u2264 \ud835\udf06 \u2264 128 , the probability of a forgery is low enough that decryption failures up to 2 \ud835\udf06-32 can be tolerated without compromising security. Therefore, the maximum number of decryption failures under a fixed key shall not exceed 2 \ud835\udf06-32 . For shorter tags, with 32 \u2264 \ud835\udf06 &lt; 64 , the forgery probability is higher, in these cases, the number of allowable decryption failures should be limited to 1. However, if a careful risk analysis shows that the system's overall security goal remains satisfied, this limit may be relaxed -up to the same bound of 2 \ud835\udf06-32 . - R6. Data limit. The total amount of data processed during encryption and decryption, including the nonce, shall not exceed 2 54 bytes for a given key. 2 In AEAD schemes, context commitment is a security property that ensures a ciphertext cannot be decrypted successfully under two different, adversarially-chosen contexts -where context includes a secret key, nonce, and associated data. - R7. Key update. The key shall be updated to a new key once the total amount of input data reaches the limit of 2 54 bytes, and should be updated when the number of decryption failures reaches its limit. ## 4.4. Security Properties This section provides the security properties of Ascon-AEAD128 in various scenarios, including single-key and multi-key settings, nonce-respecting and nonce-misuse settings, and with or without the truncation option. In the single-key setting, the security of the scheme is analyzed under the assumption that the scheme uses a single key; in contrast, in the multi-key setting, multiple independent keys are used, and the adversary may interact with many instances of the scheme, each with a different key.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions."}]}
{"id": "nist_01878", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SC-26 in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Control SC-26: Predefined Segmentation Negate, Contain", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_01879", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Section 91) situations, tailoring actions may 56 NIST Special Publication 800-53 (Revision 5), separates the control catalog from the control baselines that have been included historically in that publication. A new companion publication, NIST Special Publication 800-53B, Control Baselines and Tailoring Guidance for Federal Information Systems and Organizations defines the recommended baselines. NIST Special Publication 800-53B is referenced throughout the RMF in the relevant tasks. 57 Tailored control baselines may also be referred to as overlays . An organizationally-tailored control baseline is analogous to an organization-wide overlay since an overlay is a tailored baseline that services a community of interest, in this case, the organization. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ be restricted or limited by the developer of the tailored baseline or by the issuing authority for the tailored baseline. Tailored baselines (or overlays) have been developed by communities of interest for cloud and shared systems, services, and applications; industrial control systems; privacy; national security systems; weapons and space-based systems; high value assets; 58 mobile device management; federal public key infrastructure; and privacy risks. Organizations may also benefit from developing one or more Cybersecurity Framework Profiles . A Cybersecurity Framework Profile uses the Subcategories in the Framework Core to align cybersecurity outcomes with mission or business requirements, risk tolerance, and resources of the organization. 59 The prioritized list of cybersecurity outcomes developed at the organization and mission/business process levels can be helpful in facilitating consistent, risk-based decisions at the system level.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, risk management framework. General security reference material without sensitive content. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_01880", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain SP 800-12 Revision 1 according to NIST 2017 NIST_ITL Cybersecurity Program Annual Report According to 2017 NIST_ITL Cybersecurity Program Annual Report, SP 800-12 Revision 1: An Introduction to Information Security June 2017 https:/ /csrc.nist.gov/publications/detail/sp/800-12/ rev-1/final https:/ /doi.org/10.6028/NIST.SP.800-12r1 Organizations rely heavily on the use of information technology (IT) products and services to run their day-to-day activities. Ensuring the security of these products and services is of the utmost importance for the success of the organization. This publication introduces the information security principles that organizations may leverage to understand the information security needs of their respective systems.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01881", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Common Platform Enumeration_ Name Matching Specification Version 2.3 say about Appendix A-References? According to Common Platform Enumeration_ Name Matching Specification Version 2.3, Appendix A-References: The following documents are indispensable references for understanding the application of this specification.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Platform Enumeration_ Name Matching Specification Version 2.3."}]}
{"id": "nist_01882", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 8 CNA Acceptance Process according to NIST Collaborative Vulnerability Metadata Acceptance Process (CVMAP) for CVE Numbering Authorities (CNAs) and Authorized Data Publishers According to Collaborative Vulnerability Metadata Acceptance Process (CVMAP) for CVE Numbering Authorities (CNAs) and Authorized Data Publishers, 8 CNA Acceptance Process: Participation in the submission process automatically begins when the CNA includes submission category information within their provided CVE records. As submissions are received and NVD analysts complete a Verification of CVE records, an email will be sent to the CNA to notify them that an audit has occurred and provide a link to the audit results. Once the CNA provides the acceptable number of CVE records that contain information for a specific submission category, a determination of acceptance level will be made. A sample size has been selected based on the experience that it takes a new NVD analyst to become proficient in providing CVE record metadata. The current sample size can be found at https://nvd.nist.gov/vuln/cvmap/How-We-Assess-Acceptance-Levels for each submission category provided. While this requirement may be difficult to achieve for smaller CNAs in a short period of time, it is necessary in order to maintain the consistency of the NVD data. The NVD user base is comprised of thousands of businesses and local, state, and Federal Government agencies that rely on the NVD to provide a consistent result set. As this process matures, improvements and efficiencies may be achieved to allow for a reduction in the sample size. The Acceptance Thresholds defined below will be applied to determine what Acceptance Level the CNA's information will be assigned within the NVD.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Collaborative Vulnerability Metadata Acceptance Process (CVMAP) for CVE Numbering Authorities (CNAs) and Authorized Data Publishers."}]}
{"id": "nist_01883", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach say about D.3 CASCADING OF ERRORS? According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach, D.3 CASCADING OF ERRORS: The cascading of errors is the domino effect of errors throughout an application system. An error in one part of the program or application triggers a second yet unrelated error in another part of the application system. This second error may trigger a third error, and so on. The cascading of error risk is frequently associated with making changes to application systems. A change is made and tested in the program in which the change occurs. However, some condition has been altered as a result of the change, which causes an error to occur in another part of the application system. Cascading of errors can occur between applications. This risk intensifies as appHcations become more integrated. For example, a system that is accepting orders may be tied through a series of applications to a system that replenishes inventory based upon orders. Thus, an insignificant error in the order entry program can \"cascade\" through a series of applications resulting in a very serious error in the inventory replenishment program. The types of conditions that lead to cascading of errors include: 1. Inadequately tested appHcations; 2. Failure to communicate the type and date of changes being implemented; and 3. Limited testing of program changes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach."}]}
{"id": "nist_01884", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Author ORCID iDs according to NIST Guidelines for Media Sanitization According to Guidelines for Media Sanitization, Author ORCID iDs: Ramaswamy Chandramouli: 0000-0002-7387-5858 Eric Hibbard: 0009-0001-8112-1263", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Media Sanitization."}]}
{"id": "nist_01885", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols provide? (Section 67) on truncation protection service is specified, the transport entity shall compare the final sent and received sequence numbers with the sequence numbers of the final sent and received DT and ED TPDUs. The handling of a mismatch of sequence numbers is a local matter. This is a security relevant event and reporting to an audit authority is recommended. This procedure is not used with the connectionless transport service (ISO 8602). Upon receipt of a TPDU, the peer address associated with the cryptographic key shall be compared to the source address of the TPDU. If the addresses do not match, the SE TPDU shall be discarded. This is a security relevant event and shall be reported to the layer management entity. Security labels are used in all classes to provide support for access control and to provide support for data separation based on sensitivity. The procedure makes use of the following TPDU and parameter: - SETPDU; - key-id - label. When a cryptographic asociation specifies use of an explicit security label on every TPDU, the label shall be sent in the LABEL field of the protected header of each SE TPDU. Upon receipt of a SE TPDU containing the LABEL parameter, the transport entity shall verify that the LABEL parameter falls within the set of acceptable security levels for the cryptographic association. If a SE TPDU is received with an improper LABEL, the TPDU shall be discarded. This is a security relevant event and shall be reported to the layer management. Pad parameter processing is used in all classes for cryptographic algorithms which process data in blocks of specific sizes. The procedure makes use of the following TPDU and parameter: - SE TPDU encapsulating any TPDUs defined in ISO 8073 or ISO 8602; - pad. A received pad parameter value is discarded. If the connection-oriented service (kg tc) is in use, the key associated with a connection shall be deleted as part of the connection release procedure.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols."}]}
{"id": "nist_01886", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Domain Name System-Based Electronic Mail Security say about 1.2 Solution? (Part 1) According to Domain Name System-Based Electronic Mail Security, 1.2 Solution: 1.2 Solution DNSSEC protects against unauthorized modifications to domain name information to prevent connection to spoofed or malicious hosts. The NCCoE initiated a collaborative project with industry partners to develop a proof-of-concept security platform that provides trustworthy mail server-to-mail server email exchanges across organizational boundaries. Products comprising the security platform include client mail user agents (MUAs) 6 , DNS servers (authoritative and caching/recursive) 7 , mail transfer agents (MTAs) 8 , and X.509 cryptographic key certificate sources (components and services). The network infrastructure products are similar to those found in every enterprise and used to perform basic IT functions and handle email. The certificate utilities are needed to produce X.509 certificates 9 for mail servers and end users to support Transport Layer Security (TLS) 10 and Secure/Multipurpose 5 RFC 6698, The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security Protocol : TLSA 6 According to NIST SP 800-177, an MUA is a software component (or web interface) that allows an end user to compose and send messages to one or more recipients. An MUA transmits new messages to a server for further processing (either final delivery or transfer to another server). 7 According to Section 3.2 of SP 800-177, there are two main types of name servers: authoritative name servers and caching name servers. The term authoritative is with respect to a zone. If a name server is an authoritative source for DNS resource records for a particular zone (or zones) of DNS addresses, it is called an authoritative name server for that zone (or zones). An authoritative name server for a zone provides responses to name resolution queries for resources for that zone, using the records in its own zone file.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_01887", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-128 in Secure Biometric Match-on-Card Feasibility Report? (Part 8) Control ES-128: ution of the host PC, which is 1/60 second or 17 ms. Such fluctuations are recorded whenever a fixed duration phenomenon is measured repeatedly, starting at random points with respect to a clock tick. Assuming the DUT response time is fixed, the actual DUT response time is approximately the computed average response time, as reported in Appendix A. Whether the assumption holds or not, a 17 ms fluctuation is less than 3% of the measured values in all cases. In some cases, one or more of the following anomalies were observed while obtaining timing metrics for a DUT: + The entire protocol sequence could not be executed (e.g., a secure session could not be established with the DUT). Hence, some graphs may have less than 100 time values for matching and/or non-matching results (an example appears in Figure C-29). + A matching template was sent to a DUT for verification and the DUT responded with a 'No match' result. Consequently, there may be more non-matching than matching time values (an example appears in Figures C-35 and C-36). + Anomalous time values were observed that exceed the 17 ms host clock resolution (an example appears in Figure C-29). These anomalies may have been caused by a number of different factors, such as Radio Frequency (RF) noise between the DUT and smart card reader, and the actual negotiated operating speed of the DUT. ## 5. Conclusion The timing metrics obtained from the SBMOC feasibility study showed that it is possible to securely perform biometric match-on-card operations over the contactless interface of a smart card within 2.5 seconds, while meeting the constraints in Appendix D except the accuracy constraint. The study also showed that the amount of time required to complete an SBMOC operation is dependent on a number of factors, such as the cryptographic mechanisms used, the minutia count of the reference and sample fingerprint templates, and the format of the fingerprint templates.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Biometric Match-on-Card Feasibility Report."}]}
{"id": "nist_01888", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1.4 Document Structure according to NIST Recommended Criteria for Cybersecurity Labeling of Consumer Software According to Recommended Criteria for Cybersecurity Labeling of Consumer Software, 1.4 Document Structure: The remainder of this document is organized as follows: - Section 2 - contains the baseline technical criteria for the label and methodology used to arrive at those criteria - Section 3 - describes criteria for the labeling approach and consumer-focused label information - Section 4 - describes conformity assessment and proposes multiple approaches for a labeling scheme - Appendix A - provides additional details on labeling criteria and considerations, including labeling approaches, consumer education, usability, and consumer testing - Appendix B - contains an abbreviated excerpt from the Secure Software Development Framework", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Recommended Criteria for Cybersecurity Labeling of Consumer Software."}]}
{"id": "nist_01889", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cell Phone Forensic Tools_ an Overview and Analysis provide? (Section 15) | | SEARCH FUNCTIONALITY........................................................................................................... | 52 | | GRAPHICS LIBRARY ................................................................................................................... | 53 | | REPORT GENERATION ................................................................................................................ | 53 | | SCENARIO RESULTS ................................................................................................................... | 55 | | SIM CARD ACQUISITION ........................................................................................................... | 56 | | SYNOPSIS OF OXYGEN PHONE MANAGER .................................................................... | 57 | | SUPPORTED PHONES .................................................................................................................. | 57 | | ACQUISITION STAGE ..................................................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_01890", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Framework for Designing Cryptographic Key Management Systems provide? (Section 212) ties and turning off nonessential services. Hardening a computer involves several steps to form layers of protection. | | Hash Value | The fixed-length bit string produced by a hash function. | | Identifier | A text string used to indicate an entity (e.g., one that is performing a key management function) and by the CKMS access control system to select a specific key from a collection of keys. | | Interoperability | A measure of the ability of one set of entities to physically connect to and logically communicate with another set of entities. | | Key | See cryptographic key. | | Key Agreement | A key establishment procedure where the resultant keying material is a function of information contributed by two or more participants, so that no entity can predetermine the resulting value of the keying material independently of any other entity's contribution. | | Key Confirmation | A procedure to provide assurance to one entity (the key confirmation recipient) that another entity (the key confirmation provider) actually possesses the correct secret keying material and/or shared secret. | | Key Distribution | The transport of a key and other keying material from an entity that either owns or generates the key to another entity that is intended to use the key. (Sometimes called key transport.) | | Key Entry | The process by which a key (and perhaps its metadata) is entered into a cryptographic module in preparation for active use. | | Key Establishment | The process by which a key is securely shared between two or more entities, either by transporting a key from one entity to another (key transport) or deriving a key from information shared by the entities (key agreement). | | Key Label | A key label is a text string that provides a human-readable and perhaps machine-readable set of descriptors for the key.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, key management. Contains security framework guidance for authentication systems. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_01891", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Draft NISTIR 7831 , Common Remediation Enumeration (CRE) Version 1.0 according to NIST Computer Security Division 2012 Annual Report According to Computer Security Division 2012 Annual Report, Draft NISTIR 7831 , Common Remediation Enumeration (CRE) Version 1.0: This GLYPH(cmap:df00)ocument GLYPH(cmap:df00)efines the Common RemeGLYPH(cmap:df00)iation Enumeration (CRE) 1.0 specification. CRE is part of a suite of enterprise remeGLYPH(cmap:df00)iation specifications that enable automation and enhanced correlation of enterprise remediation activities. Each CRE entry represents a unique remediation activity and is assigneGLYPH(cmap:df00) a globally unique CRE iGLYPH(cmap:df00)entifier (CRE-ID). This specification GLYPH(cmap:df00)escribes the core concepts of CRE, the technical components of a CRE entry, outlines how CRE entries are created, the technical requirements for constructing a CRE-ID, anGLYPH(cmap:df00) how CRE-IDs may be assigned. CRE-IDs are intended to be boundary objects that are broaGLYPH(cmap:df00)ly useable in enterprise security management products and information domains that participate in remediation activities or make assertions about remediation actions. Contact: Mr. David Waltermire GLYPH(cmap:df00)aviGLYPH(cmap:df00).waltermire@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_01892", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Guide to Integrating Forensic Techniques into Incident Response? (Part 120) Control HA-1: not a valid address within the organizationGLYPH&lt;146&gt;s networksGLYPH&lt;151&gt;the incident handler should rely on other data sources to identify the host that actually sent the e-mail message. The organizationGLYPH&lt;146&gt;s e-mail servers are another likely source of information. Each of the server IP addresses listed in the e-mail header should contain some record of the e-mail, including the message ID value, which should facilitate quick identification of pertinent records. As mentioned previously, the final e-mail server in the list may contain a copy of the e-mail. Backups of that server may contain a copy of the e-mail, but only if it was held there for delivery for several hours or more. Other services associated with e-mail, such as antivirus software and spam filters, may also contain basic records of e-mail activity, but are unlikely to contain many details. Another possible source of information is authentication records. Although few e-mail servers require users to authenticate to send e-mail, they typically do require authentication to deliver e-mail to users. Because users often send and receive e-mail during a single session, authentication logs may contain records for receiving e-mail that can be helpful in determining who may have sent a particular e-mail. Another possible source of information is a record of the network traffic generated by sending or receiving the e-mail. Packet sniffers or network forensic analysis tools that were monitoring network activity might have captured the activity, including the actual IP addresses of the sending or receiving hosts, the contents and header of the e-mail, and any associated authentication activity. Ultimately, the incident handler should identify the hosts that were used to send and receive the e-mail, as well as all intermediate hosts that transferred the e-mail from sender to receiver.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Guide to Integrating Forensic Techniques into Incident Response."}]}
{"id": "nist_01893", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2008 Annual Report provide? (Section 3) During Fiscal Year 2008 (FY2008), CSD successfully responded to numerous challenges and opportunities in fulfilling its mission. CSD carried out a diverse research agenda and participated in many national priority initiatives, leading to the development and implementation of high-quality, cost-effective security and privacy mechanisms that improved information security across the federal government and throughout the national and international information security community. In FY2008, CSD continued to develop standards, metrics, tests, and validation programs to promote, measure, and validate the security in information systems and services. Recognizing the potential benefits of more automation in technical security operations, CSD hosted the Information Security Automation Program (ISAP), which formalizes and advances efforts to enable the automation and standardization of technical security operations, including automated vulnerability management and policy compliance evaluations. The CSD also continued to work closely with federal agencies to improve their understanding and implementation of the Federal Information Security Management Act (FISMA) to protect their information and information systems. CSD supported a major intelligence community and national security community initiative to build a unified framework for information security across the federal government. This initiative is expected to result in greater standardization and more consistent and cost-effective security for all federal information systems. As technology advances and security requirements evolve, CSD critically evaluates existing standards, guidelines, and technologies to ensure that they adequately reflect the current state of the art.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2008 Annual Report."}]}
{"id": "nist_01894", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Mary Raguso Susan Symington according to NIST Securing Web Transactions_ TLS Server Certificate Management According to Securing Web Transactions_ TLS Server Certificate Management, Mary Raguso Susan Symington: The MITRE Corporation June 2020 This publication is available free of charge from: http://doi.org/10.6028/NIST.SP.1800-16 The first draft of this publication is available free of charge from: <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_01895", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Test Personal Identity Verification (PIV) Cards Version 2 say about D.4.15.10 Test PIV Card 15: Retired Key Management Certificate F? According to NIST Test Personal Identity Verification (PIV) Cards Version 2, D.4.15.10 Test PIV Card 15: Retired Key Management Certificate F: Serial Number : 1504 (0x5e0) Signature Algorithm : ecdsa-with-SHA256 Issuer : CN=Test ECC P-256 CA for Test PIV Cards, ou=Test CA, o=Test Certificates 2010, c=US Validity : Not Before: Oct 1 08:30:00 2010 GMT, Not After: Oct 1 08:30:00 2030 GMT Subject : CN=Test E. Cardholder XV, ou=Test Agency, ou=Test Department, o=Test Government, c=US Subject Public Key Info : id-ecPublicKey, P-256", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_01896", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does SRI International_ Improving the Security of Your UNIX System provide? (Section 23) ould never be trusted. Also, if there are any machines at your organization that are installed in 'public' areas (e.g., terminal rooms) as opposed to private offices, you should not trust these hosts. On Sun systems, hosts.equiv is controlled with the Yellow Pages software. As distributed, the default hosts.equiv file distributed by Sun contains a single line; + This indicates that every known host (i.e., the complete contents of the host file) should be considered a trusted host. This is totally incorrect and a major security hole, since hosts outside the local organization should never be trusted. A correctly configured hosts.equiv should never list any 'wildcard' hosts (such as the only specific host names should be used. When installing a new system from Sun distribution tapes, you should be sure to either replace the Sun default hosts.equiv with a correctly configured one, or delete the file altogether. The .rhosts file [SunSSa, 1397] is similar in concept and format to the hosts.equiv file, but allows trusted access only to specific host-user combinations, rather than to hosts in general.* Each user may create a .rhosts file in his home directory, and allow access to her account without a password. Most people use this mechanism to allow trusted access between accounts they have on systems owned by different organizations who do not trust each other's hosts in hosts.equiv. Unfortunately, this file presents a major security problem; While hosts.equiv is under the system administrator's control and can be managed effectively, any user may create a .rhosts file granting access to whomever he chooses, without the system administrator's knowledge. The only secure way to manage .rhosts files is to completely disallow them on the system. The system administrator should check the system often for violations of this policy (see Section 3.3. 1.4).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: SRI International_ Improving the Security of Your UNIX System."}]}
{"id": "nist_01897", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-1 in Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events? (Part 6) Control IP-1: 050: Executive Technical Workshop on Improving Cybersecurity and Consumer Privacy [2] - \uf0a7 NIST Special Publication (SP) 800-30 Rev. 1: Guide for Conducting Risk Assessments [3] - \uf0a7 NIST SP 800-37 Rev. 1: Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach [4] - \uf0a7 NIST SP 800-39: Managing Information Security Risk [5] - \uf0a7 NIST SP 800-40 Rev. 3: Guide to Enterprise Patch Management Technologies [6] - \uf0a7 NIST SP 800-53 Rev. 4: Security and Privacy Controls for Federal Information Systems and Organizations [7] - \uf0a7 Federal Information Processing Standard 140-3: Security Requirements for Cryptographic Modules [8] - \uf0a7 NIST SP 800-86: Guide to Integrating Forensic Techniques into Incident Response [9] - \uf0a7 NIST SP 800-92: Guide to Computer Security Log Management [10] - \uf0a7 NIST SP 800-100: Information Security Handbook: A Guide for Managers [11] - \uf0a7 NIST SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems [12] - \uf0a7 Office of Management and Budget, Circular Number A-130: Managing Information as a Strategic Resource [13] - \uf0a7 NIST SP 800-61 Rev. 2: Computer Security Incident Handling Guide [14] - \uf0a7 NIST SP 800-83 Rev. 1: Guide to Malware Incident Prevention and Handling for Desktops and Laptops [15] - \uf0a7 NIST SP 800-150: Guide to Cyber Threat Information Sharing [16] - \uf0a7 NIST SP 800-184: Guide for Cybersecurity Event Recovery [17] ## 1.3 Benefits The NCCoE's practice guide can help your organization: - \uf0a7 develop a plan for identifying assets and vulnerabilities and protecting these assets from a cybersecurity event - \uf0a7 facilitate detection, response, and recovery from a DI event by collecting information about the enterprise before an attack occurs .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware, incident response. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_01898", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Example according to Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Example: The defender organization makes changes to a", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_01899", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is References according to Security and Privacy Controls for Information Systems and Organizations? References: [SP 800-124], [IR 8023].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01900", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CS-3 in U.S. Department of Energy Risk Assessment Methodology? (Part 120) Control CS-3: N/A 12/89 2/90 11/89 Accapting riak Whan naw room la available Scheduled for correction Purchaae required (2) Based on rasults of Step 1 and Stop 2, ara tha maasuraa in-placa sufficiant given: Hardware and Software: Cost(s) Yes HH | - No System Software and Data: Characteristics and Importance Yes rYn I I No Comments: <!-- image --> <!-- image --> | DEPARTMENT OF ENERGY ADP SYSTEM RISK ASSESSMENT | DEPARTMENT OF ENERGY ADP SYSTEM RISK ASSESSMENT | DEPARTMENT OF ENERGY ADP SYSTEM RISK ASSESSMENT | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | PAGE 4 | |---------------------------------------------------|---------------------------------------------------|---------------------------------------------------|---------------------|---------------------------|-------------------------| | 4^ THREAT ANO VUlNERABtUTY ANALYSfS | 4^ THREAT ANO VUlNERABtUTY ANALYSfS | 4^ THREAT ANO VUlNERABtUTY ANALYSfS | ftEVIEW | ftEVIEW | | | (1) | ASSET AREA | (a) THREATS AND | VULNERABILITY(IES) | (b) PROBA- BILITY (H.M.L) | (e) PRIORITY OF CONCERN | | b) | Physical (Facility): | Storm* | | H | 1 | | b) | Personnai: Accidents Emotional, | mental, health Sensitive data disclosure Lighting | problem | M M H H | 1 2 1 1 | | c) Information, Data, and Emissions: | | Power Fluctuations | | H | 1 | | d) *) Computer", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: U.S. Department of Energy Risk Assessment Methodology."}]}
{"id": "nist_01901", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study provide? (Section 56) _\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ [SHORT TITLE LINE 2] 38. How does your organization determine or measure the effectiveness of your security awareness program? Check all that apply. \u25a1 Required training completion rates \u25a1 Audit reports or FISMA (Federal Information Security Modernization Act of 2014) evaluations \u25a1 Phishing click rates (number of people who click on a simulated phishing email/link) \u25a1 Employee reporting of simulated phishing emails \u25a1 Employee reporting of potential phishing emails (outside of phishing simulations) \u25a1 Employee reporting of other security incidents \u25a1 Surveys \u25a1 Informal employee feedback/comments (for example, in-person, emails) \u25a1 Attendance at security awareness events \u25a1 Online views of training materials \u25a1 Security incident trends \u25a1 We don't try to determine the effectiveness \u25a1 Other: \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ &lt;If 'We don't try to determine the effectiveness,' skip next question&gt; 39. How does your security awareness program use program effectiveness data? Check all that apply. \u25a1 We use the data to demonstrate our compliance with training mandates. \u25a1 We provide the data to leadership to show the value of the security awareness program. \u25a1 We use the data to justify additional resources for the security awareness program. \u25a1 We provide the data to employees so there's more transparency about the security awareness program. \u25a1 We use the data to improve/inform the security awareness program. \u25a1 We provide the data to other groups in our organization to help improve/inform their own programs or processes. \u25a1 Other: \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ 40. If you are a manager or executive who is involved in making decisions about the security awareness program, what data would help demonstrate the value and effectiveness of the security awareness program?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study."}]}
{"id": "nist_01902", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain integrity according to NIST Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, integrity: Guarding against improper information modification or destruction and includes ensuring information nonrepudiation and authenticity. [79]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_01903", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 198) sions is required are de\ufb01ned; AC-12(01) a logout capability is provided for user-ini\ue000ated communica\ue000ons sessions whenever authen\ue000ca\ue000on is used to gain access to <AC-12(01)_ODP informa\ue000on resources>. POTENTIAL ASSESSMENT METHODS AND OBJECTS: AC-12(01)-Examine [SELECT FROM: Access control policy; procedures addressing session termina\ue000on; user logout messages; system design documenta\ue000on; system con\ufb01gura\ue000on se\ue001ngs and associated documenta\ue000on; system audit records; system security plan; other relevant documents or records]. AC-12(01)-Interview [SELECT FROM: System/network administrators; organiza\ue000onal personnel with informa\ue000on security responsibili\ue000es; system developers]. AC-12(01)-Test [SELECT FROM: System session termina\ue000on mechanisms; logout capabili\ue000es for user-ini\ue000ated communica\ue000ons sessions]. AC-12(02) SESSION TERMINATION | TERMINATION MESSAGE ASSESSMENT OBJECTIVE: Determine if: AC-12(02) an explicit logout message is displayed to users indica\ue000ng the termina\ue000on of authen\ue000cated communica\ue000on sessions. POTENTIAL ASSESSMENT METHODS AND OBJECTS: AC-12(02)-Examine [SELECT FROM: Access control policy; procedures addressing session termina\ue000on; user logout messages; system design documenta\ue000on; system con\ufb01gura\ue000on se\ue001ngs and associated documenta\ue000on; system audit records; system security plan; other relevant documents or records]. CHAPTER FOUR PAGE 89 Reference produced from open data h\ue003ps://github.com/usnistgov/oscal-content T h i s p u b l i c a \ue000 o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h \ue003 p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P. 8 0 0 - 5 3 A r 5 NIST SP 800-53A, REV. 5 ASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS AC-12(02) SESSION TERMINATION | TERMINATION MESSAGE AC-12(02)-Interview [SELECT FROM: System/network administrators; organiza\ue000onal personnel with informa\ue000on security responsibili\ue000es; system developers].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01904", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 8.1.5.3 Generation and Distribution of Other Keying Material according to NIST Recommendation for Key Management_ Part 1 \u2013 General According to Recommendation for Key Management_ Part 1 \u2013 General, 8.1.5.3 Generation and Distribution of Other Keying Material: Keys are often generated in conjunction with or are used with other keying material. This other keying material shall be protected in accordance with Section 6.2. Table 6 specifies the type(s) of protection required for keying material other than keys.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_01905", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Sub-step 1.3 Review Security Assessment Plan Documentation: according to NIST Automation Support for Security Control Assessments_ Software Vulnerability Management According to Automation Support for Security Control Assessments_ Software Vulnerability Management, Sub-step 1.3 Review Security Assessment Plan Documentation:: - Review the defect checks documented in Section 3.2 to get an initial sense of the proposed items to be tested. - Review the security assessment plan narratives in Section 3.2 to understand how the defect checks apply to the controls that support vulnerability management.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Vulnerability Management."}]}
{"id": "nist_01906", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Control according to Security and Privacy Controls for Information Systems and Organizations? Control: Notify the user, upon successful logon to the system, of the date and time of the last", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01907", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.2 The S-boxes according to NIST Validating the Correctness of Hardware Implementations of the NBS Data Encryption Standard According to Validating the Correctness of Hardware Implementations of the NBS Data Encryption Standard, 2.2 The S-boxes: The non-linear substitution tables, or S-boxes, constitute the most important part of the algorithm. The purpose of the S-boxes is to ensure that the algorithm is not linear, and hence too weak to stand up under cryptanaly tic attack [1,2]. Each of the eight S-boxes, such as is shown in figure 2, contains 64 entries, organized as a 4x16 matrix. Each entry is a four bit binary number, represented as 0-15 in figure 2, so the output of the parallel connection of eight S-boxes is 32 bits. A particular entry in a single S-box is selected by six bits, two of which select a row and four select a column. The entry in the corresponding row and column is the output for that input. Each row in each S-box is a permutation of the numbers 0-15, so no entry is repeated in any one row. There is no obvious small set of inputs that could be used to verify the S-boxes, so an extensive series of Monte-Carlo experiments was performed to discover a relatively small set of inputs that would exercise every S-box entry at least once. Nearly 200 separate trials were made, and among these were several test sets of 19 inputs which exercised every S-box entry. One of these sets is used as the DES test set for the S-boxes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validating the Correctness of Hardware Implementations of the NBS Data Encryption Standard."}]}
{"id": "nist_01908", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for Securing Radio Frequency Identification (RFID) Systems say about 8.1.2 Phase 2: Acquisition/Development? (Part 2) According to Guidelines for Securing Radio Frequency Identification (RFID) Systems, 8.1.2 Phase 2: Acquisition/Development: mation, the design team determined that the passive RFID system would operate in the high frequency range (13.56 MHz), and the semiactive RFID system would operate at microwave frequencies (2.45 GHz). While the risk of eavesdropping from locations outside the facility was considered to be very low, the design team still thought it would be of value to mitigate the risk to the greatest extent feasible. Therefore, they ensured that design drawings placed readers away from windows and exterior walls. Preferred locations were over doorways in rooms and on ceiling mounts in hallways. The devices would be prohibited in the radiology unit, but would be placed at entries to the unit. Previously installed shielding in the walls would prevent emissions from impacting the operation of the imaging equipment inside the unit. The design team determined that stationary readers would be connected to the RFID middleware infrastructure using Ethernet, which is also used to network the desktop computers and servers in the building. To accomplish this, the plan called for the installation of additional network cabling and drops, and use of the existing Ethernet switches, which had considerable excess capacity. Having the RFID systems, desktops, and servers all cabled into the same switches created a risk that the RFID system could be used as a platform to launch an attack on the rest of the network. To mitigate this risk, the design called for a dedicated VLAN to host the RFID-related network hosts. Traffic could only pass from the RFID VLAN to other network segments if it traversed the network firewall required by policy in the initiation phase. Once the architecture was completed, the CIO assigned two members of the design team to the job of procuring the system with her review and approval. They paid particular attention to the products' audit and management capabilities. Four vendors provided demonstrations of their products and submitted bids.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_01909", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does PIV Data Model Test Guidelines say about July 2006 July 2006? According to PIV Data Model Test Guidelines, July 2006 July 2006: <!-- image --> U.S. Department of Commerce U.S. Department of Commerce Carlos M. Gutierrez, Secretary U.S. Department of Commerce U.S. Department of Commerce Carlos M. Gutierrez, Secretary National Institute of Standards and Technology . National Institute of Standards and Technology William A. Jeffrey, Director National Institute of Standards and Technology . National Institute of Standards and Technology William A. Jeffrey, Director", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_01910", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 1 \u2013 General say about 8.1.5.1.1 Distribution of Public Keys? According to Recommendation for Key Management_ Part 1 \u2013 General, 8.1.5.1.1 Distribution of Public Keys: Static public keys are relatively long-lived and are typically used for several executions of an algorithm. Ephemeral public keys are short-lived. The distribution of the static or ephemeral public key should provide assurance to the receiver of the public key that the true owner of the key is known (i.e., the claimed owner is the actual owner); this requirement may be disregarded if anonymity is acceptable. However, the strength of the overall architecture and trust in the validity of the protected data depends, in large part, on assurance of the public-key owner's identity. In addition, the distribution of the public key shall provide assurance to the receiver that: 1. The purpose/usage of the key is known (e.g., for RSA digital signatures or elliptic-curve key agreement); 2. Any parameters associated with the public key are known (e.g., domain parameters); 3. The public key is valid (e.g., the public key satisfies the required arithmetical properties); and 4. The owner actually possesses the corresponding private key.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_01911", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to SSL VPNs say about 3.2 SSL VPN Functions? (Part 3) According to Guide to SSL VPNs, 3.2 SSL VPN Functions: turn requires administrative access to the local system. The client is typically an active content agent, so the system must have the ability to load the agent and the necessary privileges to run it. This can cause challenges on public systems, where users might not have those privileges, and on managed systems where security policy prevents such applets and controls. A more limited form of network extension is sometimes called port forwarding . The three core functions allow SSL VPNs to provide secure remote access to a variety of applications. SSL VPN products vary in quality and effectiveness by the way they implement these three core functions. For example, SSL VPN products may offer support for different protocols via proxy and application translation; others might offer more or less control of the level of network access for network extensions. When evaluating SSL VPN products, it is important to have identified the remote access needs and applications served.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to SSL VPNs."}]}
{"id": "nist_01912", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Key Notarization System for Computer Networks provide? (Section 6) D) | 20 | | 10. | DIGITAL SIGNATURES | DIGITAL SIGNATURES | 20 | | | 10.1 | RATIONALE | 20 | | :' . | 10.2 | EXAMPLE | 21 | | | 10.3 | THE AUTHENTICATION VALUE AS A SIGNATURE | 22 | | | 10.4 | NONPUBLIC KEY VERSUS PUBLIC KEY SIGNATURES | 23 | | 11. | ILLUSTRATIVE EXAMPLE | ILLUSTRATIVE EXAMPLE | 23 | | | 11.1 | INITIALIZATION | 23 | | | 11.2 | THE TRANSMITTER | 24 | | | 11.3 | THE RECEIVER | 24 | | i | 11.4 | KEY SUPERSESSION | 25 | | 12. | SUMMARY | SUMMARY | 25 | | APPENDIX | APPENDIX | APPENDIX | 26 | A Key Notarization System For Computer A cryptographic, Key Notarization System is proposed for computer networks to protect personal (nonshared) files, to communicate securely both on and off-line with local and remote users, to protect against key substitution, to authenticate system users, to authenticate data, and to provide a digital signature capability using a nonpublic key encryption algorithm. The system is implemented by the addition of key notarization facilities which give users the capability of exercising a set of commands for key management as well as for data encryption functions. Key notarization facilities perform notarization which, upon encryption, seals a key or password with the identities of the transmitter and Intended receiver.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: A Key Notarization System for Computer Networks."}]}
{"id": "nist_01913", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Applications Using Approved Hash Algorithms provide? (Section 15) ithm that computes aMAC from a message and a key. | | Message digest | The result of applying a hash function to a message. Also known as a 'hash value' or 'hash output'. | |---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Preimage | A message X that produces a given message digest when it is processed by a hash function. | | Preimage resistance | An expected property of a hash function such that, given a randomly chosen message digest, message_digest , it is computationally infeasible to find a preimage of the message_digest , See 'Preimage'. | | Random bit | A bit for which an attacker has exactly a 50% probability of success of guessing the value of the bit as either a zero or one. It is also called an unbiased bit. | | Random bit generator | A device or algorithm that can produce a sequence of bits that appear to be both statistically independent and unbiased. | | Randomized hashing | A process by which the input to a hash function is randomized before being processed by the hash function. | | Random number | A value in a set of numbers that has an equal probability of being selected from the total population 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Applications Using Approved Hash Algorithms."}]}
{"id": "nist_01914", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 301) , National Institute of Standards and Technology, Gaithersburg, Maryland, August 2012, 78 pp. http://csrc.nist.gov/publications/drafts/800-90/draft-sp800-90b.pdf [accessed 8/11/2014]. E. Barker and J. Kelsey, Recommendation for Random Bit Generator (RBG) Constructions, DRAFT NIST SP 800-90C, National Institute of Standards and Technology, Gaithersburg, Maryland, August 2012, 50 pp. http://csrc.nist.gov/publications/drafts/800-90/draft-sp800-90c.pdf [accessed 8/11/2014]. 248 15. E. Barker, Recommendation for Digital Signature Timeliness, NIST SP 800-102, National Institute of Standards and Technology, Gaithersburg, Maryland, Septebmer 2009, 30 pp. http://csrc.nist.gov/publications/nistpubs/800-102/sp800-102.pdf [accessed 8/11/2014]. 16. E. Barker and A. Roginsky, Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths, NIST SP 800-131A, National Institute of Standards and Technology, Gaithersburg, Maryland, January 2011, 27 pp. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf [accessed 8/11/2014]. 17. American National Standard Institute (ANSI), Protocol Specification for Interfacing to Data Communication Networks, ANSI C12.22-2008, National Electrical Manufacturers Association (NEMA), Rosslyn, Virginia, 2008. 18. S. Santesson, M. Myers, R. Ankney, A. Malpani, S. Galperin, and C. Adams, X.509 Internet Public Key Infrastructure Online Certificate Status Protocol \u2013 OCSP, IETF Network Working Group RFC 6960, June 2013. http://www.ietf.org/rfc/rfc6960.txt [accessed 8/11/2014]. 19. B. Aboba, L. Blunk, J. Vollbrecht, J. Carlson, and H. Levkowetz, Extensible Authentication Protocol (EAP), Internet Engineering Task Force (IETF) Network Working Group Request for Comments (RFC) 3748, June 2004. http://www.ietf.org/rfc/rfc3748.txt [accessed 8/11/2014]. 20. B. Aboba, D. Simon, and P. Eronen, Extensible Authentication Protocol (EAP) Key Management Framework, IETF Network Working Group RFC 5247, August 2008.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01915", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain System Requirements according to NIST Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector According to Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector, System Requirements: - \uf0a7 CPUs: 12 - \uf0a7 Memory: - 5 GB RAM - \uf0a7 Storage: 500 GB (thin provision) - \uf0a7 Operating System: CentOS 7 - \uf0a7 Network Adapter 1: VLAN 1901 - \uf0a7 Network Adapter 2: SPAN\\_PACS", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector."}]}
{"id": "nist_01916", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Contingency Planning Guide for Federal Information Systems say about Control Enhancements:? According to Contingency Planning Guide for Federal Information Systems, Control Enhancements:: - (1) The organization identifies an alternate processing site that is separated from the primary processing site so as not to be susceptible to the same hazards. Enhancement Supplemental Guidance : Hazards that might affect the information system are typically defined in the risk assessment. - (2) The organization identifies potential accessibility problems to the alternate processing site in the event of an area-wide disruption or disaster and outlines explicit mitigation actions. - (3) The organization develops alternate processing site agreements that contain priority-of-service provisions in accordance with the organization's availability requirements. - (4) The organization fully configures the alternate processing site so that it is ready to be used as the operational site supporting essential missions and business functions. - (5) The organization ensures that the alternate processing site provides information security measures equivalent to that of the primary site. | LOW Not Selected | MOD CP-7 (1) (2) (3) (5) | HIGH CP-7 (1) (2) (3) (4) (5) | |--------------------|----------------------------|---------------------------------|", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Contingency Planning Guide for Federal Information Systems."}]}
{"id": "nist_01917", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-1 in Identity and Access Management for Electric Utilities? (Part 1) Control AC-1: Identities and credentials are managed for authorized devices and users Application Company Product Version Use CA Identity Management Platform Identity Manager R12.0 SP14 Build 9140 Implements workflows for creating digital identities and authorizing them access to physical and logical resources, including authoritative source NIST SP 1800-2B: Identity and Access Management for Electric Utilities 15 T h i s p u b l i c a t i o T n h i i s s p a u v b a i . l i i l c a a b t l i e o n f r e i s e a o v f a c i l h a a b r l e g e f r f e r o e m o f : c h h t t a p r : g / e / d f r o o m o r : g h / t 1 t 0 p . : 6 / / 0 d 2 o 8 i / . N o r I g S / T 1 . S 0 P . 6 1 0 8 2 0 8 0 / - N 2 I . S T . S P 1 8 0 0 - 2 . . . Security Characteristics Example Capability CSF Subcategory Application Company Product Version Use Provision, modify or revoke access throughout all federated entities Mechanisms for centrally managed provisioning of access RSA 6.9.74968 Identity Management and Governance (IMG) Governance Lifecycle Virtual Directory Adaptive Directory 7.1.5 R29692 Credential Management GlobalSign Enterprise PKI N/A Implements workflows for creating digital identities and authorizing them access to physical and logical resources Authoritative source for digital identities and authorized access to resources Provides North American Energy Standards Board (NAESB)- compliant X.509 certificates to OT personnel NIST SP 1800-2B: Identity and Access Management for Electric Utilities 16 T h i s p u b l i c a t i o T n h i i s s p a u v b a i . l i i l c a a b t l i e o n f r e i s e a o v f a c i l h a a b r l e g e f r f e r o e m o f : c h h t t a p r : g / e / d f r o o m o r : g h / t 1 t 0 p . : 6 / / 0 d 2 o 8 i / . N o r I g S / T 1 . S 0 P . 6 1 0 8 2 0 8 0 / - N 2 I . S T . S P 1 8 0 0 - 2 . . .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: identity management, credential management, pki. Contains security framework guidance for authentication systems. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_01918", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Glossary of Computer Security Terminology provide? (Section 73) --------------------------------------------------------------------------------| | cross-talk | 1) An unwanted transfer of energy from one communications channel to another channel. (FIPS PUB 39; AR 380-380) | | crypto | A marking or designator identifying all COMSEC keying material used to protect or authenticate telecommunications carrying classified national security information and sensitive, but unclassified government or government-derived information, the loss of which could adversely affect the national security interest. (NTISSI 4002; NACSI8104) | | crypto-aIgorith m | A well-defined procedure or sequence of rules or steps used to produce a key stream or cipher text from plain text and vice versa.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, national security. Contains guidance on protecting sensitive government information. Source: Glossary of Computer Security Terminology."}]}
{"id": "nist_01919", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5 General Findings according to NIST Implementing a Zero Trust Architecture_ High-Level Document According to Implementing a Zero Trust Architecture_ High-Level Document, 5 General Findings: When deploying ZTA, the following capabilities are considered to be fundamental to determining whether a request to access a resource should be granted and, once granted, whether the access session should be permitted to persist: - \uf0a7 Authentication and periodic reauthentication of the requesting user's identity - \uf0a7 Authentication and periodic reauthentication of the requesting endpoint - \uf0a7 Authentication and periodic reauthentication of the endpoint that is hosting the resource being accessed - \uf0a7 Each authentication and reauthentication includes authorization and reauthorization In addition, the following capabilities are also considered highly desirable: - \uf0a7 Verification and periodic reverification of the requesting endpoint's health - \uf0a7 Verification and periodic reverification of the health of the endpoint that is hosting the resource being accessed", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Implementing a Zero Trust Architecture_ High-Level Document."}]}
{"id": "nist_01920", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Electronic Health Records on Mobile Devices say about puppet will install here? (Part 59) According to Securing Electronic Health Records on Mobile Devices, puppet will install here: d steps and corresponding screenshots. First install IIS and then install the .NET Framework. Table 11-2 summarizes the required IIS components and .NET Framework features followed by the screenshots. Table 11-2 IIS Components and .NET Features Required Option Common HTTP Features Health and Diagnostics Application Development Security Value IIS Default Document Directory Browsing HTTP Errors Static Content HTTP Logging .NET Extensibility 4.5 ASP .NET 4.5 ISAPI Extensions ISAPI Filters Request Filtering NIST SP 1800-1C: Securing Electronic Health Records on Mobile Devices 66 Required Option Management Tools .NET Framework 4.5 Features WCF Services Value IIS Management Console .NET Framework .NET Framework 4.5 ASP.NET 4.5 HTTP Activation TCP Port Sharing Figure 11-1 Web Server (IIS) Components Selection Screenshot T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 1 . . NIST SP 1800-1C: Securing Electronic Health Records on Mobile Devices 67 Figure 11-2 .NET Framework 4.5 Features Selection T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 1 . . Microsoft Office 2013 Filter Pack Download it from Microsoft website (http://www.microsoft.com/en-us/download/ details.aspx?id=40229) and install it. Java Runtime Environment (JRE) 8 Download and install JRE 8. Refer to 64-142952.html for details. All pre-installation software must be installed and configured before installing RSA Archer. 11.1.3 Installation 1. Create folders C:\\ArcherFiles\\Indexes and C:\\ArcherFiles\\Logging (will be used later). 2. Obtain/Download the installer package from RSA; extract the installation package. 3. Run installer. a.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Electronic Health Records on Mobile Devices."}]}
{"id": "nist_01921", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TE-1 in Mobile Device Security_ Bring Your Own Device (BYOD)? (Part 204) Control TE-1: | User Authentication Configuration ............................................................................ | 39 | | | 2.4.7 | VPN Configuration ...................................................................................................... | 43 | | | 2.4.8 | Enable Automatic Application and Threat Updates................................................... | 53 | | 2.5 | Kryptowire...................................................................................................................55 | Kryptowire...................................................................................................................55 | | | | 2.5.1 | Kryptowire and MaaS360 Integration ........................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_01922", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain The Security Problem according to NIST Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992 According to Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992, The Security Problem: - Many diverse CIS assets - Many diverse security products and systems - No overall security architecture", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992."}]}
{"id": "nist_01923", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Conformance Test for FDDI Medium Access Control (MAC) say about FDDI MAC Conformance Test C Language Test Generated by the TTCN Translator? (Part 24) According to A Conformance Test for FDDI Medium Access Control (MAC), FDDI MAC Conformance Test C Language Test Generated by the TTCN Translator: _lastlevel) { _level +-1; D; lUT receives its own while (TRUE) ( ``` ``` /* line 1119 \"FDDI.MP\" --[2]? TIMEOUT */ /* Tester holds Token and sends Idle symbols until TVX expires. */ if (Timeout (\"TVX. \") ) { _level +-1; return (FALSE) } /* line 1121 \"FDDI.MP\" [2] IDLE */ pIDLE -IDLE__I(); Send_PDU_IDLE (pIDLE) ; _level +-1; while (TRUE) { /* line 1124 \"FDDI.I^\" [3] */ if ((a 0)) { _level +' 1; /* line 1126 \"FDDI.MP\" [4]? GOTO */ goto D; } /* line 1128 \"FDDI.MP\" [3] */ Start_timer (\"TRT.TRTclaim\", (long) T_Max 1000); _level += 1; _timername \u00b7= \"TRT.\"; while (TRUE) { /* line 1130 \"FDDI.MP\" [4]? CLAIM */ /* IDT issues Claim frame. */ pCLAIM = CLAIM_R1 () ; _buffer *= Receive_PDU (_timername) ; if (Is_PDU_CLAIM(pCLAIM, _buffer) ) { _level +\u00b7= 1; while (TRUE) { /* line 1135 \"FDDI.MP\" [5]? TIMEOUT */ /* * Tester holds lUT's Claim frame to cause that the Claim frame * fails. */ if (Timeout (\"TRT. \") ) { _level +' 1; while (TRUE) { /* line 1137 \"FDDI.MP\" --[6] */ Start_timer (\"TRT.TRTbeacon\", (long) T_Max 1000) _level +* 1; _timemame -\"TRT.\"; while (TRUE) { /* line 1139 \"FDDI.MP\" --[7]? BEACON */ /* lUT issues Beacon frame. */ pBEACON -BEAC0N_R1(); _buffer -Receive_PDD (_timername) if ( I s_PDD_BEACON (pBEACON, _buffer) ) { _level +\u00bb 1; while (TRUE) { /* line 1143 \"FDDI.MP\" [8]! BEACON */ /* Tester repeats lUT's Beacon frame. */ pBEACON -BEAC0N_T1(); Send_PDU_BEACON (pBEACON) Start_timer (\"TRT.TRTclaim\", (long) T_Max 1000); _level +-1; _timername ' \"TRT.\"; while (TRUE) { /* line 1147 \"FDDI.MP\" --[9]? CLAIM */ /* * After IDT receives its own Beacon frame, it * issues Claim frame. */ pCLAIM -CLAIM_R1 () ; _buffer -Receiv\u20ac_PDU (__timemame) ; if (I s_PDD_CLAIM (pCLAIM, _buffer) ) { _level +-1; ``` ``` while (TRUE) ( /* line 1151 \"FDDI.MP' --[10] I CLAIM */ /* Tester repeats lUT's Beacon frame. */ pCLAIM -CLAIM_T1 () ; Send_PDU_CLAIM (pCLAIM) Start_timer (\"TRT. \", (long) TTRT 1000); _level +' 1; _timemame -\"TRT.\"; while (TRUE) { /* line 1155 \"FDDI.MP\" [11]?", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, token. Contains security framework guidance for authentication systems. Source: A Conformance Test for FDDI Medium Access Control (MAC)."}]}
{"id": "nist_01924", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DS-2 in Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)? (Part 6) Control DS-2: ions=re- submit( 120) NIST SP 1800-15D: Securing Small-Business and Home Internet of Things Devices 265 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Test Case Field Description table=100 priority=810 n_packets=0 ip in_port=\"wlp2s0.2486\" dl_src=00:c0:ca:97:d1:1f nw_dst=10.135.1.1 actions=resubmit( 120) table=100 priority=810 n_packets=0 ip in_port=\"wlp2s0.2486\" dl_src=00:c0:ca:97:d1:1f nw_dst=104.237.132.42 actions=resubmit( 120) table=100 priority=810 n_packets=0 ip in_port=\"wlp2s0.2486\" dl_src=00:c0:ca:97:d1:1f nw_dst=198.71.233.87 actions=resubmit( 120) table=100 priority=805 n_packets=103 in_port=\"wlp2s0.2486\" dl_src=00:c0:ca:97:d1:1f actions=out- put:diagout1 table=100 priority=800 n_packets=0 in_port=\"wlp2s0.2486\" dl_src=00:c0:ca:97:d1:1f actions=re- submit( 110) table=100 priority=460 n_packets=0 in_port=wlp2s0 dl_type=0x888e actions=resubmit( 120) table=100 priority=0 n_packets=0 actions=output:di- agout1 [Omitted for length] Micronets Gateway and Micronets Manager logs verifying onboarding: DPP Onboarding Initiated: \u2022 Micronets Gateway: \u201cDPPHandler.onboard_device: Issuing DPP onboarding commands for device\u201d 2020-06-16 14:03:32,897 micronets-gw-service: INFO DPPHandler.onboard_device: Issuing DPP onboarding commands for device '463165abc19725aefffc39def13ce09b17167fba' in mi- cronet 'generic... 2020-06-16 14:03:32,898 micronets-gw-service: INFO DPPHandler.send_dpp_onboard_event: sending: 2020-06-16 14:03:32,899 micronets-gw-service: INFO { \"DPPOnboardingStartedEvent\": { \"deviceId\": \"463165abc19725aefffc39def13ce09b17167fba\", \"macAddress\": \"00:C0:CA:97:D1:1F\", \"micronetId\": \"Generic\", NIST SP 1800-15D: Securing Small-Business and Home Internet of Things Devices 266 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_01925", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does An Analysis of Computer Security Safeguards for Detecting and Preventing Intentional Computer Misuse say about U.S. DEPARTMENT OF COMMERCE? According to An Analysis of Computer Security Safeguards for Detecting and Preventing Intentional Computer Misuse, U.S. DEPARTMENT OF COMMERCE: National Bureau of Standards Washington, D.C. 20234 OFFICIAL BUSINESS Penalty for Private Use, $300 POSTAGE AND FEES PAID U.S. DEPARTMENT OF COMMERCE COM-215 <!-- image --> SPECIAL FOURTH-CLASS RATE BOOK", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: An Analysis of Computer Security Safeguards for Detecting and Preventing Intentional Computer Misuse."}]}
{"id": "nist_01926", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Hewlett-Packard ScanJet Plus UP and IIC according to NIST Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST According to Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST, Hewlett-Packard ScanJet Plus UP and IIC: - I. The Hewlett-Packard ScanJet Plus IIP and EC are graphics and text scanners. The IIP model is a gray scale scanner, and the IIC model is a color scanner. The output resolution of both models is 400 dots per inch. 2. The scanners are useful for scanning and inserting graphics, text and handwritten equations into the ERN. 3. These scanners operate with PCs running Microsoft Windows. 4. The HP model costs $1,700 and the IIC model costs $2,700.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Preliminary Functional Specifications of a Prototype Electronic Research Notebook for NIST."}]}
{"id": "nist_01927", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Fiscal Year 2024 Cybersecurity and Privacy Annual Report say about CRYPTOGRAPHY? According to Fiscal Year 2024 Cybersecurity and Privacy Annual Report, CRYPTOGRAPHY: Cryptography is foundational to our security and data protection needs. The standards, guidelines, recommendations, and tools provided by NIST's Cryptography priority area enable the trustworthy assurance of integrity and confidentiality in all types of information and technology - now and in the future.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Fiscal Year 2024 Cybersecurity and Privacy Annual Report."}]}
{"id": "nist_01928", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record provide? (Section 99) | | B* | | | Req. # - ID | Ref. in Base Std. | Requirement Summary | L e v e l t a t u s | S | Assertion ID | Test Assertion Test Note | Imp.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record."}]}
{"id": "nist_01929", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach say about 4.5.2 Overview of the System Design Phase? (Part 4) According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach, 4.5.2 Overview of the System Design Phase: nal Control Related Specifications (FIPS PUBS 73 &amp; 102) -The purpose is to set forth security and internal control specifications to meet the functional security and internal control requirements. This document may be included as an appendix to System/Subsystem, Program and Data Base Specifications document. 3. Validation, Verification, and Testing Plan and Specifications (FIPS PUB 101) -The purpose of the VV&amp;T Plan is to plan for the evaluation of quality and correctness of the software, including requirements and design documentation. The W&amp;T Plan also contains plans for the testing of software, including detailed program specifications, descriptions, internal contols and security specifications, and procedures for all tests, as well as test data reduction and evaluation criteria. The three updated documents are: 1. Audit Plan 2. Project Plan 3. System Decision Paper", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach."}]}
{"id": "nist_01930", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.4 Portal Use Case according to NIST 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings According to 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings, 4.4 Portal Use Case: The other use case mentioned in the previous section involves the client using a web browser to access a web server, which in turn accesses Grid services on behalf of the client. This use case is becoming more common as a means to allow for easy access to Grid services with a minimal footprint installation on the client system. The primary observation in this case is that the portal effectively functions as a \u00d2chasm\u00d3 that must be bridged. Either X.509 or Shibboleth/SAML can be used to authenticate to the portal, but neither has a delegation method that allows for the delegation of authority from the user of a web browser to a portal (see, however, recent work of Cantor [4]). This is the socalled n -tier problem ( n &gt; 2), an active research area. We note that MyProxy has been used traditionally in the Grid community to enable a portal to use a client\u00d5s username and password to obtain X.509 credentials for the client. Recent work [23] has also shown that this can be extended to web single signon using PubCookie [33]. We believe this approach can be adapted to allow Shibboleth-issued SAML authentication assertions to be used to obtain X.509 credentials from MyProxy 4 . 4 The newly formed \u00d2ShibGrid\u00d3 projects, ShibGrid and SHEBANGS, sponsored by the UK Joint Information Systems Committee has similar goals As in the previous section, these X.509 credentials would have the principal name, taken from the NameIdentifier element in the SAML assertion, embedded in them. This would allow the Grid service to query the SAML Attribute Authority in an identical manner as described previously.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings."}]}
{"id": "nist_01931", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does An Introduction to Privacy Engineering and Risk Management in Federal Systems provide? (Section 45) o be assessed and the relationships among those factors. 65 In information security, the risk factors include the threats to the system and the vulnerabilities that can be exploited by those threats. 66 However, the terms 'threat' and 'vulnerability' fail to capture the essence of many privacy problems for individuals. Returning to the example of the smart meters, the smart meters are the part of the system collecting the information and thereby creating the problems for individuals (e.g., loss of trust; chilling effect on ordinary behavior). An information security risk model would be unlikely to perceive this behavior of the smart meter as a 'threat' since the activity is an authorized part of the functioning of the system itself. While it is not inconceivable to expand a threat-based model to apply to the purposeful processing of PII, overloading this term runs the risk of causing more confusion and miscommunication than clarity, and ultimately creating more difficulties in determining meaningful privacy risk assessments and appropriate mitigations. Consequently, agencies need terminology more suited to the nature of privacy in systems to be able to identify privacy risk as distinct from information security risk. As described in section 2.2, the potential circumstance or event of concern is a problem that individuals experience as a byproduct of authorized processing of PII. Therefore, rather than adding more concepts to the term 'threat,' a more information-rich factor for a privacy risk model is to identify the operation that a system is performing on PII, that could cause an adverse effect or a problem for individuals-in short, a problematic data action . Problematic data action means a data action that causes an adverse effect, or problem, for individuals. In the information security risk model the primary risk factors are expressed as the likelihood that a vulnerability will be exploited by a threat and the impact of such occurrence.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: An Introduction to Privacy Engineering and Risk Management in Federal Systems."}]}
{"id": "nist_01932", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TG-005 in Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)? (Part 44) Control TG-005: an IVP, when executed by an auditor, has, in some way, more \"value\" since it could be argued that a greater degree of Division of Duties was observed during that execution. E2 Users authorized to TP. Gomments As mentioned above the Paper makes reference to \"Users\". The Group felt that this word should be replaced, in many cases with Job Function, the concept being that individual users should only acquire access to GDIs, through approved TPs, by virtue of their Job Functions. The Job Functions, as mentioned above, are specified in Job Descriptions and the \"map\" of the Division of Duties is shown in the Organization Ghart for that organization. The Division of Duties over the whole process by which TPs are set up and users acquire access to them is obviously critical to the stature of the Integrity Trusted Gomputer Base (ITGB) The Group also felt that there should be a series of IVPs to periodically check the integrity of these definitions of access to TPs and GDIs. E3 Users must be authenticated. Gomments The Group felt that this is a function which must be performed by the Trusted Gomputer Base (TGB) . The user must be authenticated before any opportunity is provided to invoke a TP. The Group felt that the remaining rules which are listed below should be deleted for the reasons given. El GDIs changed only by authorized TPs. Comments This rule is subsumed by E2 , and this was generally agreed by all Groups during the general discussion. E4 Authorization Lists changed only by Security Officer. Comments This was regarded as only a particular implementation example of Rule E2 . It was seen as being an advantage to have a similar procedure as for normal TPs, since the Authorization Lists would have to be changed by a TP. C3 Suitable separation of duties. Comments This is another implementation example of Rule E2 Issues Questions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)."}]}
{"id": "nist_01933", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.1.4 Technology Transfer according to NIST Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls, 4.1.4 Technology Transfer: As discussed above in 3.3 and 3.4, the knowledge of what it takes to truly improve the security of a system is not widespread. Current research efforts, notably the KVM/370 (Kernel ized VM/370) [6], KSOS (Kernel ized Secure Operating System) [21], UCLA Secure Unix [24], and PSOS (Provably Secure Operating System) [15] projects --as well as the MULTICS GUARDIAN effort [22] --have developed some experience in using the kinds of software tools and management approaches that seem necessary. To aid the transfer of this technology, a report should be written that carefully documents the experiences of each of these efforts. The report should cover what the goals of each project were (or are), what kinds of tools were used, the experience --especially learning curve in using them, the costs involved, and the results. Costs should include both the expense df the effort and the effect on the product --performance and compatibility. The point here is not so much the detailed technology involved --as that has to be covered by other means but a feel for \"what it really takes to make a system secure.\"", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls."}]}
{"id": "nist_01934", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-002 in Guidelines for Smart Grid Cybersecurity? (Part 219) Control IP-002: idge. For large inter-domain systems, a federated approach is the most reasonable solution for large inter- domain systems. In general, any two domains should be allowed to cross-sign as they see fit. However, the activity of cross-signing with many other domains can result in significant overhead. Utility companies may wish to form regional consortiums that would provide bridging services for its member utility companies to help alleviate this concern. Small utilities could outsource their PKI. This is not necessarily the same as going to a public PKI provider, such as a large CA organization, and getting an \u201cInternet model\u201d certificate. With the Internet model, a certificate mainly proves that the organization is the rightful owner of the domain name listed in the certificate. For smart grid, this is probably not sufficient. Certificates should be used to prove ownership, as well as being used for authorization credentials. Smart grid certificates could be issued under smart grid\u2013sanctioned policies and could carry authorization credentials. 222 IEEE 802.16 (WiMAX) PKI certificates, by comparison, do not prove ownership; they can only be used to prove that the entity with the corresponding private key is the entity listed in the certificate. An AAA server must then be queried to obtain the authorization credential of the device. 4.1.2.4.4 Need for a Model Policy A CP is a document that describes the policies under which a particular certificate was issued. A typical CP document contains a rich set of requirements for all PKI participants, including those that are ascribed to the RP. A CP document also contains legal statements, such as liability limits that the PKI is willing to accept. RFC 3647 provides an outline and description for a template CP document. Most PKIs follow this template. A certificate reflects the CP that it was issued under by including a CP Extension.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, pki. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_01935", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain UNIX according to NIST Computer Security Training & Awareness Course Compendium According to Computer Security Training & Awareness Course Compendium, UNIX: COURSE TITLE: Audit and Security of Unix-Based Operating Systems COURSE LENGTH: 3 DAYS", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Training & Awareness Course Compendium."}]}
{"id": "nist_01936", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-12 in Engineering Trustworthy Secure Systems? (Part 48) Control AM-12: nd that new, unanticipated, and otherwise unforeseen adverse consequences will occur despite proactive planning and instituting of means and methods to control loss and the extent of its consequences. The reactive aspect promotes informed operational decision-making after the system is in use and a loss condition occurs, proactively providing an operations capability to address the loss condition and handle the loss. The reactive aspect complements the preemptive aspect by providing an informed basis and means for an external entity (e.g., a human operator or system) to act when failures occur. Essentially, the reactive aspect is a proactive engineering activity about providing a reactive capability. An effective design will optimize protection against loss to the extent practical while recognizing that losses will occur irrespective of the protections put in place. Optimization decisions across preemptive and reactive approaches must consider assets, stakeholders, concerns, and objectives. Achieving a proper mix requires establishing security objectives and conducting requirements elicitation and analysis to unambiguously ascertain the scope of security in terms of addressing failure and the associated consequences in its preemptive and reactive aspects. ## D.2. Design Considering Emergence A system is expected to deliver the required capabilities as authorized, as intended, and at the specified level of performance. It should not deliver unauthorized or unintended capabilities. One cause of unintended behaviors and outcomes lies with the concept of emergence . Emergence refers to the behaviors and outcomes that result from how individual system elements compose to form the system beyond the collection of behaviors and outcomes of the individual system elements. This composition is covered in the design principle of Structured Decomposition and Composition and illustrated in Figure 2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_01937", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Storage Encryption Technologies for End User Devices provide? (Section 62) e organization's facilities. Some storage encryption products allow the passwordbased authentication recovery mechanisms to be used and permit the user to temporarily use passwordbased authentication. However, because this is generally a reduction in the strength of authentication, many organizations do not permit its use. This means that a loss of authenticator could cause an extended loss of availability to the data, until the user can receive a new authenticator (e.g., smart card, cryptographic token) and an administrator can configure the device to use the new authenticator. Recovery mechanisms increase the availability of the storage encryption solution for individual users, but they can also increase the likelihood that an attacker can gain unauthorized access to encrypted storage by abusing the recovery mechanisms. Organizations should consider the tradeoff between availability and security when selecting and planning recovery mechanisms. Some storage encryption products also offer protection against authentication-guessing attempts. For example, if there are too many consecutive failed authentication attempts, some products can either lock the computer for a period of time or increase the delay between attempts. In particularly high-security situations, some products can be configured so that too many failed attempts causes the product to wipe all the protected data from the device. This approach strongly favors security over functionality. After the solution has been designed, the next step is to implement and test a prototype of the design. Ideally, implementation and testing should first be performed on lab or test devices. Only implementations in final testing should be conducted on production devices. Aspects of the solution to evaluate include the following: - GLYPH&lt;c=31,font=/PKMAFP+Webdings&gt; Protection. Each type of information that needs protection should be protected in accordance with the information gathered during the Identify Needs phase.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Guide to Storage Encryption Technologies for End User Devices."}]}
{"id": "nist_01938", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Enhancing Resilience of the Internet and Communications Ecosystem_ A NIST Workshop Proceedings provide? (Section 17) n bolting it on later, was a widely shared belief. Far too many products are shipped with known vulnerabilities; these products may be detected, attacked, and compromised within minutes of deployment. Secure update mechanisms are needed to address vulnerabilities discovered during the normal product lifetime. Clear and effective processes to address end-oflife issues are also needed, as vulnerabilities in obsolete products cannot be addressed, ensuring that adversaries have a reliable starting point when penetrating an enterprise or establishing a botnet. Participants noted a systemic education and awareness problem. Almost 6 % of the recommendations/comments during workshop breakout sessions focused on the importance of education and awareness. Many attendees cited transportation safety, where seatbelt usage and crash test ratings have led to better outcomes, as an education and awareness success story. Others cited the same sector as a cautionary tale, with long lead times before widespread acceptance of seat belts and other technological improvements. Energy Star was also the subject of repeated discussion, with simple metrics for consumers. An independent body to test and certify security-relevant features, and offer a more accessible rating scheme, was frequently cited as an important step towards consumer identification of products with strong security features. Perceived market incentives do not align with our security and resilience goals, according to many workshop participants. Product developers and vendors minimize cost and time to market, rather than build in security or offer efficient security updates. Much of the discussion focused on techniques to create market incentives, such as independent product certification, but some felt that more active government intervention (e.g., regulation) would eventually be needed to overcome market failures.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Enhancing Resilience of the Internet and Communications Ecosystem_ A NIST Workshop Proceedings."}]}
{"id": "nist_01939", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines on Firewalls and Firewall Policy provide? (Section 70) sed or personal firewalls built in to the hosts' operating systems? If so, how easily can these conflicts be resolved? The configuration phase involves all facets of configuring the firewall platform. This includes installing hardware and software, configuring policies, configuring logging and alerting, and integrating the firewall into the network architecture. Once the firewall has been chosen and acquired, the hardware, operating system, and underlying firewall software should be installed for a software-based firewall. Next, for both software-based and hardwarebased firewalls, patches and vendor updates should be installed on the system. During this stage, the firewall should also be hardened to decrease the risk of vulnerabilities and protect the system against unauthorized access. Any console software needed for remote access should also be installed at this time. During the installation and configuration, only the administrator doing that work should be able to manage the firewall. All other management services for the firewall, such as SNMP, should be disabled, and these services should be left disabled permanently unless needed. If the firewall supports having a separate administrator account for each person performing firewall administration duties, configure such accounts. Network firewalls should be placed in a room that meets the product's recommended environmental requirements for temperature, humidity, space, power, etc. This room should also be physically secured to prevent unauthorized personnel from accessing the firewall. Comparing the logs of multiple systems when analyzing problems is very important, so the internal clocks in each firewall should be consistent with those in all other systems used by the organization. The best way to do this is to have all systems synchronize with an authoritative time source. Once hardware and software has been installed and secured, administrators can create the firewall's policies.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Firewalls and Firewall Policy."}]}
{"id": "nist_01940", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings provide? (Section 22) the use of the following relationship types : - Supports : Concept A supports concept B when A can be applied alone or in combination with one or more other concepts to achieve B in whole or in part. - Is supported by : Concept A is supported by concept B when B can be applied alone or in combination with one or more other concepts to achieve A in whole or in part. - Identical: Concept A and concept B are identical. They use exactly the same wording. - Equivalent: Concept A and concept B are equivalent. They have the same meaning but different wording. - Contrary: Concept A and concept B each have one or more elements that contradict one or more elements of the other concept. The contradictions may be opposites but do not have to be. This is based on the contrary concept type in Section 6.5.4 of [ISO704]. - No relationship: Concept A and concept B are not related or are not sufficiently related to merit another supportive relationship type. The supports and is supported by relationships are more than simply cause and effect. They can also indicate whether or not the supporting concept is necessary for achieving the supported concept. One of the following relationship properties can optionally be assigned to each supports and is supported by relationship: - Example of: The supporting concept C is one way (an example) of achieving the supported concept D in whole or in part. However, the supported concept D could also be achieved without applying the supporting concept C. In other words, one can accomplish D without C. This is based on the generic relationship type in Section 5.5.4.2 of [ISO704]. - Integral to: The supporting concept C is integral to and a component of the supported concept. The supporting concept must be applied as part of achieving the supported concept. In other words, one cannot accomplish D without C. This is based on the partitive relationship type in Section 5.5.4.3 of [ISO704].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings."}]}
{"id": "nist_01941", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings say about 5.6 Implementation, Performance, Availability? (Part 1) According to 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings, 5.6 Implementation, Performance, Availability: 5.6 Implementation, Performance, Availability The technical realisation of a VA service is not a central topic of this paper. However, the following observations are made: - -A VA is an on-line trust service subject to severe requirements for availability and security. These requirements are enforced on the software and hardware used as well as on the operational environment of the service. 5 This is almost always the case for PKIs that require particular software to be installed. An agreement covers both purchase of software and acceptance as an authorised RP. - -A VA needs to handle the heterogeneity encountered in the PKI area, including support for various certificate profiles, cryptographic algorithms and protocols. - -For scaling, a VA must be replicated. Synchronisation between instances of the VA service and optimisation of collection of revocation information and auxiliary information must be in place. Outsourcing certificate processing to a VA may improve performance since an optimised and dedicated installation is used at the VA. The avoidance of certificate path discovery and validation procedures greatly improves speed in cases where this would normally be needed. However, the VA solution must scale, and performance is influenced by factors like the communication link between RP and VA. When RPs operating critical services rely on a VA, the VA's availability must be guaranteed. There are two main issues involved: - -Availability of the VA towards the RPs. This is similar to availability of other critical systems, and measures are reliable systems and communication links, redundancy, protection against DoS attacks and so on. - -Availability of updated status information from the CAs.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings."}]}
{"id": "nist_01942", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control WE-125 in Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities? (Part 48) Control WE-125: ble size (see line 1458 ). As the content of this array is read and copied to bp , so too is a huge amount of data from over its upper bound. The three-state BF chain so far (see the upper row in Fig. 17) shows that data can be read from over the bound of the array pointed by pl . However, it does not show why an exploit would reach sensi/t\\_i.ligave informa/t\\_i.ligaon, such as private keys or login creden/t\\_i.ligaals. The vulnerability triggered by the missing size veri/uniFB01ca/t\\_i.ligaon bug is only a part (although the main one) of the puzzle. ``` typedef struct ssl3_record_st { int type; /* type of record */ unsigned int length; /* How many bytes available */ unsigned int off; /* read/write offset into ' buf' */ unsigned char *data; /* pointer to the record data */ unsigned char *input; /* where the decode bytes are */ unsigned char *comp; /* only used with decompression - malloc()ed */ unsigned long epoch; /* epoch number, needed by DTLS1 */ unsigned char seq_num[8]; /* sequence number, needed by DTLS1 */ } SSL3_RECORD; 1448 dtls1_process_heartbeat(SSL *s) 1449 { 1450 unsigned char *p = &s->s3->rrec.data[0], *pl; 1451 unsigned short hbtype; 1452 unsigned int payload; 1453 unsigned int padding = 16; /* Use minimum padding */ 1454 1455 /* Read type and payload length first */ 1456 hbtype = *p++; 1457 n2s(p, payload); 1458 pl = p; ... 1465 if (hbtype == TLS1_HB_REQUEST) 1466 { 1467 unsigned char *buffer, *bp; ... 1470 /* Allocate memory for the response, size is 1 byte 1471 * message type, plus 2 bytes payload, plus 1472 * payload, plus padding 1473 */ 1474 buffer = OPENSSL_malloc(1 + 2 + payload + padding); 1475 bp = buffer; 1476 1477 /* Enter response type, length and copypayload */ 1478 *bp++ = TLS1_HB_RESPONSE; 1479 s2n(payload, bp); 1480 memcpy(bp, pl, payload); /* Naive implementation of memcpy() void *memcpy (void *dst, const void *src, size_t n) { size_t i; for (i=0; i<n; i++) *(char *) dst++ = *(char *) src++; return dst; } pl bp payload ``` Fig. 18.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities."}]}
{"id": "nist_01943", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Operational Technology (OT) Security provide? (Section 171) tes of that object and the requesting subject. For federal employees and contractors, Personal Identity Verification (PIV), used in accordance with FIPS 201, may be required to achieve access control. Organizations may also consider one or more of these techniques when determining how to support local access controls within their environments. Supplemental guidance for access controls can be found in the following documents: \u2022 NIST SP 800-63-3, Digital Identity Guidelines \u2022 NIST SP 800-73-4, Interfaces for Personal Identity Verification \u2022 NIST SP 800-76-2, Biometric Specifications for Personal Identity Verification \u2022 NIST SP 800-78-4, Cryptographic Algorithms and Key Sizes for Personal Identity Verification \u2022 NIST SP 800-96, PIV Card to Reader Interoperability Guidelines \u2022 NIST SP 800-97, Establishing Wireless Robust Security Networks: A Guide to IEEE 802.11i \u2022 NIST SP 800-162, Guide to Attribute Based Access Control (ABAC) Definition and Considerations OT-Specific Recommendations and Guidance Organizations should consider the following: \u2022 Some logical access controls, such as RBAC, support the principle of least privilege and the separation of duties by 98 NIST SP 800-82r3 September 2023 Guide to Operational Technology (OT) Security providing a uniform means to manage access to OT devices while reducing the cost of maintaining individual device access levels and minimizing errors. These logical access controls can also restrict OT user privileges to only those required to perform each person\u2019s job (i.e., configuring each role based on the principle of least privilege). The level of access can take several forms, including viewing, using, and altering specific OT data or device functions. \u2022 Solutions that provide credential management, authentication, authorization, and system use monitoring technical capabilities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Guide to Operational Technology (OT) Security."}]}
{"id": "nist_01944", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways say about 1.6 Typographic Conventions? According to Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways, 1.6 Typographic Conventions: The following table presents typographic conventions used in this volume. | Typeface/Symbol | Meaning | Example | |-------------------|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| | Italics | file names and path names; references to documents that are not hyperlinks; new terms; and placeholders | For language use and style guidance, see the NCCoE Style Guide . | | Bold | names of menus, options, command buttons, and fields | Choose File > Edit. | | Monospace | command-line input, onscreen computer output, sample code examples, and status codes | mkdir | | Monospace Bold | command-line user input contrasted with computer output | service sshd start | | blue text | link to other parts of the document, a web URL, or an email address | All publications from NIST's NCCoE are available at |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Improving Enterprise Patching for General IT Systems_ Utilizing Existing Tools and Performing Processes in Better Ways."}]}
{"id": "nist_01945", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Electronic Mail Security say about 3.1 OpenPGP? (Part 4) According to Guidelines on Electronic Mail Security, 3.1 OpenPGP: encrypted HTTP session. Some gateways can also perform these functions for emails sent to lists of users. For example, a single user could send an encrypted and signed email to a mailing list address. The gateway would decrypt the email and re- 15 Sites include the Free Software Foundation (http://www.gnupg.org/), Hushmail (http://www.hushmail.com/), International PGP Site (http://www.pgpi.org/), OpenPGP Site (http://www.openpgp.org/), and PGP (commercial version) (). 16 For more information about the DSA and the associated Digital Signature Standard (DSS), see FIPS PUB 186-2, Digital Signature Standard (DSS), 17 FIPS PUB 140-2, Security Requirements for Cryptographic Modules ; FIPS PUB 180-2, Secure Hash Standard (SHS) , and FIPS PUB 186-2, Digital Signature Standard (DSS) are available at encrypt it for all the individual recipients of the mailing list. Each recipient can then decrypt the email and verify the original signature.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_01946", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Use of ISO_IEC 24727 provide? (Section 18) ate a cardholder's PIN. Instead of creating a smart card specific command, the client-application invokes the ISO/IEC 24727-3 'DIDAuthenticate' service and passes the PIN number through the interface. The ISO/IEC 24727-3 implementation then packages the PIN number into a Generic Card Interface instruction and sends it to the ISO/IEC 24727-2 implementation. The Generic Card Interface instruction is packaged in accordance with the 'discovered' data objects on the card. In order to do the discovery, an ISO/IEC 24727-3 implementation needs to come to know which key reference to use within the card-application. This mapping from the named 'PIN number' to the key reference is discovered through a data structure called the registry. The registry is card-application specific and can be retrieved from an on-card storage location (from the card-application's Application Capability Description (ACD) when it is activated) or from an alternative off-card storage location. The registry contains data object information, access control requirements, key references, cryptographic algorithm references, and protocol references supported by the card-application. The registry also provides associations between the objects and key references. The SALII implementation receives a service action on its interface, and with the help of the registry, translates the service into a sequence of requests/commands for the Part 2 Generic Card Interface. This is illustrated in Figure 2. Figure 2 - Use of the Registry by ISO/IEC 24727-3 <!-- image --> ISO/IEC 24727-3 provides a set of normative authentication protocols. Currently, IDMS implementations use authentication protocols to meet their requirements but the protocols may differ from implementation to implementation. For example, two IDMS implementations might use an on-card biometric comparison authentication protocol.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, sso. Contains security framework guidance for authentication systems. Source: Use of ISO_IEC 24727."}]}
{"id": "nist_01947", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Block Cipher Modes of Operation_ Galois_Counter Mode (GCM) and GMAC say about Appendix B: Authentication Assurance? (Part 1) According to Recommendation for Block Cipher Modes of Operation_ Galois_Counter Mode (GCM) and GMAC, Appendix B: Authentication Assurance: Appendix B: Authentication Assurance The creation of an authentication tag by the authenticated encryption function provides the mechanism whereby assurance of the authenticity of the plaintext and AAD (and IV) can be obtained upon the execution of the authenticated decryption function. The nature of this assurance depends on the output of the authenticated decryption function: - If the output is the plaintext, then the design of the mode provides strong, but not absolute, assurance that the purported source of the data created the tag, i.e., that the plaintext and the AAD (and the IV and the tag) are authentic. Consequently, the mode also provides strong assurance that this information was not subsequently altered, either intentionally or unintentionally. - If the output is FAIL , then it is certain that at least one of the given inputs (i.e., the ciphertext, the AAD, the IV, or the tag) is not authentic. In the first case, the assurance is not absolute because forgeries are possible, in principle. In other words, an adversary, i.e., a party without access to the key or to the authenticated encryption function, may be able to produce the correct tag for some triple of ciphertext, AAD, and IV. As with any tag-based authentication mechanism, if the adversary chooses a t -bit tag at random, it is expected to be correct for given data with probability 1/2 t . With GCM, however, an adversary can choose tags that increase this probability, proportional to the total length of the ciphertext and AAD. Consequently, GCM is not well-suited for use with short tag lengths or very long messages. In particular, if n denotes the total number of blocks in the encoding (i.e., the input to the GHASH function in the definition of S in Secs.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Block Cipher Modes of Operation_ Galois_Counter Mode (GCM) and GMAC."}]}
{"id": "nist_01948", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Securing Public Web Servers say about H? According to Guidelines on Securing Public Web Servers, H: Host-based intrusion detection and prevention software, 4-6 Hypertext Preprocessor (PHP), 6-14", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Securing Public Web Servers."}]}
{"id": "nist_01949", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Access Control Documents say about 4.3.3 PERFORMPAA? According to Secure Data Network Systems (SDNS) Access Control Documents, 4.3.3 PERFORMPAA: Inputs; Message Originator's Composite ID Information Message Recipient's Composite ID Information Outputs: PAA Result = Pass/Fail Enforcement Vector (EV) Error Condition Functionality; The purpose of the Perform PAA function is to compare both the message originator's and message recipient's Composite ID information to determine whether or not a commonly held set of security attributes exists on which an association can be based. In the PAA procedure, a UA is responsible for calling all the PAA functionality which the local configuration dictates. For a detailed description of PAA refer to section 4. 1 If PAA is successfully completed then PAA Result = Pass, and the EV is passed to the Perform PAE function so that it can perform its processing If the PAA is unsuccessful then PAA Result = Fail and an error condition is generated The error condition generated by a failed PAA would indicate that no allowable set of communications exists between the two peers, this is an access control decision. In the case of an outgoing multicast message, this error condition is only tied to the specific recipient for . whom the attempt to perform PAA is made. If PAA fails, control of the processing is returned to the MSP along with the appropriate error condition.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Access Control Documents."}]}
{"id": "nist_01950", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Wireless Infusion Pumps in Healthcare Delivery Organizations provide? (Section 392) s, J. Martin, Ed., J. Burbank, and W. Kasch, Network Time Protocol Version 4: Protocol and Algorithms Specification, Internet Engineering Task Force (IETF) Request for Comments (RFC) 5905, June 2010. https://www.ietf.org/rfc/rfc5905.txt [accessed 2/7/18]. [12] U.S. Department of Commerce. Announcing the Advanced Encryption Standard (AES), Federal Information Processing Standards (FIPS) Publication 197, November 2001. http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.197.pdf [accessed 2/7/18]. [13] Cisco Wireless Controller Configuration Guide, Release 8.0, Cisco [Web site], guide/b_cg80.html [accessed 2/7/18]. [14] D. Simon, B. Aboba, and R. Hurst, The EAP-TLS Authentication Protocol, Internet Engineering Task Force (IETF) Network Working Group Request for Comments (RFC) 5216, March 2008. https://www.ietf.org/rfc/rfc5216.txt [accessed 2/7/18]. [15] C. Rigney, S. Willens, A. Rubens, and W. Simpson, Remote Authentication Dial In User Service (RADIUS), Internet Engineering Task Force (IETF) Network Working Group Request for Comments (RFC) 2865, June 2000. https://tools.ietf.org/html/rfc2865 [accessed 2/7/18]. [16] [17] S. Santesson, M. Myers, R. Ankney, A. Malpani, S. Galperin, and C. Adams, X.509 Internet Public Key Infrastructure Online Certificate Status Protocol \u2013 OCSP, Internet Engineering Task Force (IETF) Request for Comments (RFC) 6960, June 2013. https://tools.ietf.org/html/rfc6960 [accessed 2/7/18]. Symantec\u2122 Data Center Security: Server, Monitoring Edition, and Server Advanced 6.7 MP1 Planning and Deployment Guide, Symantec [Web site], Center-Security:-Server-Advanced-6.7-or-6.7-MP1/?locale=EN_US [accessed 2/7/18]. NIST SP 1800-8C: Securing Wireless Infusion Pumps 257", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Securing Wireless Infusion Pumps in Healthcare Delivery Organizations."}]}
{"id": "nist_01951", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to NIST_SP_800-53r5_Security_Privacy_Controls? Discussion: Automated tools and mechanisms include host-based, network-based,", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01952", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Stateful Hash-Based Signature Schemes say about B.2? (Part 5) According to Recommendation for Stateful Hash-Based Signature Schemes, B.2: type) { case xmssmt-sha2_20/2_192: case xmssmt-sha2_40/2_192: case xmssmt-shake256_20/2_256: case xmssmt-shake256_40/2_256: case xmssmt-shake256_20/2_192: case xmssmt-shake256_40/2_192: xmss_reduced xmss_red_arr_d2[2]; case xmssmt-sha2_60/3_192: case xmssmt-shake256_60/3_256: case xmssmt-shake256_60/3_192: xmss_reduced xmss_red_arr_d3[3]; case xmssmt-sha2_20/4_192: case xmssmt-sha2_40/4_192: case xmssmt-shake256_20/4_256: case xmssmt-shake256_40/4_256: case xmssmt-shake256_20/4_192: case xmssmt-shake256_40/4_192: xmss_reduced xmss_red_arr_d4[4]; case xmssmt-sha2_60/6_192: case xmssmt-shake256_60/6_256: case xmssmt-shake256_60/6_192: xmss_reduced xmss_red_arr_d6[6]; case xmssmt-sha2_40/8_192: case xmssmt-shake256_40/8_256: case xmssmt-shake256_40/8_192: xmss_reduced xmss_red_arr_d8[8]; case xmssmt-sha2_60/12_192: case xmssmt-shake256_60/12_256: case xmssmt-shake256_60/12_192: ``` ``` xmss_reduced xmss_red_arr_d12[12]; }; /* Types for bitmask seed */ union seed switch (xmssmt_algorithm_type type) { case xmssmt-sha2_20/2_192: case xmssmt-sha2_20/4_192: case xmssmt-sha2_40/2_192: case xmssmt-sha2_40/4_192: case xmssmt-sha2_40/8_192: case xmssmt-sha2_60/3_192: case xmssmt-sha2_60/6_192: case xmssmt-sha2_60/12_192: case xmssmt-shake256_20/2_192: case xmssmt-shake256_20/4_192: case xmssmt-shake256_40/2_192: case xmssmt-shake256_40/4_192: case xmssmt-shake256_40/8_192: case xmssmt-shake256_60/3_192: case xmssmt-shake256_60/6_192: case xmssmt-shake256_60/12_192: bytestring24 seed_n24; case xmssmt-shake256_20/2_256: case xmssmt-shake256_20/4_256: case xmssmt-shake256_40/2_256: case xmssmt-shake256_40/4_256: case xmssmt-shake256_40/8_256: case xmssmt-shake256_60/3_256: case xmssmt-shake256_60/6_256: case xmssmt-shake256_60/12_256: bytestring32 seed_n32; }; /* Types for XMSS^MT root node */ union xmssmt_root switch (xmssmt_algorithm_type type) { case xmssmt-sha2_20/2_192: case xmssmt-sha2_20/4_192: case xmssmt-sha2_40/2_192: case xmssmt-sha2_40/4_192: case xmssmt-sha2_40/8_192: case xmssmt-sha2_60/3_192: case xmssmt-sha2_60/6_192: case xmssmt-sha2_60/12_192: ``` ``` case xmssmt-shake256_20/2_192: case xmssmt-shake256_20/4_192: case xmssmt-shake256_40/2_192: case xmssmt-shake256_40/4_192: case xmssmt-shake256_40/8_192: case xmssmt-shake256_60/3_192: case xmssmt-shake256_60/6_192: case xmssmt-shake256_60/12_192: bytestring24 root_n24; case xmssmt-shake256_20/2_256: case xmssmt-shake256_20/4_256: case xmssmt-shake256_40/2_256: case xmssmt-shake256_40/4_256: case xmssmt-shake256_40/8_256: case xmssmt-shake256_60/3_256: case xmssmt-shake256_60/6_256: case xmssmt-shake256_60/12_256: bytestring32 root_n32; }; ```", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Stateful Hash-Based Signature Schemes."}]}
{"id": "nist_01953", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services provide? (Section 155) ce, such as PNT interference or corrections for leap seconds. There are four Subcategories within the Communications category that apply to the PNT Profile, as summarized in the table below. Table 19. Communications Subcategories Applicable to PNT | Respond Communications Subcategory | Applicability to PNT | References (PNT-Specific) | |-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | CO-1: Personnel know their roles and order of operations when a response is needed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_01954", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Derived PIV Application and Data Model Test Guidelines provide? (Section 172) 0x5B byte, respectively) Note: In Step 2 it may be necessary to send the VERIFY command with a correct Derived PIV Application Password in order to prevent the retry counter from decrementing to zero. | |--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Expected Result(s) | 1. From Step 1, the command returns the application property template with the status word '90 00'. 2. From Step 2, the command returns either status word: 1) '6A 80' (incorrect parameter in command data field) or 2) '63 CX' and the retry counter is decremented by 1 (where 'X' is the number of tries remaining). | | Postcondition(s) | Current password is unchanged.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_01955", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Applications Using Approved Hash Algorithms provide? (Section 38) umber generators were either specified or approved by reference in FIPS 186-2 [FIPS 186-2]; however, their use is limited (see SP 800-131A [SP 800-131A]). RBGs may be constructed using hash functions. The hash function used by the RBG shall be selected so that the RBG can provide a security strength that meets or exceeds the minimum security strength required for the random bits that it generates. See SP 80057, Part 1, for the security strength that can be provided for each approved hash function for random number generation. | [SP 800-38B] | NIST Special Publication (SP) 800-38B, Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication, May 2005. | |----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| | [SP 800-38C] | NIST Special Publication (SP) 800-38C, Recommendation for Block Cipher Modes of Operation: the CCM Mode for Authentication and Confidentiality, July 2007. | | [SP 800-38D] | NIST Special Publication (SP) 800-38D, Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC, November 2007. | | [SP 800-56A] | NIST Special Publication (SP) 800-56A, Recommendation for Pair-Wise Key Establishment | 5 Commonly known as deterministic random bit generators or pseudorandom number generators. | | Schemes Using Discrete Logarithm Cryptography, March 2007. | |---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [SP 800-56B] | NIST Special Publication (SP) 800-56B, Recommendation for Pair-Wise Key Establishment Using Integer Factorization Cryptography, August 2009.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Recommendation for Applications Using Approved Hash Algorithms."}]}
{"id": "nist_01956", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control BM-650 in Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard? (Part 53) Control BM-650: image --> Howard Crumb Federal Reserve Bank 33 Liberty Street New York, N. Y. 10045 The following paper has been extracted from the verbal presentation of Mr. Crumb at the February 15th Conference. A written paper had not been submitted at the time of publication of these proceedings. ## 1. Introduction This afternoon I plan to discuss the Federal Reserve Communications System, some of our concerns for security, and the type of operations that the communications system supports. The Federal Reserve System was created by an act of Congress in 1913. Its job was to insure an orderly economic growth, supervise and regulate banks, act as a fiscal agent for the United States Treasury, and provide for an improved collection system. The United States is divided into twelve Federal Reserve regions and there is a Federal Reserve bank in each of the regions. Each bank is an independent corporation. The overall guidance for the Federal Reserve system comes from its Board of Governors located in Washington, D. C. However, each of the banks is responsible for its own operation. ## 2. FEDWIRE Communications System With this introduction, I would like to talk about the communications system between these banks frequently referred to as the FEDWIRE. This system is used to transfer balances between Federal Reserve member banks throughout the country. There was a manual system before FEDWIRE was installed consisting of couriers which transferred money among the member banks, and as a result was vulnerable to those hazards and threats affecting physical transportation. The FEDWIRE was developed to eliminate charges for transfer of funds imposed by the courier system and to make the transfer of funds much faster. The FEDWIRE consists of a central communications site at Culpeper, Virginia and communication lines to each of the Federal Reserve Banks. Similarly, each Federal Reserve Bank is linked to its member banks within its own region or district.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard."}]}
{"id": "nist_01957", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security Requirements for Controlled Unclassified Information provide? (Section 99) and the system. A.03.15.03.d[01]: the rules of behavior are reviewed &lt;A.03.15.03.ODP[01]: frequency&gt; . A.03.15.03.d[02]: the rules of behavior are updated &lt;A.03.15.03.ODP[01]: frequency&gt; . [SELECT FROM: security planning policy and procedures; rules of behavior for system users; signed acknowledgements of rules of behavior; records for rules of behavior reviews and updates; system security plan; other relevant documents or records] [SELECT FROM: personnel with rules of behavior establishment, review, and update responsibilities; personnel with literacy training and awareness responsibilities; personnel with role-based training responsibilities; authorized users of the system who have signed rules of behavior; personnel with information security responsibilities] NIST SP 800-171Ar3 May 2024 [SELECT FROM: processes for establishing, reviewing, disseminating, and updating rules of behavior; mechanisms for supporting or implementing the establishment, dissemination, review, and update of rules of behavior] Source Assessment Procedure: PL-04 Determine if: A.03.16.01.ODP[01]: systems security engineering principles to be applied to the development or modification of the system and system components are defined. A.03.16.01: &lt;A.03.16.01.ODP[01]: systems security engineering principles&gt; are applied to the development or modification of the system and system components.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_01958", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0 say about Cybersecurity Framework Alignment:? (Part 36) According to NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0, Cybersecurity Framework Alignment:: ate 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-P6: Effectiveness of protection technologies is shared. | | | 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-P7: Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are established, in place, and managed. | | | 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-P8: Response and recovery plans are tested. | | | 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-P9: Privacy procedures are included in human resources practices (e.g., deprovisioning, personnel screening). | | | 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-P10: A vulnerability management plan is developed and implemented. | | | appropriate data processing safeguards. | Identity Management, Authentication, and Access Control (PR.AC-P): Access to data and devices is limited to authorized individuals, processes, and devices, and is managed consistent with the assessed risk of unauthorized access.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, incident response. Contains technical security guidance that could inform defensive posture. Source: NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0."}]}
{"id": "nist_01959", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in 2016 NIST_ITL Cybersecurity Program Annual Report? (Part 212) Control HA-3: d methods to effectively monitor and detect data corruption in commodity components (server, operating system, applications, and software configurations) as well as custom applications and data. The project also explored issues of auditing and reporting (user activity monitoring, file system monitoring, database monitoring, scanning backups/snapshots for malware and rapid recovery solutions) to support recovery and investigations. To address real-world business challenges around data integrity, the resulting example solution was composed of open-source and commercially available components. Ultimately, this project resulted in a publicly available NIST Cybersecurity Practice Guide-a description of the solution and practical steps needed to implement an example solution that addresses these existing challenges. ## Domain Name System-Based Security for Electronic Mail ## https:/ /nccoe.nist.gov/projects/building\\_blocks/secured\\_ email The Domain Name System-Based Security for Electronic Mail project produced a proof-of-concept security platform that demonstrated trustworthy email exchanges across organizational boundaries. The product of the project was a security platform that included the authentication of mail servers, the signing and encryption of email, and binding cryptographic key certificates to the servers; it also included a practice guide that explained how to configure and use the demonstrated platform to satisfy both operational and security requirements. Domain Name System Security Extension (DNSSEC) protocols were used to authenticate server addresses and certificates by binding the X.509 certificates used for TLS to DNS names verified by DNSSEC.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_01960", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Introduction to Cybersecurity for Commercial Satellite Operations provide? (Section 49) The selection of the subcategories results in Table 5 , which is the Target Profile. These include NIST references and those from other sources, such as Standards Development Organizations (SDOs), the Committee on National Security Systems Instruction (CNSSI) 1200, and others that are relevant to the organization. Table 5. Target Profile | Functions | | Informative Reference | Informative Reference | |-------------|---------------------------------------------------------------------------------------------|--------------------------------------------------------------|---------------------------------------------------------------------| | | Subcategories | SP 800-53, Rev. 4 | SP 800-53, Rev. 5 | | Identify | ID.RA-1: Asset vulnerabilities are identified and documented. | CA-2, CA-7, CA- 8, RA3, RA-5, SA-5, SA-11, SI- 2, SI-4, SI-5 | CA-2, CA-7, CA-8, RA-3, RA-5, SA-5, SA-11, SI-2, SI-4, SI- 5, PM-15 | | | ID.RA-2: Cyber threat intelligence is received from information-sharing forums and sources. | SI-5, PM-15, PM-16 | SI-5, PM-15, PM-16, RA-10 | | Functions | Subcategories | Informative SP 800-53, Rev. 4 | Reference SP 800-53, Rev.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Introduction to Cybersecurity for Commercial Satellite Operations."}]}
{"id": "nist_01961", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Training & Awareness Course Compendium say about VENDOR:? (Part 1) According to Computer Security Training & Awareness Course Compendium, VENDOR:: VENDOR: USDA Graduate School 600 Maryland Ave., S.W. Washington, D.C. 20024 (202) 382-8620 Internal auditors have a major role in reviewing the security and controls in sensitive automated systems. This course provides practical guidelines ant techniques for auditing and evaluating the adequacy of security and internal controls in sensitive automated systems. Major problem areas are discussed and examples illustrating the results of inadequate security and controls are presented. In addition, the responsibilities of management, internal audit, and data processing personnel are discussed. This course also provides the attendee with a comprehensive methodology for conducting security and internal control audits of sensitive data processing systems. Using a case study approach, the course illustrates how to identify and quantify the vulnerabilities of automated systems to fraud, disclosure, delay and other threats. The internal control techniques which can be applied to address these vulnerabilities are discussed, as well as the requirements of OMB circulars A- 127 and A-130. COURSE TITLE: Fundamentals of Computer Security for Federal Information Systems COURSE LENGTH: 5 DAY VENDOR: USDA Graduate School 600 Maryland Ave., S.W. Washington, D.C. 20024 (202) 447-7124 This five-day course provides those responsible for computer security with an overview of security issues specifically related t the federal government. Designed to introduce and cover the fundamentals areas of concern facing computer security officers, from mainframe to PC's. The objectives are covered by lecture, group discussion, slide and video presentations. The instructor will provide extensive insights into computer security based on operational experiences. In addition, hands-on risk analysis exercises will be performed. The student will be provided with extensive materials, including demonstration diskettes and public domain anti-virus software.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Training & Awareness Course Compendium."}]}
{"id": "nist_01962", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SR-12 in NIST_SP_800-53r5_Security_Privacy_Controls? (Part 80) Control SR-12: t of criteria for the provision of security services. [SP 800-160-1 adapted] security policy filter A set of rules that governs all aspects of security-relevant system and system component behavior. A hardware and/or software component that performs one or more of the following functions: content verification to ensure the data type of the submitted content; content inspection to analyze the submitted content and verify that complies with a defined policy; malicious content checker that evaluates the content for malicious code; suspicious activity checker that evaluates or executes the content in a safe manner, such as in a sandbox or detonation chamber and monitors for suspicious activity; or content sanitization, cleansing, and transformation, which modifies the submitted content to comply with a defined policy. APPENDIX A PAGE 417 NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ security requirement [FIPS 200, Adapted] security service [SP 800-160-1] security-relevant information selection operation T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : senior agency information security officer h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I senior agency official for privacy [OMB A-130] senior information security officer sensitive compartmented information [CNSSI 4009] A requirement levied on an information system or an organization that is derived from applicable laws, executive orders, directives, regulations, policies, standards, procedures, or mission/business needs to ensure the confidentiality, integrity, and availability of information that is being processed, stored, or transmitted.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01963", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.2 provide? (Section 26) strate some uses of XCCDF security checklists and tools. - \uf0b7 Scenario 1 - An industry consortium, in conjunction with a product vendor, wants to produce a security checklist for an application server. The core security settings are the same for all OS platforms on which the server runs, but a few settings are OS-specific. The consortium crafts one checklist for the core settings and writes several OS-specific ones that supplement the core settings. Users download the core checklist and the OS-specific checklists that apply to their installations, and then run an assessment tool to score their compliance with the checklists. - \uf0b7 Scenario 2 - An academic group produces a checklist for secure configuration of a particular server operating system version. A government agency issues a set of rules extending the academic checklist to meet more stringent user authorization criteria imposed by statute. A medical enterprise downloads both the academic checklist and the government extension, tailors them to fit their internal security policy, and uses them for an enterprise-wide audit using a commercial security audit tool. Reports outputted by the tool include remediation measures which the IT staff can use to bring their systems into full internal policy compliance. (Note that remediation processes should be carefully planned and implemented.) These scenarios demonstrate some of XCCDF's range of capabilities. XCCDF can represent complex conditions and relationships about the systems to be assessed, and it can incorporate descriptive material and remediative measures. It is also designed to be modular; for example, XCCDF benchmarks acquire programmatically ascertainable information through lower-level check system languages. The basic unit of structure for a checklist is a rule. A rule simply describes a state or condition which the target of the document should exhibit. A simple checklist might consist of a list of rules, but richer ones require additional structure.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.2."}]}
{"id": "nist_01964", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is FR according to A Framework for Designing Cryptographic Key Management Systems? FR: 6.108 A CKMS design shall specify the key revocation mechanism(s) and associated relying entity notification mechanism(s) used or available for use.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_01965", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Cyber Threat Information Sharing provide? (Section 48) ------------------------------------| | Phishing Email Samples | Email headers may contain information such as: \u2022 Mail agent IP addresses, \u2022 Host or domain names, and \u2022 Email addresses. An email message body may also contain PII, CUI, or other types of sensitive information. | Organizations should anonymize email samples and remove any sensitive information that is not necessary for describing an incident or event of interest. | | System, Network, and Application Logs | Log files may contain PII, CUI or other types of sensitive information. Log data may reveal IP addresses, ports, protocols, services, and URLs, as well as connection strings, logon credentials, portions of financial transactions, or other activities captured in URL parameters. | Organizations should perform IP address, timestamp, port, and protocol anonymization and remove any sensitive information that is not necessary for describing an incident or event of interest. Before sharing log data, it may also be necessary to sanitize URLs that contain identifying information such as session or user identifiers. Application logs may require redaction and anonymizing operations that are specific to particular application log formats. | | Malware Indicators and Samples | Although organizations are unlikely to encounter sensitive information in malware indicators or samples, sensitive information may be present depending on how targeted the malware is and what collection methods were used to gather a sample. | Organizations should remove PII, CUI, and other types of sensitive information that is not necessary for describing an incident or event of interest. | A variety of methods exist to designate handling requirements for shared threat information. These designations identify unclassified information that may not be suitable for public release and that may require special handling.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, cui. Contains guidance on protecting sensitive government information. Source: Guide to Cyber Threat Information Sharing."}]}
{"id": "nist_01966", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Guidance for First Responder Mobile and Wearable Devices say about B.1.3 Test 3: Device Ruggedization Ratings? (Part 1) According to Security Guidance for First Responder Mobile and Wearable Devices, B.1.3 Test 3: Device Ruggedization Ratings: B.1.3 Test 3: Device Ruggedization Ratings Security Objective(s) : Device availability and integrity through survivability, healthy mobile ecosystem through continuous operation, and ease of management in day-to-day operations. Test Description : Implementation of ruggedization ensures durability for First Responder applications and survivability of day-to-day use. This test identifies the Ingress Protection (IP) ratings and any ruggedization information available for the device. IP ratings are followed by two numbers that correspond with the device's protection. The first number defines protection against solid objects. The second number defines the device's protection against liquids. A larger number designates more protection against environmental particulate or liquids. The lowest and highest IP rating for a device is IP00 and IP69 respectively [6]. Physical survivability of First Responder mobile devices ensures the integrity of responder data. IP ratings and certification ensure data integrity by reducing the occurrence of device failure in extreme environments as well as reliable communications. Test Procedures: Utilizing the methodologies described in Test 1, obtain metrics to determine any certifications of ruggedization. Through local observation, inspect any protective surfaces or covers that enhance device survival in demanding environments. Check any fortifications that ensure battery operation or temperature threshold parameters. Test Outcome: Device ruggedization metrics and certifications are obtained through a combination of online documentation, product inserts, and queries to the manufacturer's technical support. Physical observations can also determine if a device is built specifically for First Responder applications. Attributes include, but are not limited to, features such as protective glass, fortified case, and high-impact plastics. The most common ruggedization standard utilized is the MIL-STD-810G [17].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Guidance for First Responder Mobile and Wearable Devices."}]}
{"id": "nist_01967", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Secure Web Services provide? (Section 44) e open standards communities that created Web services developed a number of security standards for Web services. Figure 2-9 illustrates a notional reference model for Web services security standards. This reference model maps the different standards to the different functional layers of a typical Web service implementation. These layers are modeled after the OSI Reference Model but are not intended to be interpreted as strictly hierarchical. Figure 2-9. Web Services Security Standards: Notional Reference Model <!-- image --> Standards at the network, transport and XML security layers are used to secure messages as they are transmitted over the network. The security standards IPsec, SSL/TLS (Secure Sockets Layer/Transport Layer Security), XML Encryption and XML Signature each operate on SOAP messages at a different level. Above the XML Security layer, there are two types of standards: standards built on top of SOAP and standalone standards. Message security standards WS-Security and WS-SecureConversation define how to use XML Signature, XML Encryption and credentials to secure SOAP at the message layer while reliable messaging standards define the protocols and constructs necessary to ensure that messages will be received. The access control standards are not unique to Web services; XACML can define the access policy for any system and SAML can be used to define assertions in any environment. The policy layer's WS-Policy defines a grammar to communicate the policy requirements of a Web service. These standards are described in more detail in Section 3. Security management specifications define other Web services to manage credentials such as PKI certificates within the SOA. Identity management standards take advantage of access control standards, policy standards and SOAP standards to offer services for distributing and managing user identities and credentials within the SOA.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, identity management, pki. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services."}]}
{"id": "nist_01968", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Key Management Documents say about 7. Attribute Negotiation Service? According to Secure Data Network Systems (SDNS) Key Management Documents, 7. Attribute Negotiation Service: The KMASE K-TEK-ATTRIBUTES service provides the attribute negotiation activities. The K-TEK-ATTRIBUTES service verifies the cryptographic compatibility with the TEK, negotiates the communication and security attributes associated with the TEK, and exchanges Compromised Key List (CRL) numbers. Additionally, K-TEK-ATTRIBUTES allows a KMAP to associate the attributes of a previous TEK with a new TEK. The K-TEK-ATTRIBUTES parameters are illustrated in Table 1. Table 1 - K-TEK-ATTRIBUTES parameters | Parameter Name | Req | ind | rsp | cnf | |------------------|-------|----------|-------|--------| | init-kid | | | M | M( = ) | | resp-kid | M | M( = ) | | | | proposed-options | U | U( = ) | | | | selected-options | | | M | M( = ) | | add-info | U | U( = ) | U | U( = ) | | old-resp-kid | U | U{ = ) | | | | cri-ver | M | IVI( = ) | | | | result | | | M | M( = ) | Legend: blank - not applicable M - presence is mandatory U - presence is user option = - p value is semantically equal to value to its left in the table", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_01969", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain tampering according to NIST Engineering Trustworthy Secure Systems According to Engineering Trustworthy Secure Systems, tampering: An intentional but unauthorized act resulting in the modification of a system, components of systems, its intended behavior, or data. [89]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_01970", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 916) f processing information with different classifications and categories that simultaneously permits access by users with different security clearances and denies access to users who lack authorization. multiple security levels [CNSSI 4009] Capability of a system that is trusted to contain, and maintain separation between, resources (particularly stored data) of different security domains. APPENDIX A PAGE 408 h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ national security system [OMB A-130] T h s i p u b l i c a t i o n i s network network access nonce [SP 800-63-3] nondiscretionary access control nonlocal maintenance Any 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\u2014(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. A system implemented with a collection of connected components.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, security clearance, national security. Contains guidance on protecting sensitive government information. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_01971", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Organizations should ensure that the mail clients are deployed, configured, and used properly to meet the security requirements of the organization. according to NIST Guidelines on Electronic Mail Security According to Guidelines on Electronic Mail Security, Organizations should ensure that the mail clients are deployed, configured, and used properly to meet the security requirements of the organization.: In many respects, the client side of email represents a greater risk to security than the mail server. Numerous issues need to be carefully considered and addressed to provide an appropriate level of security for mail clients. Securely installing, configuring, and using mail client applications would generally include the following steps: - GLYPH&lt;c=31,font=/HABHKN+Webdings&gt; Patch and upgrade the mail client applications - GLYPH&lt;c=31,font=/HABHKN+Webdings&gt; Configure mail client security features, such as disabling automatic opening of messages and enabling anti-spam and anti-phishing features - GLYPH&lt;c=31,font=/HABHKN+Webdings&gt; Configure mailbox authentication and access - GLYPH&lt;c=31,font=/HABHKN+Webdings&gt; Secure the client host's operating system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_01972", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation say about 5.2 Combined ROV and RPKI Reference Architecture Example? (Part 1) According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, 5.2 Combined ROV and RPKI Reference Architecture Example: 5.2 Combined ROV and RPKI Reference Architecture Example Figure 5-4 depicts examples of all three reference architectures (ROV, hosted RPKI, and delegated RPKI) in one realistic network diagram. It shows three ASes (AS A, AS B, and AS C), each of which is capable of participating in RPKI -based ROV, both as a network operator and as an address holder. Figure 5-4 also includes icons representing RIR RPKI C As and repositories. Figure 5-4 Example ROV and RPKI Reference Architectures <!-- image --> Viewing the architecture in Figure 5-4, in terms of its depiction of address holders, AS A represents an address holder that is implementing the delegated model of RPKI. T his AS has set up its own CA and repository and is responsible for creating, signing, and storing ROAs for the addresses that it holds and for any addresses that it may sub-allocate to its customers. ROAs for all addresses that have been allocated to AS A must be downloaded from the repository that is associated with AS A. Assuming that AS A received its address allocation from an RIR, that RIR's repository will point to AS A's repository. On the other hand, AS B and AS C represent address holders that are implementing the hosted model of RPKI. They have not set up their own CA or repositories. When they want to have ROAs created for the addresses that they hold, they must request that the entity that allocated the addresses to them creates, signs, and stores the ROAs on their behalf. AS B or AS C may have received its address allocation from its RIR, in which case it would use a tool (i.e., a web interface to an RIR tool) to request that the RIR creates, manages, and stores its ROAs. Alternatively, AS B or AS C may have received its address allocation from its ISP (i.e., from AS A). In this case, it would rely on AS A to create, manage, and store its ROAs.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, sso. Contains security framework guidance for authentication systems. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_01973", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation say about 5.5 BGP Flow Specification (Flowspec)? (Part 22) According to Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation, 5.5 BGP Flow Specification (Flowspec): . 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. piir-nist-sp1800-14b-draft.pdf | | [NIST-CSF] | Cybersecurity Framework, National Institute of Standards and Technology [Web site], http://www.nist.gov/cyberframework/ | | [NIST-RIDR] | 'Robust Inter-Domain Routing,' NIST RIDR project. https://www.nist.gov/programs-projects/robust-inter-domain-routing | | [NIST-RPKI] | 'RPKI Deployment Monitor,' NIST's online monitor with Global and Regional views. https://rpki-monitor.antd.nist.gov/ | | [NIST-SRx] | BGP Secure Routing Extension (BGP-SRx): Open source Origin Validation and BGPsec Path Validation implementations in Quagga. | | [NSA-BGP] | 'A guide to Border Gateway Protocol (BGP) Best Practices,' NSA Technical Report, September 2018.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, csf. General security reference material without sensitive content. Source: Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation."}]}
{"id": "nist_01974", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case say about Prerequisites? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case, Prerequisites: Connectivity between your Linux clients and AD server: Ensure the Linux clients can reach the AD Domain Controller. Configure the appropriate DNS settings on the Linux client. Set the search domain to domain name of Active Directory. Verify the DNS-settings in the /etc/resolv.conf file of your Linux server. The following instructions are for a Debian/Ubuntu system: 1. Download the Centrify Express (CentrifyDC) free package from https://launchpad.net or https://www.centrify.com/express/linux/download/ as per CPU architecture of the Linux client. 2. Install the package: dpkg -i &lt;package\\_name&gt; 3. Install any dependencies if prompted. Re-run when done. 4. Run the command adlicense --express to activate the free express mode. <!-- image --> 5. Run the command: adjoin --workstation domain-name . This will prompt you to enter a Domain Administrator password. <!-- image --> 6. Run adinfo to verify the domain join status. The CentrifyDC mode should show as connected . 7. Login to the Linux host using AD credentials. - a. For example: ssh username.domain-name@hostname.domain-name - b. OR by entering &lt;Domain-Name\\Username&gt; on a Desktop based version 8. Enable sudo for AD-resources using the following steps - a. Add the following line in /etc/sudoers file (using the command visudo) to make an AD Domain Group a sudoer <!-- image --> ``` %adgroup ALL=(ALL) ALL ``` Where, adgroup , is a group from the Active directory. The group names from active directory are transformed into all lower-case letters with underscores replacing spaces. For instance, %domain\\_admins for the Domain Admins group.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case."}]}
{"id": "nist_01975", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-200901022 in Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171? (Part 46) Control PD-200901022: in awareness training for [ Assignment: organization- defined roles ] that are aligned with current threat scenarios and provide feedback to individuals involved in the training and their supervisors. | | x | | AT-6 | Training Feedback | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ TABLE C-3: AUDIT AND ACCOUNTABILITY REQUIREMENT MAPPINGS | SECURITY REQUIREMENTS | Defense-in-Depth Protection Strategy | Defense-in-Depth Protection Strategy | Defense-in-Depth Protection Strategy | NIST SP 800-53 Relevant Security Controls | |---------------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------| | | PRA | DLO | CRS | | | There are no enhanced security requirements for audit and accountability.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_01976", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identity and Access Management for Electric Utilities provide? (Section 72) twork is not connected to the NIST enterprise network. Table 5-1 lists the software and hardware components that we used in the build, as well as the specific function that each component contributes. NIST SP 1800-2B: Identity and Access Management for Electric Utilities 39 Table 5-1 Build Architecture Component List Product Vendor Component Name Function Dell Dell Dell VMware Microsoft Microsoft Windows Windows PowerEdge R620 Physical server hardware PowerConnect 7024 Physical network switch EqualLogic NAS vSphere vCenter Server Version 5.5 Windows Server 2012 r2 AD Server Virtual server and workstation environment Authentication and authority Windows 7 Information management Windows Server 2012 r2 Domain Name System (DNS) Server Structured Query Language (SQL) Server DNS Database AlertEnterprise Enterprise Guardian Interface and translation between the IdAM central store and the PACS management server Identity and access automation management application, IdAM provisioning Identity Manager Release 12.6.05 Build 06109.28 ISE Network Server 3415 Network access controller Catalyst 3650 Digital Certificates Ozone Authority Ozone Console Ozone Envoy Ozone Server TrustSec-enabled physical network switch Cloud certificate authority Central attribute management system Ozone administrative management console Enterprise identity store interface Ozone centralized attribute- based authorization server T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . CA Cisco Cisco GlobalSign MAG MAG MAG MAG NIST SP 1800-2B: Identity and Access Management for Electric Utilities 40 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_01977", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2014 Annual Report say about F E D E R A L I N F O R M AT I O N S E C U R I T Y M A N A G E M E N T A C T ( F I S M A ) I M P L E M E N T A T I O N P R O J E C T? (Part 5) According to Computer Security Division 2014 Annual Report, F E D E R A L I N F O R M AT I O N S E C U R I T Y M A N A G E M E N T A C T ( F I S M A ) I M P L E M E N T A T I O N P R O J E C T: on NIST standards and guidelines; and - Continued the development of a preliminary draft of SP 800-18 Revision 2, Guide for Developing Security Plans for Federal Information Systems and Organizations. In FY 2015, CSD intends to: - Finalize SP 800-53A Revision 4, Assessing Security and Privacy Controls in Federal Information Systems and Organizations; - P ublish an errata update to SP 800-53 Revision 4; - Begin the automation of the SP 800-53 revision and public comment process in support of more timely updates to counter threats and keep up with technological advancements; - Finalize SP 800-16, A Role-Based Model for Federal Information Technology / CyberSecurity Training; - Finalize SP 800-160, Systems Security Engineering: An Integrated Approach to Building Trustworthy Resilient Systems; - Publish the IPD of SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations; - Begin the development of SP 800-60 Revision 2, Guide for Mapping Types of Information and Information Systems to Security Categories; - Finalize SP 800-18 Revision 2, Guide for Developing Security Plans for Federal Information Systems and Organizations; - Expand cybersecurity outreach to include additional state, local, and tribal governments, as well as private sector organizations and academic institutions; and - Continue to support federal agencies in the effective implementation of the NIST RMF. http:/ /csrc.nist.gov/groups/SMA/fisma", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_01978", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2011 Annual Report say about National Initiative for Cybersecurity Education (NICE)? (Part 2) According to Computer Security Division 2011 Annual Report, National Initiative for Cybersecurity Education (NICE): a Digital Nation.' This plan was developed from separate drafts that expressed the views of the four component areas into a comprehensive document that will be submitted for Cyber IPC approval. NIST organized and hosted the second annual NICE Workshop, ' Shaping the Future of Cybersecurity Education, ' held on September 20-22, 2011. The workshop served as a forum for the community to openly discuss progress, solutions, challenges, and proposals relating to the goals of the NICE program. Over 500 attendees from academia, government, and industry joined in the workshop, either in person or virtually through webinars/ webcasts. The participation of universities, community colleges, high schools, and other training associations, including international groups from Canada, Japan, Brazil and Italy, exceeded expectations. As part of its outreach role, the NIST NICE Leadership Team (NNLT) members also attended more than 100 events, symposia, forums, competitions, educational outreach meetings, and workshops to promote the initiative. In FY2012, NIST plans to finalize the NICE Strategic Plan, communications plan, and component-specific implementation plans and baseline studies. NIST will also continue to improve the NICE website and host the third annual NICE workshop. http://www.nist.gov/nice/ Contacts: Dr. Ernest McDuffie, NICE Project Lead (301) 975-8897 ernest.mcduffie@nist.gov Ms. Magdalena Benitez (301) 975-6182 mbenitez@nist.gov Mr. Bill Newhouse (301) 975-2869 william.newhouse@nist.gov Ms. Pat Toth (301) 975-5140 ptoth@nist.gov Ms. Richard Kissel (301) 975-5017 richard.kissel@nist.gov Ms. Celia Paulsen (301) 975-5981 celia.paulsen@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2011 Annual Report."}]}
{"id": "nist_01979", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events say about D.3 Test Case: Data Integrity IP-1? (Part 2) According to Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events, D.3 Test Case: Data Integrity IP-1: | | Description | Show that the DI solution can identify and resolve vulnerabilities and protect against ransomware. | | Associated Cybersecurity Framework Subcategories | ID.AM-1, ID.AM-2, ID.RA-1, ID.RA-2, ID.RA-6, DE.CM-8, PR.IP-12, RS.MI-3, PR.IP-4, PR.DS-1, PR.DS-6, PR.PT-1, PR.MA-2 | | Preconditions | User navigates to a malicious website and clicks on an ad for a virus cleaner. The virus cleaner is actually ransomware, which propagates across the domain and encrypts user files. | | Procedure | The denylisting capability is used to prevent access to and downloads from known malicious sites. The inventory capability is used to identify organizational assets and devices. The network protection capability is used to prevent the propagation of ransomware across the enterprise. The vulnerability management capability is used to identify vulnerabilities that allow malware to propagate. The integrity monitoring and logging collect integrity information and baseline the file system. | | Expected Results (pass) | The vulnerability that allows the ransomware to propagate is identified (CR 1.a). The user cannot access the site when it is blocked (CR 1.b). | | | The user cannot download the ransomware from the site when it is blocked (CR 1.c).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_01980", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-6 in NIST_SP_800-37r2_Risk_Management_Framework? (Part 127) Control AM-6: d and transferred to the plan of actions and milestones. Findings from a system-level control assessment may necessitate an update to the system risk assessment and the organizational risk assessment. 93 The updated risk assessments and any inputs from the senior accountable official for risk management or risk executive (function) determines the initial remediation actions and the prioritization of those actions. System owners and common control providers may decide, based on a system or organizational risk assessment, that certain findings are inconsequential and present no significant security or privacy risk. Such findings are retained in the security and privacy assessment reports and monitored during the monitoring step. The authorizing official is responsible for reviewing and understanding the assessor findings and for accepting the security and privacy risks (including any supply chain risks) that result from the operation the system or the use of common controls. In all cases, organizations review assessor findings to determine the significance of the findings and whether the findings warrant any further investigation or remediation. Senior leadership involvement in the mitigation process is necessary to ensure that the organization's resources are effectively allocated in accordance with organizational priorities-providing resources to the systems that are supporting the most critical missions and business functions or correcting the deficiencies that pose the greatest risk. References: [SP 800-53A]; [SP 800-160 v1] (Verification and Validation Processes). ## PLAN OF ACTION AND MILESTONES TASK A-6 Prepare the plan of action and milestones based on the findings and recommendations of the assessment reports. Potential Inputs: Updated security and privacy assessment reports; updated security and privacy plans; organization- and system-level risk assessment results; organizational risk management strategy and risk tolerance.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_01981", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Government Smart Card Interoperability Specification, Version 2.1? (Part 32) Control HA-1: integers. See Example 3 in the Section E.3 for more information. ## E.2.1 Variable Length String Data Ten BSI function calls accept and/or return variable-length string data identified in Table E-1. Table E-1: BSI functions using the discovery method | BSI function | Discovery buffer | Discovery length | |---------------------------------------------------|--------------------|--------------------| | gscBsiUtilGetVersion () | *uszVersion | *unVersionLen | | gscBsiUtilGetCardProperties () | *uszCCCUniqueID | *unCCCUniqueIDLen | | gscBsiUtilGetReaderList () | *uszReaderList | *unReaderListLen | | gscBsiUtilPassthru () (See Note in Section E.3.9) | *uszCardResponse | *unCardResponseLen | | gscBsiGcReadTagList () | *TagArray | *unNbTags | | gscBsiGcReadValue () | *uszValue | *unValueLen | | gscBsiGetChallenge () | *uszChallenge | *unChallengeLen | | gscBsiSkiInternalAuthenticate () | *uszCryptogram | *unCryptogramLen | | gscBsiPkiCompute () | *uszResult | *unResultLen | | gscBsiPkiGetCertificate () | *uszCertificate | *unCertificateLen | Each of these functions is invoked in the discovery mode by passing in a NULL value for the discovery buffer parameter. With the exception of gscBsiGcReadTagList () , each of these returns (Discovery call) the size in bytes (including the NULL Terminator) of the buffer needed to store the return variablelength string data. The lone exception, gscBsiGcReadTagList () , returns the number of tags in the tag array, so that the size of the array buffer needed is given by '*unNbTags * size of (GCtag)'.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_01982", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Privacy Controls for Information Systems and Organizations provide? (Section 244) zational system exchanges information and other systems. For mission-essential systems, services, and applications, including high value assets, it is necessary to identify such information exchanges. The transparency of the controls or protection measures in place in such downstream systems connected directly or indirectly to organizational systems is essential to understanding the security and privacy risks resulting from those information exchanges. Organizational systems can inherit risk from downstream systems through transitive connections and information exchanges, which can make the organizational systems more susceptible to threats, hazards, and adverse impacts. Related Controls: SC-7. References: [OMB A-130], [FIPS 199], [SP 800-47]. CA-4 SECURITY CERTIFICATION [Withdrawn: Incorporated into CA-2.] CA-5 PLAN OF ACTION AND MILESTONES Control: a. Develop a plan of action and milestones for the system to document the planned remediation actions of the organization to correct weaknesses or deficiencies noted during the assessment of the controls and to reduce or eliminate known vulnerabilities in the system; and b. Update existing plan of action and milestones [Assignment: organization-defined frequency] based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities. Discussion: Plans of action and milestones are useful for any type of organization to track planned remedial actions. Plans of action and milestones are required in authorization packages and subject to federal reporting requirements established by OMB. Related Controls: CA-2, CA-7, PM-4, PM-9, RA-7, SI-2, SI-12. CHAPTER THREE PAGE 88 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01983", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.3.4.1 The Information System and Assets Are Monitored to Identify Cybersecurity Events and Verify the Effectiveness of Protective Measures according to NIST Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity According to Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity, 5.3.4.1 The Information System and Assets Are Monitored to Identify Cybersecurity Events and Verify the Effectiveness of Protective Measures: This Cybersecurity Framework Subcategory is supported by the utility cyber monitoring and microgrid cyber monitoring components of the cyber demarcation point, and by the log analysis capability. Each of these monitors aspects of the system and identifies cybersecurity events.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity."}]}
{"id": "nist_01984", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Workstation Login according to NIST 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings According to 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings, Workstation Login: Workstation login that results in users having a personal certificate can be conducted in three ways: - With a user name and password using autoenroll certificates, - With a user name and password using KX.509 certificates (manual), or - With a smart card. The highlight of all logins is that, at the end of login, the user has both a Kerberos credential Fig.7: Authentication Communication From Logon to Application <!-- image -->", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_01985", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? (Part 241) Control HA-1: of a system are also its weaknesses. This is also true with off-line generation. Off-line generation makes key generation easy not only for legitimate users of of the system but for illegitimate ones. An issue that PKIs must consider in their design is that of a Directory Harvest Attack , in which senders of unwanted advertisements or outright fraudulent confidence games use the directory as a way to discover information paths into the system. Off-line generation of keys allows spammers and other attackers to to pre-generate email attacks in their own system or create a distributed system for encrypted attacks. These attacks are not an issue in off-line systems. Off-line generation has the disadvantage that there is complete transparency in the directory, since the directory is an algorithm. Anyone with that algorithm has all possible entries in the directory and their public keys, and this can be exploited in side-channel attacks that are not attacks on the cryptographic system per se , but the way the system is used. Off-line generation has as an additional disadvantage increased revocation problems. A conventional PKI must be able to re-issue certificates and handle for revisions in the PKI. An off-line IBE system must not only handle revocation of the certificates themselves but a revocation of the algorithmic parameters that comprise its own PKI. No IBE system before this one has even considered this real-world problem. In fact, the key advantages of this on-line system are that it considers and solves these real-world problems. ## 6.3 On-Line IBE for the On-Line World Sadly, trends in the real world make the advantages of off-line IBE moot, and turns its disadvantages into outright security problems. There is little need for off-line generation in an on-line world, and the advantages of off-line generation benefit attackers more than defenders. Nonetheless, IBE has desirable characteristics.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_01986", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Test Personal Identity Verification (PIV) Cards Version 2 say about Authority Key Identifier :? According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Authority Key Identifier :: A5:E9:44:0B:AA:5C:29:EC:B2:DF:5F:90:74:DC:A5:6F:58:65:54:35", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_01987", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to Security and Privacy Controls for Information Systems and Organizations? Discussion: Authentication feedback from systems does not provide information that would", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_01988", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Personal Identity Verification Card Management Report say about 2. Overview of Card Management Elements? According to Personal Identity Verification Card Management Report, 2. Overview of Card Management Elements: Card management is the term applied to the preparation of a smart card token before its issuance to the cardholder and the provision of administrative functions for the card during its lifetime of use in the possession of the cardholder. Card management is particularly important because it so basically affects the security characteristics of the card, and security is the raison d'etre of smart cards. In this section, the basic elements of card management will be considered.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Personal Identity Verification Card Management Report."}]}
{"id": "nist_01989", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Malware Incident Prevention and Handling for Desktops and Laptops provide? (Section 43) able to alter critical settings. Antivirus administrators should perform continuous monitoring to confirm that hosts are using current antivirus software and that the software is configured properly. Implementing all of these recommendations should strongly support an organization in having a strong and consistent antivirus deployment across the organization. A possible measure for improving malware prevention is to use multiple antivirus products for key hosts, such as email servers. For example, one antivirus vendor might have a new signature available several hours before another vendor, or an organization might have an operational issue with a particular signature update. Another possibility is that an antivirus product itself might contain an exploitable vulnerability; having an alternative product available in such cases could provide protection until the issue with the primary product has been resolved. Because running multiple antivirus products on a single host simultaneously is likely to cause conflicts between the products, if multiple products are used concurrently, they should be installed on separate hosts. For example, one antivirus product could be used on perimeter email servers and another on internal email servers. This could provide more effective detection of new threats, but also would necessitate increased administration and training, as well as additional hardware and software costs. Although antivirus software has become a necessity for malware incident prevention, it is not possible for antivirus software to stop all malware incidents. As discussed previously in this section, antivirus software does not excel at stopping previously unknown threats. Antivirus software products detect malware primarily by looking for certain characteristics of known instances of malware. This is highly effective for identifying known malware, but is not so effective at detecting the highly customized, tailored malware increasingly being used.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit, malware. Contains technical security guidance that could inform defensive posture. Source: Guide to Malware Incident Prevention and Handling for Desktops and Laptops."}]}
{"id": "nist_01990", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does PIV Data Model Test Guidelines say about A.4 Biometric Fingerprint Mapping? (Part 3) According to PIV Data Model Test Guidelines, A.4 Biometric Fingerprint Mapping: ithm in the SignerInfo is based on the expiration date of the PIV card and is in accordance wi 800-78. | | TE06.02.12.01 | digest signed attribute in 10.2.1.9: Verify message SignerInfo | tes. The tester shall validate the presence of a MessageDigest attribute in the signed attribu | | TE06.02.12.02 | ssage digest signed attribute in 10.2.1.9: Verify me SignerInfo | gest attribute against the hash of the The tester shall validate the value of the MessageDi concatenated CBEFF_HEADER and the STD_BIOMETRIC_RECORD. | | TE06.02.13.01 | 10.2.1.10: Verify PIV sig distinguishe ner d name | The tester shall validate the presence of a pivSigner- DN attribute in the signed attributes. | | DTR from Section 6 | Test Assertion from Section 10 | DTR Description | |----------------------|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | TE06.02.13.02 | 10.2.1.10: Verify PIV sig distinguishe ner d name | r- tric The tester shall validate the value of the pivSigne DN attribute is the same as the subject name that appears in the certificate that signed the biome data. | | TE06.02.14.01 | 10.2.1.11: Verify FASC-N | N .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_01991", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-512 in Computer Security Division 2009 Annual Report? (Part 73) Control HA-512: d terms. The search results show the detailed checklist metadata and a link to any SCAP content for the checklist, as well as links to any supporting resources associated with the checklist. Although checklists are encouraged for use in both the private and public sectors, federal agencies are required to use security configuration checklists from the NCP. In February 2008, revised Part 39 of the Federal Acquisition Regulation (FAR) was published. Paragraph (d) of section 39.101 states, 'In acquiring information technology, agencies shall include the appropriate IT security policies and requirements, including use of common security configurations available from the NIST website at . Agency contracting officers should consult with the requiring official to ensure the appropriate standards are incorporated.' In Memorandum M08-22, Office of Management and Budget (OMB) mandated the use of SCAP Validated products for continuous monitoring of Federal Desktop Core Configuration (FDCC) compliance. The NCP is defined in NIST SP 800-70 Revision 1, which can be found at http://csrc.nist.gov/publications/ , Contact: Mr. Stephen Quinn (301) 975-6967 stephen.quinn@nist.gov ## Security Content Automation Protocol (SCAP) Validation Program The Security Content Automation Protocol (SCAP) Validation Program performs conformance testing to ensure that products correctly implement SCAP . Conformance testing is necessary because SCAP is a complex specification consisting of six individual specifications that work together to meet various use cases. A single error in product implementation could result in undetected vulnerabilities or policy non-compliance within agency and industry networks. The SCAP Validation Program was created on request by the OMB to support the Federal Desktop Core Configuration (FDCC).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2009 Annual Report."}]}
{"id": "nist_01992", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report on Secure Hardware Assurance Reference Dataset (SHARD) Program say about //www.researchgate.net/publication/240767493\\_Verification\\_and\\_Fault\\_Localization\\_i n\\_VHDL\\_Programs? According to Report on Secure Hardware Assurance Reference Dataset (SHARD) Program, //www.researchgate.net/publication/240767493\\_Verification\\_and\\_Fault\\_Localization\\_i n\\_VHDL\\_Programs: Stefan Staber, Barbara Jobstmann, and Roderick Bloem. 2005. 'Finding and fixing faults.' In Advanced Research Working Conference on Correct Hardware Design and Verification Methods. Springer, pp. 35-49. https://www.semanticscholar.org/paper/Finding-and-fixi ng-faults-Jobstmann-Staber/e34670945b5be85db9866491510f6f441cfed7f1 - They have three examples in Figs. 6, 7, and 8. They are written in a Verilog-like language. - They 'assume that a (partial) specification is given in linear-time temporal logic (LTL) \u2026'. J. C. Madre, O. Coudert, and J. P. Billon. 1989. 'Automating the diagnosis and the rectification of design errors with PRIAM', In 1989 IEEE International Conference on ComputerAided Design. Digest of Technical Papers. 30-33. DOI: 10.1109/ICCAD.1989.76898 Claire Le Goues, Michael Dewey-Vogt, Stephanie Forrest, and Westley Weimer, 'A Systematic Study of Automated Program Repair: Fixing 55 out of 105 Bugs for $8 Each' in 2012 34th International Conference on Software Engineering (ICSE). Available at https: //clairelegoues.com/assets/papers/legoues12icse.pdf This deals with software, not hardware.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report on Secure Hardware Assurance Reference Dataset (SHARD) Program."}]}
{"id": "nist_01993", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Federal Computer Security Program Managers' Forum according to NIST Computer Security Division 2008 Annual Report According to Computer Security Division 2008 Annual Report, Federal Computer Security Program Managers' Forum: T he FCSPM Forum is covered in detail in the Outreach section of this report. Membership is free and open to federal employees. For further information, contact Ms. Marianne Swanson, (301) 975-3293, marianne. swanson@nist.gov.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2008 Annual Report."}]}
{"id": "nist_01994", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 1034) nal personnel with responsibili\ue000es for managing DNS]. [SELECT FROM: Mechanisms suppor\ue000ng and/or implemen\ue000ng data origin authen\ue000ca\ue000on and data integrity veri\ufb01ca\ue000on for name/address resolu\ue000on services]. SC-21(01) SECURE NAME/ADDRESS RESOLUTION SERVICE (RECURSIVE OR CACHING RESOLVER) | DATA ORIGIN AND INTEGRITY [WITHDRAWN: Incorporated into SC-21.] CHAPTER FOUR PAGE 564 Reference produced from open data h\ue003ps://github.com/usnistgov/oscal-content T h i s p u b l i c a \ue000 o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h \ue003 p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P. 8 0 0 - 5 3 A r 5 NIST SP 800-53A, REV. 5 ASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS SC-22 ARCHITECTURE AND PROVISIONING FOR NAME/ADDRESS RESOLUTION SERVICE ASSESSMENT OBJECTIVE: Determine if: SC-22[01] SC-22[02] SC-22[03] the systems that collec\ue000vely provide name/address resolu\ue000on services for an organiza\ue000on are fault-tolerant; the systems that collec\ue000vely provide name/address resolu\ue000on services for an organiza\ue000on implement internal role separa\ue000on; the systems that collec\ue000vely provide name/address resolu\ue000on services for an organiza\ue000on implement external role separa\ue000on. POTENTIAL ASSESSMENT METHODS AND OBJECTS: SC-22-Examine [SELECT FROM: System and communica\ue000ons protec\ue000on policy; procedures addressing architecture and provisioning for name/address resolu\ue000on services; access control policy and procedures; system design documenta\ue000on; assessment results from independent tes\ue000ng organiza\ue000ons; system con\ufb01gura\ue000on se\ue001ngs and associated documenta\ue000on; system audit records; system security plan; other relevant documents or records]. SC-22-Interview [SELECT FROM: System/network administrators; organiza\ue000onal personnel with informa\ue000on security responsibili\ue000es; organiza\ue000onal personnel with responsibili\ue000es for managing DNS].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_01995", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does General Access Control Guidance for Cloud Systems say about 5.8 Guidance for APIs? According to General Access Control Guidance for Cloud Systems, 5.8 Guidance for APIs: An API in the SaaS model serves as an interface between the cloud server and its users. The API should be designed to protect against both accidental and malicious attempts to circumvent any AC policy. Applications for organizations and third parties often build upon the APIs, which introduce the AC complexity of the new layered API. For example, if the APIs do not require memory access for their tasks, then the AC policy for the APIs should enforce the non-memory access. Additionally, AC policies should be specified to manage the authorization process for web APIs. For example, when APIs connect through SOAP and REST protocols, the AC should control whether to allow end users to interface between Microsoft or non-Microsoft tools and technologies. For authorized API connections through Simple Object Access Protocol (SOAP) and Representational State Transfer (REST) protocols, the AC should grant all related access requested by the protocols. For unauthorized API connections through these protocols, no access or partial access should be granted by the AC.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: General Access Control Guidance for Cloud Systems."}]}
{"id": "nist_01996", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for the Use of PIV Credentials in Facility Access say about A.8 Authentication Using On-Card Biometric Comparison (OCC-AUTH)? According to Guidelines for the Use of PIV Credentials in Facility Access, A.8 Authentication Using On-Card Biometric Comparison (OCC-AUTH): The PIV Card may optionally implement on-card biometric comparison (OCC). With OCC, biometric comparison data is stored on the card and cannot be read but may be used by the card to authenticate the cardholder. The OCC-AUTH authentication mechanism is implemented by performing OCC over secure messaging. The PACS authenticates the PIV Card as part of the process of establishing secure messaging, and the response from the PIV Card indicating that OCC was successful can be verified since the response includes a message authentication code. Therefore, OCC-AUTH provides two-factor authentication - something you have (i.e., the card via establishment of the secure messaging protocol with the PACS application) and something you are (i.e., a fingerprint via OCC). The OCC-AUTH authentication mechanism is highly resistant to cloning. However, it does not protect against use of a revoked card. Additionally, not all PIV Cards support OCCAUTH, as both secure messaging and OCC are optionally card capabilities. The recommendations in Section A.5 also apply to OCC-AUTH.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Use of PIV Credentials in Facility Access."}]}
{"id": "nist_01997", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Digital Signature Standard (DSS) provide? (Section 88) of a sequence corresponds to the most significant bit of the corresponding integer, and the last bit corresponds to the least significant bit. 1. b 1 , b 2 , \u2026 , bn The bit string to be converted. 1. C The requested integer representation of the bit string. 1. Let ( b 1 , b 2 , \u2026 , bn ) be the bits of b from leftmost to rightmost. 2. \ud835\udc36\ud835\udc36 = \u2211 2 ( \ud835\udc5b\ud835\udc5b-\ud835\udc56\ud835\udc56 ) \ud835\udc5d\ud835\udc5d \ud835\udc56\ud835\udc56 \ud835\udc5b\ud835\udc5b \ud835\udc56\ud835\udc56=1 3. Return C . In this standard, the binary length of an integer C is defined as the smallest integer n satisfying C &lt; 2 n . An integer x in the range 0 \u2264 x &lt; 2 n may be converted to an n -long sequence of bits by using its binary expansion as shown below: <!-- formula-not-decoded --> Note that the first bit of a sequence corresponds to the most significant bit of the corresponding integer, and the last bit corresponds to the least significant bit. 1. C 1. b 1, b 2, \u2026 , bn The bit string representation of the integer C . The non-negative integer to be converted. 1. Let ( b 1, b 2, \u2026 , bn ) represent the bit string, where bi = 0 or 1, and b 1 is the most significant bit, while bn is the least significant bit. 2. For any integer n that satisfies C &lt; 2 n , the bits bi shall satisfy: <!-- formula-not-decoded --> 3. Return b 1, b 2, \u2026 , bn . In this standard, the binary length of the integer C is defined as the smallest integer n that satisfies C &lt; 2 n . An integer may be converted to octet strings according to the following procedure: 1. Non-negative integers C and L , where C &lt;256 L . 1. Octet-string X of length L . 1. The integer C can be uniquely written as C = CL -1 256 L -1 + CL -2 256 L -2 + \u2026 + C 1 256 + C 0, where each coefficient Ci is an integer in the interval [0,255]. 2. Set X to the octet string ( CL -1 , CL2, \u2026, C 1, C 0); 3. Output X . An n -long sequence of bits { x 1 , \u2026 , x n } may be converted to an octet string according to the following procedure: 1. b 1 , b 2 , \u2026 , bn , the bit string to be converted. 2. N , an integer modulus. 1. Octet-string X of length L .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Digital Signature Standard (DSS)."}]}
{"id": "nist_01998", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations provide? (Section 75) a server to check whether the key size and algorithms presented in a client public-key certificate are acceptable is for the server to examine the public key and algorithm in the client's certificate. An indirect mechanism is to check that the certificate policies extension in the client public-key certificate indicates the minimum cryptographic strength of the signature and hashing algorithms used and for the server to perform certificate policy processing and checking. The server shall check the client key length if client authentication is performed and the server implementation provides a mechanism to do so. Federal agencies shall use the key size guidelines provided in SP 800-131A [10] to check the client key size. Clients may use the list of trust anchors sent by the server in the CertificateRequest message to determine if the client's certification path terminates at one of these trust anchors. The list sent by the server is known as a 'hints list.' When the server and client are in different PKI domains and the trust is established via direct cross-certification between the two PKI domains (i.e., the server PKI domain and the client PKI domain) or via transitive cross-certification (i.e., through cross-certifications among multiple PKI domains), the client may erroneously decide that its certificate will not be accepted by the server since the client's trust anchor is not sent in the hints list. To mitigate this failure, the server shall either: 1) maintain the trust anchors of the various PKIs whose subscribers are the potential clients for the server and include them in the hints list or 2) be configured to send an empty hints list so that the client can always provide a certificate it possesses. The hints list shall be distinct from the server's trust anchor store.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations."}]}
{"id": "nist_01999", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Engineering Trustworthy Secure Systems say about The Problem Context? (Part 1) According to Engineering Trustworthy Secure Systems, The Problem Context: The Problem Context The problem context defines the basis for an adequately secure system. It focuses on stakeholders' concerns about unacceptable losses given their mission, operational capability, and performance needs and concerns, as well as all associated cost, schedule, performance, and riskdriven constraints. The problem context enables the engineering team to focus on acquiring as complete an understanding of the stakeholder problem as practical, to explore all feasible solution class options, and to select the solution class option or options to be pursued. The problem context includes: - Defining security objectives - Defining security requirements - Determining measures of success - Determining life cycle security concepts 52 The security objectives are foundational, establishing and scoping what it means to be adequately secure in terms of protection against asset loss and the significance of such loss. The security objectives have associated measures of success. These measures of success constitute specific and measurable criteria relative to operational performance measures and stakeholder concerns. Measures of success include both the strength of protection and the level of assurance in the protection capability that has been engineered. These measures influence developing security requirements and assurance claims. Protection needs are determined based on the security objectives, life cycle concepts, and stakeholder concerns. The protection needs are subsequently transformed into stakeholder security requirements and associated constraints, as well as the measures needed to validate that all requirements have been met. A well-defined and stakeholder-validated problem definition and context provide the foundation for all systems engineering and systems security engineering and supporting activities.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_02000", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Intrusion Detection and Prevention Systems (IDPS) provide? (Section 77) nsive logging of data related to detected events. This data can be used to confirm the validity of alerts, to investigate incidents, and to correlate events between the IDPS and other logging sources. Data fields commonly logged by network-based IDPSs include the following: - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Timestamp (usually date and time) - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Connection or session ID (typically a consecutive or unique number assigned to each TCP connection or to like groups of packets for connectionless protocols) - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Event or alert type 21 - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Rating (e.g., priority, severity, impact, confidence) - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Network, transport, and application layer protocols - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Source and destination IP addresses - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Source and destination TCP or UDP ports, or ICMP types and codes - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Number of bytes transmitted over the connection - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Decoded payload data, such as application requests and responses - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; State-related information (e.g., authenticated username) 21 In the console, the event or alert type often links to supporting information for the specific vulnerability or exploit, such as references for additional information and associated Common Vulnerabilities and Exposures (CVE) numbers. - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Prevention action performed (if any). Most network-based IDPSs can also perform packet captures. Typically this is done once an alert has occurred, either to record subsequent activity in the connection or to record the entire connection if the IDPS has been temporarily storing the previous packets. Network-based IDPSs typically offer extensive and broad detection capabilities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Guide to Intrusion Detection and Prevention Systems (IDPS)."}]}
{"id": "nist_02001", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2012 Annual Report? (Part 123) Control HA-3: exploring and developing a model for revocation of credentials and attributes in a feGLYPH(cmap:df00)erateGLYPH(cmap:df00) environment, with a particular focus on identifying missing requirements. To address the use of biometrics in authentication for transactions online, NIST is considering highlevel requirements for the use of biometrics in a multi-factor authentication framework, such as liveness detection (sometimes called biometric spoof detection), biometric template protection (for revoking anGLYPH(cmap:df00) renewing biometric creGLYPH(cmap:df00)entials), anGLYPH(cmap:df00) web services stanGLYPH(cmap:df00)arGLYPH(cmap:df00)s for securely anGLYPH(cmap:df00) uniformly handling biometric data online. NIST is leading multiyear projects anGLYPH(cmap:df00) collaborating with the international research and standards communities in all three of these areas. With respect to liveness detection, NIST is leading the GLYPH(cmap:df00)evelopment of the first stanGLYPH(cmap:df00)arGLYPH(cmap:df00)s activity on liveness GLYPH(cmap:df00)etection anGLYPH(cmap:df00) helGLYPH(cmap:df00) a workshop to GLYPH(cmap:df00)iscuss a framework for measurement, interchangeable data, and testing in March 2012. On the topic of biometric template protection, a paper on 'Criteria TowarGLYPH(cmap:df00)s Metrics for Benchmarking Template Protection Algorithms' was published at this year's International Conference on Biometrics, the result of a grant from NIST anGLYPH(cmap:df00) collaboration with researchers in CSD. This work was followeGLYPH(cmap:df00) up with a workshop in July 2012, co-hosteGLYPH(cmap:df00) with Fraunhofer anGLYPH(cmap:df00) the Biometrics Institute, at the Association Fran\u00e7aise de Normalisation (AFNOR) (colocateGLYPH(cmap:df00) with a biometric stanGLYPH(cmap:df00)arGLYPH(cmap:df00)s meeting).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, sso. Contains security framework guidance for authentication systems. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_02002", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Derived PIV Application and Data Model Test Guidelines provide? (Section 44) ------------------------------------------------------------------------------------| | DTR-06.03.05.01 | Key reference '80' shall be able to be verified by the Derived PIV Application VERIFY command. | \u2022 [SP800-157], Appendix B.2 - Derived PIV Application Token Command Interface \u2022 [SP800-73], Part 2, Section 3.2.1 - VERIFY Card Command | | DTR-06.03.05.02 | When the key reference is '80' and the current value of the retry counter associated with the key reference is zero, then the comparison shall not be made, and the Derived PIV Application shall return the status word '69 83'. | \u2022 [SP800-157], Appendix B.2 - Derived PIV Application Token Command Interface \u2022 [SP800-73], Part 2, Section 3.2.1 - VERIFY Card Command | | DTR-06.03.05.03 | When the key reference is '80' and the authentication data in the command data field does not satisfy the criteria in Appendix B.2.1 of [SP800-157], then the token command shall fail and the Derived PIV Application shall return either the status word '6A 80' or '63 CX'. If status word '6A 80' is returned, the security status and the retry counter of the key reference shall remain unchanged. If status word '63 CX' is returned, the security status of the key reference shall be set to FALSE and the retry counter associated with the key reference shall be decremented by one.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token, sso. Contains security framework guidance for authentication systems. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_02003", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is INFO according to Identity and Access Management for Electric Utilities? INFO: ObjectIdentifierFactory Read 240.165 kb in 3.313 ms; Indexed 2,415 Arcs in", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_02004", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-2 in Proceedings of the Workshop of the Federal Criteria for Information Technology Security? (Part 8) Control AC-2: for Protection Profiles, Security Targets, and Products. ## Session Overview and General Observations The session began with an introductory briefing on the purpose and scope of the session tasking. The moderators provided background on how the current evaluation ch^ter evolved. This included working group discussions on whether the draft FC should include; 1. evaluation authorities and oigatuzational structures (e.g.. Trust Technology Assessment Program (TTAIO). 2. q)ecific forms of an evaluation process (e.g.. Trusted Produa Evaluation Program (TFEP) Process Improvement Team), 3. qualifications of evaluators, 4. specific evaluation techniques and methods, and/or 5. evaluation metrics. It was explained that it had been decided that the first three items this list were deemed to be out-of-scope because they are essentially business, a -sions and could change. Therefore only the last two items were addressed in the FC. it was also explained that this caused many reviewers to see this chapter as being incomplete. Finally, the moderator introduction included the presentation of the above 'key** questions prompted by a review of all the public commentary on evaluation assurance in the draft FC. This irutial context set a constructive tone and allowed the participatus to respond with positive direction and comments. The essentials of the session discussions are captured below. While the session was lightly attended, the scsdon had a good cross-section of interests and opiiuons. The participants consisted of approximately 9 individuals representing vendors, accreditors, integrators, European CCEB, National Computer Security Center (NCSC), National Security Agency (NSA), and evaluators. Their participation was generally lively and discussion extended well beyond the allowed session timeframe.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Proceedings of the Workshop of the Federal Criteria for Information Technology Security."}]}
{"id": "nist_02005", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ID-19 in Securing Telehealth Remote Patient Monitoring Ecosystem? (Part 328) Control ID-19: | 45 C.F.R. \u00a7\u00a7 164.308(a)(7)(ii)(D) 164.308(a)(8) 164.316(b)(2)(iii) | | RS.IM-2: Response strategies are updated. | N/A | N/A | 45 C.F.R. \u00a7\u00a7 164.308(a)(7)(ii)(D) 164.308(a)(8) | | RC.RP-1: Recovery plan is executed during or after a | N/A | N/A | 45 C.F.R. \u00a7\u00a7 164.308(a)(7) 164.308(a)(7)(i) 164.308(a)(7)(ii) 164.308(a)(7)(ii)(C) | | Cybersecurity Framework v1.1 Subcategory | Device Cybersecurity Capabilities | Manufacturer Nontechnical Supporting Capabilities | HIPAA Security Rule Mapping to Cybersecurity Framework Subcategory | |--------------------------------------------|-------------------------------------|-----------------------------------------------------|----------------------------------------------------------------------| | cybersecurity incident. | | | 164.310(a)(2)(i) 164.312(a)(2)(ii) | ## E-2 Device Capabilities Supporting Functional Evaluations Table E-2 below builds on the functional evaluations included in Section 6 of this document.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_02006", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1.3 Relationship to Other Publications according to NIST IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog According to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog, 1.3 Relationship to Other Publications: This publication directly relates to SP 800-213 [800-213]. It also follows from the foundational cybersecurity for IoT work from NIST documented in NISTIR 8228 [IR8228] and the NISTIR 8259 series [IR8259, IR8259A, IR8259B]. Direct mappings and references to SP 800-53 [80053] are also used in the catalog to show the connection between device cybersecurity requirements and security controls a federal organization may be using.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog."}]}
{"id": "nist_02007", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Application Whitelisting say about 3. Application Whitelisting Planning and Implementation? (Part 1) According to Guide to Application Whitelisting, 3. Application Whitelisting Planning and Implementation: 3. Application Whitelisting Planning and Implementation This section discusses considerations for planning and implementing application whitelisting technologies for end user devices. As with any new technology deployment, application whitelisting technology planning and implementation should be addressed in a phased approach. A successful deployment can be achieved by following a clear, step-by-step planning and implementation process. The use of a phased approach for deployment can minimize unforeseen issues and identify potential pitfalls early in the process. This model also allows for incorporating advances in new technology and adapting the technology to the ever-changing enterprise. The following is an example of planning and implementation phases: 1. Initiate the Solution. The first phase involves identifying current and future needs for application whitelisting; specifying requirements for performance, functionality, and security; and developing necessary policies. 2. Design the Solution. The second phase involves all facets of designing the application whitelisting solution. Examples include architectural considerations, whitelist management, cryptography policy, and security aspects of the solution itself. 3. Implement and Test a Prototype. The next phase involves implementing and testing a prototype of the designed solution in a lab or test environment. The primary goals of the testing are to evaluate the functionality, management, performance, and security of the solution. 4. Deploy the Solution. Once the testing is completed and all issues are resolved, the next phase includes the gradual deployment of the application whitelisting technology throughout the enterprise. 5. Manage the Solution. After the solution has been deployed, it is managed throughout its lifecycle. Management includes solution maintenance and support for operational issues.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Application Whitelisting."}]}
{"id": "nist_02008", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Considerations for Voice Over IP Systems provide? (Section 83) ages. In general, MEGACO/H.248 Packages include more detail than MGCP Packages. They define additional properties and statistics along with event and signal information that may occur on terminations. Figure 8: General Scenario for MEGACO/H.248 Usage <!-- image --> Megaco (RFC 3525) recommends security mechanisms that may be in underlying transport mechanisms, such as IPsec. H.248 goes a step further by requiring that implementations of the H.248 protocol implement IPsec if the underlying operating system and the transport network support IPsec. Implementations of the protocol using IPv4 are required to implement the interim AH scheme. H.248 states that implementations employing the AH header shall provide a minimum set of algorithms for integrity checking using manual keys (compliant to RFC 2402). The interim AH scheme is the use of an optional AH header, which is defined in the H.248 protocol header. The header fields are exactly those of the SPI, \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ SEQUENCE NUMBER and DATA fields as defined in RFC 2402. The semantics of the header fields are the same as the \"transport mode\" of RFC 2402, except for the calculation of the Integrity Check Value. For more details on the calculation of the ICV check H.248. The interim AH interim scheme does not provide protection against the eavesdropping and replay attacks. For MEGACO, manual key management is assumed and replay protection, defined for IPsec, may not be used in this scenario (the sequence number in the AH may overrun when using manual key management, since re-keying is not possible). Furthermore, H.248 states that implementations employing the ESP header shall provide a minimum set of algorithms for integrity checking and encryption (compliant to RFC 2402). Moreover, implementations should use IKE (RFC 2409) to permit more robust keying options.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_02009", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation provide? (Section 198) -step actions required to implement the test case. A procedure may consist of a single sequence of steps or multiple sequences of steps (with delineation) to indicate variations in the test procedure. | | Expected Results | The expected results for each variation in the test procedure, assuming that the test functions as intended. | The expected results for each variation in the test procedure, assuming that the test functions as intended. | The expected results for each variation in the test procedure, assuming that the test functions as intended. | | Actual Results | As expected or the observed results. | As expected or the observed results. | As expected or the observed results. | | Additional Comments (If Needed) | None. | None. | None. | During all harness tests, the RUT communicates the validation result of selected routes to an iBGP peer by using the Extended Community String specified in [RFC 8097] or via the regular community string using the type 0x4300 and values 0-2, as specified in [RFC 8097], only in 4-octet notation, rather than 8-octet notation. However, visual verification was used with appropriate show commands to verify the expected results with tests performed using hardware with a live RPKI data stream. The route validation results, as well as the RPKI table within the RUT, will be retrieved and logged. For all tests, the commands used are as follows: - To 'Verify that this route is installed in the routing table' and 'Verify that the RUT evaluates this route advertisement as valid, invalid, or not found,' use: show ip bgp . - To 'Verify that the RUT receives VRP information,' use: show ip bgp rpki table . - To 'Verify that this route is installed in the routing table' and 'Verify that the RUT evaluates this route advertisement as valid, invalid, or not found,' use: show table . - To 'Verify that the RUT receives VRP information,' use: show validation database . Test SIDR Requirement CR-1.1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_02010", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security and Privacy Controls for Information Systems and Organizations provide? (Section 565) canning coverage can be expressed as a percentage of components within the system, by the particular types of systems, by the criticality of systems, or by the number of vulnerabilities to be checked. Conversely, the depth of vulnerability scanning coverage can be expressed as the level of the system design that the organization intends to monitor (e.g., component, module, subsystem, element). CHAPTER THREE PAGE 243 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ Organizations can determine the sufficiency of vulnerability scanning coverage with regard to its risk tolerance and other factors. Scanning tools and how the tools are configured may affect the depth and coverage. Multiple scanning tools may be needed to achieve the desired depth and coverage. [SP 800-53A] provides additional information on the breadth and depth of coverage. Related Controls: None. (4) VULNERABILITY MONITORING AND SCANNING | DISCOVERABLE INFORMATION Determine information about the system that is discoverable and take [Assignment: organization-defined corrective actions]. Discussion: Discoverable information includes information that adversaries could obtain without compromising or breaching the system, such as by collecting information that the system is exposing or by conducting extensive web searches. Corrective actions include notifying appropriate organizational personnel, removing designated information, or changing the system to make the designated information less relevant or attractive to adversaries.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02011", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Authority Information Access : according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Authority Information Access :: CA Issuers - CA Issuers - ldap://smime2.nist.gov/cn=Expired%20Test%20RSA%202048- bit%20CA%20for%20Test%20PIV%20Cards,ou=Test%20CA,o=Test%20Certificates%20 2010,c=US?cACertificate;binary,crossCertificatePair;binary OCSP - Key Usage : critical Key Encipherment", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_02012", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is FR according to A Framework for Designing Cryptographic Key Management Systems? FR: 6.114 The CKMS design shall specify the mechanisms used to detect unauthorized modifications to the CKMS system hardware, software and data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_02013", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation say about E.2 Requirements? (Part 12) According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, E.2 Requirements: --|----------------------|------------------| | | | matches this route is added to the RPKI, so the route is re- evaluated as valid . | | | | CR-1.7.1 | | | IPv4 address type | SIDR- ROV- 1.7.1 | | CR-1.7.2 | | | IPv6 address type | SIDR- ROV- 1.7.2 | | CR-1.8 | | The advertised route is initially evaluated as invalid due to the presence of one ROA that covers this route, but that has an ASN different from that of the route's origin. This is the only ROA that covers the route. It is deleted from the RPKI, so the route is re- evaluated as not found .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_02014", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Wireless Infusion Pumps in Healthcare Delivery Organizations provide? (Section 326) . . o r g / 1 0 6 0 2 8 / N I S T . S P 1 8 0 0 - 8 . . Leader Automatic Channel Assignment Channel Assignment Mode........................ AUTO Channel Update Interval........................ 600 seconds Anchor time (Hour of the day).................. 0 Update Contribution Noise........................................ Enable Interference................................. Enable Load......................................... Disable Device Aware................................. Disable CleanAir Event-driven RRM option............... Disabled Channel Assignment Leader...................... wlc (192.168.250.2) (::) Last Run....................................... 21 seconds ago Last Run Time.................................. 0 seconds DCA Sensitivity Level.......................... MEDIUM (15 dB) DCA 802.11n/ac Channel Width................... 20 MHz DCA Minimum Energy Limit....................... -95 dBm Channel Energy Levels Minimum...................................... -127 dBm Average...................................... -127 dBm Maximum...................................... -127 dBm Channel Dwell Times Minimum...................................... 0 days, 00 h 00 m 19 s Average...................................... 0 days, 00 h 00 m 19 s Maximum...................................... 0 days, 00 h 00 m 19 s 802.11a 5 GHz Auto-RF Channel List Allowed Channel List......................... 36,40,44,48,52,56,60,64,100, 104,108,112,116,120,124,128, 132,136,140,144,149,153,157, 161 Unused Channel List.......................... 165 802.11a 4.9 GHz Auto-RF Channel List Allowed Channel List.........................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Wireless Infusion Pumps in Healthcare Delivery Organizations."}]}
{"id": "nist_02015", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control VE-20131763 in CVSS Implementation Guidance? (Part 36) Control VE-20131763: Analysis: Vector: AV:N/AC:M/Au:N/C:P/I:P/A:N Base Score: 5.8 CWE: CWE-601 - URL Redirection to Untrusted Site ('Open Redirect') | Metric | Value | Explanation | |-------------------|---------|------------------------------------------------------------------------------------------------------------| | Access Vector | Network | From keyword 'remote attackers' | | Access Complexity | Medium | From description 'users to arbitrary web sites and conduct phishing attacks' indicating victim interaction | | Authentication | None | Not required | | Confidentiality | Partial | From Table 2 Open Redirect Scoring Template | | Integrity | Partial | From Table 2 Open Redirect Scoring Template | | Availability | None | From Table 2 Open Redirect Scoring Template | ## A.20 CVE-2013-0900 - Use-After-Free ## CVE Description: Use-after-free vulnerability in Microsoft Internet Explorer 6 through 10 allows remote attackers to execute arbitrary code via a crafted web site that triggers access to a deleted object, aka \"Internet Explorer CCaret Use After Free Vulnerability.\" Analysis: Vector: AV:N/AC:M/Au:N/C:C/I:C/A:C Base Score: 9.3 CWE: CWE-416 - Use After Free | Metric | Value | Explanation | |-------------------|----------|-------------------------------------------------------------------------| | Access Vector | Network | From keyword 'remote attackers' | | Access Complexity | Medium | From description 'via a crafted web site' indicating victim interaction | | Authentication | None |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, cve-. Contains technical security guidance that could inform defensive posture. Source: CVSS Implementation Guidance."}]}
{"id": "nist_02016", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-3 in Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders? (Part 29) Control AC-3: enge, the signed FIDO assertion could not be used to authenticate to Google because the RP can also verify the application ID associated with the signed challenge, and it would not be the expected ID. A more advanced credential theft attack involves an active machine-in-the-middle that can intercept the user's requests to the legitimate RP and act as a proxy between the two. To avoid TLS server certificate validation errors, in this case, the attacker must obtain a TLS certificate for the legitimate RP site that is trusted by the user's device. This could be accomplished by exploiting a vulnerability in a commercial certificate authority; it presents a high bar for the attacker but is not unprecedented. Application ID validation is not sufficient to prevent this attacker from obtaining an authentication challenge from the RP, proxying it to the user, and using the signed assertion that they get back from the user to authenticate to the RP. To prevent this type of attack, the FIDO specifications permit token binding to protect the signed assertion that is returned to the RP by including information in the assertion about . the TLS channel over which it is being delivered. If there is a machine in the middle (or a proxy of any kind) between the user and the RP, the RP can detect it by examining the token-binding message included in the assertion and comparing it with the TLS channel over which it was received. Token binding is not widely implemented today, but with finalization of the token-binding specification in RFC 8471 [18] and related RFCs, adoption is expected to increase. Many of the federation threats discussed in Section 3.5.3 can be addressed by signing assertions, ensuring their integrity and authenticity.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_02017", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Roles and Assessment Methods according to NIST Automation Support for Security Control Assessments_ Software Asset Management According to Automation Support for Security Control Assessments_ Software Asset Management, Roles and Assessment Methods: | Determination Statement ID | Implemented By | Assessment Boundary | Assessment Responsibility | Assessment Methods | Selected | Rationale for Risk Acceptance | Frequency of Assessment | Impact of Not Implementing | |------------------------------|------------------|-----------------------|-----------------------------|----------------------|------------|---------------------------------|---------------------------|------------------------------| | CM-10(b){2} | DSM | ISCM-TN | MAN | TBD | | | | |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_02018", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST_SP_800-37r2_Risk_Management_Framework say about REQUIREMENTS DEFINITION? (Part 3) According to NIST_SP_800-37r2_Risk_Management_Framework, REQUIREMENTS DEFINITION: urity Framework Profile s defined for the organization. For instance, multiple requirements can be aligned and even deconflicted using the Function-CategorySubcategory structure of the Framework Core. The Profiles can then be used to inform the development of organizationally-tailored control baselines described in the RMF Prepare-Organization Level step, Task P-4. References: [SP 800-39] (Organization Level); [SP 800-64]; [SP 800-160 v1] (Stakeholder Needs and Requirements Definition Process); [SP 800-161] (Multi-Tiered Risk Management); [IR 8179]; [NIST CSF] (Core [Protect, Detect, Respond, Recover Functions]; Profiles).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: csf, rmf, fips. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_02019", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings say about 'Making PKI Easy to Use' Proceedings? According to 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings, 'Making PKI Easy to Use' Proceedings: William T. Polk Nelson E. Hastings Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Kent Seamons Brigham Young University July 2006 <!-- image --> U.S. DEPARTMENT OF COMMERCE Carlos M. Gutierrez, Secretary TECHNOLOGY ADMINISTRATION Robert Cresanti, Under Secretary of Commerce for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY William Jeffrey, Director 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings."}]}
{"id": "nist_02020", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1 provide? (Section 91) | users and systems is established and managed | ISO/IEC 27001:2013 A.12.1.1, A.12.1.2, A.13.1.1, A.13.1.2 NIST SP 800-53 Rev. 4 AC-4, CA-3, CM-2, SI-4 | | | and the potential impact of events is understood. | DE.AE-2: Detected events are analyzed to understand attack targets and methods | CIS CSC 3, 6, 13, 15 COBIT 5 DSS05.07 ISA 62443-2-1:2009 4.3.4.5.6, 4.3.4.5.7, 4.3.4.5.8 ISA 62443-3-3:2013 SR 2.8, SR 2.9, SR 2.10, SR 2.11, SR 2.12, SR 3.9, SR 6.1, SR 6.2 ISO/IEC 27001:2013 A.12.4.1, A.16.1.1, A.16.1.4 NIST SP 800-53 Rev. 4 AU-6, CA-7, IR-4, SI-4 | | | and the potential impact of events is understood. | DE.AE-3: Event data are collected and correlated from multiple sources and sensors | CIS CSC 1, 3, 4, 5, 6, 7, 8, 11, 12, 13, 14, 15, 16 COBIT 5 BAI08.02 ISA 62443-3-3:2013 SR 6.1 ISO/IEC 27001:2013 A.12.4.1, A.16.1.7 NIST SP 800-53 Rev. 4 AU-6, CA-7, IR-4, IR-5, IR-8, SI-4 | | | and the potential impact of events is understood. | DE.AE-4: Impact of events is determined | CIS CSC 4, 6 COBIT 5 APO12.06, DSS03.01 ISO/IEC 27001:2013 A.16.1.4 NIST SP 800-53 Rev. 4 CP-2, IR-4, RA-3, SI-4 | | | and the potential impact of events is understood. | DE.AE-5: Incident alert thresholds are established | CIS CSC 6, 19 COBIT 5 APO12.06, DSS03.01 ISA 62443-2-1:2009 4.2.3.10 ISO/IEC 27001:2013 A.16.1.4 NIST SP 800-53 Rev.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1."}]}
{"id": "nist_02021", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1 provide? (Section 45) s, the more rational, effective, and valuable its cybersecurity approach and investments will be. Over time, self-assessment and measurement should improve decision making about investment priorities. For example, measuring - or at least robustly characterizing - aspects of an organization's cybersecurity state and trends over time can enable that organization to understand and convey meaningful risk information to dependents, suppliers, buyers, and other parties. An organization can accomplish this internally or by seeking a third-party assessment. If done properly and with an appreciation of limitations, these measurements can provide a basis for strong trusted relationships, both inside and outside of an organization. To examine the effectiveness of investments, an organization must first have a clear understanding of its organizational objectives, the relationship between those objectives and supportive cybersecurity outcomes, and how those discrete cybersecurity outcomes are implemented and managed. While measurements of all those items is beyond the scope of the Framework, the cybersecurity outcomes of the Framework Core support self-assessment of investment effectiveness and cybersecurity activities in the following ways: - \uf0b7 Making choices about how different portions of the cybersecurity operation should influence the selection of Target Implementation Tiers, - \uf0b7 Evaluating the organization's approach to cybersecurity risk management by determining Current Implementation Tiers, - \uf0b7 Prioritizing cybersecurity outcomes by developing Target Profiles, - \uf0b7 Determining the degree to which specific cybersecurity steps achieve desired cybersecurity outcomes by assessing Current Profiles, and - \uf0b7 Measuring the degree of implementation for controls catalogs or technical guidance listed as Informative References. The development of cybersecurity performance metrics is evolving.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1."}]}
{"id": "nist_02022", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Understanding Stablecoin Technology and Related Security Considerations say about Exchanges and Fund Movement? According to Understanding Stablecoin Technology and Related Security Considerations, Exchanges and Fund Movement: This section discusses how centralized and decentralized cryptocurrency exchanges work from a technical perspective and how stablecoins can be transferred between different non-interoperable blockchains.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Understanding Stablecoin Technology and Related Security Considerations."}]}
{"id": "nist_02023", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Minimum Security Requirements for Federal Information and Information Systems say about 11. Waivers.? According to Minimum Security Requirements for Federal Information and Information Systems, 11. Waivers.: No provision is provided under FISMA for waivers to FIPS made mandatory by the Secretary of Commerce.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Minimum Security Requirements for Federal Information and Information Systems."}]}
{"id": "nist_02024", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is The senior information security officer is an organizational official responsible for according to Managing Information Security Risk_ Organization, Mission, and Information System View? The senior information security officer is an organizational official responsible for: (i) carrying out the chief information officer security responsibilities under FISMA; and (ii) serving as the primary liaison for the chief information officer to the organization's authorizing officials, information system owners, common control providers, and information system security officers. The senior information security officer: (i) possesses professional qualifications, including training and experience, required to administer the information security program functions; (ii) maintains information security duties as a primary responsibility; and (iii) heads an office with the mission and resources to assist the organization in achieving more secure information and information systems in accordance with the requirements in FISMA. The senior information security officer (or supporting staff members) may also serve as authorizing official designated representatives or security control assessors. The role of senior information security officer has inherent U.S. Government authority and is assigned to government personnel only.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Managing Information Security Risk_ Organization, Mission, and Information System View."}]}
{"id": "nist_02025", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain availability according to NIST Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN) According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN), availability: Any kind of malicious activity that attempts to collect, disrupt, deny, degrade, or destroy information system resources or the information itself. [NIST-SP-800-30r1]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)."}]}
{"id": "nist_02026", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does CVSS Implementation Guidance provide? (Section 49) ons upon a login, which allows physically proximate attackers to obtain credentials by resubmitting the login form via the back button of a web browser on an unattended workstation after an RT logout. Analysis: Vector: AV:L/AC:L/Au:N/C:P/I:P/A:P Base Score: 4.6 CWE: CWE-310 - Cryptographic Issues | Metric | Value | Explanation | |-------------------|---------|----------------------------------------------------------| | Access Vector | Local | From keyword 'physically proximate' | | Access Complexity | Low | No special conditions exist | | Authentication | None | Not required | | Confidentiality | Partial | Attacker obtains the credentials of the application user | | Integrity | Partial | Attacker obtains the credentials of the application user | | Availability | Partial | Attacker obtains the credentials of the application user | The Bluetooth stack in Microsoft Windows XP SP2 and SP3, and Vista Gold and SP1, allows physically proximate attackers to execute arbitrary code via a large series of Service Discovery Protocol (SDP) packets. From reference link [1], the range of the Bluetooth radio in this context is listed as 0 m to 100 m. Analysis: Vector: AV:A/AC:L/Au:N/C:C/I:C/A:C Base Score: 8.3 CWE: CWE-20 - Improper Input Validation | Metric | Value | Explanation | |-------------------|------------------|--------------------------------------------------------------------------------------------------------------------| | Access Vector | Adjacent Network | From keyword 'physically proximate' and within Bluetooth range. See Additional Considerations .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: CVSS Implementation Guidance."}]}
{"id": "nist_02027", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information provide? (Section 2) 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 Copyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax Approved by the NIST Editorial Review Board on YYYY-MM-DD [Will be added to final publication.] Fisher W, Ajmo J, Umarji S, Dog S, Russell M, Scarfone K (2025) Multi-Factor Authentication for Criminal Justice Information Systems: Implementation Considerations for Protecting Criminal Justice Information. (National Institute of Standards and Technology, Gaithersburg, MD), NIST internal Report (IR) NIST IR 8523. https://doi.org/10.6028/NIST.IR.8523 William Fisher: 0009-0004-7569-5668 Jason Ajmo: 0009-0007-4046-6146 Sudhi Umarji: 0000-0001-6842-8167 Spike Dog: 0009-0000-0201-6776 Mark Russell: 0009-0004-1273-392X Karen Scarfone: 0000-0001-6334-9486 psfr-nccoe@nist.gov National Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000 Additional information about this publication is available at including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). Most recent cybersecurity breaches have involved compromised credentials. Migrating from single-factor to multi-factor authentication (MFA) reduces the risk of compromised credentials and unauthorized access.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, mfa. Contains security framework guidance for authentication systems. Source: Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information."}]}
{"id": "nist_02028", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Control Baselines for Information Systems and Organizations say about 2.4 TAILORING CONTROL BASELINES? (Part 1) According to Control Baselines for Information Systems and Organizations, 2.4 TAILORING CONTROL BASELINES: 2.4 TAILORING CONTROL BASELINES After selecting an appropriate control baseline, organizations initiate a tailoring process to align the controls more closely with the specific security and privacy requirements identified by the organization. The tailoring process is part of an organization-wide risk management process that includes framing, assessing, responding to, and monitoring information security and privacy risks. Tailoring decisions are dependent on organizational or system-specific factors. While tailoring decisions are focused on security and privacy considerations, the decisions are typically aligned with other risk-related issues that organizations must routinely address. Risk-related issues such as cost, schedule, and performance are considered in the determination of which controls to employ and how to implement controls in organizational systems and environments of operation. 24 The tailoring process can include but is not limited to the following activities: 25 - Identifying and designating common controls - Applying scoping considerations - Selecting compensating controls - Assigning values to organization-defined control parameters via explicit assignment and selection operations - Supplementing baselines with additional controls and control enhancements - Providing specification information for control implementation Organizations use risk management guidance to facilitate risk-based decision making regarding the applicability of the controls in the baselines. Ultimately, organizations employ the tailoring process to achieve cost-effective solutions that support organizational mission and business needs and provide security and privacy protections commensurate with risk. Organizations have the flexibility to tailor at the organization level for systems in support of a line of business or a mission or business process, at the individual system level, or by using a combination of the two.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Control Baselines for Information Systems and Organizations."}]}
{"id": "nist_02029", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Effective Use of Computing Technology in Vote-Tallying provide? (Section 183) | / - ^ * uO | | V - | C\\J | CTi C\\J | '~ | | 1 | | X a | LO O o o o o | | o o | LO o o | o | oo o | LO o | o | Q. #^ If) 4-&gt; O 'rO O) SQ-&lt;+-O sO) JD E Z5 2: fO -M 0 1- | to -M U 0 C 0 -r- un cu | 0 , | CO n CO | CO CO r- | | r_ CO | 0 | | |---------------------------------|--------------|-----------|------------|----------|----------|------|----| | 00 +-> U 0 C 0 \u2022- 0 U CVJ 0) s- | CO CO cn Ln | cn 1 CO | , ro | LO <sD | , ro | 0 | , | | U 0 c CXD 0 \u2022.- 0 u 1- | CTi | 0 CTi CVJ | CvJ , | <=!- <X> | CO | 0 | , | | u 0 c 00 0 \u2022>- LD U | 00 00 | 00 OsJ | 00 , | C\\J | 0 CO | 0 | , | | 0 0 c 0 -r- CM U (NJ | 0 0 CTi 1 | | 00 cn | LO | CT) C\\J | 0 | | | 0 C 0 0 -r- 0 .- 0 | 0 0 | CTi | \u00ab^ | 00 | r-~. C\\J | 0 r- | | | CO +-> u 0 c: in \u2022>- 0 0) Gl. | 0 0 LO LT) | 0 uo | | CO | CO C\\J | CTi | r- | | X c CO -a | LD 0 0 0 0 0 | C\\J 0 0 | LO 0 0 | 0 | CO 0 | LO 0 | 0 | CTi O II o &lt;U +J c o u cu q: o 4-&gt; CO +j u c o (U &amp;-4o sE 00 J3 1. U.S. General Accounting Office Interagency Agreement with the National Bureau of Standards Institute for Computer Sciences and Technology, February 10, 1974, Procedures 1. 2. ibid. Procedures 1 . C 3. ibid. Purpose of Agreement . 4. Sidney B. Geller, \"The Effects of Magnetic Fields on Magnetic Storage Media Used in Computers,\" U.S. Department of Commerce, National Bureau of Standards, Washington, D.C., NBS Technical Note 735, July, 1972. 5. Susan K. Reed and Martha M. Gray, \"Controlled Accessibility Bibliography,\" U.S. Department of Commerce, National Bureau of Standards, Washington, D.C., NBS Technical Note 780, June, 1973. 6. Clark R. Renninger and Dennis K.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Effective Use of Computing Technology in Vote-Tallying."}]}
{"id": "nist_02030", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-256 in Derived PIV Application and Data Model Test Guidelines? (Part 40) Control HA-256: . For Steps 2, 3, 4, 5A, 5B, 6 and 7, each command returns the requested data object along with the status word '90 00'. 3. For Step 8, the command returns status word '6A 82' (data object not found). | | Postcondition(s) | N/A | ## 8.3.3 GENERAL AUTHENTICATE Command ## 8.3.3.1 Internal Authenticate with the Derived PIV Authentication Key | Test Assertion | TA-08.03.03.01 | |----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Purpose | Verifies that the Derived PIV Application responds to the GENERAL AUTHENTICATE command appropriately when authenticating to the test toolkit application. | | DTR(s) | \u2022 DTR-06.02.02.09 \u2022 DTR-06.03.01.01 \u2022 DTR-06.03.01.02 \u2022 DTR-06.03.04.01 \u2022 DTR-06.03.04.05 | | Vendor Documentation | None.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_02031", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Access Control for SAR Systems say about 1.3 Audience and Assumptions? According to Access Control for SAR Systems, 1.3 Audience and Assumptions: This document assumes that the readers have basic knowledge of access control, particularly attribute-based access control. Because of the constantly changing nature of the information technology industry, readers are strongly encouraged to take advantage of other resources (including those listed in this document) for more current and detailed information.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Access Control for SAR Systems."}]}
{"id": "nist_02032", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Acquisition Consistency according to Cell Phone Forensic Tools_ an Overview and Analysis? Acquisition Consistency: N.A. - The MD5/SHA1 hashing algorithms are used to determine whether a case file has been damaged, not to verify that the acquired data has not been altered after acquisition. (NA)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_02033", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DP-10 in Computer Security_ Selected Articles? (Part 3) Control DP-10: racter ``` ## FIGURE 1. ## STAGE II The C compiler is written in C. What I am about to describe is one of many 'chicken and egg' problems that arise when compilers are written in their own language. In this case, I will use a specific example from the C compiler. C allows a string construct to specify an initialized character array The individual characters in the stnng can be escaped to represent unpnntable characters. For example. ## 'Hello world\\n' represents a string with the character '\\n,\" representing the new line character. Figure 2.1 is an idealization of the code in the C compiler that interprets the character escape sequence. This is an amazing piece of code. It 'knows' in a completely portable way what character code is compiled for a new line in any character set. The act of knowing then allows it to recompile itself, thus perpetuating the knowledge. Suppose we wish to alter the C compiler to include the sequence '\\y' to represent the vertical tab character. The extension to Figure 2.1 is obvious and is presented in Figure 2.2. We then recompile the C compiler. but we get a diagnostic. Obviously, since the binary version of the compiler does not know about the source is not legal C. We must 'train' the compiler. After it 'knows' what '\\v' means, then our new change will become legal C. We look up on an ASCII chart that a vertical tab is decimal 11. We alter our source to look like Figure 2.3. Now the old compiler accepts the new source. We install the resulting binary as the new official C compiler and now we can write the portable version the way we had it in Figure 2.2. This is a deep concept. It is as close to a 'learning' program as 1 have seen. You simply tell it once, then you can use this self-referencing definition. ## STAGE ID Again, in the C compiler.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security_ Selected Articles."}]}
{"id": "nist_02034", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Threat Analysis on UOCAVA Voting Systems provide? (Section 147) | X | INCIDENT HANDLING | Officials should monitor their IT systems and communications services for disruptions and possible attacks. | | IR-5 | X | X | INCIDENT MONITORING | Officials should monitor their IT systems and communications services for disruptions and possible attacks. | | MA-2 | | X | CONTROLLED MAINTENANCE | System administrators should closely monitor the maintenance of vital IT systems to ensure the proper hardware and software updates are performed on such systems. | | MA-3 | | X | MAINTENANCE TOOLS | System administrators should closely monitor the maintenance of vital IT systems to ensure the proper hardware and software updates are performed on such systems. | | MA-5 | | X | MAINTENANCE PERSONNEL | System administrators should closely monitor the maintenance of vital IT systems to ensure the proper hardware and software updates are performed on such systems. | | PE-2 | X | X | PHYSICAL ACCESS AUTHORIZATIONS | Officials should control physical access to vital systems and sensitive information. This includes physical access to IT systems and communications equipment. | | PE-3 | X | X | PHYSICAL ACCESS CONTROL | Officials should control physical access to vital systems and sensitive information. This includes physical access to IT systems and communications equipment.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: A Threat Analysis on UOCAVA Voting Systems."}]}
{"id": "nist_02035", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Defect Check Rationale Table according to NIST Automation Support for Security Control Assessments_ Software Asset Management According to Automation Support for Security Control Assessments_ Software Asset Management, Defect Check Rationale Table: Defect Check Rationale Table A failure in effectiveness of this control item results in a defect in one or more of the following defect checks: | Determination Statement ID | Defect Check ID | Defect Check Name | Rationale If an [organization-defined measure] for this defect check is above [the organization-defined threshold], then defects in identifying specific software programs authorized to execute on the system related to this control item might be the cause of the defect, i.e.,\u2026 | |------------------------------|-------------------|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | CM-7(5)(a){1} | SWAM- F01 | Unauthorized software executes | the execution of unauthorized software. | | CM-7(5)(a){1} | SWAM- F02 | Unauthorized software installer | the execution of software not installed by an authorized installer. | | CM-7(5)(a){1} | SWAM- F03 | Unauthorized software directory/folder location | the execution of software not loaded from an approved directory/folder location. | | CM-7(5)(a){1} | SWAM- F04 | Untrusted core software | lack of core software integrity at start-up. | | CM-7(5)(a){1} | SWAM- L04 | Devices moving in/out of protective boundaries not in policy compliance | devices' software not being adequately strengthened and/or sanitized for movement into or out of protective boundaries. |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_02036", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain A.2.2 Key Translation Center (KTC) Architecture according to NIST Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations According to Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations, A.2.2 Key Translation Center (KTC) Architecture: A KTC is used to translate keys for future communications between KTC subscribers. The architecture is shown in Figure 6 and is similar to the KDC architecture shown in Figure 5, except that a KTC is used instead of a KDC. Subscribers share a key-wrapping key with the KTC that is used to protect the generated keys during communication. KTCs are further described in SP 80071. Figure 6: KTC Components <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations."}]}
{"id": "nist_02037", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Secure Web Services? (Part 75) Control ES-1: ed by a certificate authority or by passing custom tokens generated by a TTP, as is done in a Kerberos environment. Traditionally, these trust mechanisms have worked well within a single organization. Once information sharing crosses organizational boundaries, entities communicating with one another do not necessarily have the same source of trust. Before the advent of Web services, information sharing across organizational boundaries traditionally was handled by using a proxy that bridges the boundary or by cross-signing certificates. In a SOA, Web services from multiple organizations should be able trust one another without requiring extensive restructuring of the trust environment. To this end, trust federation frameworks can be configured to use an organization's pre-existing authentication mechanisms. Liberty Alliance provides both Web application and Web service federation using SAML to perform the trust brokering. WSFederation allows different security realms to federate by defining trust brokers, who will validate security tokens used between Web services using WS-Trust. The following subsections provide additional information on the trust frameworks identified above. It must be noted, however, that these frameworks continue to evolve. Thus, the material provided is meant to offer a current snapshot of the features they offer as of this guide's date of publication. ## 3.3.2 Trust Federation Frameworks The following subsections provide additional details of the Liberty Alliance and WS-Trust frameworks. These standards provide similar features and functionality using different techniques and have been designed with different goals in mind. Determining which framework is best for a particular organization depends greatly on what is deployed and on the organization's architectural goals. ## 3.3.2.1 Liberty Alliance The Liberty Alliance aims to develop a standards-based identity federation framework suitable for businesses and governments.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, certificate authority, token. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services."}]}
{"id": "nist_02038", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.2 Acronyms according to NIST Recommendation for Existing Application-Specific Key Derivation Functions According to Recommendation for Existing Application-Specific Key Derivation Functions, 3.2 Acronyms: | ANS | American National Standard | |-------|------------------------------------------------| | CMAC | Block Cipher-based Message Authentication Code | | DLC | Discrete Logarithm Cryptography | | E-E | Extraction-then-Expansion | |-------|------------------------------------------------| | FIPS | Federal Information Processing Standard | | HKDF | Hash-based Key Derivation Function | | IETF | Internet Engineering Task Force | | IKE | Internet Key Exchange | | IKEv1 | IKE version 1 | | IKEv2 | IKE version 2 | | KDF | Key Derivation Function | | MAC | Message Authentication Code | | NIST | National Institute of Standards and Technology | | PRF | Pseudorandom Function | | RFC | Request for Comments | | SA | Security Association | | SHA | Secure Hash Algorithm | | SSH | Secure Shell | | SP | Special Publication | | TLS | Transport Layer Security | | TPM | Trusted Platform Module |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Existing Application-Specific Key Derivation Functions."}]}
{"id": "nist_02039", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation provide? (Section 166) ---------------|----------------------|-------------------| | | | is deleted from the RPKI, so the route still evaluates as invalid . | | | | CR-1.9.1 | | | IPv4 address type | SIDR- ROV- 1.9.1 | | CR-1.9.2 | | | IPv6 address type | SIDR- ROV- 1.9.2 | | CR-1.10 | | The advertised route is initially evaluated to be invalid due to the fact that it contains AS_SET, even though there is an ROA that covers the route and that has a maximum length greater than the route's prefix. A second advertisement is received for this same route that does not contain AS_SET and that is matched by the ROA that is already in the RPKI. The route in this second advertisement is evaluated as valid .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_02040", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Appendix B Acronyms according to NIST_SP_800-53r5_Security_Privacy_Controls? Appendix B Acronyms: Add \u201cOPM Office of Personnel Management\u201d", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02041", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2017 NIST_ITL Cybersecurity Program Annual Report say about https:/ /doi.org/10.1145/3018981.3018986? According to 2017 NIST_ITL Cybersecurity Program Annual Report, https:/ /doi.org/10.1145/3018981.3018986: Defense-in-depth is an important security architecture principle that has significant application to industrial control systems (ICS), cloud services, storehouses of sensitive data, and many other areas. We claim that an ideal defense-in-depth posture is 'deep,' containing many layers of security, and 'narrow,' the number of node independent attack paths is minimized. Unfortunately, accurately calculating both depth and width is difficult using standard graph algorithms because of a lack of independence between multiple vulnerability instances (i.e., if an attacker can penetrate a particular vulnerability on one host, then they can likely penetrate the same vulnerability on another host). To address this, we represent known weaknesses and vulnerabilities as a type of colored attack graph. We measure depth and width through solving the shortest color path and minimum color cut problems. We prove both of these to be NPHard and thus, for our solution, we provide a suite of greedy heuristics. We then empirically apply our approach to large randomly generated networks as well as to ICS networks generated from a published ICS attack template. Lastly, we discuss how to use these results to help guide improvements to defense-in-depth postures. D. Moody , R. Perlner and D. Smith-Tone . Improved Attacks for Characteristic-2 Parameters of the Cubic ABC Simple Matrix Encryption Scheme . 8th International Workshop on PostQuantum Cryptography (PQCrypto 2017) , Utrecht, The Netherlands, June 26-28, 2017. In Lecture Notes in Computer Science 10346, Post-Quantum Cryptography - PQCrypto 2017 , pp. 255-271.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02042", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automation Support for Security Control Assessments_ Volume 1_ Overview say about 6.5 Defect Check Rationale Table? (Part 2) According to Automation Support for Security Control Assessments_ Volume 1_ Overview, 6.5 Defect Check Rationale Table: trol item level. Rather, the assessment criteria are designed so that if the control item fails, the defect check control item-determination statement (CI-DS) assessment criteria shows that it failed. See Section 7.2 on root cause analysis for information on how to determine which control item(s) caused the defect check to fail. If the CI is determined to have failed, then its control has at least partially failed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Volume 1_ Overview."}]}
{"id": "nist_02043", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does The Network Security Center_ a System Level Approach to Computer Network Security say about 3.2 An Implementation Example? (Part 1) According to The Network Security Center_ a System Level Approach to Computer Network Security, 3.2 An Implementation Example: 3.2 An Implementation Example Section 3.1 described, in an implementation independent manner, the NSC data structures for identification/authentication and access request authorization. The set notation that was used avoided details of implementation. This section will present an example implementation of the NSC data structures. This section is an example, not a precise prescription for building an NSC. The example serves to illustrate how an NSC might be implemented. Each situation is different, however, and the circumstances of a different situation may make this particular implementation inappropriate. The example is still of value, since it illustrates the range of issues that govern the design of a specific implementation. 3.2.1 Scope of Example. This example will initially consider a network of approximately ten network sites (hosts) and about 1000 network users. It is assumed that each subject will require a new access via the NSC about every 20 minutes. It is also assumed that the authentication/authorization dialogue will be complete within one minute, including appropriate typing delays and user \"think time.\" Each subject is treated as a user. This is obvious for users at terminals; other entities (such as processes) are considered to be acting on behalf of a particular user. For the example, user identifiers will be assumed to be eight alphanumeric characters long, which provides 36^ (more than 2 x 10^^) unique identifiers, ample range to accommodate any foreseeable network population. The size of the authentication value is assumed to be eight bytes, which is consistent with the length of an NBS standard encryption algorithm key, if a scheme where the authenticator is used as an encryption key is adopted. If a password scheme is adopted, any value longer than eight characters will likely prove too difficult for users to memorize. This example considers objects of the form of data files located at network hosts.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: The Network Security Center_ a System Level Approach to Computer Network Security."}]}
{"id": "nist_02044", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Implementation according to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations? Implementation: As a part of a comprehensive, defense-in-breadth information security strategy, the enterprise established a C-SCRM program to address the management of cybersecurity risks throughout the supply chain. The C-SCRM PMO is responsible for conducting assessments of cybersecurity risks that arise from business partners seeking to integrate with [system name] in accordance with enterprise-wide C-SCRM Level 2 policy requirements. CSCRM training and awareness materials must also be provided for all individuals prior to receiving access to [system name].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_02045", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Accuracy, Integrity, and Security in Computerized Vote-Tallying say about 6.9.3 Treatment of Rejected Ballots? According to Accuracy, Integrity, and Security in Computerized Vote-Tallying, 6.9.3 Treatment of Rejected Ballots: Some ballot readers (primarily mark-sense readers) include a \"gono-go\" decision, depending on whether the reader can read the ballot at all. Such readers may refuse to count ballots in the \"no-go\" status. Administrative regulations should require such rejected ballots to be counted manually, so that no voter loses the voting franchise because of machine failure. The use of the term \"rejected ballots,\" implies that none of the ballot readers used could distinguish a hole from no-hole or mark from no-mark at a location on a ballot at which a hole or mark indicates an intention to cast a vote. If a ballot reader can correctly distinguish the voting intentions made by the voter in all the appropriate locations on the ballot, it is successfully reading the ballot (even if a voting intention cannot be counted because of an overvote or the voter submitted an undervote by failing to vote for an office) . If the ballot is correctly read. the term \"rejected ballots\" should not be used.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Accuracy, Integrity, and Security in Computerized Vote-Tallying."}]}
{"id": "nist_02046", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PA-5060 in Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation? (Part 100) Control PA-5060: ied from outside the project. - \uf0a7 Analyze the Security Aspects of Decision Information (DM-2): - DM-2.1 - Select and declare the security aspects of the decision management strategy for each decision. - DM-2.2 - Determine the desired security outcomes and measurable security selection criteria. - DM-2.3 - Identify the security aspects of the trade space and alternatives. - DM-2.4 - Evaluate each alternative against the security evaluation criteria. - \uf0a7 Plan Security Risk Management (RM-1): - RM-1.1 - Define the security aspects of the risk management strategy. - RM-1.2 - Define and record the security context of the risk management process. - \uf0a7 Evaluate and Select Solution Classes (BA-4): - BA-4.1 - Assess each alternative solution class, taking into account the security objectives, limitations, constraints, and other relevant security considerations. - BA-4.2 - Select the preferred alternative solution class (or classes) based on the identified security objectives, trade space factors, and other criteria defined by the organization. - \uf0a7 Define Stakeholder Protection Needs (SN-2) - This was a continuation of the task from the concept phase. - \uf0a7 Develop the Security Aspects of Operational and Other Life-Cycle Concepts (SN-3): - SN-3.1 - Define a representative set of scenarios to identify all required protection capabilities and security measures that correspond to anticipated operational and other life-cycle concepts. - SN-3.2 - Identify the security-relevant interaction between users and the system. - \uf0a7 Transform Stakeholder Protection Needs into Security Requirements (SN-4) - This was a continuation of the task from the concept phase. - \uf0a7 Prepare for System Security Requirements Definition (SR-1) - This is a continuation of the task from the concept phase. - \uf0a7 Define System Security Requirements (SR-2): - SR-2.1 - Define each security function that the system is required to perform.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_02047", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Digital Identity Guidelines_ Federation and Assertions say about 4.4. Discovery and Registration? (Part 1) According to Digital Identity Guidelines_ Federation and Assertions, 4.4. Discovery and Registration: 4.4. Discovery and Registration To perform a federation transaction with a general-purpose IdP, the RP has to perform discovery and registration with that IdP, as discussed in Sec. 3.6. The RP SHALL associate the assertion validation keys and other relevant configuration information with the IdP's identifier, as stipulated by the trust agreement. If the validation keys and configuration information are retrieved over a network connection, request and retrieval SHALL be made over an authenticated protected channel from a location that is associated with the IdP's identifier by the trust agreement. In many federation protocols, this is accomplished by the RP fetching the public keys and configuration data from a URL that is specified in the trust agreement as being controlled by the IdP or offered on the IdP's behalf. It is also possible for the RP to be configured directly with this information in a manual fashion, whereby the RP's system administrator enters the IdP information directly into the RP software's configuration. In some systems, particularly those governed by multi-lateral trust agreements, the discovery process can be facilitated by a third-party discovery and registration service. Additionally, the RP SHALL register its information with either the IdP or an authority that the IdP trusts, as stipulated by the trust agreement. In many federation protocols, the RP is assigned an identifier during this stage, which the RP will use in subsequent communication with the IdP. Parties that seek to federate MAY use a trusted third party to facilitate the discovery and registration processes if that trusted third party is identified in the trust agreement. For example, a consortium could use a hosted service that collects the configuration records of IdPs and RPs directly from participants. Instead of going to the IdP directly for its discovery record, an RP would instead go to this service and retrieve the key material for its target IdP .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Digital Identity Guidelines_ Federation and Assertions."}]}
{"id": "nist_02048", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Web Transactions_ TLS Server Certificate Management provide? (Section 236) risks of not managing TLS server certificates properly, additional risks often plague TLS implementations themselves. Proper protocol specification does not guarantee the security of implementations. In particular, when integrating into higher level protocols, TLS and its PKI-based authentication are sometimes the source of misunderstandings and implementation shortcuts. An extensive survey of these issues can be found in Proceedings of the 2012 ACM Conference on Computer and Communications Security. Under the RMF, the first step in managing risk is determining the impacts of exploitation of system confidentiality, integrity, and availability vulnerabilities. NIST SP 800-53-controls needed to mitigate system vulnerabilities are keyed to the Federal Information Processing Standards (FIPS) 199 impact levels. Based on the risks identified, and assuming a Standards for Security Categorization of Federal Information and Information Systems , FIPS 199 [13] moderate impact level (exploitation of vulnerabilities would result in serious harm to the system and its mission), a number of NIST SP 800-53 controls are assigned to address TLS server certificate risks: AC-1, AC-5, AC-6, AC-16, AT-2, AU-1, AU-2, AU-3, AU-6, AU-12, AU-13, AU-14, CA-1, CA-2, CA-5, CA-7, CM-2, CM-3, CM-5, CM-6, CM-8, CM-9, CM-12, CP-2, CP-3, CP-4, CP-7, CP-13, IA-3, IA-4, IA-5, IA-9, IR-1, IR-2, IR-3, IR-4, MA-1, MA-6, PL-2, PL-9, PL-10, PM-1, PM-2, PM-4, PM-5, PM-7, PM-9, RA-3, RA-5, RA-7, SA-1, SA-3, SA-4, SA-10, SC-1, SC-6, SC-8, SC-12, SC-17, SC23, and SI-4. Appendix C of Volume B describes these security controls and their relevance to the best practices identified in Volume B. The objective of this project is to demonstrate how the processes for obtaining and maintaining TLS server certificates in medium and large IT enterprises can be made less labor-intensive and error prone, to reduce security and operational risks.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_02049", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Technical Guide to Information Security Testing and Assessment say about 3.4 System Configuration Review? (Part 1) According to Technical Guide to Information Security Testing and Assessment, 3.4 System Configuration Review: 3.4 System Configuration Review System configuration review is the process of identifying weaknesses in security configuration controls, such as systems not being hardened or configured according to security policies. For example, this type of review will reveal unnecessary services and applications, improper user account and password settings, and improper logging and backup settings. Examples of security configuration files that may be reviewed are Windows security policy settings and Unix security configuration files such as those in /etc . Assessors using manual review techniques rely on security configuration guides or checklists to verify that system settings are configured to minimize security risks. 8 To perform a manual system configuration review, assessors access various security settings on the device being evaluated and compare them with recommended settings from the checklist. Settings that do not meet minimum security standards are flagged and reported. The Security Content Automation Protocol (SCAP) is a method for using specific standards to enable automated vulnerability management, measurement, and policy compliance evaluation. 9 NIST SCAP files are written for FISMA compliance and NIST SP 800-53A security control testing. Other tools can be used to retrieve and report security settings and provide remediation guidance. Automated tools are often executed directly on the device being assessed, but can also be executed on a system with network access to the device being assessed. While automated system configuration reviews are faster than manual methods, there may still be settings that must be checked manually. Both manual and automated methods require root or administrator privileges to view selected security settings. Generally it is preferable to use automated checks instead of manual checks whenever feasible. Automated checks can be done very quickly and provide consistent, repeatable results.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Technical Guide to Information Security Testing and Assessment."}]}
{"id": "nist_02050", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Personal Identity Verification (PIV) of Federal Employees and Contractors say about B.2 PIV Background Investigation Indicator Certificate Extension (Deprecated)? According to Personal Identity Verification (PIV) of Federal Employees and Contractors, B.2 PIV Background Investigation Indicator Certificate Extension (Deprecated): The PIV background investigation indicator (previously known as the NACI indicator) is deprecated under this version of the Standard, and it is expected that the indicator will be removed from a future revision. Instead of the on-card indicator, background investigative status is commonly maintained in each agency IDMS and personnel security system as well as in the Central Verification System (or successor). The status of the investigation can be communicated as needed using federation protocols. If used, the PIV background investigation indicator extension indicates to the issuer whether the subject's background investigation was incomplete at the time of credential issuance. The PIV background investigation indicator extension is always non-critical. The value of this extension is asserted as follows: - TRUE if, at the time of credential issuance, (1) the FBI National Criminal History Fingerprint Check has completed, and (2) a background investigation has been initiated but has not completed. - FALSE if, at the time of credential issuance, the subject's background investigation has been completed and successfully adjudicated. The PIV background investigation indicator extension is identified by the id-piv-NACI object identifier. The syntax for this extension is defined by the following ASN.1 module: ``` PIV-Cert-Extensions { 2 16 840 1 101 3 6 10 1 } DEFINITIONS EXPLICIT TAGS ::= BEGIN --EXPORTS ALL ----IMPORTS NONE --id-piv-NACI OBJECT IDENTIFIER ::= { 2 16 840 1 101 3 6 9 1 } NACI-indicator ::= BOOLEAN END ```", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Personal Identity Verification (PIV) of Federal Employees and Contractors."}]}
{"id": "nist_02051", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CP-09 in Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations? (Part 74) Control CP-09: on mechanisms can also monitor systems for anomalous or unexpected behaviors and take appropriate actions. Malicious code protection mechanisms include signature- and non-signature-based technologies. Non-signature-based detection mechanisms include artificial intelligence techniques that use heuristics to detect, analyze, and describe the characteristics or behavior of malicious code and to provide controls against such code for which signatures do not yet exist or for which existing signatures may not be effective. Malicious code for which active signatures do not yet exist or may be ineffective includes polymorphic malicious code (i.e., code that changes signatures when it replicates). Non-signature-based mechanisms include reputation-based technologies. Pervasive configuration management, anti-exploitation software, and software integrity controls may also be effective in preventing unauthorized code execution. If malicious code cannot be detected by detection methods or technologies, organizations can rely on secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that the software only performs intended functions. Organizations may determine that different actions are warranted in response to the detection of malicious code. For example, organizations can define actions to be taken in response to the detection of malicious code during scans, malicious downloads, or malicious activity when attempting to open or execute files. ## REFERENCES Source Control: SI-03 Supporting Publications: SP 800-83 [76], SP 800-125B [65], SP 800-177 [70] ## 03.14.03 Security Alerts, Advisories, and Directives - a. Receive system security alerts, advisories, and directives from external organizations on an ongoing basis. - b. Generate and disseminate internal system security alerts, advisories, and directives, as necessary.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_02052", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DS-2 in Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)? (Part 111) Control DS-2: 8.30.181 pi@pi-1:~ $ NIST SP 1800-15D: Securing Small-Business and Home Internet of Things Devices 355 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Exercise Field Description pi@pi-1:~ $ ssh pi@10.135.4.2 pi@10.135.4.2's password: Last login: Wed Jun 17 10:30:58 2020 from 192.168.30.181 pi@pi-2:~ $ pi@pi-2:~ $ ssh pi@10.135.5.2 ssh: connect to host 10.135.5.2 port 22: Connection timed out pi@pi-3:~ $ ssh pi@10.135.4.2 ssh: connect to host 10.135.4.2 port 22: Connection timed out pi@pi-3:~ $ ssh pi@10.135.4.3 ssh: connect to host 10.135.4.3 port 22: Connection timed out Flow rules: Every 2.0s: sudo ovs-ofctl dump-flows brmn001 --names | /opt/micronets-gw/bin/format-ofctl-dump Wed Jun 17 16:57:42 2020 table=0 priority=500 n_packets=0 dl_dst=01:80:c2:00:00:00/ff:ff:ff:ff:ff:f0 actions=drop table=0 priority=500 n_packets=0 dl_src=01:00:00:00:00:00/01:00:00:00:00:00 actions=drop table=0 priority=500 n_packets=0 icmp icmp_code=1 actions=drop table=0 priority=450 n_packets=28 in_port=LOCAL actions=resubmit( 200) table=0 priority=400 n_packets=20 in_port=\"wlp2s0.2844\" actions=resubmit( 100) NIST SP 1800-15D: Securing Small-Business and Home Internet of Things Devices 356 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_02053", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is FR according to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)? FR: 6.46 For each key type, the CKMS design shall specify: the circumstances under which keys of each type and their metadata are stored, where the keys and metadata are stored, and how the keys and metadata are protected.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_02054", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.1 PASSWORD USAGE according to NIST United States Federal Employees' Password Management Behaviors \u2013 A Department of Commerce Case Study According to United States Federal Employees' Password Management Behaviors \u2013 A Department of Commerce Case Study, 3.1 PASSWORD USAGE: On average, DOC employees had nine (range: 1 to 400) accounts at work that require logins. Due to the wide range of the data, medians were used for calculating the central tendency. The median of frequently used passwords was five (range: 0 to 105) and the median of occasionally used passwords was four (range: 0 to 245). Further breaking down the number of accounts requiring logins, showed that 21.8 % of the employees had less than or equal to five accounts, 41.5 % had between six to ten accounts, 25.4 % had between 11 to 20 accounts, and 11.0 % had more than 20 accounts.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: United States Federal Employees' Password Management Behaviors \u2013 A Department of Commerce Case Study."}]}
{"id": "nist_02055", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 2017 NIST_ITL Cybersecurity Program Annual Report provide? (Section 302) us actors. The draft describes methods to improve the security of the PMS, and how these methods can help protect the business from network intrusions that might lead to data breaches and fraud. Based on industry research and in collaboration with hospitality industry stakeholders, the NCCoE is starting a project that aims to help hospitality organizations implement stronger security measures within and around the PMS, with a focus on the POS system through network segmentation, pointto-point encryption, data tokenization, multifactor authentication for remote and partner access, network and user behavior analytics, and business-only usage restrictions. In collaboration with the hospitality business community and technology vendors who implement standards that improve cybersecurity, the NCCoE will explore methods to strengthen the security of the PMS and its connections and will develop an example implementation composed of open-source and commercially available components. This project will produce a NIST Cybersecurity Practice Guide-a freely available description of the solution and practical steps needed to effectively secure the PMS and its many connections within the hotel IT system. Baldrige Cybersecurity Excellence Builder: Key questions for improving your organization's cybersecurity performance, v1.0 April 2017 https:/ /www.nist.gov/baldrige/products-services/ baldrige-cybersecurity-initiative The Baldrige Cybersecurity Excellence Builder is a voluntary self-assessment tool that enables organizations to better understand the effectiveness of their cybersecurity risk management efforts. It helps your organization identify strengths and opportunities for improvement in managing cybersecurity risk based on your organization's mission, needs, and objectives.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02056", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Section 292) | | PM-29 | Risk Management Program Leadership Roles | | | x | | | | PM-30 | Supply Chain Risk Management Strategy | x | x | x | x | | | PM-31 | Continuous Monitoring Strategy | | | x | x | x | | PM-32 | Purposing | | | | x | x | | PS-1 | Policy and Procedures | x | x | x | x | x | | PS-3 | Personnel Screening | x | x | | x | x | | PS-6 | Access Agreements | x | x | | x | x | | PS-7 | External Personnel Security | x | | | x | | | PT-1 | Policy and Procedures | | x | x | x | x | | RA-1 | Policy and Procedures | x | | x | x | x | | RA-2 | Security Categorization | x | | x | x | x | | RA-3 | Risk Assessment | x | | x | x | x | | RA-3 (1) | Risk Assessment | Supply Chain Risk Assessment | x | x |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_02057", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives provide? (Section 39) ity - b. Message Content Standards - c. Barriers to Entry - d. Supply Chain traceability Ecosystems - e. Metrics - f. Patterns in Supply Chain Traceability - g. Ecosystem Scale and Interoperability 4. The authors encourage further research, experimentation, and discussion in manufacturing domains to explore the topics above and discover further innovations to improve traceability of manufacturing supply chains. The remaining sections of the paper are: Section 2 'Manufacturing Supply Chain Overview and Imperatives' reviews the current state of supply chain risk analysis and introduces an ecosystem perspective to complement the current per stakeholder perspective in Supply Chain Risk Management (SCRM) analysis. Section 3 'Traceability' reviews the desired benefits traceability may offer and example domains for which traceability is applicable. Section 4 'Technologies Supporting Traceability' reviews technologies, both mature and emerging, which can be used to link goods and services to data records, then share the data records across a wide set of supply chain stakeholders. Section 5 'Considerations for Adoption of Blockchain' reviews the challenges and risks associated with establishing a blockchain capability for a subset of the supply chain and the resulting ecosystem. Blockchain is one technology with features corresponding to drivers for supply chain traceability, such as pedigree and provenance for products and records. Section 6 'Industry Case Studies &amp; Analysis' reviews the methodology for industry engagement, organizations who submitted case studies, and the summaries of the submitted case studies. Following are the analyses of the case studies viewed through perspectives or mental models selected in the methodology. Full description of the analysis methods and full case studies are found in the Appendices. Section 7 'Future Research' summarizes indications of future research needed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives."}]}
{"id": "nist_02058", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guidelines on Active Content and Mobile Code? (Part 14) Control ES-1: e of Standards and Technology (NIST) developed this document in furtherance of its statutory responsibilities under the Federal Information Security Management Act (FISMA) of 2002, Public Law 107-347. NIST is responsible for developing standards and guidelines, including minimum requirements, for providing adequate information security for all agency operations and assets; but such standards and guidelines shall not apply to national security systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), 'Securing Agency Information Systems,' as analyzed in A-130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in A-130, Appendix III. 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 The purpose of this document is to provide an overview of active content and mobile code technologies in use today and offer insights for making informed IT security decisions on their application and treatment. The discussion gives details about the threats, technology risks, and safeguards for end user systems, such as desktops and laptops. Although various end user applications, such as email clients, can involve active content, Web browsers remain the primary vehicle for delivery and are underscored in the discussion. The tenets presented for Web browsers apply equally well to other end user applications and can be inferred directly.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: Guidelines on Active Content and Mobile Code."}]}
{"id": "nist_02059", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Dramatically Reducing Software Vulnerabilities_ Report to the White House Office of Science and Technology Policy say about 1 Introduction? (Part 2) According to Dramatically Reducing Software Vulnerabilities_ Report to the White House Office of Science and Technology Policy, 1 Introduction: triggered or intentionally exploited and result in a violation of desired system properties. A weakness is an undesired characteristic of a system's requirements, design or implementation [Black11a]. This definition excludes - manual configuration or operational mistakes, such as installing a program as worldreadable or setting a trivial password for administrator access; - insider malfeasance, such as exfiltration by Edward Snowden; - functional bugs, such as the mixture of SI (International System of Units) and Imperial units, which led to the loss of the Mars Climate Orbiter in 1999 [Oberg99]; - purposely introduced malware or corrupting 'mis-features' in regular code, such as allowing root access if the user name is 'JoshuaCaleb' and - software weaknesses that cannot be exploited (by 'outsiders') as a result of input filtering or other mitigations. Great strides have been made in defining software vulnerabilities, cataloging them and understanding them. Additionally, great strides have been made in educating the software community about vulnerabilities, attendant patches and underlying weaknesses. This work, however, is insufficient. Significant vulnerabilities are found routinely, many vulnerabilities lie undiscovered for years and patches are often not applied. Clearly a different approach-one that relies on improving software-is needed. Strengthening protection requires increasing assurance that the products people develop and deploy are highly resistant to malicious cyber activities, because they include very few vulnerabilities \u2026 [FCRDSP16, p. 17]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, malware. Contains technical security guidance that could inform defensive posture. Source: Dramatically Reducing Software Vulnerabilities_ Report to the White House Office of Science and Technology Policy."}]}
{"id": "nist_02060", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation say about Executive Summary? (Part 2) According to Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation, Executive Summary: en two transit networks. \ufffdere are instances in which the recommendations for interdomain traffic exchange between transit networks will vary from those for exchanges between stub and transit networks. \ufffde provided recommendations reduce the risk of accidental attacks (caused by misconfigu ration) and malicious attacks in the routing control plane, and they help detect and prevent IP address spoofing and resulting DoS/DDoS attacks. \ufffdese recommendations primarily cover technologies (for security and robustness) to be used in border routers that operate the Border Gateway Protocol (commonly called BGP routers). However, they also extend to other systems that support reachability on the internet (e.g., Resource Public Key Infrastructure (RPKI) repositories, Domain Name System (DNS), other open internet services). It is expected that the guidance and applicable recommendations from this publication will be incorporated into the security plans and operational processes of federal enterprise networks. Likewise, it is expected that applicable recommendations will be incorporated into the service agreements for federal contracts for hosted application services and internet transit services. \ufffdis document also contributes to the ongoing efforts by NIST and NTIA [DOC -Botnet] [BotnetRoadmap] to respond to Presidential Executive Order 13800 [PEO-13800]. Technologies recommended in this document for securing interdomain routing control traffic include Resource Public Key Infrastructure (RPKI), BGP origin validation (BGP-OV), and prefix filtering. Additionally, technologies recommended for mitigating DoS/DDoS attacks include prevention of IP address spoofing using source address validation (SAV) with access control lists (ACLs) and unicast Reverse Path Forwarding (uRPF).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, pki. Contains security framework guidance for authentication systems. Source: Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation."}]}
{"id": "nist_02061", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Risk response constraints according to Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Risk response constraints: Limited operational resources to", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_02062", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Card Technology Developments and Gap Analysis Interagency Report say about Technology Issues and Standardization Gaps? (Part 2) According to Card Technology Developments and Gap Analysis Interagency Report, Technology Issues and Standardization Gaps: logical and physical access control in Federal government applications. However, the basic GSC-IS smart card service provider model is flexible enough to support a much broader range of applications. It does not preclude use of current storage technologies, including optical technologies. GSC-IS is based on the ISO 7816 standards, and NIST is pursuing formal standardization of GSC-IS on behalf of the GSC community. The following additional technology issues were identified: - \u0083 Existing standards do not address a true multi-application platform with multiple security domains that enable software applications from different vendors to share the same media. Although significant cost savings and ease of card and system management benefits might result from development of such a platform, the workshop and subsequent interviews revealed neither the validated requirements nor the technical capabilities necessary to the development. No consensus among the user community regarding additional requirements for interconnecting multiple technologies, either on a card or in a reader/processor device was identified in either workshop proceedings or user interviews. - \u0083 With respect to the design of multi-technology cards, the issue of the physical location of each technology on the same card is a concern. No standard exists that defines the technologies that may co-exist on a single card. The detailed location and layout of different combinations of components have not been specified, nor have physical and mechanical specifications for some technologies or groups of technologies been specified. Such specification of the mutual effects of co-existing technologies and varying operational requirements of each technology may prove useful in the future. For example, when chip failure occurs on a contactless smart card, the magnetic stripe also present on the card may also be affected. The life expectancy of the magnetic stripe is then reduced as a result of a chip-related problem.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Card Technology Developments and Gap Analysis Interagency Report."}]}
{"id": "nist_02063", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Domain Name System-Based Electronic Mail Security say about 3.4.4 Cybersecurity Framework Functions, Categories, and Subcategories Addressed by the Project? (Part 3) According to Domain Name System-Based Electronic Mail Security, 3.4.4 Cybersecurity Framework Functions, Categories, and Subcategories Addressed by the Project: y are based upon cross-sector guidance most frequently referenced during the Framework development process. This project supported the Cybersecurity Framework's Protect, Detect, and Respond Functions. Applicability to specific Functions, Categories, and Subcategories is described in the following paragraphs.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_02064", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Recommended Confidentiality Impact Level according to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices? Recommended Confidentiality Impact Level: Given potentially serious to severe legal consequences of unauthorized disclosure, the provisional confidentiality impact level recommended for legal investigation information is moderate .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_02065", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Trusted Geolocation in the Cloud_ Proof of Concept Implementation say about HTCC 4.1.0 Product Documentation:? According to Trusted Geolocation in the Cloud_ Proof of Concept Implementation, HTCC 4.1.0 Product Documentation:: ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Trusted Geolocation in the Cloud_ Proof of Concept Implementation."}]}
{"id": "nist_02066", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Derived Personal Identity Verification (PIV) Credentials say about Figure 2-6 Certificate Profile Attributes? According to Derived Personal Identity Verification (PIV) Credentials, Figure 2-6 Certificate Profile Attributes: <!-- image --> 5. Repeat Step 4 for the PIV-Auth-1-yr-v2, PIV-CardAuth-1yr-v1, and PIV-Sig-1yr-v1 certificate profiles. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_02067", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog? Discussion: Some IoT devices may have multiple users within an organization and require support for role and account management. These accounts may then be used are part of the identification, authentication, and authorization of users based on roles and privileges.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog."}]}
{"id": "nist_02068", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Data Integrity_ Recovering from Ransomware and Other Destructive Events provide? (Section 67) last known good | Data Integrity -1 | | CR 2 | The DI example imple- mentation shall recover when malware destroys data on user's machine. | | | | CR 2.a | | Provide file integrity monitor | Data Integrity -2 | | CR 2.b | | Revert to last known good | Data Integrity -2 | | CR 3 | The DI example imple- mentation shall recover when a user modifies a configuration file in viola- tion of established base- lines.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Recovering from Ransomware and Other Destructive Events."}]}
{"id": "nist_02069", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Requirements for Cryptographic Modules say about SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES? (Part 4) According to Security Requirements for Cryptographic Modules, SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES: formation about the CMVP can be obtained from the - a. National Institute of Standards and Technology, Information Technology Laboratory, 100 Bureau Drive, Stop 8900, Gaithersburg, MD 20899-8900. - b. Canadian Centre for Cyber Security, P.O. Box 9703, Terminal, Ottawa, Ontario K1G 3Z4 - c. CMVP URL 10. Approved Security Functions. Cryptographic modules that conform to this standard shall employ Approved security functions such as cryptographic algorithms, cryptographic key management techniques, and authentication techniques that have been approved for protecting Federal government sensitive information. Approved security functions include those that are either: - a. specified in a Federal Information Processing Standard (FIPS), - b. adopted in a FIPS and specified either in an appendix to the FIPS or in a document referenced by the FIPS, - c. specified in NIST SP 800-140C as an Approved security function, or - d. specified in NIST SP 800-140D as an Approved sensitive security parameter establishment method. 11. Interpretation. Questions concerning the content and specifications of this standard should be addressed to: Director, Information Technology Laboratory, ATTN: FIPS 140-3 Interpretation, National Institute of Standards and Technology, 100 Bureau Drive, Stop 8900, Gaithersburg, MD 20899-8900. Resolution of questions regarding this standard will be provided by the validation authorities at the National Institute of Standards and Technology and the Canadian Centre for Cyber Security. 12. Implementation Schedule. This standard becomes effective six months after approval by the Secretary of Commerce. A minimum transition period of 6 months after approval is provided for testing labs to develop and implement FIPS 140-3 testing. A test report for modules demonstrating compliance will be submitted to the CMVP for review and validation.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Security Requirements for Cryptographic Modules."}]}
{"id": "nist_02070", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.3.4.1 SP 800-56B Key Transport according to NIST Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms According to Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms, 5.3.4.1 SP 800-56B Key Transport: SP 800-56B specifies a method for transporting keys whereby the sender uses the receiver's public key to securely transport keying material to the receiver. Figure 7 provides a simplified example of the key-transport method in SP 800-56B. The receiver must have a key pair that is used during a key-transport transaction. Key transport is accomplished as follows. The sender: 1. Obtains the public key of the intended receiver, 2. Generates a symmetric key to be transported, 3. Encrypts the symmetric key using the receiver's public key, and 4. Sends the resulting ciphertext key to the receiver. The receiver: 5. Uses the private key to decrypt the ciphertext key, thus obtaining the original plaintext key. 6. Optionally performs key confirmation; although this step is optional, it is highly recommended to provide assurance that both parties now have the same symmetric key. 85 SP 800-71, Recommendation for Key Establishment Using Symmetric Block Ciphers . Figure 7: SP 800-56B Key Transport Example <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms."}]}
{"id": "nist_02071", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Contacts: according to NIST Computer Security Division 2011 Annual Report According to Computer Security Division 2011 Annual Report, Contacts:: Mr. Fernando Podio fernando.podio@nist.gov Mr. Dylan Yaga dylan.yaga@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2011 Annual Report."}]}
{"id": "nist_02072", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE) provide? (Section 165) ng to all three data actions identified in the privacy risk assessment. These training and support mitigations can help Orvilia appropriately inform employees about the system and its data processing. Training sessions can also highlight any privacy-preserving techniques used, such as for disclosures to third parties. Training should include confirmation from employees that they understand the actions that can be taken on their devices and the consequences-whether this involves blocking access or wiping data. Employees may also be informed of data retention periods and when their data will be disposed of. This can be more effective than sharing a privacy notice, which research has shown that individuals are unlikely to read. This can be achieved using push notifications, similar to those pictured in screenshots in Appendix H, Threat Event 6, to help directly link administrative actions on devices to relevant threats and help employees understand why an action is being taken. Notifications of changes to policies can help increase system predictability by setting employee expectations appropriately with the way the system processes data and the resulting actions. By providing employees with a point of contact in the organization who can respond to inquiries and concerns regarding the system, employees can gain a better understanding of the system's processing of their data, which enhances predictability. Detailed information and screenshots for some of this practice guide's threat events and their testing results are provided below. A part of Threat Event 1's testing conclusions is shown in the following screen capture, where the calendar access permission is being set to a risk score of 10. This allows MobileIron to automatically apply the mobile threat protection high-risk label to the device and quarantine the device until the privacy-intrusive application is removed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_02073", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities say about 5. Comparing CCSS to CVSS and CMSS? (Part 2) According to The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities, 5. Comparing CCSS to CVSS and CMSS: nd CMSS, because their vulnerabilities can be exploited without exploit code and are already known to exist. Also, CMSS vulnerabilities and many CCSS vulnerabilities do not have complete remediations. So CCSS and CMSS have similar sets of temporal metrics, quite different from those of CVSS, that address the general prevalence of attacks against the vulnerability and the general effectiveness of available remediation measures, such as using antivirus software or conducting awareness activities. CCSS and CMSS also offer similar sets of environmental metrics, which are considerably more complex than CVSS's metrics. CVSS has three: Collateral Damage Potential, Target Distribution, and Security Requirements. These metrics are all part of CCSS and CMSS as well, although Target Distribution has been renamed Local Vulnerability Prevalence. Two other metrics have been added to CCSS and CMSS: Perceived Target Value, which measures how attackers value the targets in a specific local environment as opposed to other environments, and Local Remediation Level, which measures the effectiveness of mitigation measures in the local environment. CCSS and CMSS also divide their environmental metrics into two groups: Exploitability and Impact. This allows Exploitability and Impact environmental subscores to be generated for CCSS and CMSS; such subscores are not available in CVSS. 15 The other specifications are NIST IR 7435 and NIST IR 7517 ().", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities."}]}
{"id": "nist_02074", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems say about B. CONCEPT OF EMERGENCY RESPONSE? According to Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems, B. CONCEPT OF EMERGENCY RESPONSE: The following list provides emergency phone numbers for use during a crisis:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems."}]}
{"id": "nist_02075", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-1 in Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity? (Part 45) Control AC-1: Table 5-1 Mapping of Device Cybersecurity Capabilities and Nontechnical Supporting Capabilities to NIST Cybersecurity Framework Subcategories of the IIoT Project | Cybersecurity Framework v1.1 Subcategory | Device Cybersecurity Capabilities | Manufacturer Nontechnical Supporting Capabilities | Related NERC CIP ID(s) | |---------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------| | PR.AC-1: Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users, and processes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity."}]}
{"id": "nist_02076", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain ASSESSMENT OBJECTIVE according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, ASSESSMENT OBJECTIVE: Determine if: A.03.04.11.a[01]: the location of CUI is identified and documented. A.03.04.11.a[02]: the system components on which CUI is processed are identified and documented. A.03.04.11.a[03]: the system components on which CUI is stored are identified and documented. A.03.04.11.b[01]: changes to the system or system component location where CUI is processed are documented. A.03.04.11.b[02]: changes to the system or system component location where CUI is stored are documented.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02077", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to IPsec VPNs provide? (Section 288) | Public Law | | PAKE | Password Authenticated Key Exchange | | PAP | Password Authentication Protocol | | PFS | Perfect Forward Secrecy | | PKCS | Public Key Cryptography Standards | | PKI | Public Key Infrastructure | | PMTUD | Path Maximum Transmission Unit Discovery | | POP | Post Office Protocol | | PPK | Post-quantum Pre-shared Key | | PPP | Point-to-Point Protocol | | PPTP | Point-to-Point Tunneling Protocol | | PRF | Pseudorandom Function | | PSK | Pre-shared Key | | PSS | Probabilistic Signature Scheme | | QoS | Quality of Service | | RADIUS | Remote Authentication Dial In User Service | | RAM | Random Access Memory | | RFC | Request for Comment | | RMON | Remote Monitoring | | S/MIME | Secure/Multipurpose Internet Mail Extensions | | SA | Security Association | | SAD | Security Association Database | | SAN | subjectAltName | | SDN | Software Defined Networking | | SDP | Session Description Protocol | | SDWAN | Software Defined Wide Area Network | | SHA | Secure Hash Algorithm | |---------|--------------------------------------------------------| | SHS | Secure Hash Standard | | SIP |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, sso. Contains security framework guidance for authentication systems. Source: Guide to IPsec VPNs."}]}
{"id": "nist_02078", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Advanced Identity Workshop on Applying Measurement Science in the Identity Ecosystem_ Summary and Next Steps provide? (Section 1) Summary and Next Steps Michael E. Garcia Paul A. Grassi This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.IR.8103 <!-- image --> Summary and Next Steps Michael E. Garcia Paul A. Grassi Applied Cybersecurity Division Information Technology Laboratory This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.IR.8103 September 2016 <!-- image --> U.S. Department of Commerce Penny Pritzker, Secretary National Institute of Standards and Technology Willie May, Under Secretary of Commerce for Standards and Technology and Director This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.IR.8103 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. 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 ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Advanced Identity Workshop on Applying Measurement Science in the Identity Ecosystem_  Summary and Next Steps."}]}
{"id": "nist_02079", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Domain Name System-Based Electronic Mail Security say about Zones that pre-publish the new public key should observe the following:? (Part 1) According to Domain Name System-Based Electronic Mail Security, Zones that pre-publish the new public key should observe the following:: Zones that pre-publish the new public key should observe the following: 31. Checklist item 31: The secure zone that pre-publishes its public key should do so at least one TTL period before the time of the key rollover. 32. Checklist item 32: After removing the old public key, the zone should generate a new signature (RRSIG RR), based on the remaining keys (DNSKEY RRs) in the zone file. 33. Checklist item 33: A DNS administrator should have the emergency contact information for the immediate parent zone to use when an emergency KSK rollover must be performed. 34. Checklist item 34: A parent zone must have an emergency contact method made available to its delegated child subzones in case of emergency KSK rollover. There also should be a secure means of obtaining the new KSK. 35. Checklist item 35: Periodic re-signing should be scheduled before the expiration field of the RRSIG RRs found in the zone. This is to reduce the risk of a signed zone being rendered bogus because of expired signatures. 36. Checklist item 36: The serial number in the SOA RR must be incremented before re-signing the zone file. If this operation is not done, secondary name servers may not pick up the new signatures because they are refreshed purely on the basis of the SOA serial number mismatch. The consequence is that some security-aware resolvers will be able to verify the signatures (and thus have a secure response) but others cannot. 37. Checklist item 37: Recursive servers/resolvers should be placed behind an organization's firewall and configured to only accept queries from internal hosts (e.g., Stub Resolver host). 38. Checklist Item 38: Whenever Aggregate Caches are deployed, the forwarders must be configured to be Validating Resolvers. 39. Checklist item 39: Each recursive server must have a root hints file containing the IP address of one or more DNS root servers. The information in the root hints file should be periodically checked for correctness. 40.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_02080", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Expected Outputs according to NIST_SP_800-37r2_Risk_Management_Framework? Expected Outputs: Documented authorization boundary.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_02081", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Purpose: according to NIST Government Smart Card Interoperability Specification, Version 2.1 According to Government Smart Card Interoperability Specification, Version 2.1, Purpose:: Computes a symmetric key cryptogram in response to a challenge. In cases where the card reader authenticates the smart card, this function does not return a cryptogram. In these cases a BSI\\_TERMINAL\\_AUTH will be returned if the card reader successfully authenticates the smart card. BSI\\_ACCESS\\_DENIED is returned if the card reader fails to authenticate the smart card. ``` Prototype: ( ``` Parameters: ``` unsigned long gscBsiSkiInternalAuthenticate IN unsigned long hCard , IN string AID , IN octet algoID , IN sequence<byte> challenge , INOUT sequence<byte> cryptogram ); ``` hCard: AID: algoID:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_02082", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain COMMON ABBREVIATIONS according to NIST Guide for Conducting Risk Assessments According to Guide for Conducting Risk Assessments, COMMON ABBREVIATIONS: APT Advanced Persistent Threat BCP Business Continuity Plan BIA Business Impact Analysis CNSS Committee on National Security Systems COOP Continuity of Operations DoD Department of Defense DHS Department of Homeland Security DNI Director of National Intelligence EA Enterprise Architecture FIPS Federal Information Processing Standards FISMA Federal Information Security Management Act ICS Industrial Control System IEC International Electrotechnical Commission ISO International Organization for Standardization IT Information Technology JTF Joint Task Force NIST National Institute of Standards and Technology NOFORN Not Releasable to Foreign Nationals ODNI Office of the Director of National Intelligence OMB Office of Management and Budget RAR Risk Assessment Report RMF Risk Management Framework SCAP Security Content Automation Protocol SP Special Publication TTP Tactic Technique Procedure U.S.C. United States Code \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, rmf, fips. General security reference material without sensitive content. Source: Guide for Conducting Risk Assessments."}]}
{"id": "nist_02083", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations provide? (Section 44) 10 specifies how TLS is to be used in government applications. | | Trust anchor | An authoritative entity represented by a public key and associated data (see RFC 5914 11 ). | | Unauthorized disclosure | An event involving the exposure of information to entities not authorized access to the information. | | User | A human entity. | | Validity period | The period of time during which a certificate is intended to be valid; the period of time between the start date and time and end date and time in a certificate. | 8 RFC 5246, The Transport Layer Security (TLS) Protocol Version 1.2. 9 RFC 8446, The Transport Layer Protocol (TLS) Version 1.3. 10 SP 800-52, Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations . 11 RFC 5914, Trust Anchor Format. Wrapped keying material Keying material that has been encrypted and its integrity protected using an approved key wrapping algorithm and a key wrapping key in order to disguise the value of the underlying plaintext key. X.509 certificate The X.509 public-key certificate or the X.509 attribute certificate, as defined by the ISO/ITU-T 12 X.509 standard. Most commonly (including in this document), an X.509 certificate refers to the X.509 public-key certificate.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations."}]}
{"id": "nist_02084", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks? (Part 44) Control AM-1: | IoT devices may be complex and dynamic, with sensing functionality that can collect PII being frequently added and removed. Consideration 1 | PA-3, Purpose Specification | \u2022 PII may be hard to track such that individuals, as well as device owners/operators, may not have reliable assumptions about how PII is being processed, causing informed decision making to be more difficult. | | Challenges for Individual IoT Devices | Challenges for Individual IoT Devices | Affected Draft NIST SP 800-53 Revision 5 Controls | Implications for the Organization | |-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 43. | The IoT device may be accessed remotely, allowing the sharing of PII outside the control of the administrator. | PA-4, Information Sharing with External Parties | \u2022 PII may be shared in ways that are out of compliance with regulatory requirements or an organization's policies.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks."}]}
{"id": "nist_02085", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide say about 5.3.4. Person or Entity Authentication (\u00a7 164.312(d)) 139? (Part 4) According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide, 5.3.4. Person or Entity Authentication (\u00a7 164.312(d)) 139: es, such as a fingerprint \u2022 MFA utilizes two or more authentication approaches to enforce stronger authentication. \u2022 Consider implementing MFA solutions 140 when the risk to ePHI is sufficiently high. | \u2022 What are the strengths and weaknesses of each available option? \u2022 Which can be best supported with assigned resources (e.g., budget/staffing)? \u2022 What level of authentication is appropriate for each access to ePHI based on the assessment of risk? \u2022 Has the organization identified all instances of access to ePHI (including by services, vendors, or application programming interfaces [APIs]) and considered appropriate authentication requirements based on the risk assessment? | 139 See Sec. 5.3.1, HIPAA Standard: Access Control ; Sec. 5.3.2, HIPAA Standard: Audit Controls ; and [SP 800-63B], Digital Identity Guidelines: Authentication and Lifecycle Management . 140 Some MFA implementations may offer greater protection than others. Consider the pros and cons of each MFA option in light of the risk to ePHI.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, mfa. Contains security framework guidance for authentication systems. Source: Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide."}]}
{"id": "nist_02086", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Fingerprint Identification and Mobile Handheld Devices_ An Overview and Implementation provide? (Section 14) n the fingerprint template information file, and the user gains access to the device. Note that for the lightweight variant, fingerprint templates are maintained in the memory of the fingerprint unit. Once enrolled, subsequently powering on or booting up the device prompts the user to provide a live fingerprint image for verification. The verification process uses information from the mechanism settings file to encrypt information between the device and the fingerprint reader. A correct match against the enrolled fingerprint templates in the fingerprint information file results in successful authentication and access is granted to the device. If too many authentication failures occur, further attempts are blocked temporarily to prevent unrestricted password guessing attempts. Any time after gaining access, a user can update the set of enrolled fingerprints by using an available icon to launch the process and providing a live fingerprint image for verification, which then follows the same procedure described above for verification at power on or boot up. In Figure 3, the 'Verify Fingerprint' boxes associated with fingerprint update do not show the information flows discussed above, but are present implicitly. Successful verification allows the user to enroll new fingerprint images adding to or replacing the existing set. A successful enrollment updates the fingerprint template information file and the user regains access to the device. For user authentication the fundamental threat is an attacker impersonating a user and gaining control of the device and its contents. Fingerprint units should be embedded into devices that are designed to resist physical tampering and avoid exposing the communications channel between the device and the unit.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Fingerprint Identification and Mobile Handheld Devices_ An Overview and Implementation."}]}
{"id": "nist_02087", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Key Management Documents say about 7.3.3 Confidentiality and Integrity Algorithm? According to Secure Data Network Systems (SDNS) Key Management Documents, 7.3.3 Confidentiality and Integrity Algorithm: The confidentiality and integrity algorithm option is used for negotiating use of algorithms other than that used to form the TEK for data security. This option includes the negotiation of the algorithm mode and the icv length, as defined above.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_02088", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain allowlist according to NIST Digital Identity Guidelines_ Federation and Assertions According to Digital Identity Guidelines_ Federation and Assertions, allowlist: A documented list of specific elements that are allowed, per policy decision. In federation contexts, this is most commonly used to refer to the list of RPs that are allowed to connect to an IdP without subscriber intervention. This concept has historically been known as a whitelist .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Digital Identity Guidelines_ Federation and Assertions."}]}
{"id": "nist_02089", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Zero Trust Architecture say about 2.1 Principios de la confianza cero? (Part 3) According to Zero Trust Architecture, 2.1 Principios de la confianza cero: nte puede incluir la cuenta de usuario (o la identidad del servicio) y cualquier otra caracter\u00edstica asociada asignada por la empresa a esa cuenta o artefacto para autenticar las tareas automatizadas. El estado de los activos solicitados puede incluir caracter\u00edsticas del dispositivo como las versiones de software instaladas, la ubicaci\u00f3n de la red, la hora y la fecha de la solicitud, el comportamiento observado previamente y las credenciales instaladas. Los factores de comportamiento incluyen, entre otros, an\u00e1lisis automatizados del sujeto, an\u00e1lisis del dispositivo y mediciones de las desviaciones de los patrones de utilizaci\u00f3n observados. La pol\u00edtica es el conjunto de reglas de acceso basado en los atributos que una organizaci\u00f3n asigna a un sujeto, a una base de datos o a una aplicaci\u00f3n. Las caracter\u00edsticas del entorno pueden incluir factores como la ubicaci\u00f3n de la red del solicitante, la hora, los ataques activos notificados, etc. Estas reglas y particularidades se basan en las necesidades del desarrollo empresarial y en un nivel de riesgo aceptable. Las pol\u00edticas de acceso a los recursos y los permisos de acci\u00f3n pueden variar en funci\u00f3n de la sensibilidad de estos y de los datos. Adem\u00e1s, se aplican los principios de m\u00ednimo privilegio para restringir tanto la visibilidad como la accesibilidad. 5. La empresa supervisa y mide la integridad y la postura de seguridad de todos los activos propios y de los asociados. Ning\u00fan activo es intr\u00ednsecamente confiable, por lo que la empresa examina la postura de seguridad de cada uno de ellos cuando eval\u00faa la solicitud de un recurso. Una organizaci\u00f3n que implemente una ZTA debe establecer un programa de Diagn\u00f3stico y Mitigaci\u00f3n Continuos (CDM) o un sistema similar para supervisar el estado de los dispositivos y las aplicaciones. A su vez, debe aplicar parches o correcciones si es necesario.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Zero Trust Architecture."}]}
{"id": "nist_02090", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to IPsec VPNs say about 8.3 WireGuard? (Part 2) According to Guide to IPsec VPNs, 8.3 WireGuard: (continuous packet sequence numbers). It supports PPK and has the same seamless reconnection properties as IKEv2 MOBIKE, where a device can switch network interfaces without losing the VPN connection. WireGuard takes advantage of multiple CPUs when present, unlike typical SSL VPNs that are bound to one CPU. The protocol does not allow for DHCP-style IP address allocation, and IP addresses are hardcoded in its configuration file on the client and server. DNS configuration has to be conveyed via a provisioning protocol. WireGuard lacks authentication support using certificates or PSKs. It does not support a transport mode configuration, making it less suitable for mesh encryption. It does not support AES-GCM. WireGuard is mostly intended as a remote access VPN even though it leaves most of the configuration of such functionality to an additional, unspecified provisioning protocol. While it can be used in a gateway-to-gateway or host-to-host architecture, it misses the optimizations and flexibility of IPsec in these architectures.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to IPsec VPNs."}]}
{"id": "nist_02091", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Digital Identity Guidelines provide? (Section 70) igital Identity Guidelines selection, additional assessments and evaluations that are specific to the baseline controls for the assurance levels may be required for the underlying information system. \u2022 Customer Experience \u2013 Determine whether implementation of the initial assurance levels may create substantial or unacceptable barriers to individuals seeking to access services. Customer experience assessments SHALL consider impacts that result from the identity management controls to ensure that they do not cause undue burdens, frustrations, or frictions for individuals and that there are pathways to provide service to users of all capabilities, resources, technology access, and economic statuses. \u2022 Threat Resistance \u2013 Determine whether the defined assurance level and related controls will address specific threats to the online service based on the operational environment, its threat actors, and known tactics, techniques, and procedures (TTPs). Threat assessments SHALL consider specific known and potential threats, threat actors, and TTPs within the implementation environment for the identity management functions. For example, certain benefits programs may be more subject to familial threats or collusion. Based on their assessments, organizations MAY implement supplemental controls specific to the communities served by their online service. Conversely, organizations MAY tailor their assessed xAL down or modify their baseline controls if their threat assessment indicates that a reduced threat posture is appropriate based on their environment. Organizations SHOULD leverage consultation and feedback from the entities and communities served to ensure that the tailoring process addresses their known constraints. Organizations SHOULD also conduct additional business-specific assessments as appropriate to fully represent mission- and domain-specific considerations that have not been captured here.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Digital Identity Guidelines."}]}
{"id": "nist_02092", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CP-08(03) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control CP-08(03): TELECOMMUNICATIONS SERVICES | SEPARATION OF PRIMARY AND ALTERNATE PROVIDERS", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_02093", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document say about Appendix A Glossary? (Part 2) According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document, Appendix A Glossary: thority | An authorized entity that stores, signs, and issues digital cryptographic key certificates. It acts to validate identities and bind them to cryptographic key pairs with digital certificates. | | Certificate and Key | Functions for securely issuing, monitoring, facilitating, and executing | | Governance | digital X .509 certificates and managing the cryptographic keys exchanged using the certificates. | | Client | System entities that request and use a service provided by another system entity called a server. Usually, it is understood that the client and server are automated components of the system, and the client makes the request on behalf of a human user. Clients may initiate encrypted traffic. They are interfaces for human users, devices, applications, and processes to access network functions, including the requesting of certificates and keys. | | Cryptography | The discipline that embodies the principles, means, and methods for the transformation of data to hide their semantic content, prevent their unauthorized use, or prevent their undetected modification. It embodies the principles, means, and methods for providing information security, including confidentiality, data integrity, non- repudiation, and authenticity. | | Decryption | The process of a confidentiality mode that transforms encrypted data into the original usable data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document."}]}
{"id": "nist_02094", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Device Security_ Bring Your Own Device (BYOD) say about 3.3 Assumptions? (Part 2) According to Mobile Device Security_ Bring Your Own Device (BYOD), 3.3 Assumptions: has the technology in place to support this implementation or has access to the off-the-shelf technology used in this build, which we assume will perform as described by the respective product vendor. - The organization has familiarized itself with existing standards and any associated guidelines (e.g., NIST Cybersecurity Framework [1]; NIST Privacy Framework [2]; NIST SP 800-124 Revision 2, Guidelines for Managing the Security of Mobile Devices in the Enterprise [6]; NIST SP 1800-4 Mobile Device Security: Cloud and Hybrid Builds [7]) relevant to implementation of the example solution proposed in this practice guide. We also assume that any existing technology used in the example solution has been implemented in a manner consistent with these standards. - The organization has instituted relevant mobile device security and privacy policies, and these will be updated based on implementation of this example solution. - The organization will provide guidance and training to its employees regarding BYOD usage and how to report device loss or suspected security issues in which their devices are involved. This guidance will be periodically reviewed and updated, and employees will be regularly trained on BYOD usage.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_02095", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Security for Full Virtualization Technologies provide? (Section 20) lines, including minimum requirements, for providing adequate information security for all agency operations and assets; but such standards and guidelines shall not apply to national security systems. 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 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. The purpose of the guide is to discuss the security concerns associated with full virtualization technologies for server and desktop virtualization, and to provide recommendations for addressing these concerns. All forms of virtualization other than server and desktop full virtualization are outside the scope of this document. Most existing recommended security practices remain applicable in virtual environments. The practices described in this document build on and assume the implementation of practices described in other NIST publications. The intended audience for this document is system and security administrators, security program managers, information system security officers, and others who have responsibilities for or are otherwise interested in the security of server or desktop full virtualization technologies. This document assumes that readers have some operating system, networking, and security expertise.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: Guide to Security for Full Virtualization Technologies."}]}
{"id": "nist_02096", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 795) hash, and using the public key to verify the hash information. Organizations that employ cryptographic mechanisms also consider cryptographic key management solutions. Related Controls: SC-12, SC-13. (7) SOFTWARE, FIRMWARE, AND INFORMATION INTEGRITY | INTEGRATION OF DETECTION AND RESPONSE Incorporate the detection of the following unauthorized changes into the organizational incident response capability: [Assignment: organization-defined security-relevant changes to the system]. Discussion: Integrating detection and response helps to ensure that detected events are tracked, monitored, corrected, and available for historical purposes. Maintaining historical records is important for being able to identify and discern adversary actions over an extended time period and for possible legal actions. Security-relevant changes include CHAPTER THREE PAGE 346 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ unauthorized changes to established configuration settings or the unauthorized elevation of system privileges. Related Controls: AU-2, AU-6, IR-4, IR-5, SI-4. (8) SOFTWARE, FIRMWARE, AND INFORMATION INTEGRITY | AUDITING CAPABILITY FOR SIGNIFICANT EVENTS Upon detection of a potential integrity violation, provide the capability to audit the event and initiate the following actions: [Selection (one or more): generate an audit record; alert current user; alert [Assignment: organization-defined personnel or roles]; [Assignment: organization-defined other actions]].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: adversary, incident response. Contains technical security guidance that could inform defensive posture. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02097", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Attribute Metadata_ A Proposed Schema for Evaluating Federated Attributes say about Table of Contents? (Part 6) According to Attribute Metadata_ A Proposed Schema for Evaluating Federated Attributes, Table of Contents: | 8 | | | | 3.2.1 Metadata Categories | ............................................................................8 | | 4 | Use Cases.............................................................................................................19 | Use Cases.............................................................................................................19 | | | | 4.1 Federated Access to Classified Document in an Information Sharing Environment.......................................................................................................... | 4.1 Federated Access to Classified Document in an Information Sharing Environment..........................................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Attribute Metadata_ A Proposed Schema for Evaluating Federated Attributes."}]}
{"id": "nist_02098", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Fiscal Year 2021 Cybersecurity and Privacy Annual Report say about Foreword? (Part 2) According to Fiscal Year 2021 Cybersecurity and Privacy Annual Report, Foreword: ge risk (for example, we are launching an update process for the Cybersecurity Framework and reviewing a host of other NIST frameworks and guidance documents with an eye on improving their alignment). We have also made selections of finalists and alternate candidates to be considered for PQC standardization. Stay tuned for updates to our foundational digital identity guidelines and for information on some of our new projects related to cybersecurity workforce and privacy (and be on the lookout for a Workforce Framework). We also will unveil a new tool that will make it simpler and quicker for users of NIST cybersecurity and privacy products to navigate content across NIST resources. While Picasso was famous for a completely different form of art, cybersecurity and privacy is our 'art'-and our science-and we are ready for 50 more years of innovation, collaboration, and action.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Fiscal Year 2021 Cybersecurity and Privacy Annual Report."}]}
{"id": "nist_02099", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Recovering from Ransomware and Other Destructive Events say about Notes:? According to Data Integrity_ Recovering from Ransomware and Other Destructive Events, Notes:: - a. It is recommended that you install Tripwire Log Center on a separate system from Tripwire Enterprise. - b. You will need to install JRE8 and the Crypto library. Instructions are also in the Tripwire Log Center Installation Guide. - c. You may need to unblock port 9898 on your firewall for the Tripwire enterprise agents. - d. Do not install PostgreSQL if you wish to use a database on another system. - e. When it finishes installing there should be a configuration wizard.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Recovering from Ransomware and Other Destructive Events."}]}
{"id": "nist_02100", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain ASSESSMENT OBJECTIVE according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, ASSESSMENT OBJECTIVE: Determine if: A.03.14.02.ODP[01]: the frequency at which malicious code protection mechanisms perform scans is defined . A.03.14.02.a[01]: malicious code protection mechanisms are implemented at system entry and exit points to detect malicious code. A.03.14.02.a[02]: malicious code protection mechanisms are implemented at system entry and exit points to eradicate malicious code. A.03.14.02.b: malicious code protection mechanisms are updated as new releases are available in accordance with configuration management policy and procedures. A.03.14.02.c.01[01]: malicious code protection mechanisms are configured to perform scans of the system &lt;A.03.14.02.ODP[01]: frequency&gt; . A.03.14.02.c.01[02]: malicious code protection mechanisms are configured to perform real-time scans of files from external sources at endpoints or system entry and exit points as the files are downloaded, opened, or executed. malicious code protection mechanisms are configured to block malicious code, quarantine malicious code, or take other actions in response to A.03.14.02.c.02: malicious code detection.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02101", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines say about References? (Part 3) According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines, References: 1d872639 - [19] GitLab Docs (2023) Dependency Scanning . Available at - [20] GitLab Docs (2023) Secret Detection . Available at - [21] GitLab Docs (2023) Push Rules . Available at ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines."}]}
{"id": "nist_02102", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Trustworthy Email provide? (Section 148) y trust only a specific certificate or public key. Essentially, DANE replaces reliance on the security provided by the CA system with reliance on the security provided by DNSSEC. DANE complements TLS. \ufffde TLS handshake yields a n encrypted connection between a server and a client and provides a server's X.509 certificate to the client. 22 \ufffde TLS protocol does not define how the certificate should be authenticated . Some implementations may do this as part of the TLS handshake, and some may leave it to the application to perform authentication. Whichever way is used , there is still a vulnerability: a CA can issue certificates for any domain, and if that a CA is compromised (as has happened more than once all too recently), an attacker can have it can issue a replacement certificate for any domain and take control of a server's connections. Ideally, issuance and delivery of a certificate should be tied absolutely to the given domain. DANE creates this explicit link by allowing the server domain owner to create a TLSA resource record in the DNS [RFC6698] [RFC7671] , which identifies the certificate, its public key, or a hash of either . When the client receives an X.509 cer tificate in the TLS negotiation, it looks up the TLSA RR for that domain and matches the TLSA data against the certificate as part of the client' s certificate validation procedure . DANE has a number of usage models (called Certificate Usage s) to accommodate users who require different forms of authentication. \ufffdese Certificate Usages are given mnemonic names [RFC7218]: - With Certificate Usage DANE-TA(2), the TLSA RR designates a trust-anchor that issued one of the certificates in the PKIX chain . [RFC7671] requires that DANE-TA(2) trust anchors be included in the server \"certificate message\" unless the entire certificate is specified in the TLSA record ( i.e., usage 2 0 0, indicating the TLSA RR contains a local root certificate ).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Trustworthy Email."}]}
{"id": "nist_02103", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Graphics Files Format according to Cell Phone Forensic Tools_ an Overview and Analysis Update? Graphics Files Format: N.A. - The Motorola C333 does not support graphic files (e.g., . bmp , . jpg , . gif , . png , . tif ). (NA)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis Update."}]}
{"id": "nist_02104", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Inter-Chapter Dependencies according to NIST Proceedings of the Workshop of the Federal Criteria for Information Technology Security According to Proceedings of the Workshop of the Federal Criteria for Information Technology Security, Inter-Chapter Dependencies: The discussion included global perspectives on the expression of requirements. Since we don't want to be too general or too prescriptive, the requirement for expressing what to build and what counts for success remains an issue. From the discussion, we still seem to have bi-polar views endorsing on the one hand, increased generalization to allow vendor flexibility, and on the othCT hand, increased detailed specifications to constrain evaluator interpretations. Since the criteria written to date, including the PC. provide mostly generalized expression of requirements, the criteria themselves mandate both vendor and evaluator interpretation. This is a natural process, but it has led to adversarial relationships and some ''leligious' conflicts between vendors and evaluators. It was noted that dependency linkages between and among functional, developmental, and evaluation requirements should be explicitly noted at ^propriate points in conjunction with a requirement statement One thing that did seem important to the discussicxi was the need to express the functional and development requirements in measurable (qualitative and/or quantitative) terms and directly link both vendor and evaluator actions to these requirements. This action linkage is important whenever the requirements are qualitative, and subjective judgement must be applied. Additionally, the issue of proprietary information contained in evaluator criteria interpretations was discussed. Since many, if not most, of these evaluator interpretations involve assessments of one or more vendor's solutions (expressed in proprietary terms) against a particular TCSEC requirement, these interpretations are not available to the vendors at large. Since the evaluators' interpretations provide a measure (in some cases an extremely significant measure) of what counts for success, a means to publicly express this measure, without compromising propHietary information, must be devised.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Proceedings of the Workshop of the Federal Criteria for Information Technology Security."}]}
{"id": "nist_02105", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Confidentiality_ Detect, Respond to, and Recover from Data Breaches say about 2.4.3 Add Stealthwatch Flow Collector to the Management Console? According to Data Confidentiality_ Detect, Respond to, and Recover from Data Breaches, 2.4.3 Add Stealthwatch Flow Collector to the Management Console: 1. Navigate to the Stealthwatch Flow Collector Console from a web browser. The URL will be address of Stealthwatch FC &gt;&gt;. 2. Login using the default username and password (should be provided by product vendor). 3. Click Continue . <!-- image --> <!-- image --> 4. Change the passwords for the admin and root accounts. 5. Click Next . 6. Confirm the networking information is correct and click Next . 7. Confirm the domain name for Flow Collector is correct. <!-- image --> <!-- image --> 8. Click Next . 9. Add the DNS server(s) Stealthwatch should be using. 10. Click Next . 11. Enter the NTP server(s) Stealthwatch should use. <!-- image --> <!-- image --> 12. Click Next . 13. Click Restart and Proceed . <!-- image --> <!-- image --> 14. After it restarts, log in again, and click Continue . 15. Enter the IP of the Stealthwatch Management Console. 16. Click Save . <!-- image --> <!-- image --> 17. Accept the certificate by clicking Yes . 18. Enter the username and password for the Stealthwatch Management Console. 19. Click Next . 20. Enter the Domain and Flow Collection Port . <!-- image --> <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Confidentiality_ Detect, Respond to, and Recover from Data Breaches."}]}
{"id": "nist_02106", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Situational Awareness for Electric Utilities? (Part 174) Control AM-1: Radiflow iSID Web Dashboard <!-- image --> Allow learning to take place for 5 to 7 days. - Toggle the Detection switch on the left bar under Main Network. - Setup and configuration are now complete. ## 2.12 RSA Archer Security Operations Management (E13) Governance, risk, and compliance (GRC) platforms allow an organization to link strategy and risk, adjusting strategy when risk changes, while remaining in compliance with laws, regulations, and security policies. RSA Archer Security Operations Management, based in part on the RSA Archer GRC platform, was used to perform the task of the Analysis Workflow Engine and Security Incident Response and Management. For more information, visit \u2026 - - - ## 2.12.1 System Requirements This build installed a multihost RSA Archer GRC platform node on a VMware VM with the Microsoft Windows Server 2012R2 operating system to provide the Security Incident Response Management environment needed. Note: All components, features, and configurations presented in this guide reflect what we used based on vendors' best practices and requirements. Please refer to vendors' official documentation for complete instructions for other options. ## 2.12.2 Preinstallation We chose the multihost deployment option for installing and configuring the GRC platform on multiple VMs under the Microsoft Windows Server 2012R2 Operating System. The web application and services are running on one server, instance database/Microsoft SQL Server is running on one server, and integration components for Security Incident Response are running on a third server.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Situational Awareness for Electric Utilities."}]}
{"id": "nist_02107", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 116) h [Assignment: organization-defined information, source, and destination objects] to enforce [Assignment: organization-defined information flow control policies] as a basis for flow control decisions. Discussion: Information flow enforcement mechanisms compare security and privacy attributes associated with information (i.e., data content and structure) and source and destination objects and respond appropriately when the enforcement mechanisms encounter information flows not explicitly allowed by information flow policies. For example, an information object labeled Secret would be allowed to flow to a destination object labeled Secret, but an information object labeled Top Secret would not be allowed to flow to a destination object labeled Secret. A dataset of personally identifiable information may be tagged with restrictions against combining with other types of datasets and, thus, would not be allowed to flow to the restricted dataset. Security and privacy attributes can also include source and destination addresses employed in traffic filter firewalls. Flow enforcement using explicit security or privacy attributes can be used, for example, to control the release of certain types of information. Related Controls: None. (2) INFORMATION FLOW ENFORCEMENT | PROCESSING DOMAINS Use protected processing domains to enforce [Assignment: organization-defined information flow control policies] as a basis for flow control decisions. Discussion: Protected processing domains within systems are processing spaces that have controlled interactions with other processing spaces, enabling control of information flows between these spaces and to/from information objects. A protected processing domain can be provided, for example, by implementing domain and type enforcement.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, top secret. Contains guidance on protecting sensitive government information. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02108", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Non-Fungible Token Security say about Transferable (Section 3.3.1.2)? According to Non-Fungible Token Security, Transferable (Section 3.3.1.2): 5. There is likely no smart contract mechanism to restore stolen tokens to their rightful owner. 6. If a smart contract enables the contract manager to restore stolen tokens, this feature could be used by the manager to confiscate, freeze, or unilaterally transfer tokens. 7. A smart contract may not allow a manager to restore stolen tokens, but the smart contract may have a manager-controlled update mechanism whereby this feature could be added in the future (enabling the previously mentioned security concern). 8. Coding errors in the smart contract could enable attackers to steal tokens and transfer them to their accounts.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Non-Fungible Token Security."}]}
{"id": "nist_02109", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet say about 5.5 Claim of Supported Test Assertions? (Part 2) According to Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet, 5.5 Claim of Supported Test Assertions: No) there are any known deviations from (or exceptions to) the requirements found in the base standard and identified in the Conformance Testing Methodology for the associated Record Types in the IUT. For specific exceptions, the Implementation Support column of the tables of requirements and assertions can be used to indicate the difference on a per-assertion basis. In addition, if the deviation is general and applies to the entire Record Type, a description should be provided. This option is useful for cases where there have been modifications to the base standard that are not reflected in the conformance testing methodology, where the IUT provider believes there is a defect in the base standard or conformance testing methodology, and other instances where the implementation does not fully conform to the AN-2013 standard requirements. The testing laboratory may use testing tools that implement this CTMF and any the test assertions included in any derivative conformant publications (such as those which document additional requirements) to provide a determination of the level of conformance of the IUT to the AN-2013 standard.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet."}]}
{"id": "nist_02110", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PA-220 in Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)? (Part 177) Control PA-220: Administrator OM-NET-001 Network Operations Specialist | | Specific product used | How the component functions in the build | Applicable Cybersecurity Framework Version 1.1 Subcategories | Applicable NIST SP 800-53 Revision 4 Controls | ISO/IEC 27001:2013 | CIS 6 | NIST SP 800-181 NICE Framework Work Roles | |-------------------------|--------------------------------------------|---------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| | | | | | Transfer Policies and Procedures A.14.1.2 Securing Application Services on Public Networks A.14.1.3 Protecting Application Services Transactions | CSC 15 Wireless Access Control CSC 18 Application Software Security | | | | | PR.AC-6- Identities are proofed and bound to credentials and asserted in interactions | Access Control AC- 1, AC-2, AC-3, AC- 16, AC-19, AC-24 Identification and Authentication IA- 1, IA-2, IA-4, IA-5, IA-8 Physical and Environmental Protection PE-2, PS-3 | A.7.1.1 Screening A.9.2.1 User Registration and De-Registration | CSC 16 Account Monitoring and Control | OV-SPP-002 Cyber Policy and Strategy Planner OV-MGT-002 Communications Security (COMSEC) Manager OM-ADM-001 System Administrator | | Specific product used | How the component functions in the build | Applicable Cybersecurity Framework Version 1.1 Subcategories | Applicable NIST SP 800-53 Revision 4 Controls | ISO/IEC 27001:2013 | CIS 6 | NIST SP 800-181 NICE Framework Work Roles | |-------------------------|--------------------------------------------|----------------------------------------------------------------|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_02111", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Developing Trust Frameworks to Support Identity Federations say about Identity Management Programs and Other Resources? According to Developing Trust Frameworks to Support Identity Federations, Identity Management Programs and Other Resources: - The Vocabulary of Identity System Liability , The Open Identity Exchange/Edwards Wildman Palmer LLP, by Thomas J. Smedinghoff, Mark Deem, and Sam Eckland. - TeleSign Consumer Account Security Report, An International Study of Digital Security Concerns and Practices. ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Trust Frameworks to Support Identity Federations."}]}
{"id": "nist_02112", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identity and Access Management for Electric Utilities provide? (Section 105) \u2022 directory service and console access manager components on the OT network (i.e., ensuring that only authorized users can access and add, modify, or delete information on these components) \u2022 IT network access-control switch that serves as a gateway to the OT network from the IT network \u25aa protecting the integrity of the information exchanges between the following components: \u2022 \u2022 identity manager and the identity stores identity store and the directory service on the OT network \u2022 directory service and the console access manager components on the OT network, as well as the network access-control and policy-enforcement system within the IT network \u2022 network access-control and component identity stores \u2022 network access-control component on the IT network and the IT network access-control switch that serves as a gateway to the OT network Based on the information flows for supporting PACS authentication, PACS access control, and PACS authorization described in Section 5.6.7, securing the part of the IdAM example solution that supports PACS access control requires the following actions: \u25aa securing access to the following components: \u2022 \u2022 identity, authorization, and workflow manager; identity store; and IdAM translator components on the IdAM network (i.e., ensuring that only authorized users can", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_02113", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile say about 7. Manufacturing Profile Subcategory Guidance? (Part 110) According to Cybersecurity Framework Manufacturing Profile, 7. Manufacturing Profile Subcategory Guidance: Low, Moderate and High Incorporate lessons learned from ongoing incident handling activities into incident response procedures, training, and testing, and implement the resulting changes accordingly. | 62443-2-1:2009 4.3.4.5.10 IR-4 | | | Improvements (RS.IM) | | Low, Moderate and High Update the response plans to address changes to the organization, manufacturing system, attack vectors, or environment of operation and problems encountered during plan implementation, execution, or testing. Updates may include, for example, responses to disruptions or failures, and predetermined procedures. Enable a process for the response plan to evolve to reflect new threats, improved technology, and lessons learned.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: attack vector, incident response. Contains technical security guidance that could inform defensive posture. Source: Cybersecurity Framework Manufacturing Profile."}]}
{"id": "nist_02114", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IA-5 in A Threat Analysis on UOCAVA Voting Systems? (Part 45) Control IA-5: tered voter (e.g, forged signature). | Hostile Individuals Hostile Individuals | Mod. Mod. | Mod. Mod. | Integrity-Mod. Integrity-Mod. | IA-1, IA-2, IA-4, IA-5, IA-7 IA-1, IA-2, IA-4, IA-5, IA-7 | | Voter coerced into voting a particular way. Voter coerced into voting a particular way. | Hostile Individuals Hostile Organizations Hostile Individuals Hostile Organizations | Low Low | Mod Mod | Confid.-Mod Confid.-Mod | Outside control of officials. Outside control of officials. | | Election official offices have too few fax machines and/or telephone lines to handle demand. Election official offices have too few fax machines and/or telephone lines to handle demand. | Telephone Operators System Operators Telephone Operators System Operators | Low Low | High High | Avail.-High Avail.-High | IR-4, IR-5 IR-4, IR-5 | | A denial of service attack against the election official office jams fax machines and/or telephone lines. A denial of service attack against the election official office jams fax machines and/or telephone lines. | Telephone Operators Hostile Organizations Telephone Operators Hostile Organizations | Mod. Mod. | High High | Avail.-High Avail.-High | IR-4, IR-5, CP-7, CP-8, SC-5 IR-4, IR-5, CP-7, CP-8, SC-5 | | Personally identifiable material is intercepted en route. Personally identifiable material is intercepted en route. | Telephone Operators Hostile Organizations Telephone Operators Hostile Organizations | High High | Low Low | Confid.-Mod. Confid.-Mod.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Threat Analysis on UOCAVA Voting Systems."}]}
{"id": "nist_02115", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IA-5 in A Threat Analysis on UOCAVA Voting Systems? (Part 79) Control IA-5: | X | INCIDENT HANDLING | Officials should monitor their IT systems and communications services for disruptions and possible attacks. | | IR-5 | X | X | INCIDENT MONITORING | Officials should monitor their IT systems and communications services for disruptions and possible attacks. | | MA-2 | | X | CONTROLLED MAINTENANCE | System administrators should closely monitor the maintenance of vital IT systems to ensure the proper hardware and software updates are performed on such systems. | | MA-3 | | X | MAINTENANCE TOOLS | System administrators should closely monitor the maintenance of vital IT systems to ensure the proper hardware and software updates are performed on such systems. | | MA-5 | | X | MAINTENANCE PERSONNEL | System administrators should closely monitor the maintenance of vital IT systems to ensure the proper hardware and software updates are performed on such systems. | | PE-2 | X | X | PHYSICAL ACCESS AUTHORIZATIONS | Officials should control physical access to vital systems and sensitive information. This includes physical access to IT systems and communications equipment. | | PE-3 | X | X | PHYSICAL ACCESS CONTROL | Officials should control physical access to vital systems and sensitive information. This includes physical access to IT systems and communications equipment.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: A Threat Analysis on UOCAVA Voting Systems."}]}
{"id": "nist_02116", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 2019 NIST_ITL Cybersecurity Program Annual Report provide? (Section 22) Framework. Since NIST has researched industry practices in cyber supply chain risk management (C-SCRM) through engagement with industry leaders, the group was able to identify some helpful practices. 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. CREDIT: Shutterstock / faithie <!-- image --> Network and data security are essential in today's environment of increasingly open and interconnected systems, networks, and mobile devices. Cryptographic standards, algorithms, and methods for encryption, key establishment, and digital signatures provide a critical foundation for mobile device conversations, secure e-Commerce transactions, electronic lock access, and much more. Cryptography is a continually evolving field that drives research and innovation. The Data Encryption Standard (DES) was groundbreaking but today would fall far short of the necessary levels of protection. The accomplishments below demonstrate NIST's continued dedication to the role it has fulfilled for nearly 50 years-leading public and private collaborations to foster continued improvement and reliability in cryptographic techniques and technology. In recent years, there has been a substantial amount of research on quantum computers-machines that exploit quantum mechanical phenomena to solve mathematical problems that are difficult or intractable for conventional computers. When the capacity to build large-scale quantum computers exists, they will be able to break many of the public-key cryptosystems currently in use. This would seriously compromise the confidentiality and integrity of digital communications on the internet and elsewhere.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2019 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02117", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Section 14) istry [4]. The requirements do not apply to nonfederal organizations that are collecting or maintaining information on behalf of a federal agency or using or operating a system on behalf of an agency. 8 The security requirements in this publication are only applicable to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. 9 The requirements are intended for use by federal agencies in contractual vehicles or other agreements that are established between those agencies and nonfederal organizations. Appropriately scoping requirements is an important factor in determining protection-related investment decisions and managing security risks for nonfederal organizations. If nonfederal organizations designate system components for the processing, storage, or transmission of CUI, those organizations may limit the scope of the security requirements by isolating the system components in a separate security domain. Isolation can be achieved by applying architectural and design concepts (e.g., implementing subnetworks with firewalls or other boundary protection devices and using information flow control mechanisms). Security domains may employ physical separation, logical separation, or a combination of both. This approach can provide adequate security for CUI and avoid increasing the organization's security posture beyond what it requires for protecting its missions, operations, and assets. The remainder of this special publication is organized as follows: - Section 2 describes the assumptions and methodology used to develop the security requirements for protecting the confidentiality of CUI, the format of the requirements, and the tailoring criteria applied to the NIST guidelines to obtain the requirements. - Section 3 lists the security requirements for protecting the confidentiality of CUI in nonfederal systems and organizations.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_02118", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-1 in Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity? (Part 111) Control AC-1: admin user. 4. Setup and configure network settings for FTD. Ensure that the device will not be managed locally and that the FTD system will run in transparent mode. <!-- image --> <!-- image --> 5. Configure the manager settings with the IP address of ISE and a registration key. The key opted to use in this build is cisco123 . This key is required for integration into FMC. ## 2.3.3.2 Cisco Firepower Management Center Installation and Configuration 1. Obtain OVF and VMDK file from Cisco representative and deploy to virtual environment. Power on VM after deployment is completed. 2. Open VM Console and log in with username admin and password Admin123 . Once logged in, view and accept the EULA. 3. Configure network for FMC system. DHCP was utilized in this setup. Type y to verify configuration. 4. Once logging in to the web interface for FMC, click the gear icon in the top left, then select Integration. Select the tab at the top entitled Identity Sources . 5. Fill out each line for the ISE instance. IP address or Fully Qualified Domain Name (FQDN), the pxGrid Server certificate authority is the self-signed certificate in ISE, the same certificate is used for the MNT certificate, and the FMC Server Certificate is the certificate generated in ISE for the pxGrid. Ensure that the checkboxes for Session Directory Topic and SXP Topic are selected. Click Test to verify successful connection, then click Save . <!-- image --> <!-- image --> <!-- image --> 6. To add the FTD, select Device &gt; Device Management , then click Add. 7. On the pop-up window, fill in all blanks, with the Host as the IP address of the FTD, a Display Name , and place copy the registration key created earlier to Registration Key . The lab used cisco123 as the registration key. For Access Control Policy , click the drop-down box, then select Create New Policy . Give it a name, description, and ensure Block all traffic is selected as the default action. Click Save . <!-- image --> <!-- image --> 8.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, certificate authority. Contains security framework guidance for authentication systems. Source: Securing Distributed Energy Resources_ An Example of Industrial Internet of Things Cybersecurity."}]}
{"id": "nist_02119", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Attribute Considerations for Access Control Systems say about Executive Summary? (Part 3) According to Attribute Considerations for Access Control Systems, Executive Summary: annot be accessed during an information system emergency (e.g., low bandwidth, loss of service). In addition, the fail over and backup capability of attribute repositories need to be considered. Management provides mechanisms for maintaining attributes to ensure the efficiency and consistent use of attributes, including metadata, hierarchical structures for attribute grouping, minimization and transformation methods for attribute performance, and additional support capabilities (e.g., attribute integration with authentication, logs for recording attribute access and updates). NIST 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. 6", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Attribute Considerations for Access Control Systems."}]}
{"id": "nist_02120", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 03.01.05 Least Privilege according to NIST Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, 03.01.05 Least Privilege: - a. Allow only authorized system access for users (or processes acting on behalf of users) that is necessary to accomplish assigned organizational tasks. - b. Authorize access to [ Assignment: organization-defined security functions ] and [ Assignment: organization-defined security-relevant information ]. - c. Review the privileges assigned to roles or classes of users [ Assignment: organization-defined frequency ] to validate the need for such privileges. - d. Reassign or remove privileges, as necessary.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_02121", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Training & Awareness Course Compendium provide? (Section 93) such that as problems arise, the student will be able to recognize, in a working environment, that legal issues must be addressed. COURSE TITLE: GBA 577: Advanced EDP Auditing COURSE LENGTH: 3.5 HRS. California State Polytechnic Univ, Pomona College of Business Administration Computer Information Systems Department 3801 West Temple Avenue Pomona, CA 91768-4083 Dan Manson: (714) 869-3244 Auditing in a computer information systems environment involves evidence that originates or is maintained in a computer system. The course provides students with an understanding of the role of the EDP Audit function, the purpose of controls in a computer environment, and skills required to perform EDP Audits. Advanced concepts in EDP Auditing. Understanding EDP controls, types of EDP audits, risk assessment and concepts, and techniques used in EDP audits. Prerequisite: CIS 433 or permission of instructor. COURSE TITLE: Computer Security for the End-User COURSE LENGTH: 1 DAY VENDOR: COMSIS 8737 Colesville Road, Suite 1100 Silver Spring, MD 20910 Ronald E. Freedman: (301) 588-0800 This course provides training to end-users who operate sensitive and mission-critical systems and/or rely upon automated information systems to perform their work. COURSE TITLE: Information Systems Security (CSI 214) COURSE LENGTH: 1 SEMESTER Anne Arundel Community College Engineering and Computer Technology Careers 219 101 College Parkway Arnold, MD 21012-1895 Gail Reese: (410) 541-2758 A survey of topics in data retention and control and techniques associated with data, computer systems, network and installation security. The student will obtain skills related to occupations in data libraries and data security at computer installations. NOTE: Three semester hours; prerequisite: CSI 113 or permission of department head. COURSE TITLE: COURSE LENGTH: 2 DAYS TEMPEST Program Management and Systems Engineering Security Engineering Services, Inc.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Computer Security Training & Awareness Course Compendium."}]}
{"id": "nist_02122", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does CVSS Implementation Guidance provide? (Section 32) 4 Affecting the application. This section showcases a list of example vulnerabilities scored via the CVSS to assist vulnerability analysts in scoring vulnerabilities via the CVSS. The scores are based on information provided by the NVD and includes the CVE ID, CWE ID, CVSS base score, CVSS vector, a description of the vulnerability, and a justification for each CVSS base score. Mozilla Firefox before 17.0, Firefox ESR 10.x before 10.0.11, Thunderbird before 17.0, Thunderbird ESR 10.x before 10.0.11, and SeaMonkey before 2.14 implement cross-origin wrappers with a filtering behavior that does not properly restrict write actions, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted web site. The scoring template for Cross-site Scripting takes into consideration SCORING TIP #2 which states: 'When scoring a vulnerability, consider the direct impact to the target host only. For example, consider a cross-site scripting vulnerability: the impact to a user's system could be much greater than the impact to the target host. However, this is an indirect impact.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: CVSS Implementation Guidance."}]}
{"id": "nist_02123", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN) say about threat? According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN), threat: 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, or denial of service. [NIST-SP-800-53]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)."}]}
{"id": "nist_02124", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Random Number Generation Using Deterministic Random Bit Generators say about 11.4.1 Errors Encountered During Normal Operation? According to Recommendation for Random Number Generation Using Deterministic Random Bit Generators, 11.4.1 Errors Encountered During Normal Operation: Many errors that occur during normal operation may be caused by a consuming application's improper DRBG request or possibly the current unavailability of entropy; these errors are indicated by 'ERROR\\_FLAG ' in the pseudocode. In these cases, the consuming application user is responsible for correcting the request within the limits of the user's organizational security policy. For example, if a failure indicating an invalid requested security strength is returned, a security strength higher than the DRBG or the DRBG instantiation can support has been requested. The user may reduce the requested security strength if the organization's security policy allows the information to be protected using a lower security strength, or the user shall use an appropriately instantiated DRBG. Catastrophic errors (i.e., errors indicated by the CATASTROPHIC\\_ERROR\\_FLAG in the pseudocode) detected during normal operation shall be treated in the same manner as an error detected during health testing (see Section 11.4.2).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Number Generation Using Deterministic Random Bit Generators."}]}
{"id": "nist_02125", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-002 in Guidelines for Smart Grid Cybersecurity? (Part 206) Control IP-002: art grid marketplace. Implementation of the IPRM will lead to reduced deployment costs of smart grid systems and devices, and enhanced product quality with respect to interoperability and conformance. This will ultimately provide increased end-user customer satisfaction and confidence to the buyer through meaningful certification programs. For instance, as electric utilities turn to Advanced Metering Infrastructures (AMIs) to promote the development and deployment of the smart grid, one aspect that can benefit from 34 The Companion Spreadsheet to the Guide for Assessing the High-Level Security Requirements in NISTIR 7628 is available at: 35 IPRM Version 2.0, January 2012. sggrid/pub/SmartGrid/SmartGridTestingAndCertificationCommittee/IPRM_final_-_011612.pdf 215 standardization is the upgradeability of Smart Meters. The National Electrical Manufacturers Association (NEMA) standard SG-AMI 1-2009, Requirements for Smart Meter Upgradeability, describes functional and security requirements for the secure upgrade\u2014both local and remote\u2014 of smart meters. Draft NISTIR 7823, Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework, describes conformance test requirements that may be used voluntarily by testers and/or test laboratories to determine whether smart meters and upgrade management systems conform to the requirements of NEMA SG-AMI 1-2009. 216 CHAPTER 4 CRYPTOGRAPHY AND KEY MANAGEMENT This chapter identifies technical cryptographic and key management issues across the scope of systems and devices found in the smart grid along with potential alternatives. The identified alternatives may be existing standards, methods, or technologies, and their optimal adaptations for the smart grid.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02126", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation say about Procedure Examine the VC attached to the RUT to verify that it is not storing any ROAs that cover the following three addresses:? (Part 3) According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, Procedure Examine the VC attached to the RUT to verify that it is not storing any ROAs that cover the following three addresses:: t the second and third ROAs are no longer in the repository): - (10.10.128.128/19, 19, AS 65501) is present. - (10.10.128.192/19, 19, AS 65501) is absent. - (10.10.128.224/19, 19, AS 65501) is absent. - Wait for an amount of time to elapse that is greater than the RPKI -to-VC content update interval, or, alternatively, force the validator/VC to be updated with the latest RPKI repository information. - Verify that a VRP for only the first ROA created in Step 4 above has been received by the VC that is attached to the RUT. - Wait for an amount of time to elapse that is greater than the VC-to-router refresh interval. - Verify that a VRP for only the first ROA created in Step 4 is received by the RUT (i.e., no VRP for the second or third ROA is received by the router). (Use the show ip bgp rpki table command at the RUT to list the VRP information that it has received from its VC.)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_02127", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Testing of Equipment according to Accuracy, Integrity, and Security in Computerized Vote-Tallying? Testing of Equipment: Each unit of tabulating equipment shall be tested \"using all applicable ballot formats.\"", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Accuracy, Integrity, and Security in Computerized Vote-Tallying."}]}
{"id": "nist_02128", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Managing Information Security Risk_ Organization, Mission, and Information System View provide? (Section 171) | A major subdivision or component of an information system consisting of information, information technology, and personnel that performs one or more specific functions. | | Supplementation (Security Controls) | The process of adding security controls or control enhancements to a security control baseline from NIST Special Publication 800-53 or CNSS Instruction 1253 in order to adequately meet the organization's risk management needs. | | System | See Information System . | | System Security Plan [NIST SP 800-18] | Formal document that provides an overview of the security requirements for an information system and describes the security controls in place or planned for meeting those requirements. | | System-Specific Security Control [NIST SP 800-37] | A security control for an information system that has not been designated as a common control or the portion of a hybrid control that is to be implemented within an information system. | | Tailoring [NIST SP 800-53, CNSSI 4009] | The process by which a security control baseline is modified based on: (i) the application of scoping guidance; (ii) the specification of compensating security controls, if needed; and (iii) the specification of organization-defined parameters in the security controls via explicit assignment and selection statements. | | Tailored Security Control Baseline | A set of security controls resulting from the application of tailoring guidance to the security control baseline. See Tailoring .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Managing Information Security Risk_ Organization, Mission, and Information System View."}]}
{"id": "nist_02129", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations provide? (Section 7) nd structured process that integrates information security and risk management activities into the system development life cycle. Ongoing monitoring is a critical part of that risk management process. In addition, an organization's overall security architecture and accompanying security program are monitored to ensure that organization- wide operations remain within an acceptable level of risk, despite any changes that occur. Timely, relevant, and accurate information is vital, particularly when resources are limited and agencies must prioritize their efforts. Information security continuous moni toring (ISCM) is defined as maintaining ongoing awareness of information security, vulnerabilities, and threats to support organizational risk management decisions. Any effort or process intended to support ongoing monitoring of information security across an organization begins with leadership defining a comprehensive ISCM strategy encompassing technology, processes, procedures, operating environments, and people. This strategy: - Is grounded in a clear understanding of organizational risk tolerance and helps officials set priorities and manage risk consistently throughout the organization; - Includes metrics that provide meaningful indications of security status at all organizational tiers; - Ensures continued effectiveness of all security controls; - Verifies compliance with information security requirements derived from organizational missions/business functions, federal legislation, directives, regulations, policies, and standards/guidelines; - Is informed by all organizational IT assets and helps to m aintain visibility into the security of the assets; - Ensures knowledge and control of changes to organizational systems and environments of operation; and - Maintains awareness of threats and vulnerabilities.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, continuous monitoring. General security reference material without sensitive content. Source: Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations."}]}
{"id": "nist_02130", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio say about Comparing ICTRM and ERM? (Part 2) According to Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio, Comparing ICTRM and ERM: zation. The enterprises discussed in this publication have more complex compositions [IR8170] . Most ICTRM responsibilities tend to be carried out by the individual organizations within an enterprise. In contrast, the ERM responsibility for tracking key enterprise risks and their impacts on objectives is at the highest-level enterprise, held by top-level corporate officers and board members who have fiduciary and reporting duties not performed elsewhere in the enterprise. ERM requires identifying and understanding the various types of risk, including ICT risks, that an enterprise faces; determining the probability that these risks will occur; and estimating their potential impact. ERM processes provide senior enterprise executives with a portfolio view of key risks across the enterprise, and this portfolio considers the outputs of all ICTRM disciplines. 6 Public and private enterprises have a common primary purpose for ERM: safeguard the enterprise's mission, finances (e.g., net revenue, capital, free cash flow), and reputation (e.g., stakeholder trust) in the face of natural, accidental, and adversarial threats.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio."}]}
{"id": "nist_02131", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results say about Other Security Concerns? According to Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results, Other Security Concerns: Non-repudiation ; The workshop was unable to reach agreement as to whether this concept should be additionally included as a separate security objective. Some participants in the workshop noted that the international standard on security architecture, ISO 7498-21988(E) , in its section 5.2, includes non-repudiation as a security service \"which can be provided optionally within the framework of the OSI Reference Model.\" In the ISO standard, non-repudiation is defined (section 5.2.5) as providing \"proof\" to one of the parties to the interchange against a false denial of involvement by the other party. The ISO standard, however, contemplates that only cryptographic techniques can provide non-repudiation. Other workshop participants asserted that it is the role of a third-party arbiter, such as a judge, arbitrator or jury, to consider the evidentiary weight of any denial of involvement. In such a situation, the demonstrated comparative trustworthiness of documented audit trails will likely determine which party will prevail. Proposition 14 (see below) reflects this view, and suggests that VANs, under certain circumstances, could provide the necessary evidence for non-repudiation System-wide Security : While the propositions presented below primarily concern security of the EDI link between interchange partners, users of EDI must be concerned also with the security of their own and their interchange partner's internal systems. It must be recognized that the EDI process encompasses three broad phases -origination, transmission, and reception. Proposition 6 sets forth a necessary relationship between link security and system-wide security.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results."}]}
{"id": "nist_02132", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST_SP_800-37r2_Risk_Management_Framework say about SECURITY AND PRIVACY IN THE RMF? According to NIST_SP_800-37r2_Risk_Management_Framework, SECURITY AND PRIVACY IN THE RMF: Organizations are encouraged to collaborate on the plans, assessments, and plans of action and milestones (POAM) for security and privacy issues to maximize efficiency and reduce duplication of effort. The objective is to ensure that security and privacy requirements derived from laws, executive orders, directives, regulations, policies, standards, or missions and business functions are adequately addressed, and the appropriate controls are selected, implemented, assessed, and monitored on an ongoing basis. The authorization decision, a key step in the RMF, depends on the development of credible and actionable security and privacy evidence generated for the authorization package. Creating such evidence in a cost-effective and efficient manner is important. The unified and collaborative approach to bring security and privacy evidence together in a single authorization package will support authorizing officials with critical information from security and privacy professionals to help inform the authorization decision. In the end, it is not about generating additional paperwork, artifacts, or documentation. Rather, it is about ensuring greater visibility into the implementation of security and privacy controls which will promote more informed, risk-based authorization decisions. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: rmf, fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_02133", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Secure Web Services provide? (Section 215) 140-2, Security Requirements for Cryptographic Modules | http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf | | FIPS 186-2, Digital Signature Standard | change1.pdf | | FIPS 196, Entity Authentication Using Public Key Cryptography | http://csrc.nist.gov/publications/fips/fips196/fips196.pdf | | FIPS 201-1, Personal Integrity Verification of Federal Employees and Contractors | chng1.pdf | | HSPD-12, Policy for a Common Identification Standard for Federal Employees and Contractors | 8.html | | IR 7298, Glossary of Key Information Security Terms | 7298_Glossary_Key_Infor_Security_Terms.pdf | | Standard | URL | |--------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------| | SP 800-21-1, Guideline for Implementing Cryptography in the Federal Government | 1_Dec2005.pdf | | SP 800-25, Federal Agency Use of Public Key Technology for Digital Signatures and Authentication | | | SP 800-32, Introduction to Public Key Technology and the Federal PKI Infrastructure | http://csrc.nist.gov/publications/nistpubs/800-32/sp800-32.pdf | | SP 800-44, Guidelines on Securing Public Web Servers | | | SP 800-57, Special Publication on Key Management | Part1.pdf | | SP 800-92, Guide to Computer Security Log Management | http://csrc.nist.gov/publications/nistpubs/800-92/SP800-92.pdf | | SP 800-100, Information Security Handbook: A Guide for Managers | Mar07-2007.pdf | | Organization | URL | |------------------------------------------------------------------------------|--------------------------------| | Standards Bodies | | | IEEE Computer Society Technical Committee on Services", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, key management. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services."}]}
{"id": "nist_02134", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework say about Test Steps? According to Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework, Test Steps: 1. Tester shall install Image A on a Test Smart Meter. 2. Tester shall configure the Smart Meter as documented in the Vendor's response to RVI.NEMA-7.1. 3. Tester shall document the configuration. 4. Tester shall follow the methods in the Vendor's response to RVI.NEMA-3.1 to install Image B on the Test Smart Meter. 5. Based on the Vendor's response to RVI.NEMA-7.2, Tester shall verify that the Smart Meter's configuration persisted by comparing to the configuration documented in test step 3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework."}]}
{"id": "nist_02135", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet say about AN-2013 Annex G: Mapping to the NIEM IEPD? (Part 84) According to Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet, AN-2013 Annex G: Mapping to the NIEM IEPD: B | | RT1.29 - Fie ld: 1.004- TOT- CharCount | Table 22 | Table 22 specifies the character count for each field. | 1 | 1.004-TOT- CharCount | MO ( Count(Chars({Fld(1.004)}), Set-Int([1 to 16]) ) | | M-Fld(1.004) | | | | B | | RT1.30 - Fie ld: 1.005- DAT- FieldStructu | Table 22, Annex B, Annex G | Table 22 specifies which fields contain subfields and information items as well as the number of occurrences permitted. | 1 | 1.005-DAT- SubfieldCou nt | EQ ( Count(SubFldsIn(Fld(1.005))), Int(1) | | M-Fld(1.005) | | | | T | | re | | Afield contains a minimum of one subfield which contains a minimum of one information item.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet."}]}
{"id": "nist_02136", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Block Cipher Modes of Operation_ Methods and Techniques say about F.3.14 CFB128-AES128.Decrypt? According to Recommendation for Block Cipher Modes of Operation_ Methods and Techniques, F.3.14 CFB128-AES128.Decrypt: Key IV Segment #1 Input Block Output Block Ciphertext Plaintext Segment #2 Input Block Output Block Ciphertext Plaintext Segment #3 Input Block Output Block Ciphertext Plaintext Segment #4 Input Block Output Block Ciphertext Plaintext 2b7e151628aed2a6abf7158809cf4f3c 000102030405060708090a0b0c0d0e0f 000102030405060708090a0b0c0d0e0f 50fe67cc996d32b6da0937e99bafec60 3b3fd92eb72dad20333449f8e83cfb4a 6bc1bee22e409f96e93d7e117393172a 3b3fd92eb72dad20333449f8e83cfb4a 668bcf60beb005a35354a201dab36bda c8a64537a0b3a93fcde3cdad9f1ce58b ae2d8a571e03ac9c9eb76fac45af8e51 c8a64537a0b3a93fcde3cdad9f1ce58b 16bd032100975551547b4de89daea630 26751f67a3cbb140b1808cf187a4f4df 30c81c46a35ce411e5fbc1191a0a52ef 26751f67a3cbb140b1808cf187a4f4df 36d42170a312871947ef8714799bc5f6 c04b05357c5d1c0eeac4c66f9ff7f2e6 f69f2445df4f9b17ad2b417be66c3710", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Block Cipher Modes of Operation_ Methods and Techniques."}]}
{"id": "nist_02137", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Key Management Documents say about KMP KMS STATE TABLE (SLAVE)? (Part 2) According to Secure Data Network Systems (SDNS) Key Management Documents, KMP KMS STATE TABLE (SLAVE): | WFJREKEYrsp | | | | | | | | RKRS SLAVE KEYED | ESTAT SLAVE_KEYED | IDLE | |---------------|-------------|------------------|--------------|------------------|------------------|-------------------|------------------------|--------------------|---------------------|------------| | WF_CRLrsp | | | | | CRRS SLAVE KEYED | ESTAT SLAVE_KEYED | | | | IDLE | | SLAVE_KEYED | | | | CRLind WF_CRLrsp | | | IREKEYind WF_IREKEYrsp | | | IDLE | | WF_EXCrsp | | NKRS SLAVE_KEYED | A-ABORT IDLE | | | | | | | IDLE | | DOSSV 3AV1S | EXCind | WF_EXCrsp | | | | | | | | IDLE | | IDLE | SLAVE_ASSOC | | | | | | | | | IDLE | | | ASSOC_RESP | EXCrsp + | EXCrsp- | CRRQ | CRLrsp + | CRLrsp- | RKRQ | IREKEYrsp + | IREKEYrsp- | ASSOC_TERM | KMP STAGED REKEY STATE TABLE (USER) | WF_SRDRS | | | | | | | | SDLIVRcnf MSTR SRKEY | SDLIVRcnf- MSTR_SRKEY | IDLE | |--------------|------------|---------------------|-------------------------|----------------------|--------------|-------------------|-------------------------|------------------------|-------------------------|-----------| | WF_CRRS | | | | | | CRLcnf MSTR_SRKEY | | | CRLcnf- MSTR_SRKEY | IDLE | | WF_SRKRS | | | | SREKEYcnf MSTR_SRKEY | | | | | SREKEYcnf- MSTR_SRKEY | IDLE | | MSTR_SRKEY | | | SRKRQ", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_02138", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Effective Use of Computing Technology in Vote-Tallying say about 1. Ballot Reconciliation? (Part 1) According to Effective Use of Computing Technology in Vote-Tallying, 1. Ballot Reconciliation: 1. Ballot Reconciliation An important aspect of the supporting documentation is data demonstrating ballot reconciliation. This implies a numerical balance between the number of ballots printed and distributed to precincts and the sum of all uses to which they were pit. Figure 2 demonstrates the flow of ballots in a typical, but not necessarily universal type of election. The following is a description of this typical ballot flow. <!-- image --> actually printed must equal the number ordered. Control documentation is needed at this point. Of all those printed, most are distributed to precincts and absentees and the remainder are sent to central headquarters for possible later use. Control documentation is needed for each precinct's receipts At each precinct, the ballots are either voted unchallenged, voted challenged, spoiled, or unused. Ballots are returned to central headquarters where two reconciliations for each precinct can be made. First, the number of voted ballots (of each individual type, in case each voter is issued more than one type), challenged and unchallenged, must equal the number of voters recorded as having been issued ballots. Second, the number of ballots received at the precinct must equal the number returned from the precinct in all categories. The number of absentee ballots issued and the number returned must be noted for future reconciliations before the returned absentee ballots are dispersed into various counting categories. All unchallenged voted ballots are then inspected for machinereadability before being machine counted. Chad removal from punch-card ballots, according to pre-determined regulation, occurs at this point. Some ballots are approved for computer (or summ?rizer) input as is, and the remainder need to be duplicated. Disagreement at this point as to exactly how a ballot should be duplicated sends the ballot to the challenge process. In the duplication process, the originals are added to the \"spoiled\" total.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Effective Use of Computing Technology in Vote-Tallying."}]}
{"id": "nist_02139", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EC-62443 in Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective? (Part 19) Control EC-62443: egime, or closely regulated. Since the Internet was privatized in 1993, the USG has generally practiced a laissez faire approach to Internet standards development, allowing the private-sector to lead. Government experts participate in the IETF when they are working on a discrete need, but generally there has been little coordination of USG participants at IETF meetings to strategically track standards development that can impact national and economic security equities. In many cases, companies would be inhibited from sharing certain information with one another due to protection of proprietary information and antitrust and other rules within the United States. However, there has also been limited outreach on the side of the government to industry partners to discuss ways of coordinating before meetings on areas that have the potential to impact national security equities. Participants, whether corporate or government, produce their own trip reports, but, these reports are not shared within USG or synthesized to create a holistic picture of all relevant activities and working groups at the IETF, which number in the hundreds. This lack of coordination, which can be inherent for other individual member-based SDOs, means that participants act in isolation, and potentially against each other. Although this is appropriate in many commercial circumstances, there may be times when the USG may feel the need to leverage its U.S. industry counterparts within the IETF context to promote, shift, or eliminate a development that could have the potential to impact issues of national significance. ## Case Study - ISO An ISO standard is expected to take two to four years from inception to publication primarily due to the time required to develop international consensus on positions. The national body process treats larger and smaller countries equally.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective."}]}
{"id": "nist_02140", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain D.1.5 ECC P-256 Issuing CA Certificate according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, D.1.5 ECC P-256 Issuing CA Certificate: Serial Number : 4 Signature Algorithm : sha384WithRSAEncryption Issuer : CN=Test Trust Anchor for Test PIV Cards v2, ou=Test CA, o=Test Certificates 2020, c=US Validity : Not Before: Aug 5 08:30:00 2010 GMT, Not After: Dec 31 08:30:00 2040 GMT Subject : CN=Test ECC P-256 CA for Test PIV Cards v2, ou=Test CA, o=Test Certificates 2020, c=US Subject Public Key Info : id-ecPublicKey, P-256", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_02141", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security in ISDN say about 5.1.1 Security Protocols above ISDN? (Part 1) According to Security in ISDN, 5.1.1 Security Protocols above ISDN: 5.1.1 Security Protocols above ISDN As described in section 5.1.2 above, SDNS defines several security protocols which are suitable for use with the OSI and DoD protocol stacks above ISDN at layers 3 and 4. These protocols are above ISDN proper, but are associated with ISDN, when ISDN is used as a part of the OSI (or DoD) protocol stacks. They are expected to provide a starting point for the development of OSI standard security protocols, or similar protocols will be developed for OSI security at layers 3 and 4. Figure 5, above, illustrates the locations of the specific SDNS protocols, which are located above ISDN at layers 3 and 4. The specific variants of the SDNS SP4 and SP3 protocols are discussed in table 1 above. In this section we will simply use \"SP3\" to mean an OSI network layer security protocol standard and \"SP4\" to mean an OSI Transport layer security protocol standard, without necessarily meaning a specific SDNS protocol as presently defined. Figure 15 - Transport Layer End-to-End Encryption. <!-- image --> Where an OSI packet data stack utilizes ISDN to provide at least some (but not necessarily all) of the network layer connections, a Transport layer security protocol, such as SP4, can provide a powerful end-to-end confidentiality solution. This solution is illustrated in figure 15 for a B channel connection to a packet network, however it is equally applicable to D channel packet user data services. In figure 15 the packet networic may be implemented by packet handlers in the local office switch, or it may be an independent network reached through the circuit switch. The packet network may in fact be a LAN, or some other network which is entirely independent of ISDN. An intruder monitoring the U interface point sees the Network layer headers as plaintext and the Transport PDU as ciphertext. Since the Network headers and addresses are plaintext, and the size and frequency of packets are apparent, traffic analysis may be fruitful.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security in ISDN."}]}
{"id": "nist_02142", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-1 in Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events? (Part 117) Control IP-1: ed to restart the computer, do so. <!-- image --> 3. Click I Agree. 4. Select Evaluation License. 5. Select Active Directory Forest Recovery. <!-- image --> 6. Click the &gt; button. 7. Click OK. 8. Wait for the installation to complete. <!-- image --> <!-- image --> 9. Click the &gt; button. <!-- image --> 10. Click Finish. 11. There should now be a shortcut on the desktop linking to the web console for Semperis ADFR. 12. On the login page, enter the full domain as well as the NetBIOS name. 13. Enter the username and password of an administrator on the domain. <!-- image --> 14. Click Login. 15. Check the box next to any domain controllers that should be backed up. 16. Click Run Action. <!-- image --> 17. Enter the password in the prompt. 18. Click OK. 19. Click Close. 20. After the installation finishes, click Login at the top of the page. <!-- image --> <!-- image --> 21. Enter the login credentials for the domain. 22. Click Login. 23. Create a recovery password . (Note: In the event of a restoration, Active Directory will potentially be unavailable, so a separate password that is not domain-associated is needed here for restorations.) <!-- image --> <!-- image --> 24. Set recovery questions for the password. 25. Click Set. ## 2.9.2 Create a Backup Schedule for the Domain Controller 1. Click the Backup Settings tab. 2. Enter a name for the rule. 3. Select the days and times that the domain controller should be backed up. 4. Enter the maximum number of backups that should be kept. (Note: The oldest backup will be deleted upon creation of a new backup, which would exceed this maximum.) 5. Ensure that Encrypt and Rule enabled are both turned on. <!-- image --> 6. Click Add Backup Group. 7. Click Create new Backup Group. 8. Enter a name for the backup group. 9. Select the domain controllers to be part of the backup group. <!-- image --> <!-- image --> ## 10. Click OK. 11. Select the newly created backup group. 12. Click OK.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_02143", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Property Management Systems say about Appendix F References? (Part 2) According to Securing Property Management Systems, Appendix F References: Standards and Technology (NIST). Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1. Apr. 16, 2018. Available at - [9] Joint Task Force Transformation Initiative, Security and Privacy Controls for Information Systems and Organizations, NIST Special Publication (SP) 800-53 Rev. 5, NIST, Gaithersburg, Md., Sept. 2020. Available at - [10] P. Grassi et al., Digital Identity Guidelines, NIST SP 800-63-3, NIST, Gaithersburg, Md., June 22, 2017. Available at - [11] R. Petersen et al., Workforce Framework for Cybersecurity (NICE Framework), NIST SP 800-181 Revision 1, NIST, Gaithersburg, Md., Nov. 2020. Available at - [12] National Institute of Standards and Technology. NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0. Available at .0.pdf. - [13] S. Rose et al., Zero Trust Architecture , NIST SP 800-207, NIST, Gaithersburg, Md., Aug. 2020, 59 pp. Available at - [14] Abbasi et al., 2019 Trustwave Global Security Report , 2019 Trustwave Holdings, Inc. Available at - [15] *NIST. Risk Management Framework: Quick Start Guides . Available at - [16] Joint Task Force, Risk Management Framework for Information Systems and Organizations , NIST SP 800-37 Revision 2, NIST, Gaithersburg, Md., Dec. 2018. Available at ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, risk management framework, fips. General security reference material without sensitive content. Source: Securing Property Management Systems."}]}
{"id": "nist_02144", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD) provide? (Section 915) vailable free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Test Case Field Description My-controller: sensor ] python udpping.py --client --npings 6 --host laptop2 --port 4000 start ... Namespace(bind=False, client=True, host='laptop2', npings=6, port=4000, quiet=False, server=False, timeout=False) PING 1 03:31:59 RTT = 1.24670505524 PING 2 03:32:00 RTT = 0.812637805939 PING 3 03:32:01 RTT = 0.652308940887 PING 4 03:32:02 RTT = 0.784868001938 PING 5 03:32:02 RTT = 0.573136806488 PING 6 03:32:03 RTT = 0.481912136078 [rc=6] Manufacturer: sensor ] wget anotherman:800 --2019-07-21 05:23:07-- Resolving anotherman (anotherman)... 10.0.41.245 Connecting to anotherman (another- man)|10.0.41.245|:800... connected. HTTP request sent, awaiting response... 200 OK Length: 116855 (114K) [text/html] Saving to: \u2018index.html.1\u2019 index.html.1 100%[================================================ =====================================>] 114.12K --.- KB/s in 0.1s 2019-07-21 05:23:08 (816 KB/s) - \u2018index.html.1\u2019 saved [116855/116855] 5. Local-network, controller, my-controller, manufacturer class (in- gress)\u2014blocked: Local-network: NIST SP 1800-15D: Securing Small-Business and Home Internet of Things Devices 425 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Test Case Field Description laptop ] wget sensor:888 --2019-05-10 07:47:18-- Resolving sensor (sensor)... 10.0.41.190 Connecting to sensor (sensor)|10.0.41.190|:888... ^C laptop ] wget sensor:888 --timeout 30 --tries 2 --2019-05-10 07:47:29-- Resolving sensor (sensor)... 10.0.41.190 Connecting to sensor (sensor)|10.0.41.190|:888... failed: Connection timed out. Retrying. --2019-05-10 07:48:00-- (try: 2) Connecting to sensor (sensor)|10.0.41.190|:888... failed: Connection timed out. Giving up.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_02145", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Doug Montgomery according to NIST Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, Doug Montgomery: Advanced Network Technologies Division Information Technology Laboratory", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_02146", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EP-67 in Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)? (Part 45) Control EP-67: Maturity Level) can be relatively easy or difficult to ascertain. The Maturity Levels are described in Table 6. The listing is sorted by Core Area of Cybersecurity, then by SDO, and last by Documents. Table 7 - Cryptographic Techniques Standards Cryptographic Techniques: Techniques and mechanisms and their associated standards are used to provide: confidentiality; entity authentication; non-repudiation; key management; data integrity; trust worthy data platforms; message authentication; and digital signatures. | Documents | SDO | Description | Maturity Level (Table 6) | |--------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------| | Bluetooth LE | Bluetooth SIG | Bluetooth Low Energy (BLE) A BLE beacon is a small device - usually powered by battery or USB - that emits a Bluetooth Low Energy signal.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_02147", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Examples of Controls Contained in Rules of Behavior according to NIST Guide for Developing Security Plans for Federal Information Systems According to Guide for Developing Security Plans for Federal Information Systems, Examples of Controls Contained in Rules of Behavior: - Delineate responsibilities, expected use of system, and behavior of all users. - Describe appropriate limits on interconnections. - Define service provisions and restoration priorities. - Describe consequences of behavior not consistent with rules. - Covers the following topics: - o Work at home - o Dial-in access - o Connection to the Internet - o Use of copyrighted work - o Unofficial use of government equipment - o Assignment and limitations of system privileges and individual accountability - o Password usage - o Searching databases and divulging information. Figure 2: Rules of Behavior Examples", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Developing Security Plans for Federal Information Systems."}]}
{"id": "nist_02148", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security Requirements for Controlled Unclassified Information provide? (Section 24) sers] Source Assessment Procedures: AC-06(09), AC-06(10) Determine if: A.03.01.08.ODP[01]: the number of consecutive invalid logon attempts by a user allowed during a time period is defined . A.03.01.08.ODP[02]: the time period to which the number of consecutive invalid logon attempts by a user is limited is defined . A.03.01.08.ODP[03]: one or more of the following PARAMETER VALUES are selected: {the account or node is locked automatically for &lt;A.03.01.08.ODP[04]: time period&gt;; the account or node is locked automatically until released by an administrator; the next logon prompt is delayed automatically; the system administrator is notified automatically; other action is taken automatically}. A.03.01.08.ODP[04]: the time period for an account or node to be locked is defined (if selected) . A.03.01.08.a: a limit of &lt;A.03.01.08.ODP[01]: number&gt; consecutive invalid logon attempts by a user during &lt;A.03.01.08.ODP[02]: time period&gt; is enforced. A.03.01.08.b: &lt;A.03.01.08.ODP[03]: SELECTED PARAMETER VALUES&gt; when the maximum number of unsuccessful attempts is exceeded. [SELECT FROM: access control policy and procedures; procedures for unsuccessful logon attempts; system design documentation; system audit records; system configuration settings; system security plan; other relevant documents or records] [SELECT FROM: personnel with information security responsibilities; system developers; system administrators] [SELECT FROM: mechanisms for implementing the access control policy for unsuccessful logon attempts] Source Assessment Procedure: AC-07 Determine if: A.03.01.09: a system use notification message with privacy and security notices consistent with applicable CUI rules is displayed before granting access to the system.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02149", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 743) operations. 8.6.3 Infrastructure Interdependency Issues Maintaining the resiliency and continuous availability of the power grid itself as a critical national infrastructure is an important mandate. There are also other such critical national infrastructure elements, such as telecommunications, oil and natural gas pipelines, water distribution systems, etc., with as strong a mandate for resiliency and continuous availability. However, the unique nature of the electrical grid is that it supplies key elements toward the operation of these other critical infrastructure elements. Additionally, there are reverse dependencies emerging on smart grid being dependent on the continuous well-being of the telecommunications and digital computing infrastructure, as well as on the continuing flow of the raw materials to generate the power. These interdependencies are sometimes highly visible and obvious, but many remain hidden below the surface of the detailed review for each. There is little current understanding of the cascading effect outages and service interruptions might have, especially those of a malicious and judiciously placed nature with intent to cause maximum disruption and mass chaos. Research into interdependency issues would investigate and identify these dependencies and work on key concepts and plans toward mitigating the associated risks from the perspective of the smart grid. Such research should lead to techniques that show not only how communication failures could impact grid efficiency and reliability, how power failures could affect digital communications, and how a simultaneous combination of failures in each of the systems might impact the system as a whole, but should also apply a rigorous approach to identifying and highlighting these key interdependencies across all of these critical common infrastructure elements.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02150", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Study of Federal Agency Needs for Information Technology Security provide? (Section 79) ' 'sensitive application/ and 'sensitive system.\" These laws and directives offer latitude to the agency in applying the definitions. As in other areas, the principles are understood at a high level. However, there is much confusion, uncertainty, and frustration as to how they should be applied in specific situations, or when they should be applied, how one knows if it has been done correctly, and who certifies as to the correctness. Many of the interviewees expressed a need for clearer definitions that are easier to apply In their environments. Some felt examples of how these terms are to be applied In real-world situations would be helpful. Some of those interviewed felt they were constantly in the position of being second-guessed. They were uncertain about how much security was needed and how to justify what they implemented. This is also related to some other notions and definitions of 'system\" and 'ownership\" and 'responsibility\" and \"due care.\" Questions included: What is a system?; Is it the hardware or the software or the data or the communications?; What is ownership?; What does ownership imply or entail?; and What are the limits of responsibility? Although the message about the need for standard definitions relating to \"sensitive\" was clear, interviewees differed with respect to the organizational level (i.e., federal, agency, organization unit) at which this should be done. Many felt levels of sensitivity (and corresponding protections) are a function of the specific agency mission and environment. Some issues identified in the Interviews as directly related to the definitions of 'system\" and \"sensitive\" are: 1) determining appropriate controls for each defined system, and 2) certifying a system is adequately protected (including selecting a basis for certification).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of Federal Agency Needs for Information Technology Security."}]}
{"id": "nist_02151", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)? (Part 49) Control PD-12: | IAT = Organizational Preparedness | IAT = Organizational Preparedness | IAT = Organizational Preparedness | IAT = Organizational Preparedness | IAT = Organizational Preparedness | |----------------------------------------------|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-------------------------------------------------------------------------------| | Authorization Focus Area | Identifier | Issuer Control | Applicability | Source | | Preparation and Maintenance of Documentation | DO(DC):1 | The organization develops and implements an issuer operations plan according to the template in Appendix D.2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_02152", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007 say about Record-Level Requirements and Assertions? (Part 82) According to Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007, Record-Level Requirements and Assertions: | 3 | | Table_18 | 15.1.13 | The field value shall be selected from Table 18. | 1 | M | Table_18::10.013 | {10.013} MO[0, 1, 10, 11, 12, 13, 14, 15, 20, 30, 40, 50, 51] | 5 | | 10.003::IMT=FACE_ SAP_Mandatory | 15.1.13 | Field 10:013, the Subject Acquisition Profile (SAP), is mandatory when field 10.003 contains \"FACE'. | 2 | M | 10.003::IMT=FACE_ SAP_Mandatory | Field 10:013, the Subject Acquisition Profile (SAP), is mandatory when field 10.003 contains \"FACE'. | | | RESERVED_FIELDS | 15.1.14 | Fields 10.014 and 10.015 are reserved for definition and inclusion in future revisions of this standard.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2007."}]}
{"id": "nist_02153", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain ASSESSMENT OBJECTIVE according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, ASSESSMENT OBJECTIVE: Determine if: A.03.03.08.a[01]: audit information is protected from unauthorized access, modification, and deletion. A.03.03.08.a[02]: audit logging tools are protected from unauthorized access, modification, and deletion. A.03.03.08.b: access to management of audit logging functionality is authorized to only a subset of privileged users or roles.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02154", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DS-3 in Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches? (Part 111) Control DS-3: the Helix Comm Broker. (Note that putting a single '@' symbol here indicates UDP. Use two, such as '@@' for TCP.) 24. Create a file /etc/rsyslog.d/forcefield.conf and enter the following lines in it. ``` sftp administrator@forcefield.dc.ipdrr:/ForceField.log /tmp/ForceField.log ``` ``` Crontab -e ``` ``` 0 * * * * sftp administrator@forcefield.dc.ipdrr:/ForceField.log /tmp/ForceField.log ``` ``` *.* @192.168.1.206:514 ``` ``` sudo nano /etc/rsyslog.d/forcefield.conf $ModLoad imfile $InputFilePollInterval 10 ``` ``` $PrivDropToGroup adm $InputFileName /tmp/ForceField.log $InputFileTag FORCEFIELD $InputFileStateFile Stat-FORCEFIELD $InputFileFacility local8 $InputRunFileMonitor $InputFilePersistStateInterval 1000 ``` ## 25. Restart rsyslog. sudo service rsyslog restart ## 2.13 Integration: FireEye Helix and Dispel In this integration, we configure the collection of logs from Dispel, our network protection solution. Because Dispel controls access from users to enterprise systems, it is important to have an overview of its actions through log collection and reporting. Dispel personnel can perform this integration by simply providing them with the protocol, port, and IP address of the Helix Communications Broker and allowing them to configure it on the on-premise Dispel wicket. ## 2.14 Integration: Avrio SIFT and PKWARE PKProtect When used together, SIFT and PKProtect can protect sensitive data accidentally dropped into public shares on the enterprise. In Section 2.6, we detail how to configure SIFT to detect sensitive data in a Windows Share and move it to a location designated for sensitive information. Now, we will demonstrate how to ensure that location is protected by PKProtect, which will automatically encrypt the data. ## 2.14.1 Configuring PKWARE PKProtect 1. Navigate to the PKProtect dashboard and login. 2. Navigate to Archive &gt; Discovery . <!-- image --> 3. Click Pattern - Dictionary . 4. Enter a name for these patterns in the Name field. 5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Confidentiality_ Identifying and Protecting Assets Against Data Breaches."}]}
{"id": "nist_02155", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2011 Annual Report say about Policy Machine? (Part 3) According to Computer Security Division 2011 Annual Report, Policy Machine: ternational Committee for Information Technology Standards (INCITS) working group continued development of a three-part PM standard under the title of 'Next Generation Access Control' (NGAC). This work was conducted under three sub-projects: - Project 2193-D: Next Generation Access Control Implementation Requirements, Protocols and API Definitions; - Project 2194-D: Next Generation Access Control Functional Architecture; and - Project 2195-D: Next Generation Access Control Generic Operations &amp; Abstract Data Structures. In the coming year, we anticipate conducting a demonstration of the Cloud PM implementation, and bringing parts of the NGAC proposed standard to ballot by INCITS. We expect that this project will: - Offer users capabilities of a variety of services achieved through configuration of PM data alone, such as file management, email, workflow, and forms and records management, rather than managing overlapping user accounts, and potentially different authentication schemes for each data service, through a single authenticated session; - Deliver to select users, through the policy machine, select capabilities (of different services) under combinations of arbitrary, but mission-tailored forms of discretionary, mandatory, and history-based access controls, rather than deploying and managing different access control schemes for different data services; - Provide an inherent property of the PM, the comprehensive nature in which data services interplay. For instance, a user can attach a record, created under a relational database management service, to an email message and send that record to any chosen individual.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Computer Security Division 2011 Annual Report."}]}
{"id": "nist_02156", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) say about Appendix B: Glossary? (Part 2) According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS), Appendix B: Glossary: nology changes. | | Archive facility | A facility used for long-term key and/or metadata storage. | | Audit log | A record providing documentary evidence of specific events. | | Audit administrator | An FCKMS role that is responsible for establishing and reviewing an audit log, assuring that the log is reviewed periodically and after any security-compromise-relevant event, and providing audit reports to FCKMS managers. | | Auditor | See Audit administrator . | | Authorization | The process of verifying that a requested action or service is approved for a specific entity. | | Availability | Timely, reliable access to information or a service. | | Backup facility | A redundant system or service that is kept available for use in case of a failure of a primary facility. | | Backup (key and/or metadata) | To copy a key and/or metadata to a medium that is separate from that used for operational storage and from which the key and/or metadata can be recovered if the original values in operational storage are lost or modified. | |--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Backup (system) | The process of copying information or processing status to a redundant system, service, device or medium that can provide the needed processing capability when needed. | | Certification path | A chain of trusted public-key certificates that begins with a certificate whose signature can be verified by a relying party using a trust anchor, and ends with the certificate of the entity whose trust needs to be established. | | Ciphertext | Data in its encrypted form.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, key management. Contains security framework guidance for authentication systems. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_02157", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain SP 500-304, Conformance Testing Methodology Framework for ANSI/NIST-ITL 1-2011 Update: 2013, Data Format for the Interchange of Fingerprint, Facial &amp; Other Biometric Information according to NIST Computer Security Division 2015 Annual Report According to Computer Security Division 2015 Annual Report, SP 500-304, Conformance Testing Methodology Framework for ANSI/NIST-ITL 1-2011 Update: 2013, Data Format for the Interchange of Fingerprint, Facial &amp; Other Biometric Information: Conformance testing measures whether an implementation faithfully implements the technical requirements defined in a standard. Conformance testing provides developers, users, and purchasers with increased levels of confidence in <!-- image --> product quality and increases the probability of successful interoperability. The CSD developed a conformance testing methodology framework for ANSI/NIST-ITL 1-2011 Update: 2013, Data Format for the Interchange of Fingerprint, Facial &amp; Other Biometric Information (AN-2013). This testing methodology framework defines the test assertions implemented within CSD's conformance test tool, which is designed to test implementations of AN-2013 transactions and promotes biometrics conformity assessment efforts. This initial document includes comprehensive tables of AN2013 requirements and test assertions for transaction-wide requirements and Record Type 1 (which is required for all transactions). The tables of requirements and assertions indicate which assertions apply to the traditional encoding format, the National Information Exchange Model (NIEM)compliant encoding format, or both encoding formats. The testing methodology framework defines and makes use of a specific test assertion syntax, which clearly defines the assertions associated with each requirement.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Computer Security Division 2015 Annual Report."}]}
{"id": "nist_02158", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings provide? (Section 172) ntaining a full set of privileges, and is configured with its own PERMIS PDP. The PDP is configured with an attribute (or role) assignment policy (RAP) [7], so that it can validate the AA requests. At initialization time the DIS will check that its AC has the indirectIssuer extension in it, otherwise it will fail to start. When an AA asks for an AC to be issued, the DIS will check that the AA is allowed to do this under the RAP policy, and also that the set of attributes requested are a subset of those held by the DIS. Validation against the RAP is done by the existing PERMIS PDP code. It is passed the (unsigned) AC requested by the AA, and it validates the credentials in the AC against the RAP. The only modification needed to PERMIS is to provide it with a null signature validation object that will return signature valid to every request to validate the unsigned ACs. If the AC passes the policy, the DIS will check that the requested attributes are a subset of those it holds in its own AC. The task of the RP is now made much simpler, since it only needs to validate 1 or 2 ACs, that of the user issued by the DIS, and optionally that of the DIS issued by the SOA. Finally we wanted to simplify the use of PMIs in organizations that do not have fully functional PKIs implemented. These organizations, which are in the majority, already have a fully functional user authentication mechanism, and only have a handful of PKCs, e.g. web server certificates. It is for this reason that we have chosen to implement communications between the user and DIS as a three tiered model via an Apache web server as in path f in Figure 2. This will allow organizations to use their existing authentication method.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02159", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control FT-128 in Status Report on the Second Round of the NIST Lightweight Cryptography Standardization Process? (Part 77) Control FT-128: the selection process. Security . The design rationale, security analysis, and proofs provided by the submission team, as well as the third-party analysis, played a significant role in the selection. Analysis that covered only small number of rounds, and required significant time and memory complexities increased confidence in the claimed security margins. In some cases, third-party results raised concerns about the validity of security claims; in particular distinguishers on the underlying permutations or weak key classes were of concern. There were also attack results that invalidated security claims, such as practical forgery attacks or key recovery attacks. Performance . Software and hardware performance comparisons of the candidates were conducted by multiple public initiatives (see Section 4). Candidates that did not demonstrate significant performance benefits over current NIST standards were not favored for advancement. NIST also considered the stated goals of the candidate, performance across a variety of input sizes, and how candidates with similar features compared. Designs that demonstrated ample flexibility in selecting implementation trade-offs and could be applied to a wide variety of use cases with acceptable performance were favored. Tweak Plans . NIST also considered the tweak plans of the candidates (in particular, their impact on the performance and the security of the candidate) as a part of the evaluation. In general, tweaks requiring significant structural changes were not looked upon favorably during the selection. Diversity of Candidates . During the selection, NIST also considered the diversity of the finalists. When there were multiple promising candidates based on the same underlying primitive (e.g., permutation, block cipher, or tweakable block cipher), they were also compared to each other, and a subset of the candidates was selected from these candidates. NIST Portfolio .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Second Round of the NIST Lightweight Cryptography Standardization Process."}]}
{"id": "nist_02160", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain VENDOR: according to NIST Computer Security Training & Awareness Course Compendium According to Computer Security Training & Awareness Course Compendium, VENDOR:: RSH Consulting, Inc. 29 Caroline Park Newton, MA 02168 Bob Hansel: (617) 969-9050 This workshop provides basic information about the security features and capabilities of a Banyan VINES 5.x local area network. We will begin with an introduction to the VINES Network Operating System and its component services, such as Server Service, File Services, and VINES Security Service. We will also discuss the directory service StreetTalk and its role in security. Thereafter, user identification and authentication controls including Group and User Login parameters. Next, we will address resource access control, focusing on Access Rights Lists and console security. We follow this with a discussion on controls over WAN network links. Finally, we will address security administration and monitoring, this workshop will conclude with a discussion of tools and techniques for reviewing security in a VINES network. VM COURSE TITLE: SEC02-V: VM Security for Project Managers COURSE LENGTH: 2 DAYS", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Computer Security Training & Awareness Course Compendium."}]}
{"id": "nist_02161", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.7.1. Awareness Activities according to NIST Building a Cybersecurity and Privacy Learning Program According to Building a Cybersecurity and Privacy Learning Program, 2.7.1. Awareness Activities: Cybersecurity and privacy awareness learning activities should be conducted on an ongoing basis throughout the year to ensure that employees are aware of their roles within the organization and the appropriate steps they must take to protect information, assets, and individuals' privacy. Activities can be campaign-oriented or ad hoc based on the subject matter, threats, or vulnerabilities or take place during seasonal events. Examples of awareness activities that are appropriate for all users include: - Messages on logon screens, organizational screen savers, and email signature blocks - Employee newsletters with cybersecurity and privacy articles - Posters (physical or digital) with cybersecurity and privacy tips - A Cybersecurity Awareness Month (October) or Data Privacy Awareness Week (January) activity fair - Cybersecurity and privacy reminders and tips on employee materials (e.g., pens, notepads, etc.) - Periodic or as-needed email messages that provide timely tips or are sent in response to a cybersecurity or privacy event or issue", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Building a Cybersecurity and Privacy Learning Program."}]}
{"id": "nist_02162", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Security for Full Virtualization Technologies provide? (Section 18) ty of a full virtualization solution is heavily dependent on the individual security of each of its components, from the hypervisor and host OS (if applicable) to guest OSs, applications, and storage. Organizations should secure all of these elements and maintain their security based on sound security practices, such as keeping software up-to-date with security patches, using secure configuration baselines, and using host-based firewalls, antivirus software, or other appropriate mechanisms to detect and stop attacks. In general, organizations should have the same security controls in place for virtualized operating systems as they have for the same operating systems running directly on hardware. The same is true for applications running on guest OSs: if the organization has a security policy for an application, it should apply the same regardless of whether the application is running on an OS within a hypervisor or on an OS running on hardware. The security of the entire virtual infrastructure relies on the security of the virtualization management system that controls the hypervisor and allows the operator to start guest OSs, create new guest OS images, and perform other administrative actions. Because of the security implications of these actions, access to the virtualization management system should be restricted to authorized administrators only. Some virtualization products offer multiple ways to manage hypervisors, so organizations should secure each management interface, whether locally or remotely accessible. For remote administration, the confidentiality of communications should be protected, such as through use of FIPS-approved cryptographic algorithms and modules. Securing a hypervisor involves actions that are standard for any type of software, such as installing updates as they become available.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Security for Full Virtualization Technologies."}]}
{"id": "nist_02163", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Wireless Infusion Pumps in Healthcare Delivery Organizations provide? (Section 370) eless Infusion Pumps 230 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P 1 8 0 0 - 8 . . 04:bd:88:b6:0e:f5 Friendly 0 0 Not Heard 04:bd:88:b6:10:00 Friendly 0 0 Not Heard 04:bd:88:b6:10:10 Friendly 0 0 Not Heard 04:bd:88:b6:10:15 Friendly 0 0 Not Heard 04:bd:88:b6:10:60 Friendly 2 0 Thu Aug 18 20:06:04 2016 04:bd:88:b6:10:65 Unclassified 2 0 Thu Aug 18 20:06:04 2016 04:bd:88:b6:10:70 Friendly 0 0 Not Heard 04:bd:88:b6:10:75 Friendly 0 0 Not Heard 04:bd:88:b6:10:b5 Friendly 0 0 Not Heard 62:6d:c7:27:a6:98 Unclassified 2 0 Thu Aug 18 20:06:04 2016 6c:72:20:3e:af:26 Friendly 0 0 Not Heard 6c:72:20:3e:af:28 Friendly 0 0 Not Heard 6c:72:20:3e:af:2a Friendly 0 0 Not Heard 88:dc:96:30:d9:1b Friendly 0 0 Not Heard 8a:dc:96:30:d9:1b Friendly 0 0 Not Heard 9a:dc:96:30:d9:1b Friendly 0 0 Not Heard e0:d1:73:02:b7:ab Friendly 0 0 Not Heard e0:d1:73:02:b7:af Friendly 0 0 Not Heard e0:d1:73:02:bc:2b Friendly 0 0 Not Heard e0:d1:73:02:bc:2f Friendly 0 0 Not Heard e0:d1:73:02:f6:6b Friendly 0 0 Not Heard e0:d1:73:02:f6:6f Friendly 0 0 Not Heard e0:d1:73:02:f9:4b Friendly 0 0 Not Heard e0:d1:73:02:f9:4f Friendly 0 0 Not Heard e0:d1:73:02:fa:4b Friendly 0 0 Not Heard e0:d1:73:02:fa:4f Friendly 0 0 Not Heard e0:d1:73:02:ff:1b Friendly 0 0 Not Heard e0:d1:73:02:ff:1f Friendly 0 0 Not Heard Rogue AP RLDP Configuration Rogue Location Discovery Protocol................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Wireless Infusion Pumps in Healthcare Delivery Organizations."}]}
{"id": "nist_02164", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 11. System Interconnections/Information Sharing according to NIST Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations According to Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations, 11. System Interconnections/Information Sharing: - A list of interconnected systems and system identifiers (if appropriate); provide the system, name, organization and system type (e.g., major application or general support system); indicate if there is an ISA/MOU/MOA on file, the date of any agreement to interconnect, the FIPS 199 category, the certification and accreditation status, and the name of the authorizing official.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations."}]}
{"id": "nist_02165", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Recommendation for Key Management_ Part 1 \u2013 General? (Part 32) Control HA-3: iterate the information. For example, erasing the information might require overwriting that information multiple times with other non-related information, such as random bits or all zero or one bits. Keys stored in memory for a long time can become 'burned in.' Splitting the key into shares that are frequently updated can mitigate this problem (see [DiCrescenzo]). beginning of the originator-usage period to the end of the recipient-usage period, although the originator-usage period has historically been used as the cryptoperiod for the key. Note that in some cases, predetermined cryptoperiods may not be adequate for the security life of the protected data. If the required security life exceeds the cryptoperiod, then the protection may need to be reapplied using a new key. Figure 1: Symmetric-key cryptoperiod <!-- image --> Examples of the usage periods for symmetric keys include the following: - a. When a symmetric key is only used for securing communications, the period of time from the originator's application of protection to the recipient's processing may be negligible. In this case, the key is authorized for either purpose during the entire cryptoperiod (i.e., the originator-usage period and the recipient-usage period are the same). - b. When a symmetric key is used to protect stored information, the originator-usage period (when the originator applies cryptographic protection to stored information) may end much earlier than the recipient-usage period (when the stored information is processed). In this case, the cryptoperiod begins at the initial time authorized for the application of protection with the key and ends with the latest time authorized for processing using that key. In general, the recipient-usage period for stored information will continue beyond the originator-usage period so that the stored information may be authenticated or decrypted at a later time. - c.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02166", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Fingerprint Identification and Mobile Handheld Devices_ An Overview and Implementation provide? (Section 12) communications interfaces. Extracted templates use 512 bytes per print, allowing up to 1000 fingerprint templates to be stored in on-board memory. Templates can also be exported and stored elsewhere. A temporary session key is used with a nonce to encrypt communications to/from the unit and protect against replay. Encryption uses the Data Encryption Standard (DES) 56-bit data Electronic Code Book (ECB) mode. Session keys are managed by the PDA, using a shared master key. The fingerprint handler for the lightweight solution, as all MAF handlers, runs in user space. The handler manages the mechanism by communicating with the kernel, the fingerprint reader, and the Opie plug-in containing its user interface components. It guides the placement and 1 More information about the FIU-300 can be found at removal of fingers during fingerprint scans and controls all the necessary steps regarding the authentication process and verdict determination. The handler is triggered by the MAF enabled kernel when the user tries to access a specific level that the handler protects, and after obtaining a live fingerprint scan of the user, replies to the kernel with the result of the authentication (success or failure). The fingerprint handler is a nonpolling one - once a user is authenticated, the mechanism does not need continual fingerprint authentication checks, as long as the policy level remains at that of the mechanism or higher. The handler uses the Opie plug-in to tell its UI to display informative messages to guide the user through the sign-on and enrollment steps. The type of interaction with the fingerprint reader depends on the device interface used (e.g., serial, USB, etc.) and the command set of the reader. In the case of the FIU-300, it uses the on-board capabilities of the device to acquire the fingerprint images and templates, control the matching process, and obtain the scores of matches.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Fingerprint Identification and Mobile Handheld Devices_ An Overview and Implementation."}]}
{"id": "nist_02167", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does System and Network Security Acronyms and Abbreviations provide? (Section 26) identifier IIF information in identifiable form IIHI individually identifiable health information IIS Internet Information Services IKE Internet Key Exchange IM instant messaging IMAP Internet Message Access Protocol IMEI International Mobile Equipment Identity IMSI International Mobile Subscriber Identity INCITS InterNational Committee for Information Technology Standards IP Internet Protocol IPA initial privacy assessment IPComp Internet Protocol Payload Compression Protocol IPng Internet Protocol Next Generation IPS intrusion prevention system IPsec Internet Protocol Security IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 IPX Internet Packet Exchange IR infrared IR interagency report IRC Internet Relay Chat IrDA\u00ae Infrared Data Association\u00ae IRQ interrupt request line IRS Internal Revenue Service IRTF Internet Research Task Force IS information system ISA interconnection security agreement ISA International Society of Automation ISAC information sharing and analysis center ISAKMP Internet Security Association and Key Management Protocol ISAP Information Security Automation Program ISAPI Internet Server Application Programming Interface ISATAP Intra-Site Automatic Tunnel Addressing Protocol ISF Information Security Forum ISID Industrial Security Incident Database IS-IS Intermediate System-to-Intermediate System ISM industrial, scientific, and medical ISM information security marking ISMS information security management system ISO International Organization for Standardization ISP Internet service provider ISSEA International Systems Security Engineering Association ISSO information systems security officer", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: System and Network Security Acronyms and Abbreviations."}]}
{"id": "nist_02168", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Guide to IPsec VPNs? (Part 125) Control HA-1: t such as the current sequence number - A link to the IPComp state, if present - Flags indicating various properties (TFC padding, etc.) The maximum counters and lifetimes have a soft and hard value. When the soft value is reached, the kernel will notify the IKE daemon so that it can take preventative action. When the hard value is reached, the IPsec SA is deleted by the kernel, and the IKE daemon is notified. Each time a packet is encrypted or decrypted, this state is updated appropriately. ## 5.1.2 The Security Policy Database (SPD) The kernel maintains a list of IPsec policies in the SPD. The policy describes the nature of the traffic that matches a policy rule and links it to the state used to encrypt or decrypt the packet. Policies without states are used for on-demand IPsec connections. Figure 14 shows examples of two policies corresponding to the SAs in Figure 12. ``` src 192.168.13.6/32 dst 0.0.0.0/0 dir out priority 1040383 ptype main tmpl src 198.51.100.1 dst 203.0.113.1 proto esp reqid 1 mode tunnel src 0.0.0.0/0 dst 192.168.13.6/32 dir in priority 1040383 ptype main tmpl src 203.0.113.1 dst 198.51.100.1 proto esp reqid 1 mode tunnel ``` Figure 14: Examples of Policies Corresponding to Figure 12 on Linux The IPsec security policy information consists of: - The IP addresses of the IPsec gateways - The source IP addresses allowed in the classless inter-domain routing (CIDR) format - The destination IP addresses in CIDR format - The transport protocol covered (0 for all) - The source and destination port ranges (0 for all) 41 - A link to the associated SA state - Direction (inbound, outbound, or forward 42 ) - The priority of the policy compared to other policy rules - IPsec protocol (ESP, AH, IPComp) - Mode (transport or tunnel) - IPComp information Using the SPD and SAD, packets are processed for encryption and decryption, and all of the security policies are applied.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to IPsec VPNs."}]}
{"id": "nist_02169", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices say about Implementation Tip? (Part 6) According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Implementation Tip: Historic Exhibition | Low | Low | Low | 25 High where safety of radioactive materials, highly flammable fuels, or transmission channels or control processes at risk.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_02170", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Threat Analysis on UOCAVA Voting Systems say about 6.3.5 Web-Based? (Part 1) According to A Threat Analysis on UOCAVA Voting Systems, 6.3.5 Web-Based: 6.3.5 Web-Based Web-based Internet voting is a form of electronic voting. The election web server would need to be trusted to accurately record voters' selections. Defects in the voting system software, or malicious code installed on the voting system by hostile individuals, could cause votes to be recorded improperly, or could modify votes at a later time. Skilled hackers may find vulnerability in the voting system software that would grant them access to voter and ballot information. This could also lead to a loss of voter secrecy, or a loss of election integrity. Sophisticated attacks would leave little or no evidence. Election officials, or other individuals with physical access to voting system equipment, may be able to gain access to election information, including cast ballots. Sophisticated attackers may also be able to delete any audit records that would leave evidence of their attack. Denial of service attacks are significant threats to Internet-based voting systems. A successful denial of service attack would overwhelm the election web server with traffic, preventing legitimate voters from casting a ballot. It is very difficult to protect against denial of service attacks from an attacker with a large amount of resources. A successful denial of service attack generally requires access to a large number of computers with high-speed Internet connections. While an attacking organization may purchase these systems, it typically would use a Botnet. A Botnet is a collection of personal computers that have been infected with a virus that gives an attacker control of the computer. Control of Botnet-infected computers is sold on the black market, given nearly anyone with financial resources the technical resources to perform a denial of service attack. Many of the potential threats to a web-based Internet voting system involve attacks on equipment that are not under election officials' control. Attacks on the DNS system could lead voters to fraudulent web sites.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Threat Analysis on UOCAVA Voting Systems."}]}
{"id": "nist_02171", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) say about Appendix B: Glossary? (Part 17) According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS), Appendix B: Glossary: tographic protection and removing or verifying the protection that has been applied. This includes parties relying on the public key in a public key certificate and parties that share a symmetric key. | |-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Role-based authentication | A process that provides assurance of an entity's role by means of an authentication mechanism that verifies the role of the entity. Contrast with identity-based authentication | | Scalability testing | Testing the ability of a system to handle an increasing amount of work correctly. | | Secret key | A cryptographic key used by a secret-key (symmetric) cryptographic algorithm and that is not made public. | | Security assessment | An evaluation of the security provided by a system, device or process. | | Security strength | A number associated with the expected amount of work (that is, the base 2 logarithm of the number of operations) to cryptanalyze a cryptographic algorithm or system. | | Security testing | Testing that attempts to verify that an implementation protects data and maintains functionality as intended. | | Self testing | Testing within a system, device or process during normal operation to detect misbehavior. | | Semantics | The intended meaning of acceptable sentences of a language.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_02172", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Design Alternatives for Computer Network Security say about 3.3 THE SECURITY CONTROLLER MECHANISMS FOR ESTABLISHING A CONNECTION? According to Design Alternatives for Computer Network Security, 3.3 THE SECURITY CONTROLLER MECHANISMS FOR ESTABLISHING A CONNECTION: If the requested access of a subject to an object is authorized, the SC must then create a working connection between these two parties . The notion of \"creating a connection\" involves several levels of protocol, and therefore is dependent upon the physical and logical organization of the network. However, we will assume that the following functions must be performed in any network, and will address the issues related to these aspects. - Control over the initial requestor-to-SC connection. - Determining the path for the control messages that are used to create a working connection between the requestor and the resource - Handling exceptional conditions on a set-up attempt. - Crossing inter-network boundaries (gateways) - Initial control message contents, e.g., should requestor profile information be sent?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Design Alternatives for Computer Network Security."}]}
{"id": "nist_02173", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation say about ACKNOWLEDGMENTS? (Part 1) According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, ACKNOWLEDGMENTS: ACKNOWLEDGMENTS We are grateful to the following individuals for their generous contributions of expertise and time. | Name | Organization | |--------------------|--------------------------------------------------| | Tim Battles | AT&T | | Jay Borkenhagen | AT&T | | Chris Boyer | AT&T | | Nimrod Levy | AT&T | | Kathryn Condello | CenturyLink | | Christopher Garner | CenturyLink | | Pete r Romness | Cisco Systems | | Tony Tauber | Comcast | | Jonathan Morgan | Juniper Networks | | Carter Wyant | Juniper Networks | | Oliver Borchert | NIST ITL Advanced Networks Technologies Division | | Name | Organization | |----------------------|--------------------------------------------------| | Koti kalapudi Sriram | NIST ITL Advanced Networks Technologies Division | | Sean Morgan | Palo Alto Networks | | Tom Van Meter | Palo Alto Networks | | Andrew Gallo | The George Washington University | | Sophia Applebaum | The MITRE Corporation | | Yemi Fashina | The MITRE Corporation | | Susan Prince | The MITRE Corporation | | Susa n Symington | The MITRE Corporation | The Technology Partners/Collaborators who participated in this build submitted their capabilities in response to a notice in the Federal Register.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_02174", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Telehealth Remote Patient Monitoring Ecosystem say about 5.5 Identity Management, Authentication, and Access Control (PR.AC and PR.AC-P) Protective Technology (PR.PT-P)? (Part 4) According to Securing Telehealth Remote Patient Monitoring Ecosystem, 5.5 Identity Management, Authentication, and Access Control (PR.AC and PR.AC-P) Protective Technology (PR.PT-P): ords that relate to the patient and the RPM equipment that the patient receives. Patient-provided (e.g., 'bring your own device') biometric devices were excluded in this practice guide's architecture. The telehealth platform provider manages patient home-deployed components and, thus, assures that PR.AC-6 and PR.AC-P6 are addressed. For this practice guide, the telehealth platform provider manages components that it procured and configured. The telehealth platform provider configures the devices to include authenticators that enforce component authentication. For this practice guide, only biometric devices that are managed by telehealth platform providers are provisioned authenticators. This implements PR.AC-7 and PR.AC-P6. Patient homes may include other devices, such as personally-owned devices, that are not a part of the RPM ecosystem. Devices that are not managed by telehealth platform providers do not have authentication credentials for the RPM solution. One should note that this practice guide simulated a telehealth platform provider when exploring biometric devices that communicate over broadband.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, identity management. Contains security framework guidance for authentication systems. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_02175", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements provide? (Section 21) \\_2.3.xsd Definition: The Name Matching specification defines the procedures for comparing WFNs to each other with the purpose of determining whether they refer to some or all of the same products. Definition: The Dictionary specification defines the concept of a CPE dictionary, which is a repository of CPE names and metadata, with each name identifying a single class of IT product. The Dictionary specification defines processes for using the dictionary, such as how to search for a particular CPE name or look for dictionary entries that belong to a broader product class. Also, the 7 See the Table 2: Approved OVAL Platform Schema Versions of the SCAP 1.3 annex document, [NIST SP 800-126A], for the OVAL component specification (core schema) versions and platform schema versions that are supported by SCAP 1.3. Dictionary specification outlines all the rules that dictionary maintainers MUST follow when creating new dictionary entries and updating existing entries. Schema Locations: CPE.Applicability LanguageDefinition: The Applicability Language specification defines a standardized structure for forming complex logical expressions out of WFNs. These expressions, also known as applicability statements, are used to tag checklists, policies, guidance, and other documents with information about the product(s) to which the documents apply.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements."}]}
{"id": "nist_02176", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Secure Data Network Systems (SDNS) Key Management Documents provide? (Section 10) | 2.4.1. Transport Protocol (TP) Class 4 | 4 | | | | 2.4.2. Transport Protocol (TP) Class 0 | 4 | | | | 2.4.3. DoD Transmission-Control-Protocol (TCP) | 4 | | 2.5 | Network Layer Protocols | Network Layer Protocols | 5 | | | 2.5.1. ISO Connectionless-mode-Network-Protocol (CLNP) | 2.5.1. ISO Connectionless-mode-Network-Protocol (CLNP) | 5 | | | 2.5.2. DoD Connectionless-mode Internet Protocol (IP) | 2.5.2. DoD Connectionless-mode Internet Protocol (IP) | 5 | | | 2.5.3. CCITT X.25 Packet Layer Protocol (PLP) | 2.5.3. CCITT X.25 Packet Layer Protocol (PLP) | 5 | | 2.6 | Data Link and Physical Layer Protocols | Data Link and Physical Layer Protocols | 5 | | | 2.6.1. | Direct Dial Public Switched Telephone Network Data Link and Physical Layers | 5 | | | 2.6.2. | IEEE 802.x Data Link and Physical Layer Protocols | 6 | | | 2.6.3. | CCITT X.25 Data Link and Physical Layer Protocols | 6 | '] - r-. ' a , . r I i -r:' \u2022&gt; ' * &lt; a - a*:' f !' ' -,r&lt;-. ai ' \"??;/ -! - ' ;- ' ' . '&lt;J '\u2022 '] . &lt;- . V'.. Iqo /. lo ble.n 'bnB&gt;,5&gt;qoa8.^\\J|; V :s.i ? 0 V/ 0 1m fc 30/i )o wU;^ .3? lcn;ar/i r^n.liaOfiltjgA ,|.,S- vl ('(Si- \u2022.\u2022&gt;'&gt;o;\u00ab;;''i'^ -(ioirfsaS iojuo, laii/qSMKlT hogeiiBi'l' ; .fi.fr.S ffi.D '\u2022 nobeiniefi b iT GoCf , S^^kSr^-.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_02177", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cloud Computing Synopsis and Recommendations say about Table of Contents? (Part 10) According to Cloud Computing Synopsis and Recommendations, Table of Contents: | 5.3.4 Platform Responsibilities Managed by Providers........................................ | 5-4 | | | 5.3.5 | Savings in Up-front Costs ..........................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cloud Computing Synopsis and Recommendations."}]}
{"id": "nist_02178", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-6 in NIST_SP_800-37r2_Risk_Management_Framework? (Part 234) Control AM-6: \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ involve co-authorizing officials. 116 If so, agreements are established between the co-authorizing officials and documented in the security and privacy plans. Authorizing officials are responsible and accountable for ensuring that authorization activities and functions that are delegated to authorizing official designated representatives are carried out as specified. For federal agencies, the role of authorizing official is an inherent U.S. Government function and is assigned to government personnel only. ## AUTHORIZING OFFICIAL DESIGNATED REPRESENTATIVE The authorizing official designated representative is an organizational official designated by the authorizing official who is empowered to act on behalf of the authorizing official to coordinate and conduct the day-to-day activities associated with managing risk to information systems and organizations. This includes carrying out many of the activities related to the execution of the RMF. The only activity that cannot be delegated by the authorizing official to the designated representative is the authorization decision and signing of the associated authorization decision document (i.e., the acceptance of risk). ## CHIEF ACQUISITION OFFICER The chief acquisition officer is an organizational official designated by the head of an agency to advise and assist the head of agency and other agency officials to ensure that the mission of the agency is achieved through the management of the agency's acquisition activities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_02179", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The Network Security Center_ a System Level Approach to Computer Network Security provide? (Section 29) ced. 1.2.4 Cryptographic Mechanisms. Development of the NBS standard encryption algorithm has made it feasible to consider using encryption techniques as a part of the reference enforcement mechanism. The tutorial recommended a close functional relationship between the NSC and the encryption mechanism. The advantages of that approach can still be obtained when the two implementation levels are more completely separated. Section 2 of this report describes in more detail these cryptographic approaches. To more clearly describe the function of the NSC and how it interacts with other components of a network, the decomposition of a network is described in terms of distinct implementation levels. This decomposition is somewhat idealized, in that many existing networks do not evidence a clean separation into levels. However, it will serve as a good framework for analysis, as well as a guideline for future network development. The levels concept is a way of examining the various communications functions existing in a computer network. This concept was originally developed to describe intercomputer networks, and in particular the logical message flow within the network. For example, a user at one network site wishes to send a message of some sort to another user at a different site and he is not particularly concerned how that message gets there, merely that it does arrive unaltered and in a timely manner. Figure 1-1. Logical Vs. Actual Message Flow <!-- image --> Therefore we can think of a user level where messages are transmitted back and forth. In actuality, however, the messages may go \"down\" to another level, or \"down\" through several levels, before the actual physical message transmission takes place. At the user level messages are composed and then handed to the next level to be handled and routed as appropriate. Each level would see the level (s) below it as the message carrier. The interface between any two levels would be relatively simple.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Network Security Center_ a System Level Approach to Computer Network Security."}]}
{"id": "nist_02180", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Availability according to NIST Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Availability: The availability impact level is based on the specific mission and the data supporting that mission, not on the time required to re-establish access to worker safety information. The effects of disruption of access to most worker safety information or information systems would have a limited adverse effect on agency operations, agency assets, or individuals. Recommended Availability Impact Level: The provisional availability impact level recommended for worker safety information is low .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_02181", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TA-0 in Guidelines for Managing the Security of Mobile Devices in the Enterprise? (Part 28) Control TA-0: violations | | Wireless eavesdropping | \u2022 Use of secure connections to resources (e.g., VPN) \u2022 Mobile threat defense | | Threats | Mitigations and Countermeasures | |-------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Mobile malware | \u2022 User education \u2022 Security-focused device selection \u2022 Rapid adoption of software updates \u2022 Application vetting \u2022 OS and application isolation \u2022 Mobile threat defense | | Information loss due to insecure lock screen | \u2022 EMMtechnologies \u2022 Mobile device security policies \u2022 User education | | User privacy violations | \u2022 User education \u2022 EMMtechnologies \u2022 Application vetting | | Data loss via synchronization | \u2022 EMMtechnologies \u2022 Mobile device security policies \u2022 User education | | Shadow IT usage | \u2022 Mobile device security policies \u2022 User education | | Exploitation of vulnerabilities within the underlyingEMM platform | \u2022 Cybersecurity recommended practices \u2022 User education | | EMMadministrator credential theft | \u2022 Additional authentication for system administrators | | Insider threat | \u2022 EMMtechnologies \u2022 Mobile device security policies \u2022 User education | ## 4.3.1.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, malware. Contains technical security guidance that could inform defensive posture. Source: Guidelines for Managing the Security of Mobile Devices in the Enterprise."}]}
{"id": "nist_02182", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations say about Sample Level 2 Text? According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, Sample Level 2 Text: [The mission and business process's] C-SCRM Program shall: - Operate in accordance with the requirements and guidance set forth by [the enterprise's] C-SCRM Program; - Collaborate with the C-SCRM Program Management Office (PMO) to apply the C-SCRM practices and capabilities needed to assess, respond to, and monitor cybersecurity risks arising from pursuit of [the mission and business process's] core objectives; - Integrate C-SCRM activities into applicable activities to support [the enterprise's] objective to manage cybersecurity risks throughout the supply chain; - Assign and dedicate the resources needed for coordinating C-SCRM activities within [the mission and business process]; - Identify [the mission and business process's] critical suppliers, and assess the level of risk exposure that arises from that relationship; - Implement risk response efforts to reduce exposure to cybersecurity risks throughout the supply chain; and - Monitor [the mission and business process's] ongoing cybersecurity risk exposure in the supply chain profile, and provide periodic reporting to identified enterprise risk management and C-SCRM stakeholders.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_02183", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about Examine? According to Assessing Security Requirements for Controlled Unclassified Information, Examine: [SELECT FROM: access control policy and procedures; privacy and security policies, procedures for system use notification; documented approval of system use notification messages; system audit records; user acknowledgements of system use notification messages; system design documentation; system configuration settings; system use notification messages; system security plan; other relevant documents or records]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02184", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cell Phone Forensic Tools_ an Overview and Analysis Update provide? (Section 189) scenarios, then completely drained of all battery power and reacquired. All data was found as reported above. (Above) The following scenarios were conducted on an unlocked Motorola V300 GSM phone. Connectivity was established using Susteen's Motorola 2 Penguin cable. Connectivity and Retrieval: Proper authentication had to be provided to the password-protected device and the SIM card had to be inserted before contents were successfully acquired. Basic subscriber information (i.e. IMEI/ESN) was found and reported. Memory size is not reported. (Meet) PIM Applications: All active phone book entries were found and reported. Active calendar entries were found. Deleted PIM data was not found. (Below) Dialed/Received Phone Calls: Dialed/received phone calls were not found. (Miss) SMS/MMS Messaging: All active incoming and outgoing SMS messages were found and reported. Deleted SMS and MMS message data (i.e., images, sound bytes) were not found. (Below) Internet Messaging: No data was found. (Miss) Web Applications: Visited URLs, search queries performed, textual Web content and graphical images of visited sites were not found. (Miss) Text File Formats: Data content associated with text files (e.g., . txt , . doc , . pdf ) was not found. (Miss) Graphics Files Format: A connection could not be established allowing the transfer of graphic files (e.g., . bmp , . jpg , . gif . png , . tif ) to the Motorola V300. Images were created by using the picture camera. Active data was found and reported. (Meet). Compressed File Archive Formats: N.A. - The Motorola V300 does not support compressed archive files (e.g., . zip , . rar , . exe , . tgz ). (NA) Misnamed Files: N.A. - The Motorola V300 does not support misnamed files (e.g., . txt file renamed with a . dll extension). (NA) Peripheral Memory Cards: N.A. - The Motorola V300 does not allow for removable media. (NA) Acquisition Consistency: N.A.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Cell Phone Forensic Tools_ an Overview and Analysis Update."}]}
{"id": "nist_02185", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does An Introduction to Information Security say about 6.2 Select? According to An Introduction to Information Security, 6.2 Select: The second step of the RMF process involves selecting an initial set of baseline security controls for the system based on the security categorization as well as tailoring and supplementing the security control baseline as needed based on an organizational assessment of risk and local 7 The National Archives and Records Administration (NARA) has developed a Controlled Unclassified Information (CUI) Registry. The CUI Registry is an online repository for information, guidance, policy, and requirements on handling CUI, including issuances by the CUI Executive Agent. The registry is available at conditions. Security control selection guidance is provided in NIST SP 800-53 and in FIPS 200 .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: An Introduction to Information Security."}]}
{"id": "nist_02186", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-128 in A Framework for Designing Cryptographic Key Management Systems? (Part 111) Control ES-128: luding all its security functions. FR:9.5 The CKMS design shall specify all self-tests created and implemented by the designer and the corresponding CKMS functions whose correct operation they verify. ## 9.5 Scalability Testing Scalability is the ability of a system, network, or process, to correctly process increasing amounts of work in a graceful manner, or its ability to be enlarged to accommodate that increase. Scalability testing involves testing a device or system to learn how it reacts when the number of transactions to be processed or participants to be handled over a given period of time increases dramatically. Every device has its limitations, but some device designs scale better than others. If systems are not designed for modular scalability, adding additional devices may not be feasible. In addition, subtle problems often arise that cannot be solved by simply buying more equipment. Scalability testing is used to stress devices and systems so that these problems are known and mitigated before they become fully operational. FR:9.6 The CKMS design shall specify all scalability analysis and testing performed on the system to date. ## 9.6 Functional Testing and Security Testing The types of tests previously described can be performed to meet particular test goals. Functional testing attempts to verify that an implementation of some function operates correctly. A functional test might determine that a cryptographic algorithm implementation correctly computes the ciphertext from the plaintext, given the key. Security testing attempts to verify that an implementation functions securely. A security test might determine that, while a cryptographic algorithm implementation functions correctly (i.e. it produces the correct results), fluctuations in power consumption during the cryptographic process could lead to the compromise of the key.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_02187", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6.3. Model according to NIST Secure Data Network Systems (SDNS) Key Management Documents According to Secure Data Network Systems (SDNS) Key Management Documents, 6.3. Model: The KMAP comprises two parts: the information processor part and the communication part represented by the KMAE. When communication is required between two KMAPs, an application association is established between invocations of the processes' KMAEs. The KMAE represents an addressable set of communication capabilities which are defined by the KMASE and the ACSE. During the use of the KMASE services, the existence of an application association between cooperating KMAEs is presumed. The nature and purpose of communication over the application association are determined by the information processing context and the application context which are established for it. Note that each application association may be identified in an end system by an internal, implementation dependent, mechanism so that the KMASE service user, the KMASE, and the ACSE can refer to it. The KMASE is driven by service request and response primitives from the KMAP and by indication primitives from the presentation service provider. The KMASE, in turn, issues indication and confirm primitives to the KMAP and request primitives to the ACSE and the presentation service provider. The KMAP administers the K-MIB and the TEK-MIB in the sense of updating data in the IB upon receipt of indications and confirms and retrieving parameters from the IB when issuing requests and responses. K-MIB is a security MIB used to store key material. TEK-MIB is a security MIB used to store TEK, key identifiers (KIDs) and attributes regarding the use of the TEK.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_02188", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-8(5) in Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management? (Part 101) Control CM-8(5): s, configuration/connection requirements, and implementation guidance for organization-controlled mobile devices being established or implemented related to this control item might be the cause of ... | |------------------------------|-------------------|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | AC-19(a)(1) | HWAM- L01 | Devices moving into/out of the assessment boundary | devices not being adequately prepared for movement into or out of the assessment boundary. | | AC-19(a)(1) | HWAM- L06 | Subcomponents not authorized | a device with unauthorized subcomponents or a device lacking required subcomponents being found in the assessment boundary. | | AC-19(a)(1) | HWAM- L09 | Proposed changes are too old | requested changes not being addressed in a timely manner. | ## 3.3.3.2 Control Item AC-19(b): ACCESS CONTROL FOR MOBILE DEVICES ## Control Item Text: Control: The organization: - b. Authorizes the connection of mobile devices to organizational systems.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management."}]}
{"id": "nist_02189", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Best Practices for Privileged User PIV Authentication provide? (Section 11) ly allocated to system, network, security, and database administrators, as well as other IT administrators. Privileged accounts are exceptionally attractive targets for attackers of High Value Assets. A higher level of assurance than what is provided by single-factor authentication is therefore required for privileged users since unauthorized access to administrator capabilities can have catastrophic adverse effects on agency operations, assets, and/or individuals. As stated in the CSIP, 'The Cybersecurity Sprint directed agencies to immediately implement PIV for [\u2026] 100% of privileged users.' [1] The reason for this directive is that 'Although there is no single method by which all cyber incidents can be prevented, improving the access management of user accounts on federal information systems could drastically reduce current vulnerabilities. Privileged user accounts are a known target for malicious actors but can be protected by an existing, strong authentication solution: Personal Identity Verification (PIV) credentials. Implementing strong authentication PIV credentials, as directed in Homeland Security Presidential Directive 12: Policy for a Common Identification Standard for Federal Employees and Contractors (HSPD-12) and Federal Information Processing Standard (FIPS) 201-2: Personal Identity Verification (PIV) of Federal Employees and Contractors , is a costeffective and immediate action that agencies should take to drastically reduce their risk profiles. PIV credentials [\u2026] reduce the risk of identity fraud, tampering, counterfeiting, and exploitation.' [1] Agencies are required to perform a risk assessment to determine the level of assurance requirements of their systems according to OMB Memorandum 04-04 (M-04-04), EAuthentication Guidelines for Federal Agencies [7] (see Section 2.3).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Best Practices for Privileged User PIV Authentication."}]}
{"id": "nist_02190", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Report of the Workshop on Cryptography in Support of Computer Security provide? (Section 41) to four major clusters , namely: - . Mathematical and statistical aspects, - . Engineering aspects of designing and constructing encryption/ decryption devices and their host systems and networks - . Associated protection measures integral to the employment of data encryption , and - . The technical and administrative management technologies leading to optimal use of data encryption procedures; key management; administrative security procedures; and monitoring, evaluating and auditing encryption performance. NBS has attempted to provide to the public domain, without affecting National Security , government expertise and guidance in the proper application of cryptography as an aid in the protection of information , the maintenance of privacy and the prevention of computer abuse. NBS recognized in 1971 that the lack of any market for data encryption (outside the National Security Community) would severely constrain industrial motivation to develop additional expertise . Similarly , we knew that the long history of disinterest , the lack of formal academic structure and the almost non-existent supply of teachers would severely dampen academic motivation. Indeed, the development of technology has been slow. The major constructive changes to data are exemplified by: . The development of product lines of encryption devices incorporating the proposed NBS data encryption standard by a number of commercial vendors, . The increasing number of scientific and technical papers on the several technologies associated with cryptography which are being presented at professional meetings . The development by the Federal Reserve Board of a specification for a cryptographic device using DES to secure the data links of the Federal Reserve Communications System, and .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Report of the Workshop on Cryptography in Support of Computer Security."}]}
{"id": "nist_02191", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to SSL VPNs say about 2.1 The Need for Network and Transport Layer Security? (Part 4) According to Guide to SSL VPNs, 2.1 The Need for Network and Transport Layer Security: ion layer controls because of the difficulties in adding controls to individual applications. Network layer controls also provide a way for network administrators to enforce certain security policies. Another advantage of network layer controls is that since IP information (e.g., IP addresses) is added at this layer, the controls can protect both the data within the packets and the IP information for each packet. However, network layer controls provide less control and flexibility for protecting specific applications than transport and application layer controls. SSL tunnel VPNs provide the ability to secure both TCP and UDP communications including client/server and other network traffic, and therefore act as network layer VPNs. - \u0084 Data Link Layer. Data link layer controls are applied to all communications on a specific physical link, such as a dedicated circuit between two buildings or a dial-up modem connection to an Internet Service Provider (ISP). Data link layer controls for dedicated circuits are most often provided by specialized hardware devices known as data link encryptors ; data link layer controls for other types of connections, such as dial-up modem communications, are usually provided through software. Because the data link layer is below the network layer, controls at this layer can protect both data and IP information. Compared to controls at the other layers, data link layer controls are relatively simple, which makes them easier to implement; also, they support other network layer protocols besides IP. Because data link layer controls are specific to a particular physical link, they cannot 2 Several Request for Comment (RFC) documents from the Internet Engineering Task Force (IETF) define S/MIME, as well as standards for using it to protect email messages. One example is RFC 3852, Cryptographic Message Syntax (CMS) , available at 3 TLS is the standards-based version of SSL version 3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to SSL VPNs."}]}
{"id": "nist_02192", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CS-3 in U.S. Department of Energy Risk Assessment Methodology? (Part 63) Control CS-3: 'ra, :,&lt;..i KA b;,.. ;\u2022'. -id! '&gt;\u2022- i,^*^ ;'M *j -j ;: . i- . ...v, I*' ' ' .(c- .-t'fy'fy. k. ' y\\ 'i: .' r;V'.-tf# .. Wfcnv, .. i\u00abi^(||l^ii(V-' *\"\u2022&gt;\u2022.'. 1 \u00abfc ^\u2022^il.Vi \u2022.. wfV' ' ^''^ ..,.:r,) - ^fUf -ll : *\u00bbV' -5t;y.p/7' ,|, .f. r-lf. \u2022'\u20221.'./ '^j. ' ,,-/^iii.t--- 'jrt,.' ';-/i.;. 'Y:',^..,(i!''\"ft' .y :.,t *^,^ vo*st, 5i'''4l?16it^ ^,i:it^''i 'Off . ?j| . ' Tt I ^:. '.' r - y i'4 sit?''''T''.'7',. \u2022\u2022 f'w vr\u00ab* ' n/ \u2022. ' j',\"' VN ^ ' H \u00bb 4m ;ar'^jq^r,.i((4iv \"' 5 :i'rti i&gt;a/i . ..' . . , -r., ,rr'^,^-\\* *^.,7r. lnii,Sim.&gt;SU,cLr^L -.r-f, &gt;(n?/'ft\u00abSf,^' WjfltWSswef;?. $:yiM.oCiafil- '^'S tt-^'iBf^'l^fe^tt^ ,A^A&lt;/',ftvaiW \"-rs' fs-ns^'sri'Sr-'sir.'- :' ' k If- &lt;r' .\u2022uTrffcn'w' &gt;#*&gt;.lV'i!''3:. -''!? 't'i- f, -^01 ) tfti '&amp; -ifwvf aW/StVO^'*' .f4i&gt;iwV' W' t' .\u00bb^Y&lt;^y*ilifcrWVS ;.d j 'f-\" - '3:.o- .ci'J'i.i).te. : . fe:(t^vjf| ,j.' ,f ' I&gt;nj\u00a3 rdT nff((jL&lt;i-^ \u2022 - ..' I ^ '&lt;iT^i'! AU'&lt;:'- .'^: ^ ,'; 4 -v\" A', .', .f : 7 a 1 i: ^ \\| I f&gt;'ayf \u00bbi\u00bb\u00bb* 'T*T(l'lf \" v* J f| V,l:\u00bb ## STEP 3 \\ ## REVIEW BASELINE SECURITY REQUIREMENTS (BLSRs) AND IDENTIFY THOSE NOT MET OR PARITALLY MET ## STEP 3 GENERAL PURPOSE OF STEP 3 : The purpose of Step 3 is to determine whether your system's hardware, software, and data - as they exist today in their current operating environment and utilized by you and your organization - meet the minimum Baseline Security Requirements (BLSRs) set forth in applicable DOE Orders. In 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 (requirements) that MUST be in place, per DOE order, to protect such processing.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: U.S. Department of Energy Risk Assessment Methodology."}]}
{"id": "nist_02193", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE) provide? (Section 139) d initiate the events. The threat events used for the example solution are described below. These threat events describe how the mobile devices in Orvilia might be compromised by malicious activities. All of the threat events map to both threat sources identified in Section F.1.6. Orvilia examined the sample tables in NIST SP 800-30 Revision 1-Tables E-1, E-2, E-3, E-4, and E-5-and analyzed the sources of mobile threats identified in Task 1-4. Using this process, Orvilia leadership identified the following threat events. A mobile application can attempt to collect and exfiltrate any information to which it has been granted access. This includes any information generated during use of the application (e.g., user input), usergranted permissions (e.g., contacts, calendar, call logs, camera roll), and general device data available to any application (e.g., International Mobile Equipment Identity, device make and model, serial number). Further, if a malicious application exploits a vulnerability in other applications, the OS, or device firmware to achieve privilege escalation, it may gain unauthorized access to any data stored on or otherwise accessible through the device. Malicious actors may create fraudulent websites that mimic the appearance and behavior of legitimate ones and entice users to authenticate to them by distributing phishing messages over short message service (SMS) or email. Effective use of social engineering techniques such as impersonating an authority figure or creating a sense of urgency may compel users to forgo scrutiny of the message and proceed to authenticate to the fraudulent website; it then captures and stores the user's credentials before (usually) forwarding them to the legitimate website to allay suspicion. Malicious actors may send users SMS or email messages that contain a uniform resource locator (URL) where a malicious application is hosted.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_02194", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.4 Electronic Mail according to NIST Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters According to Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters, 4.4 Electronic Mail: Blank electronic ballots should be prepared as described in Section 4.2.5 to ensure the files have the best possible chance of being successfully delivered to voters, and contain the accurate candidate and ballot question information. Jurisdictions should follow their standard procedures for ensuring these blank ballots are correct before e-mailing them to voters. Jurisdictions should beware of spam filters which may inadvertently mark their messages as spam and not display it to users. It is difficult to ensure that e-mails sent by jurisdictions will not be marked as spam. As previously noted, use of DomainKeys Identified Mail [10] on the jurisdiction's e-mail server may reduce the changes of outgoing e-mail being marked as spam. Jurisdictions may also consult the Message Anti-Abuse Working Group's Sender Best Communications Practices for additional technical measures [13]. E-mails should be addressed to voters individually, rather than sending a single e-mail to a group of voters. The 'Reply-to' and 'From' fields of the outgoing e-mail should be set to an e-mail account monitored by election officials. Election officials should closely monitor this e-mail account for any error messages that indicate a message was not properly received by the voter. Some types of e-mail error messages were described in Section 2.2.2.2. Election officials should read the error message to determine the nature of the problem and remedy it if possible, as it may be a sign of a technical malfunction. If the problem cannot be remedied, election officials should apply the same procedures used by the jurisdiction when it has evidence that a mailed ballot did not reach its destination.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters."}]}
{"id": "nist_02195", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity of Genomic Data say about 5.5.1. Use Case Description? According to Cybersecurity of Genomic Data, 5.5.1. Use Case Description: The target stakeholder would be a small organization, such as a university or start-up, that wants to aggregate and process genomic data. A start-up has important intellectual property that needs to be protected. A university may want to utilize NIH genomic data and must implement NIH cybersecurity and privacy requirements. Both need a solution to manage the risk of aggregating and processing genomic data that can be done in a timely and cost-effective manner.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cybersecurity of Genomic Data."}]}
{"id": "nist_02196", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Executive Guide to the Protection of Information Resources say about The National Computer Systems Laboratory? According to Executive Guide to the Protection of Information Resources, The National Computer Systems Laboratory: Conducts research and provides scientific and technical services to aid Federal agencies in the selection, acquisition, application, and use of computer technology to improve effectiveness and economy in Government operations in accordance with Public Law 89-306 (40 U.S.C. 759), relevant Executive Orders, and other directives; carries out this mission by managing the Federal Information Processing Standards Program, developing Federal ADP standards guidelines, and managing Federal participation in ADP voluntary standardization activities; provides scientific and technological advisory services and assistance to Federal agencies; and provides the technical foundation for computer-related policies of the Federal Government The Laboratory consists of the following divisions:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Executive Guide to the Protection of Information Resources."}]}
{"id": "nist_02197", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Information System Security Best Practices for UOCAVA-Supporting Systems provide? (Section 11) peration of the systems. It should also be consulted by system designers when documenting system operations and administrators when assigning individuals to fulfill roles defined by the system design. State and local election officials have various responsibilities under the Uniformed and Overseas Citizens Absentee Voting Act (UOCAVA), many of which involve information security. These state and local jurisdictions have begun to use information technology (IT) systems and the Internet to facilitate UOCAVA voting; for example, they are required to make voter registration, absentee ballot applications, and general election information available electronically. These IT systems are often used to distribute election information to voters, send and collect voter registration and ballot request forms, and deliver blank ballots. This document provides voting jurisdictions with security best practices for IT and networked systems that are used to support UOCAVA voting by sending or receiving voter registration or ballot request materials, or by delivering blank ballots to voters. Some of these best practices are unique to voting systems, but most are similar to, or the same as, best practices in IT and networked systems in general. For the latter, this document summarizes and points to other security-related documents published by NIST. This 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Information System Security Best Practices for UOCAVA-Supporting Systems."}]}
{"id": "nist_02198", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Platform Firmware Resiliency Guidelines provide? (Section 34) s. Each of them may include their own expansion ROM firmware and/or microcontroller with associated firmware. In most modern platforms, host processor boot firmware is contained in a SPI flash device. BIOS and Unified Extensible Firmware Interface (UEFI) are examples of this type of firmware. In addition to boot firmware, there is platform runtime code. This is code which remains resident in memory and executable after the platform has booted. This is most typical for microcontrollers where firmware is required to execute to perform some function while the system is fully operational. An example of host processor firmware which is considered as runtime code would be System Management Mode (SMM) code. Some power supplies have their own microcontroller and associated firmware. Common battery architectures also include internal logic and firmware governing the charge and discharge behavior of the battery. Modern embedded systems use programmable logic components to provide glue logic functionality. There are two types of programmable logic components, Field Programmable Gate Arrays known as FPGAs and Complex Programmable Logic Devices known as CPLDs. FPGAs are typically loaded with bitstream programs from attached flash devices on power up. CPLDs on the other hand are programmed with a bitstream once and then they retain the function until programmed again in the field. Typically this functionality is needed for basic operations of the system and if corrupted could result in permanent denial of service of a platform. Some fans have their own microcontroller and associated firmware. The devices described above will typically contain some set of firmware and data on nonvolatile storage, either resident on the device itself or on a shared storage device (e.g., the SPI flash). This section describes firmware code and data, and briefly discusses the scope of the document related to these components.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Platform Firmware Resiliency Guidelines."}]}
{"id": "nist_02199", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Authority Key Identifier : according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Authority Key Identifier :: 8F:BE:8E:48:44:B4:DF:FA:B2:90:91:74:CD:03:57:C7:FF:E8:BD:0C", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_02200", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Status Report on the Final Round of the NIST Lightweight Cryptography Standardization Process provide? (Section 81) | \u25d7 | \u25d7 | | | \u25d7 | | faster encryption | \u25d7 | \u25d7 | \u25d7 | \u25d7 | \u25d7 | \u25d7 \u25d7 | \u2717 \u2717 | \u25d7 | | faster decryption smaller (encrypt only) | \u25d7 \u2717 | \u25d7 \u2717 | \u2717 | \u2717 | \u2717 | \u2717 | \u2717 \u2717 | \u2717 \u2717 | | smaller (decrypt only) | \u2717 | \u2717 | \u2717 \u2717 | \u2717 | \u2717 | \u2717 \u2717 | \u2717 | | | smaller (encrypt and decrypt) | \u2717 | \u2717 | | \u2717 | \u2717 | | | \u2717 | | faster encryption | \u2717 | \u2717 | \u2717 \u2717 | \u2717 | \u2717 | \u25d7 | \u2717 \u2717 | \u2717 \u2717 | | faster decryption | \u2717 | \u2717 | | \u2717 | \u2717 | \u2717 | | | | smaller (encrypt only) | \u2717 | \u2717 \u2717 | \u2717 \u2717 | \u2717 \u2717 | \u2717 \u2717 | \u2713 \u2713 | \u2717 \u2717 | \u2713 | | smaller (decrypt only) | | \u2717 | \u2717 | \u2717 | | | | \u2713 | | smaller (encrypt and decrypt) | \u2717 \u2717 | \u2717 | \u2717 | \u2717 | \u2717 \u2717", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Final Round of the NIST Lightweight Cryptography Standardization Process."}]}
{"id": "nist_02201", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2013 Annual Report provide? (Section 221) , Australia, July 1-3, 2013. In Lecture Notes in Computer Science 7959, Information Security and Privacy , C. Boyd and L. Simpson, eds., Springer, Berlin (2013) 13-26. doi:10.1007/9783-642-39059-3\\_2. Due to the symmetric padding used in the stream cipher Grain v1 and Grain-128, it is possible to find Key-IV pairs that generate shifted keystreams efficiently. Based on this observation, Lee et al. presented a chosen IV related Key attack on Grain v1 and Grain-128 at ACISP 2008. Later, the designers introduced Grain-128a having an asymmetric padding. As a result, the existing idea of chosen IV related Key attack does not work on this new design. In this paper, we present a Key recovery attack on Grain-128a, in a chosen IV related Key setting. We show that using around \u03b3\u00b7 2^32 ( \u03b3 is a experimentally determined constant and it is sufficient to estimate it as 2^8) related Keys and \u03b3\u00b7 2^64 chosen IVs, it is possible to obtain 32 \u00b7\u03b3 simple nonlinear equations and solve them to recover the Secret Key in Grain-128a. J. Boyar, M. Find and R. Peralta , 'Four Measures of Nonlinearity,' Eighth International Conference on Algorithms and Complexity (CIAC 2013) , Barcelona, Spain, May 22-24, 2013. In Lecture Notes in Computer Science 7878, Algorithms and Complexity , P . G. Spirakis and M. Serna, eds., Springer, Berlin (2013) 61-72. doi:10.1007/978-3-642-38233-8\\_6. Cryptographic applications, such as hashing, block ciphers and stream ciphers, make use of functions which are simple by some criteria (such as circuit implementations), yet hard to invert almost everywhere. A necessary condition for the latter property is to be 'sufficiently distant' from linear, and cryptographers have proposed several measures for this distance.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, cui. Contains guidance on protecting sensitive government information. Source: Computer Security Division 2013 Annual Report."}]}
{"id": "nist_02202", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Wireless Infusion Pumps in Healthcare Delivery Organizations provide? (Section 390) l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P 1 8 0 0 - 8 . . RFID RMF RTLS SD SEP SIEM SOC SP SSID SSO TCP TIR TLS U.S. URL USB VLAN WEP WLC WPA WPA2 Radio-Frequency Identification Risk Management Framework Real-Time Locating Systems Secure Digital Symantec Endpoint Protection Security Information and Events Management Security Operations Center Special Publication Service Set Identifier Single Sign-On Transmission Control Protocol Technical Information Report Transport Layer Security United States Uniform Resource Locator Universal Serial Bus Virtual Local Area Network Wired Equivalent Privacy Wireless LAN Controller Wi-Fi Protected Access Wi-Fi Protected Access II NIST SP 1800-8C: Securing Wireless Infusion Pumps 255 Appendix D References [1] J. Moy, OSPF Version 2, Internet Engineering Task Force (IETF) Network Working Group Request for Comments (RFC) 2328, April 1998. https://www.ietf.org/rfc/rfc2328.txt [accessed 2/7/18]. [2] Cisco Adaptive Security Virtual Appliance (ASAv) Quick Start Guide, 9.6, Cisco [Web site], asav.html [accessed 2/7/18]. [3] D. Bider and M. Baushke, SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol, Internet Engineering Task Force (IETF) Request for Comments (RFC) 6668, July 2012. https://tools.ietf.org/html/rfc6668 [accessed 2/7/18]. T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P 1 8 0 0 - 8 . . [4] [5] J. Postel, Internet Control Message Protocol: DARPA Internet Program Protocol Specification, Internet Engineering Task Force (IETF) Network Working Group Request for Comments (RFC) 792, September 1981. https://tools.ietf.org/html/rfc792 [accessed 2/7/18]. J. Case, M. Fedor, M.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: single sign-on, sso. Contains security framework guidance for authentication systems. Source: Securing Wireless Infusion Pumps in Healthcare Delivery Organizations."}]}
{"id": "nist_02203", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector? (Part 41) Control AM-1: s that allow HDOs to verify that an individual is who they claim to be, also ensuring that the individual has appropriate credentials to interact with clinical systems and medical imaging information. Regarding provisioning, this project assumed that following identity proofing, the organization can create and securely deliver credentials (e.g., user accounts in which the individual can select and update passwords or challenge responses known only to that individual). Identities may include multiple user accounts or access mechanisms that may be applied. For example, an individual may have a job function as an IT administrator. As a member of the HDO workforce, they may be credentialed to access certain systems such as email or productivity software. They may also have access to separate privileged accounts to be used when they perform IT administrative duties. Having separate credentials established based on functionality or role is a common practice in healthcare and provides a form of separation of duties. Medical devices and systems may also have identities, that are authenticated using digital certificates, keys, or other unique identifiers such as host identifiers or MAC addresses. ## 4.1.5.1 Access Control Access control is applied contextually, based on the identity type. This project implemented access control for privileged users, clinical users, devices, and systems. Subsections below provide more detail on the project's approach. ## 4.1.5.1.1 Privileged Access Management Privileged access includes those credentials that have permissions to systems that are greater than standard users. Privileged access accounts often allow greater visibility of resources stored on systems and may allow modifying configuration settings or permitting installation of software components. One measure that this guide implements is segregating privileged access accounts.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, privileged access. Contains security framework guidance for authentication systems. Source: Securing Picture Archiving and Communication System (PACS)_ Cybersecurity for the Healthcare Sector."}]}
{"id": "nist_02204", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.2 Threat Analysis according to NIST Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders According to Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders, 5.2 Threat Analysis: The following subsections describe how the build architecture addresses the threats discussed in Section 3.5.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, single sign-on. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_02205", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain NIST Publications: according to NIST Security Architecture Design Process for Health Information Exchanges (HIEs) According to Security Architecture Design Process for Health Information Exchanges (HIEs), NIST Publications:: - SP 800-53 Rev. 3, Recommended Security Controls for Federal Information Systems and Organizations, security controls: AC-2, Account Management; IA-4, Identifier Management; IA-5, Authenticator Management. - SP 800-57, Part 1, Recommendation for Key Management - Part 1: General. - Draft SP 800-63 Rev. 1, Electronic Authentication Guideline.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Security Architecture Design Process for Health Information Exchanges (HIEs)."}]}
{"id": "nist_02206", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain How to Cite this NIST Technical Series Publication: according to NIST 3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report According to 3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report, How to Cite this NIST Technical Series Publication:: Guo Y, Licata J, Pillitteri V, Rekhi S, Beverly R, Yuan X, Bowman S, Gregg R, Key G, Hinton C, Reuther A, Adamson R, Warren A, Bangalore P, Deumens E, Farkas C (2023) 3 rd High-Performance Computing Security Workshop: Joint NIST-NSF Workshop Report. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8476. https://doi.org/10.6028/NIST.IR.8476", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report."}]}
{"id": "nist_02207", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does De-Identifying Government Datasets_ Techniques and Governance provide? (Section 138) ities in a dataset that could be used for re-identifying data subjects. They do not determine whether someone with intimate knowledge of a specific respondent can find that respondent in the database. The only way to protect a single specific individual perceived to be at high risk of re-identification is through data perturbation (e.g., noise addition) or information reduction (e.g., removing the observation altogether). 37 Although other documents that discuss de-identification use the term risk assessment to refer to a specific calculation of ambiguity using the k-anonymity de-identification model, this document uses the term risk assessment to refer to a much broader process. Specifically, risk assessment is defined as, 'The process of identifying, estimating, and prioritizing risks to organizational operations (including mission, functions, image, 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. Synonymous with risk analysis' [149]. The key statistic calculated in re-identification studies is the conditional re-identification rate . This statistic is a proxy for disclosure risk. The rate is the number of confirmed links between the dataset and another dataset divided by the number of putative (suspected) links expressed as a percentage. If the conditional re-identification rate falls above an agreed upon threshold for any publication strata, it suggests that the data should not be released outside of a controlled environment. Re-identification studies are often an iterative process. If a re-identification study uncovers problems with the de-identified data, the data curator can engage with subject-matter experts, make changes to the dataset, and perform another re-identification study.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: De-Identifying Government Datasets_ Techniques and Governance."}]}
{"id": "nist_02208", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Role-Based Access Control : according to NIST Blockchain Networks_ Token Design and Management Overview According to Blockchain Networks_ Token Design and Management Overview, Role-Based Access Control :: In role-based access control (see NIST definition [65]), role assignation follows either a top-down approach, where privileged entities act as system owners and directly manage the roles, or a bottom-up approach, where roles are self-assigned by users with predefined conditions and time delays during which system owners may be allowed to cancel new role assignations. Roles are implemented through role manager smart contracts that are integrated with token factory contracts. Smart contract libraries that offer role-based access control have been developed, such as the Open-Zeppelin library [66]. It is also possible to implement roles in blockchains that follow the UTXO model by modifying the input and output parameters in the transaction format [67].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, token. Contains security framework guidance for authentication systems. Source: Blockchain Networks_ Token Design and Management Overview."}]}
{"id": "nist_02209", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6.2 Adversarial Attacks according to NIST Security Analysis of First Responder Mobile and Wearable Devices According to Security Analysis of First Responder Mobile and Wearable Devices, 6.2 Adversarial Attacks: The following are attacks that exemplify a malicious external entity actively exploiting a vulnerability. Each attack identifies with an adversarial threat source.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Security Analysis of First Responder Mobile and Wearable Devices."}]}
{"id": "nist_02210", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Supporting Roles according to Guide for Security-Focused Configuration Management of Information Systems? Supporting Roles: SAISO (if s/he is not the SecCM Program Manager); CIO; AO; SSO; SA; System/Software Developer", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_02211", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Recovering from Ransomware and Other Destructive Events say about ACKNOWLEDGMENTS? According to Data Integrity_ Recovering from Ransomware and Other Destructive Events, ACKNOWLEDGMENTS: We are grateful to the following individuals for their generous contributions of expertise and time. | Name | Organization | |----------------|----------------------------| | Steve Petruzzo | GreenTec USA | | Steve Roberts | Hewlett Packard Enterprise | | Dave Larimer | IBM Corporation | | John Unthank | IBM Corporation | | Jim Wachhaus | Tripwire | | Donna Koschalk | Veeam Software Corporation | | Dewain Smith | Veeam Software Corporation | | Lisa Ignosci | Veeam Software Corporation | | Name | Organization | |-----------------|-----------------------| | Brian Abe | The MITRE Corporation | | Sarah Kinling | The MITRE Corporation | | Josh Klosterman | The MITRE Corporation | | Susan Urban | The MITRE Corporation | | Mary Yang | The MITRE Corporation | The Technology Partners/Collaborators who participated in this build submitted their capabilities in response to a notice in the Federal Register. Respondents with relevant capabilities or product components were invited to sign a Cooperative Research and Development Agreement (CRADA) with NIST, allowing them to participate in a consortium to build this example solution. We worked with: | Technology Partner/Collaborator | Build Involvement | |-----------------------------------|----------------------------------------------------------| | GreenTec USA | GreenTec WORMdisk, v151228 | | Hewlett Packard Enterprise | HPE ArcSight ESM, v6.9.1 HPE ArcSight Connector, v7.4.0 | | IBM Corporation | IBM Spectrum Protect, v8.1.0 | | Tripwire | Tripwire Enterprise, v8.5 Tripwire Log Center, v7.2.4.80 | | Veeam Software Corporation | Veeam Availability Suite 9.5 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Recovering from Ransomware and Other Destructive Events."}]}
{"id": "nist_02212", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Interfaces for Personal Identity Verification_ Part 1 \u2013 PIV Card Application Namespace, Data Model and Representation say about Appendix A. PIV Data Model? (Part 16) According to Interfaces for Personal Identity Verification_ Part 1 \u2013 PIV Card Application Namespace, Data Model and Representation, Appendix A. PIV Data Model: 0xFE | LRC | 0 | Note that the optional MSCUID data element was deprecated in a previous version and eliminated in this version of SP 800-73. However, historic retired key management certificates 23 This is the recommended length. The certificate size can exceed the indicated length value. 24 The numeric values indicated in keysWithOnCardCerts and keysWithOffCardCerts are represented as unsigned binary integers. 25 The offCardCertURL data element shall be present if keysWithOffCardCerts is greater than zero and shall be absent if both keysWithOnCardCerts and keysWithOffCardCerts are zero. The offCardCertURL may be present if keyWithOffCardCerts is zero but keysWithOnCardCerts is greater than zero. MAY still include the MSCUID element, so it is retained as an optional data element above. This applies to all of the retired key management key objects represented in Table 21 -Table 40 . Table 22. Retired X.509 Certificate for Key Management 2 | Retired X.509 Certificate for Key Management 2 | Retired X.509 Certificate for Key Management 2 | 0x1002 | 0x1002 | |--------------------------------------------------|--------------------------------------------------|----------|------------| | Data Element (TLV) | Tag | Type | Max. Bytes | | Certificate | 0x70 | Variable | 1856 26 | | CertInfo | 0x71 | Fixed | 1 | | MSCUID (Optional) | 0x72 | Variable | 38 | | Error Detection Code | 0xFE | LRC | 0 | Table 23.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interfaces for Personal Identity Verification_ Part 1 \u2013 PIV Card Application Namespace, Data Model and Representation."}]}
{"id": "nist_02213", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges say about Organizations may experience challenges in their quest to meet mandatory RBT requirements.? According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges, Organizations may experience challenges in their quest to meet mandatory RBT requirements.: While many survey participants said that their organizations leverage learning management systems to automate the tracking of RBT completion, over a third are using a manual method like a spreadsheet, which can result in extra burden placed on staff. While most participants said that they do not experience challenges tracking completion, tracking contractor training was more challenging than tracking federal employee training, sometimes because current LMS may not be accessible to contract staff. Additionally, organizations were challenged in getting employees to complete training by the appointed deadline. This may be due to mandatory training overload, employee time constraints, or a lack of concrete consequences for not completing training (e.g., disabling accounts and network access). <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges."}]}
{"id": "nist_02214", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain CRL Distribution Points : according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, CRL Distribution Points :: ldap://smime2.nist.gov/cn=Test%20PIV-I%20RSA%202048- bit%20CA%20for%20Test%20PIV%20Cards%20v2,ou=Test%20CA,o=Test%20Certificat es%202020,c=US?certificateRevocationList;binary", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_02215", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-06(05) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control AC-06(05): LEAST PRIVILEGE | PRIVILEGED ACCOUNTS ASSESSMENT OBJECTIVE: Determine if:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_02216", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Control according to NIST_SP_800-53r5_Security_Privacy_Controls? Control: Track and document incidents.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02217", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AN-2011 in ANSI_NIST-ITL 1-2011 Requirements and Conformance Test Assertions? (Part 74) Control AN-2011: record consisting of header information. The second information item of this subfield (content record count / CRC) shall be the sum of the Type-2 through Type-99 records contained in this transaction. This number is also equal to 1 O 1 O 2 M 1 M 1.015- Occurrence 1.016- Occurrence 1.001- Record Header Count(1.015) LTE 1 Count(1.016) LTE 1 <See Requirement ID \u201cField: xx.001-Record Header\u201d> t-2 NIEM- 1.001- Record Header ForEach(XElm(itl:PackageInformationRecord ) { {XElm(biom:RecordCategoryCode)} EQ ASCII(01) } 1 M 1.002-VER {1.002} EQ ASCII(0500) M 1.003- Subfields <See Requirement ID \u201cField: Type1-Subfield Occurrence\u201d and \u201cField: xx.002-IDC\u201d> t-2 1 M 1.003- Subfield1 REC {US_Subfield:1 in RS_Subfield:1 in 1.003} EQ 1 2 M 1.003- Subfield1 CRC {US_Subfield:2 in 1.003} EQ Count(Records in Transaction ST Type(Records) 59 B B X B B* B* Value the count of the remaining subfields of Field 1.003 Transaction content / CNT. The maximum value for CRC is 999. MO [2 to 99]) EQ 8.1.3, Table 19, Table 1 Field: 1.003- Transaction Content Subfield 2 REC Value Each of the remaining subfields of Field 1.003 Transaction content / CNT corresponds to a single Type-2 through Type-99 record contained in the transaction. Two information items shall comprise each of these subfields: The first information item (record category code / REC), shall contain a number chosen from the \u201crecord identifier\u201d column of Table 1. Field: 1.003- Transaction Content Subfield 2 IDC Value Field: 1.003- Transaction Content Subfield 2 IDC Matches 8.1.3, Table 19 The second information item (information designation character / IDC) shall be an integer equal to or greater than zero and less than or equal to 99. See Section 7.3.1. 8.1.3, Table 19, 7.3.1 IDC references are stated in Type-1 Field 1.003 Transaction content / CNT and shall be used to relate information items in the CNT field of the Type-1 record to the other records in the transaction.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: ANSI_NIST-ITL 1-2011 Requirements and Conformance Test Assertions."}]}
{"id": "nist_02218", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Understanding Stablecoin Technology and Related Security Considerations say about Fiat Currency-Backed? (Part 3) According to Understanding Stablecoin Technology and Related Security Considerations, Fiat Currency-Backed: rstand this, consider a stablecoin pegged to the U.S. dollar (USD). In this case, the stablecoin should be worth $1 USD. In the open market, however, the price will fluctuate due to supply and demand. Stability is achieved because if the stablecoin drops in price (say to $0.98), investors can buy the stablecoin at $0.98 on the open market and then immediately redeem it with the stablecoin issuer at the price of $1 (thereby earning $0.02 per coin bought). This purchasing of the stablecoin by investors will create demand, which will increase the price back to near $1. If the price increases from $1 (say to $1.02), then investors that already own the stablecoin can sell on the open market (making a profit of $0.02 per coin sold). These sales will increase supply, thus lowering the price. Nothing in this stability mechanism requires on-blockchain smart contract knowledge of pricing. Thus, fiat currency-backed stablecoins do not require interactions with oracles (entities that post trusted prices on blockchains) or need coin holders to vote on pricing information. An interesting feature of many fiat-backed stablecoins is that they may exist simultaneously on multiple blockchains. This is possible because the primary functionality of the stablecoin is not implemented on a blockchain. The reserve pool is kept off-blockchain and, thus, can support redemptions on all blockchains on which the coin is instantiated. Lastly, fiat-backed stablecoins are more amenable to being regulated by countries than their DeFi counterparts. This is because an off-blockchain managing company registered in a particular country typically exists. This company may be subject to financial regulation, thereby subjecting the stablecoin to regulation. Table 1 summarizes the typical characteristic settings for fiat-backed stablecoins. Table 1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Understanding Stablecoin Technology and Related Security Considerations."}]}
{"id": "nist_02219", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain \u00b7 Watch for harmful pop-ups according to NIST Small Business Information Security_ The Fundamentals According to Small Business Information Security_ The Fundamentals, \u00b7 Watch for harmful pop-ups: When connected to and using the Internet, do not respond to popup windows requesting that you click 'OK' for anything. Use a popup blocker and only allow popups on websites you trust. If a window pops up on your screen unexpectedly, DO NOT close the popup window, either by clicking 'okay' or by selecting the X in the upper right corner of the popup window, especially if the pop up is informing you that your system has a virus and suggesting you download a program to fix it. Do not respond to popup windows informing you that you have to download a new codec, driver, or special program for the web page you are visiting. Some of these popup windows are actually trying to trick you into clicking on 'OK' which will allow it to download and install spyware or other malware onto your computer. Be aware that some of these popup windows are programmed to interpret any mouse click anywhere on the window as an 'OK' and act accordingly. If you encounter this kind of pop-up window, disconnect from the network and force the browser to close (in Windows, hit 'ctrl + alt + del' and delete the browser from running tasks. In OSX, right-click the application in the bar and select 'force close'). You should save any files you have open and reboot the computer, then run your anti-virus software.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: rmf, fips, security control. General security reference material without sensitive content. Source: Small Business Information Security_ The Fundamentals."}]}
{"id": "nist_02220", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Electronic Mail Security say about Administering the Mail Server? (Part 3) According to Guidelines on Electronic Mail Security, Administering the Mail Server: logs daily | | Completed | Action | |-------------|------------------------------------------------------------------------------------------------------------------------------------------------------| | | Review logs weekly (for more long-term trends) | | | Use automated log file analysis tool(s) | | | Mail server backups | | | Create a mail server backup policy | | | Back up mail server differentially or incrementally on a daily to weekly basis | | | Back up mail server fully on a weekly to monthly basis | | | Periodically archive backups | | | Recovering from a compromise | | | Report incident to organization's computer incident response capability | | | Isolate compromised system(s) or take other steps to contain attack so additional evidence can be collected | | | Consult, as appropriate, with management, legal counsel, and law enforcement expeditiously | | | Investigate similar hosts to determine if the attacker has also compromised other systems | | | Analyze the intrusion | | | Restore the system | | | Test system to ensure security | | | Reconnect system to network | | | Monitor system and network for signs that the attacker is attempting to access the system or network again | | | Document lessons learned |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_02221", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6.5.8.2 Security Considerations for IPv6 Tunnel Brokers according to NIST Guidelines for the Secure Deployment of IPv6 According to Guidelines for the Secure Deployment of IPv6, 6.5.8.2 Security Considerations for IPv6 Tunnel Brokers: Security must be a consideration for all the interactions between the tunnel broker and other entities: clients, tunnel servers, and the DNS. The appropriate security depends on how each of these interfaces is implemented: - \uf03c For HTTP clients, using SSL/TLS to protect the username and password seems appropriate. HTTP is a clear text protocol. When sending confidential information, an encrypted channel should be used. Organizations should choose implementations that are inherently more secure. For example, delivering lists of tunnel parameters is safer than downloading executable scripts that run on the client. - \uf03c SNMPv1 and SNMPv2 are clear text protocols. As such, they can disclose confidential information. SNMPv3 provides encryption but lags behind SNMPv1 and SNMPv2 in support and deployment. SNMP interfaces to tunnel servers should use IPsec or SNMP over SSH if SNMPv3 is not an option. Using this option will support confidentiality and integrity of the information passed on the channel. - \uf03c For DNS updates, either Secure Dynamic Update (RFC 3007, Secure Domain Name System (DNS) Dynamic Update ) or command scripts protected by SSH or IPsec could be used. - \uf03c If a host disconnects from the Internet and its IPv4 address is reallocated, the tunnel server may not find out about this and may keep forwarding IPv6 traffic to that address. - \uf03c Tunnel broker servers maintain state for each client. As such, they are susceptible to resource exhaustion attacks and other types of DOS attacks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_02222", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-1 in Derived Personal Identity Verification (PIV) Credentials? (Part 68) Control AC-1: r successful PIV Card authentication, the kiosk transmits PIV Card information to the MyID CMS through secure transport, where a job is created to handle the second phase of issuance to the end point. Figure 5-10 Kiosk Workflow <!-- image --> The DPC issuance process requires the use of the Identity Agent mobile application or the self-service application to complete the workflow. In the case of an iOS or Android-based mobile device, the applicant launches the Identity Agent application and scans a QR code presented by the self-service kiosk. The QR code contains the information needed for the Identity Agent mobile application to communicate securely with the MyID CMS back end. After the MyID CMS has received and validated the OTP obtained from the scanned QR code, the Identity Agent creates containers and generates a key pair on the device by using a third-party FIPS 140-2-certified OpenSSL library for cryptographic services. The public key is transmitted to the Intercede MyID back end in the form of a PKCS #10 request. We configured our MyID back-end instance to run within a local Internet Information Services instance that uses a TLS end point. An implementer should consult NIST SP 800-52, Revision 1, Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations for configuration guidance in this area [27]. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ The authentication certificate request is then relayed to the Verizon Managed PKI. We used a test instance of the Verizon Managed PKI in this project; however, the production version for U.S. federal agencies has been granted an authority to operate (ATO) that requires a security controls assessment.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_02223", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automation Support for Security Control Assessments_ Software Asset Management say about 2.3 Assessment Objects Protected and Assessed by SWAM? (Part 7) According to Automation Support for Security Control Assessments_ Software Asset Management, 2.3 Assessment Objects Protected and Assessed by SWAM: bility issues. Mobile code is distinguished by the fact that rather than being loaded from the device's mass storage, it is loaded at the time of use from the larger network (typically via a website). The code is managed externally, and may change frequently, rendering the device incapable of computing a valid digital fingerprint for the mobile code, and thus requiring other means to validate the code. Requiring the mobile code to be digitally signed by a trusted source is one method employed to validate such code. Another option is to block all mobile code not from a trusted website. A key alternate method for addressing mobile code is covered in NIST SP 800-53 control SC-44 (Detonation Chamber). Because SC-44 is not selected in the NIST SP 800-53B low, moderate, or high baselines, it is not included in this NISTIR. However, detonation chambers are effective in protecting against malicious mobile code, including mobile code downloaded from a web site, as well as mobile code in e-mails and attachments. Malicious mobile code is addressed further in the NISTIR 8011 volume on the boundary management capability. Firmware is often considered to be a hybrid between hardware and software. For the purposes of this NISTIR, firmware is code stored in non-volatile memory that can be updated. The ability to update firmware allows hardware manufacturers great flexibility, reducing the need to replace hardware when issues are found or changes need to be made. Firmware that can be updated is subject to malicious code insertion, and thus needs protection under the SWAM capability. Generally, it is possible to compute a digital fingerprint for firmware. In addition, there are hardware mechanisms to validate firmware, such as the trusted platform module (TPM). Code in memory is harder to protect than other forms of software addressed in this volume. Because changes to code in memory are very hard to detect, such changes can be very stealthy.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_02224", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Card Technology Developments and Gap Analysis Interagency Report provide? (Section 142) reader from supplier A should also work with cards from supplier B, C and D. For us in the access control industry and the contactless card industry at large, there is some room to play here I guess. Interoperability can be achieved by licensing the IC technology. That is integrating the IC customer needs in the card form factor. Interoperability: Chip level - If the reliance on a single IC technology or chip operating system is acceptable, then interoperable systems are available. And that would typically be available through a licensing scheme. My impression though is that that's not acceptable. However, if a large entity were to select a single system from a single technology, then these systems are available. Interoperability: Reader level - Also available are interoperable contactless card systems that will work with different IC suppliers that are built around multiple chip technologies by incorporating these different technologies into a single reader. A good example of that is the reader currently available through Cubic Transportation Systems. They've incorporated the Go Card technology and Mifare. I believe they also have the capability to read 14443 Type A and Type B. Plus, I'm not sure, but I think 15693 may be on the way or is currently available, the ISO standard 15693. These are not common reader platforms probably because of the cost. You have to put many things inside it to make it work including the firmware to make everything work together. Interoperability: Card Operating System level - Interoperability of card ICs from different manufacturers that have a microprocessor can also be achieved through the use of a common operating system. Even to the point where it's certainly technically feasible to port the operating systems from the contact card world to a contactless card IC. The protocol obviously, the transmission protocol, has to be different.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Card Technology Developments and Gap Analysis Interagency Report."}]}
{"id": "nist_02225", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i say about 2.2.1 Ad Hoc Mode? (Part 2) According to Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i, 2.2.1 Ad Hoc Mode: ctions cheaply, quickly, and easily with minimal hardware and user maintenance. In practice, many different types of ad hoc networks are possible, and the IEEE 802.11 specification allows all of them. Since it does not give the details of how to form a network, but rather only how to establish the links in a network, ad hoc mode as specified by 802.11 is incomplete for any particular use. This means that different products built on it typically are not interoperable, because there has not yet been standardization on any of these possible networks. An ad hoc network can be created for many reasons, such as allowing the sharing of files or the rapid exchange of e-mail. However, an ad hoc WLAN cannot communicate with external networks. A further complication is that an ad hoc network can interfere with the operation of an AP-based infrastructure mode network (see next section) that exists within the same wireless space. Figure 2-2. IEEE 802.11 Infrastructure Mode <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i."}]}
{"id": "nist_02226", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Securing Property Management Systems? (Part 27) Control AM-1: , the PMS accepts a reservation, reconciles the bill, and closes out the reservation while never exposing any data to unauthorized access. Further, the reservation data is editable in a secure manner. In this PMS reference design, all reservations are manually entered directly into the PMS and not supplied by an external CRS. ## 4.2.2 Use Case 2: Authorized User Access In Use Case 2, only authorized users can connect to their authorized devices. They are not able to gain access to devices that might enable them to escalate their privileges within the PMS reference design or conduct any unauthorized lateral movements. The access control platform in the PMS reference design allows users to connect only to the systems for which they are authorized based on their role as a hotel guest, hotel staff, or system administrator. The action of inputting or modifying a reservation requires an authorized hotel staff user to authenticate to gain access to the PMS. ## 4.2.3 Use Case 3: Secure Credit Card Transaction In Use Case 3, a credit card transaction is securely conducted. The hotel guest credit card transaction is tokenized before introduction to the PMS. Credit card data is consumed only by the payment solution application (PSA) and is immediately tokenized. The PSA function to validate the guest credit card data with a third-party payment processor is not included in the PMS reference design. The validated credit card data token is sent from the PSA to the PMS. The token is used again at checkout when the bill is paid, with only the token sent from the PMS to the PSA. ## 4.2.4 Use Case 4: Secure Interaction of Ancillary Hotel System with PMS In Use Case 4, the PMS securely interacts with a physical access control system, specifically a door lock and room-key encoder. The physical access control server is a door lock/room-key system that requires connectivity to the PMS.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, token, sso. Contains security framework guidance for authentication systems. Source: Securing Property Management Systems."}]}
{"id": "nist_02227", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Criticality Analysis Process Model_ Prioritizing Systems and Components provide? (Section 74) | | Related processes outside of criticality analysis | [CSF] - (ID.AM-1, 2, 4) Asset Management [NIST SP 800-39] - (3.1) Framing Risk [NIST SP 800-160] - (3.4.3) System Requirements Definition Process [NIST SP 800-160] - (3.4.4) Architecture Definition Process [NIST SP 800-161] - (2.2.1) Frame | | Sub-process ID | C.3 | |-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Sub-process name | Identify Interactions, Intersections, Connections, and Dependencies Within the Critical Workflow Path | | Sub-process description | This sub-process identifies the interactions, intersections, connections, and dependencies between functions and between systems/subsystems.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, csf, fips. General security reference material without sensitive content. Source: Criticality Analysis Process Model_ Prioritizing Systems and Components."}]}
{"id": "nist_02228", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Notional Supply Chain Risk Management Practices for Federal Information Systems say about 4.6.1 Acquirer - Programmatic Activities? (Part 2) According to Notional Supply Chain Risk Management Practices for Federal Information Systems, 4.6.1 Acquirer - Programmatic Activities: could be mitigated through diversifying elements or the supply chain). - b. Identify cases where a customized, rather than standard configuration may be more appropriate to reduce risks of compromise. - f) Establish organizational procedures that require design processes to address protective or corrective options which either avoid mission interruption or permit graceful degradation of the system should the system be attacked or compromised. - g) Require integrators and suppliers to deliver elements and element processes with commercially reasonable security configurations and designs to limit access and exposure. - h) Establish comprehensive testing policy and procedures. - i) Require that the system's operational environment protect the system both physically and logically. Include applicable system integration and custom code extension in use as part of the upgrade and maintenance efforts in system operation requirements. - j) Develop and implement an approach for handling and processing reported supply chain anomalies. Require the separation of duties for people and organizations as well as the separation of functions for supply chain elements and element processes. - k) Require redundancy and diversity throughout the supply chain and document the benefits, risks, costs, and contingency plans to respond to supply chain risks resulting in decisions to reduce diversity and redundancy or alternatives in availability of supply chain elements or element processes. - l) Use threat assessment techniques and information to determine if the proposed design alternatives meet defensive design criteria. - m) Use threat analysis techniques (such as threat modeling) to examine the element's design vulnerabilities. - n) Model, simulate, test, and evaluate the supply chain risks prior to decisions to limit the diversity of system/elements or suppliers. - o) Avoid use of secondary market elements unless no other sources exist.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Notional Supply Chain Risk Management Practices for Federal Information Systems."}]}
{"id": "nist_02229", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to SIMfill Use and Development provide? (Section 44) ion='1.0' encoding='UTF-8'?> <mf> <df_telecom> <ef_raw></ef_raw> <ef_adn></ef_adn> </df_telecom> </mf> ``` EF\\_ADN {10.5.1} is used to specify the abbreviated dialing number (i.e., the phone book). It takes two different subnodes, which can be mixed and repeated arbitrarily: - GLYPH&lt;c=31,font=/GHDCGG+Webdings&gt; \"contact\": A contact contains a set of information, as described below. - GLYPH&lt;c=31,font=/GHDCGG+Webdings&gt; \"empty\": Used to insert an empty record in the file. The subnode \"contact\" has three or four subnodes: - GLYPH&lt;c=31,font=/GHDCGG+Webdings&gt; \"description\": The name of the contact. It is a string that can be encoded either in the default GSM 7-bit alphabet or in UCS2. To specify which encoding to use, one can set the XML attribute \"enc\" to \"default\" for 7-bit encoding or \"ucs2\" for UCS2 encoding. If no encoding is explicitly specified, the 7-bit encoding is used by default. - GLYPH&lt;c=31,font=/GHDCGG+Webdings&gt; \"address\": Contains the phone number information of the contact, as described below. - GLYPH&lt;c=31,font=/GHDCGG+Webdings&gt; \"capability\": Index pointing to a record of EF\\_CCP. It take a decimal number between 0 and 255. This subnode is optional. - GLYPH&lt;c=31,font=/GHDCGG+Webdings&gt; \"extension\": The index of additional data that are stored in EF\\_EXT1 (see the example below). It takes a decimal number between 0 and 255. This subnode is optional. The subnode \"address\" takes three subnodes: - GLYPH&lt;c=31,font=/GHDCGG+Webdings&gt; \"ton\": The Type of Number. The possible values are listed below. - GLYPH&lt;c=31,font=/GHDCGG+Webdings&gt; \"npi\": Numbering Plan Identifier. The possible values are listed below. - GLYPH&lt;c=31,font=/GHDCGG+Webdings&gt; \"number\": The phone number of the contact. It takes a 0- to 20-digit decimal number.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to SIMfill Use and Development."}]}
{"id": "nist_02230", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PL-2 in Assessing Security and Privacy Controls in Information Systems and Organizations? (Part 10) Control PL-2: ganization and can be accepted. Conversely, system owners or common control providers may decide that certain findings marked as \u201cother than satisfied\u201d are significant and require remediation actions. In all cases, the organization reviews each assessment finding of \u201cother than satisfied\u201d and applies its judgment with regard to the severity of the finding and whether it is significant enough to warrant further investigation or remedial action.47 Senior leadership involvement in the mitigation process may be necessary to ensure that the organization\u2019s resources are effectively allocated in accordance with organizational priorities, provide resources first to the systems that support the most critical and sensitive missions for the organization, or correct the deficiencies that pose the greatest degree of risk. Ultimately, the assessment findings and any subsequent response actions (informed by the updated risk assessment) trigger updates to the key artifacts used by authorizing officials to determine the security and privacy risks of the system and its suitability for authorization to operate. The artifacts include security plans and privacy plans, security assessment reports and privacy assessment reports, and the respective plans of action and milestones. 47 Potential risk response actions include risk acceptance, risk mitigation, risk rejection, and risk transfer/sharing. [SP 800-39] provides guidance on risk response actions from a risk management perspective. CHAPTER THREE PAGE 33 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 A r 5 . I NIST SP 800-53A REV.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_02231", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about Test? According to Assessing Security Requirements for Controlled Unclassified Information, Test: [SELECT FROM: processes for intrusion detection and system monitoring; mechanisms for supporting or implementing system monitoring capabilities; mechanisms for supporting or implementing intrusion detection and system monitoring capabilities; mechanisms for supporting or implementing the monitoring of inbound and outbound communications traffic]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02232", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings? (Part 73) Control PD-12: ice: 1. The Workstation's login program uses the system's PAM library to request authentication of the user. 2. The system's PAM library passes on the authentication request to a pam\\_krb5 module. 3. The pam\\_krb5 module has been configured to attempt to authenticate the user via the pkinit extension to the krb5 authentication protocol which allows the user to prove his identity using x509 credentials rather than the traditional Kerberos shared secret(password). 4. The system's krb5.conf specifies the use of an openssl engine module called myproxy\\_engine to acquire the x509 credentials. 5. The myproxy\\_engine module prompts the user for his password using a prompter function which has been passed by reference all the way down the call stack from the original PAM aware application(in this case login.) 6. The myproxy\\_engine module generates a public/private keypair, and a certificate request. 7. The certificate request is then sent to the myproxy server along with the users username, and password as part of a myproxy protocol get request. The myproxy protocol uses the SSL/TLS protocol both to verify the authenticity of the myproxy server,(you don't want to send a valid password to the wrong server) and to ensure the privacy of the exchange. 8. Upon receiving the get command, the myproxy server uses the pam libraries on it's system to attempt to authenticate the user. 9. The pam libraries on the myproxy system pass the authentication request on to a pam\\_radius module which uses the RADIUS protocol to a locally trusted RADIUS server. This RADIUS server may verify the validity of the password locally, or forward the request on to a federated system such as Eduroam. 10. If the RADIUS server confirms the validity of the user's password, the myproxy server then creates a short lived certificate for that user, and signs it using locally accessible CA credentials(possible stored on a smart card or similar crypto system.) 11.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings."}]}
{"id": "nist_02233", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 900) entity creates or possesses for or on behalf of the Government, that a law, regulation, or Government-wide policy requires or permits an agency to handle using safeguarding or dissemination controls. However, CUI does not include classified information or information a non-executive branch entity possesses and maintains in its own systems that did not come from, or was not created or possessed by or for, an executive branch agency or an entity acting for an agency. An unauthorized copy or substitute that has been identified, marked, and/or altered by a source other than the item's legally authorized source and has been misrepresented to be an authorized item of the legally authorized source. Actions, devices, procedures, techniques, or other measures that reduce the vulnerability of a system. Synonymous with security controls and safeguards. An unintended or unauthorized intra-system channel that enables two cooperating entities to transfer information in a way that violates the system's security policy but does not exceed the entities' access authorizations. covert channel analysis [CNSSI 4009] Determination of the extent to which the security policy model and subsequent lower-level program descriptions may allow unauthorized access to information. covert storage channel [CNSSI 4009] covert timing channel [CNSSI 4009, Adapted] credential [SP 800-63-3] critical infrastructure [USA PATRIOT] A system feature that enables one system entity to signal information to another entity by directly or indirectly writing to a storage location that is later directly or indirectly read by the second entity. A system feature that enables one system entity to signal information to another by modulating its own use of a system resource in such a way as to affect system response time observed by the second entity.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, cui. Contains guidance on protecting sensitive government information. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02234", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Intrusion Detection and Prevention Systems (IDPS)? (Part 94) Control ES-1: es (device detection, service enumeration, limited vulnerability scanning). It also does not address technologies based on the IEEE 802.11n WLAN standard, which as of late 2006 has not been finalized. It is expected that the recommendations in this section should generally be applicable to wireless IDPS technologies for IEEE 802.11n-based WLANs. 26 For more information on the IEEE 802.11 standards and other aspects of wireless network security, see NIST SP 800-97, Establishing Wireless Robust Security Networks: A Guide to IEEE 802.11i, and NIST SP 800-48, Wireless Network Security: 802.11, Bluetooth and Handheld Devices (http://csrc.nist.gov/publications/nistpubs/index.html). 27 For more information on the Wi-Fi Alliance, visit their Web site at with the ratification of the IEEE 802.11i amendment, the Wi-Fi Alliance introduced WPA2, its term for interoperable equipment that is capable of supporting IEEE 802.11i requirements. WPA2 offers stronger security controls than either WPA or WEP. ## 5.1.2 WLAN Components IEEE 802.11 WLANs have two fundamental architectural components: - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Station (STA). A STA is a wireless endpoint device. Typical examples of STAs are laptop computers, personal digital assistants (PDA), mobile phones, and other consumer electronic devices with IEEE 802.11 capabilities. - GLYPH&lt;c=31,font=/HHCKCL+Webdings&gt; Access Point (AP). 28 An AP logically connects STAs with a distribution system (DS), which is typically an organization's wired infrastructure. The DS is the means by which STAs can communicate with the organization's wired LANs and external networks such as the Internet. Figure 5-1 shows an example of how APs, STAs, and DSs are related. Figure 5-1. Wireless LAN Architecture Example <!-- image --> Some WLANs also use wireless switches. A wireless switch is a device that acts as an intermediary between APs and the DS.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Guide to Intrusion Detection and Prevention Systems (IDPS)."}]}
{"id": "nist_02235", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE) say about Glossary? (Part 2) According to Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE), Glossary: an install applications onto the device. | | Demilitarized Zone (DMZ) | An interface on a routing firewall that is similar to the interfaces found on the firewall's protected side. Traffic moving between the DMZ and other interfaces on the protected side of the firewall still goes through the firewall and can have firewall protection policies applied [6]. | | Derived Personal Identity Verification (PIV) | A credential issued based on proof of possession and control of the PIV Card, so as not to duplicate the identity proofing process as defined in [SP 800-63-2]. A Derived PIV Credential token is a hardware or software-based token that contains the Derived PIV Credential [7]. | | Hypertext Transfer Protocol (HTTP) | A standard method for communication between clients and Web servers [8]. | | Hypertext Transfer Protocol Secure (HTTPS) | HTTP transmitted over TLS [9]. | | Internet Protocol (IP) addresses | Standard protocol for transmission of data from source to destinations in packet-switched communications networks and interconnected systems of such networks [10]. | |----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Lightweight Directory Access Protocol (LDAP) | The Lightweight Directory Access Protocol, or LDAP, is a directory access protocol. In this document, LDAP refers to the protocol defined by RFC 1777, which is also known as LDAP V2. LDAP V2 describes unauthenticated retrieval mechanisms [11].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_02236", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations say about REFERENCES? According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, REFERENCES: Source Control: CM-03 Supporting Publications: SP 800-124 [28], SP 800-128 [41] NIST SP 800-171r3 May 2024", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_02237", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain List of Figures according to NIST IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements According to IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements, List of Figures: | Figure 1: Visualization of the System and Environment ..................................................4 | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Figure 2: Information Security Requirements Integration to the Element Level...............7 | | Figure 3: Role of Device Cybersecurity and Non-Technical Supporting Capabilities in Satisfying Security Capabilities and Requirements..................................................9 | | Figure 4: Organizations Can Use this Section to Identify IoT Device Cybersecurity Requirements.........................................................................................................12 | | Figure 5: Steps to Updating a Risk Model and Risk Assessment using New Information about an IoT Device. ..............................................................................................19 | | Figure 6: Effects on Risk Assessment due to IoT Device Informs the Risk Assessment of the Entire System...............................................................................................22 | | Figure 7: Organizations Can Gather Information to Update the System Risk Assessment and Determine Device Cybersecurity Requirements..............................................23 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements."}]}
{"id": "nist_02238", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Audience according to NIST Integrating Cybersecurity and Enterprise Risk Management (ERM) According to Integrating Cybersecurity and Enterprise Risk Management (ERM), Audience: The primary audience for this publication includes both federal government and non-federal government cybersecurity professionals at all levels who understand cybersecurity but may be unfamiliar with the details of enterprise risk management (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 details of cybersecurity. All readers are expected to gain an improved understanding of how cybersecurity risk management (CSRM) and ERM complement and relate to each other as well as the benefits of integrating their use.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Integrating Cybersecurity and Enterprise Risk Management (ERM)."}]}
{"id": "nist_02239", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services provide? (Section 11) ......................53 | | | 4.3.2. | Security Continuous Monitoring Category.............................................................56 | | | 4.3.3. | Detection Processes Category..............................................................................61 | | | | Respond Function | .....................................................................................................63 | | 4.4.1. | Response Planning Category ...............................................................................64 | | | 4.4.2. | Communications Category....................................................................................65 | | | 4.4.3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_02240", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain CONTACTS: according to NIST 2016 NIST_ITL Cybersecurity Program Annual Report According to 2016 NIST_ITL Cybersecurity Program Annual Report, CONTACTS:: Mr. Jim Foti Mr. Patrick O'Reilly (301) 975-8018 (301) 975-4751 james.foti@nist.gov patrick.oreilly@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02241", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Attribute Metadata_ A Proposed Schema for Evaluating Federated Attributes say about Authorization? According to Attribute Metadata_ A Proposed Schema for Evaluating Federated Attributes, Authorization: The decision to permit or deny a subject access to resources (e.g., network, data, application, services) based on the evaluation of access control policies.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Attribute Metadata_ A Proposed Schema for Evaluating Federated Attributes."}]}
{"id": "nist_02242", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 2016 NIST_ITL Cybersecurity Program Annual Report provide? (Section 149) eir cryptographic algorithm implementations. The suite of validation tests for each algorithm ensures the repeatability of tests and the equivalency of results across the testing laboratories. There are several types of validation tests, all designed to satisfy the testing requirements of the cryptographic algorithms and their specifications. These include, but are not limited to, Known-Answer Tests, Monte Carlo Tests, and Multi-Block Message Tests. The Known-Answer Tests are designed to examine the individual components of the algorithm by supplying known values to the variables and verifying the expected result. Negative testing is also performed by supplying known incorrect values to assure that the implementation recognizes values that are not allowed. The Monte Carlo Test is designed to exercise the entire implementation-under-test (IUT). This test is designed to detect the presence of implementation flaws that are not detected with the controlled input of the Known-Answer Tests. The types of implementation flaws detected by this validation test include pointer problems, insufficient allocation of space, improper error handling, and incorrect behavior of the IUT. The Multi-Block Message Test (MMT) is designed to test the ability of the implementation to process multi-block messages, which requires the chaining of information from one block to the next. During the last few years, the CSD Cryptographic Technology Group (CTG) has expanded its publications to contain not only the algorithm's specifications, but also requirements for an algorithm's use. Many of these usage requirements do not fall within the scope of the CAVP, because the CAVP focuses on the correctness of the instructions within the algorithm's boundary.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02243", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Specification for Asset Reporting Format 1.1 say about 2.2 Acronyms? (Part 2) According to Specification for Asset Reporting Format 1.1, 2.2 Acronyms: | ARF | Asset Reporting Format | |--------|-----------------------------------------------------| | DISA | Defense Information Systems Agency | | DoD | Department of Defense | | FISMA | Federal Information Security Management Act | | FTP | File Transport Protocol | | HIPAA | Health Insurance Portability and Accountability Act | | HTTP | Hypertext Transport Protocol | | IETF | Internet Engineering Task Force | | IR | Interagency Report | | IT | Information Technology | | ITL | Information Technology Laboratory | | NIST | National Institute of Standards and Technology | | NSA | National Security Agency | | OCIL | Open Checklist Interactive Language | | OVAL | Open Vulnerability and Assessment Language | | PCI | Payment Card Industry | | RFC | Request for Comment | | SCAP | Security Content Automation Protocol | | SCG | Security Configuration Guide | | SOX | Sarbanes-Oxley | | STIG | Security Technical Implementation Guide | | TCP/IP | Transmission Control Protocol/Internet Protocol | | URI | Universal Resource Identifier | | URL | Universal Resource Locator | |-------|-------------------------------------------------------| | W3C | World Wide Web Consortium | | XCCDF | eXtensible Configuration Checklist Description Format | |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: national security, defense information. Contains guidance on protecting sensitive government information. Source: Specification for Asset Reporting Format 1.1."}]}
{"id": "nist_02244", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Internet of Things (IoT) Cybersecurity Colloquium_ A NIST Workshop Proceedings provide? (Section 15) d - A full-lifecycle approach to identity is needed to govern access to things on the Internet. Most IoT devices are controlled by traditional identity solutions - most commonly username and password. Because bad actors frequently leverage weak identity management practices to access devices, it is necessary to take a full-lifecycle approach to identity management in the IoT - that is, considering cybersecurity and privacy in every stage of the device lifecycle, from design to deployment to retirement. Furthermore, these devices often come hard-coded with default passwords that cannot be changed. Analysis of recent attacks reveals that the scale of distributed denial-of-service (DDoS) attacks has rapidly increased in recent years. IoT devices are frequently leveraged in these attacks. According to the speakers, there are two types of DDoS attacks: one is a large volume of attacks against the service itself, and the other is a reflection attack where traffic is sent towards a targeted service. This rise is driven, in part, by profitability: this takes the form of bad actors using devices for attacks on individuals' banking information, as well as people who hire bad actors for espionage and to cause chaos, often making payments with bitcoin and stolen credit cards. There were also discussions on the role of patching. While patching is important for ongoing device cybersecurity, it is not sufficient. There are too many exploits for patching alone to work, and there is concern about running out of time and money before bad actors do, given how quickly IoT changes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Internet of Things (IoT) Cybersecurity Colloquium_ A NIST Workshop Proceedings."}]}
{"id": "nist_02245", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cloud Computing Synopsis and Recommendations provide? (Section 159) ric Jul, Christian Limpach, Ian Pratt, Andrew Warfield, \"Live Migration of Virtual Machines,\" Proceedings of the 2nd Symposium on Networked Systems Design and Implementation, May 2-4, 2005, Boston MA. | | [Cho06] | Frederick Chong and Gianpaolo Carraro, \"Architecture Strategies for Catching the Long Tail,\" Microsoft Corporation, April 2006. http://msdn.microsoft.com/en- us/library/aa479069.aspx. | | [Com88] | Douglas Comer, \"Internetworking with TCP/IP Principles, Protocols, and Architectures,\" Prentice-Hall, Inc., 1988, ISBN 0-13-470154-2. | | [Dea04] | Jeffrey Dean and Sanjay Ghemawat, \"MapReduce: Simplified Data Processing on Large Clusters,\" Proceedings of the 6'th USENIX Symposium on Operating Systems Design and Implementation, Dec. 6-8, 2004, San Francisco, CA. | | [Die08] | T. Dierks and E. Rescorla, \"The Transport Layer Security (TLS) Protocol Version 1.2,' 2008, IETF RFC 5246, | - [Dja11] Django Software Foundation, \"django The Web framework for perfectionists with deadlines,\" 2011, http://www.djangoproject.com. - [DMT09] Distributed Management Task Force, \"Open Virtualization Format Specification, Version 1.0.0\", 2009, online: - [Eps99] Jeremy Epstein, \"Architecture and Concepts of the ARGuE Guard,\" Proceedings of the 1999 Annual Computer Security Applications Conference, Dec. 6-10, 1999, Phoenix, Arizona. - [Fed10] CIO Council, \"Proposed Security Assessment and Authorization for U.S. Government Cloud Computing, Draft version 0.96, Nov. 2010. Online: www.FedRAMP.gov. - [Fer92] David F. Ferraiolo and D.R. Kuhn, \"Role Based Access Control,\" Proceedings of the 15th National Computer Security Conference, Oct 13-16, 1992, pp. 554-563. - [Gar05] Jesse James Garrett, \"Ajax: A New Approach to Web Applications,\" 2005, ", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Cloud Computing Synopsis and Recommendations."}]}
{"id": "nist_02246", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD) provide? (Section 141) ts devices from accessing external domains and IP addresses that are associated with known current cybersecurity threats. Figure 7-2 depicts a detailed view of Build 2\u2019s threat-signaling architecture. As shown, GCA\u2019s Quad9 threat agent and Quad9 MUD manager (which are both part of Q9Thrt) are integrated into the Yikes! router to support threat signaling. Additionally, the Yikes! router requires the use of several external components to support threat signaling: Quad9 DNS service, which receives threat information feeds from a variety of threat intelligence services; Quad9 threat API, which confirms a threat as well as NIST SP 1800-15B: Securing Small-Business and Home Internet of Things Devices 87 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 information regarding how to find the threat MUD file for that threat; and the ThreatSTOP threat MUD file server, which provides the threat MUD file for the threat. Figure 7-2 Threat-Signaling Logical Architecture\u2013Build 2 The messages that are exchanged among architectural components to support threat signaling are depicted by arrows and numbered in sequence in Figure 7-2. The result of this message flow is to protect a local device from connecting to a domain that has been identified as unsafe by a threat intelligence service from which Quad9 DNS service receives information which, in this case, is ThreatSTOP. As depicted in Figure 7-2, the steps are as follows: \uf0a7 A local device (which may or may not be an IoT device and may or may not be MUD-capable) sends a DNS resolution request to its local DNS service, which is hosted on the Yikes! router (step 1). \uf0a7 If the local DNS service cannot resolve the request itself, it will forward the request to the Quad9 DNS service (step 2). \uf0a7 The Quad9 DNS service will return a DNS response to the Yikes! router\u2019s local DNS service.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_02247", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Platform Firmware Resiliency Guidelines say about 2. Trusted Platform Module (TPM)? According to Platform Firmware Resiliency Guidelines, 2. Trusted Platform Module (TPM): A TPM [4] is a security coprocessor capable of securely storing and using cryptographic keys and measurements of the state of the platform. These capabilities can be used, among other things, to secure data stored on the system, provide a strong device identity, and to attest the state of the system. While not all platforms include or make use of a TPM, on any system in which a TPM is included and used, its firmware must be protected given its criticality in helping ensure the trustworthiness of the platform. TPMs also contain non-volatile memory storage which may contain critical data and, if so, must be protected. TPM's can be either discrete hardware devices, or may be realized in", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Platform Firmware Resiliency Guidelines."}]}
{"id": "nist_02248", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AA-05 in Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems? (Part 7) Control AA-05: ----------|--------------------| | 1 | CVE- 2019- 19229 | admincgi-bin/service.fcgi on Fronius Solar Inverter devices before 3.14.1 (HM 1.12.1) allows action=download&filename= Directory Traversal. | 4-Dec-19 | V3.1: 6.5 MEDIUM | | 2 | CVE- 2019- 19228 | Fronius Solar Inverter devices before 3.14.1 (HM 1.12.1) allow attackers to bypass authentication because the password for the today account is stored in the /tmp/web_users.conf file. | 4-Dec-19 | V3.1: 9.8 CRITICAL | | 3 | CVE- 2018- 12927 | Northern Electric & Power (NEP) inverter devices allow remote attackers to obtain potentially sensitive information via a direct request for the nep/status/index/1 URI. | 28-Jun-18 | V3.0: 7.5 HIGH | | 4 | CVE- 2018- 12735 | SAJ Solar Inverter allows remote attackers to obtain potentially sensitive information via a direct request for the inverter_info.htm or english_main.htm URI. | 25-Jun-18 | V3.0: 7.5 HIGH | | 5 | CVE- 2017- 9863 | ** DISPUTED ** An issue was discovered in SMA Solar Technology products. If a user simultaneously has Sunny Explorer running and visits a malicious host, cross-site request forgery can be used to change settings in the inverters (for example, issuing a POST request to change the user password). All Sunny Explorer settings available to the authenticated user are also available to the attacker. (In some cases, this also includes changing settings that the user has no access to.) This may result in complete compromise of the device. NOTE: The vendor reports that exploitation is unlikely because Sunny Explorer is used only rarely. Also, only Sunny Boy TLST-21 and TL-21 and Sunny Tripower TL-10 and TL-30 could potentially be affected.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, cve-. Contains technical security guidance that could inform defensive posture. Source: Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems."}]}
{"id": "nist_02249", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines on PDA Forensics provide? (Section 6) ....................................................... | 3 | | 2. | BACKGROUND.................................................................................................................... 4 | BACKGROUND.................................................................................................................... 4 | | 2.1 | DEVICE CHARACTERISTICS .............................................................................................. | 4 | | 2.2 | PALM OS........................................................................................................................... | 6 | | 2.3 | POCKET PC.......................................................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on PDA Forensics."}]}
{"id": "nist_02250", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain (1) Active Association according to NIST A Formal Description of the SDNS Security Protocol at Layer 4 (SP4) According to A Formal Description of the SDNS Security Protocol at Layer 4 (SP4), (1) Active Association: - (a) active association identifier -the name of this active association instance. - (b) local address designator -the local address of an association pair. - (c) peer address designator -the peer address of an association pair. - (d) initiated by - determines which end-system sets the direction indicator as the initiator (local or peer). - (e) status -the status of the association (partially complete, usable, etc.). - (f) local credentials -the credentials used to establish this association. - (g) peer credentials -the peer entities' credentials used to establish this association. - (h) local key identifier -the identifier of the traffic key used for this association. - (i) peer key identifier -the peer entities identifier for the traffic key used for this association.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Formal Description of the SDNS Security Protocol at Layer 4 (SP4)."}]}
{"id": "nist_02251", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain D.2.2. Binary Curves in Short-Weierstrass Form according to NIST Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters According to Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters, D.2.2. Binary Curves in Short-Weierstrass Form: Point compression for binary curves in short-Weierstrass form is defined as follows:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters."}]}
{"id": "nist_02252", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines provide? (Section 52) The integrity of the code in the repository can be trusted such that it can be used for further updates. | | | 5.1.3 Integrity of Evidence Generation During Software Updates (To provide assurance to acquirers that the software they get is legitimate, steps are taken to protect the integrity of evidence generation tasks) | 1. The framework should provide protection against all known attacks on the tasks performed by the software update systems, such as metadata (hash) generation, the signing process, the management of signing keys, the integrity of the authority performing the signing, key validation, and signature verification. 2. The framework should provide a means to minimize the impact of key compromise by supporting roles with multiple keys and threshold or quorum trust (with the exception of minimally trusted roles designed to use a single key). The compromise of roles that use highly- vulnerable keys should have minimal impact. Therefore, online keys (i.e., keys used in an automated fashion) must not be used for any role that clients ultimately trust for files they may install [11]. When keys are online, exceptional care should be taken in caring for them, such as storing them in an HSM and only allowing their use if the artifacts being signed pass the policy defined in Sec. 5.1.1. 3. The framework must be flexible enough to meet the needs of a wide variety of software update systems. 4. The framework must be easy to integrate | Provide a Mechanism for Verifying Software Release Integrity (PS.2): Help software acquirers ensure that the software they acquire is legitimate and has not been tampered with.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines."}]}
{"id": "nist_02253", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Card Technology Developments and Gap Analysis Interagency Report provide? (Section 55) ents. If so, please state what the technologies are, and why they were rejected. - b. Did you encounter integration and/or interoperability issues? 3. Have you performed a Business Case Analysis? - a. If yes, is it open to the public and available on your web site? Please list resource. - b. What are the main cost drivers for your card application? 4. What are the current Card Technology Requirements? - a. Please describe the text that's required to be displayed on your cards. Include such details as how many characters are required, font requirements, maximum lengths, character size requirements, etc. - b. If you use different color backgrounds or borders for different employee/contractor designations, please list these requirements. - c. If a photograph is required to be displayed on your card, please discuss your minimum/maximum size, color, and resolution requirements? - d. Are there requirements to print on the front and/or back of your cards? If so, please state the requirements. - e. If there is a requirement for other biometric imagery to appear on the card, please describe the minimum/maximum size and resolution requirements. - f. For any requirements of storing digital biometric data on the card, please discuss your minimum data capacity and storage format requirements. - g. If a barcode is included on your card for identity/transaction cards, what are your quantitative and format requirements? - h. If holographic images are displayed on your cards, what are the size and format requirements? - i. For requirements dealing with general storage of digital data on the cards, what are your minimum data capacity, minimum storage and retrieval access time, and data storage format requirements? - j. What are your data format and form factor requirements for an installed base of or other basis for preference for magnetic storage (e.g., magnetic stripe)? - k.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Card Technology Developments and Gap Analysis Interagency Report."}]}
{"id": "nist_02254", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for the Secure Deployment of IPv6 provide? (Section 23) | Unknown Aspects .................................................................................... | 4-26 | | 4.5 | Jumbograms ........................................................................................................4-27 | Jumbograms ........................................................................................................4-27 | | | | 4.5.1 | Specification Overview............................................................................. | 4-27 | | | 4.5.2 | Security Ramifications..............................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_02255", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Section 80) ement in the successful execution of the RMF. The requirements are defined early in the SDLC in collaboration with the senior leaders and are integrated into the acquisition and procurement processes. For example, organizations can use the [SP 800-160 v1] life cycle-based systems engineering process to define an initial set of security and privacy requirements, which in turn, can be used to select a set of controls* to satisfy the requirements. The requirements or the controls can be stated in the Request for Proposal or other contractual agreement when organizations acquire systems, system components, or services. Requirements can also be added throughout the life cycle, such as with the agile development methodology where new features are continuously deployed. The NIST Cybersecurity Framework [NIST CSF] (i.e., Core, Profiles) can also be used to identify, align, and deconflict security requirements and to subsequently inform the selection of security controls for an organization. Cybersecurity Framework Profiles can provide a link between cybersecurity activities and organizational mission/business objectives, which supports riskbased decision-making throughout the RMF. While Profiles may be used as a starting point to inform control selection and tailoring activities, further evaluation is needed to ensure the appropriate controls are selected. Some organizations may choose to use the Cybersecurity Framework in concert with the NIST Systems Security Engineering publications-identifying, aligning, and deconflicting requirements across a sector, an industry, or an organization-and subsequently employing a systems engineering approach to further refine the requirements and obtain trustworthy secure solutions to help protect the organization's operations, assets, individuals. * See Section 2.3 for specific guidance on privacy control selection and managing privacy risk.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, csf, risk management framework. General security reference material without sensitive content. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_02256", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security of SQL-Based Implementations of Product Data Exchange Using STEP say about 4.2 Mandatory Access Control Policy for Confidentiality? According to Security of SQL-Based Implementations of Product Data Exchange Using STEP, 4.2 Mandatory Access Control Policy for Confidentiality: The majority of mandatory access control (MAC) models specify a security policy for the enforcement of a level and category-based mandatory security policy. In such a policy, each object has two security attributes: a security level (such as SECRET or SENSITIVE) and an optional set of categories. Categories specify 'need-to-know' areas, with the level specifying minimum clearance requirements. These security attributes are often called the label. The primary concerns in such a policy are enforcing access rights and maintaining appropriate labels as new objects are created. The policy is often described as 'read down, write up'. A user may read an object with a lower level; an object will be written with the highest level of any objects involved. For example, a user with SECRET clearance can read SENSITIVE objects. If that user uses a SECRET object and a SENSITIVE object as input, the output of the process will be labeled as SECRET. SQL can be used when a MAC policy is required, but not every SQL processor is suited to the task. SQL has no built in feature for handling labels, however nothing in the standard prevents an implementation from using and main- ^SQL does not require audit trail generation. This must be added as a value-added enhancement to the SQL processor. taining this information. First, an appropriate MAC implementation of SQL for the target OS is required. If the target OS is a MAC system, the Trusted Computing Base (TCB) subset architecture and Trusted Subject architecture can be used. If the target OS is not a MAC system, the integrity lock architecture is requiredfi. Add-on tools for detection and elimination of inference and aggregation are required. Authentication and auditing requirements are identical to those for role-based systems.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, sso. Contains security framework guidance for authentication systems. Source: Security of SQL-Based Implementations of Product Data Exchange Using STEP."}]}
{"id": "nist_02257", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Considerations for Voice Over IP Systems provide? (Section 47) e supported scenarios for this profile are endpoint to gatekeeper, gatekeeper to gatekeeper, and endpoint to endpoint. For the profile the gatekeeper-routed signaling (hop-by-hop security) is favored. Using it for the direct call model is generally possible but limited due to the fact that a shared secret has to be established between the parties that want to communicate before the actual communication takes place. This might be possible in smaller environments but may lead to a huge administrative effort in larger environments. This profile supports secure fast connect and H.245 tunneling, and may be combined with the Voice Encryption Option described in section 4.2.1.3. Note: that this profile is easy to implement but it is not really scalable for 'global' IP telephony due to the restricted key management.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_02258", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE) say about Appendix I Example Security Control Map? (Part 17) According to Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE), Appendix I Example Security Control Map: | PR.DS-2-Data in transit is protected | System and Communications Protection SC-8, SC-11, SC-12 | A.8.2.3 Handling of Assets A.13.1.1 Network Controls A.13.2.1 Information Transfer Policies and Procedures A.13.2.3 Electronic Messaging A.14.1.2 Securing Application Services on Public Networks A.14.1.3 Protecting Application Services Transactions | CSC 13 Data Protection CSC 14 Controlled Access Based on the Need to Know | OV-SPP-002 Cyber Policy and Strategy Planner OV-MGT-002 Communications Security (COMSEC) Manager OV-LGA-002 Privacy Officer/Privacy Compliance Manager OM-NET-001 Network Operations Specialist | | Specific product used | How the component functions in the build | Applicable Cybersecurity Framework Version 1.1 Subcategories | Applicable NIST SP 800-53 Revision 4 Controls | ISO/IEC 27001:2013 | CIS 6 | NIST SP 800-181 NICE Framework Work Roles | |-------------------------|--------------------------------------------|----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | | PR.PT-4- Communications and control networks are protected | Access Control AC- 4, AC-17, AC-18 Contingency Planning CP-8 System and Communications Protection SC-7, SC-19, SC-20, SC- 21, SC-22, SC-23, SC-24, SC-25, SC- 29, SC-32, SC-36, SC-37, SC-38, SC- 39, SC-40, SC-41, SC-43 | A.13.1.1 Network Controls A.13.2.1 Information Transfer Policies and Procedures A.14.1.3 Protecting Application Services Transactions | CSC 8 Malware Defenses CSC 12 Boundary Defense CSC 15 Wireless Access Control | PR-INF-001 Cyber Defense", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_02259", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Appendix B-Frequently Asked Questions (FAQ) according to NIST Guide to Protecting the Confidentiality of Personally Identifiable Information (PII) According to Guide to Protecting the Confidentiality of Personally Identifiable Information (PII), Appendix B-Frequently Asked Questions (FAQ): Privacy and security leadership and staff, as well as others, may have questions about identifying, handling, and protecting the confidentiality of personally identifiable information (PII). This appendix contains frequently asked questions (FAQ) related to PII. Organizations are encouraged to customize this FAQ and make it available to their user community.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)."}]}
{"id": "nist_02260", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NICE Framework Competency Areas_ Preparing a Job-Ready Cybersecurity Workforce provide? (Section 11) appreciates and acknowledges the contributions of those who established previous editions of cybersecurity workforce frameworks as described at the history page of the NICE Framework Resource Center. NICE released the Workforce Framework for Cybersecurity (NICE Framework) , NIST Special Publication 800-181, Revision 1, in November 2020 [1]. The revised NICE Framework established a set of building blocks-Task, Knowledge, and Skill statements-that describe cybersecurity work and what someone must know or be able to do to complete that work. It also identifies common ways these building blocks can be applied, most notably through Work Roles and, new in the NICE Framework revision 1, Competency Areas. 1 NICE Framework Competency Areas group together related Task, Knowledge, and Skill (TKS) statements to form a higher-level description of capabilities typically needed in a particular cybersecurity domain. By clearly defining what a person needs to know and do to perform well in a defined area of cybersecurity work, Competency Areas provide a means to communicate the needs of employers, the capabilities of learners (which, for the purposes of the NICE Framework includes students, job seekers, and employees), and the value of education, training, and certifications. Learners: Individuals who perform cybersecurity work, including students, job seekers, and employees. Competency Areas are defined via an employer-driven approach that enables education and training providers to be responsive to employer or sector needs by creating experiences that help learners develop and demonstrate relevant and needed capabilities. They correlate with performance on the job and can be improved through education, training (including on-the-job and apprenticeships), or other learning experiences.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: NICE Framework Competency Areas_ Preparing a Job-Ready Cybersecurity Workforce."}]}
{"id": "nist_02261", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments say about Appendix A Security Configuration Settings? (Part 51) According to Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments, Appendix A Security Configuration Settings: | | CCE- 8450 3-2 | NIST800 53-VI- NET- CFG- 00253 | Built-in | NSX | From the vSphere Web Client, go to Administration >> Single Sign-On >> Policies >> Password Policy . | Universal Distrib- uted Logical Router Password (Depend- ent on Customer Configurations) | | CCE ID | Configur ation(s) | Built-In/ Enhanced | Prod- uct | Audit Procedure | Recommended Parameter Value | |---------------|--------------------------------|----------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | CCE- 8450 4-0 | NIST800 53-VI- NET- CFG- 00281 | Built-in | NSX | Log on to NSX Manager Virtual Appliance, then go to Backup &Restore . If 'Audit Logs' or 'System Events' are excluded (by default they are NOT excluded), this is a finding. | Audit Logs and Sys- tem Events are not excluded | | CCE- 8450 5-7 | NIST800 53-VI- NET- CFG- 00282 | Built-in | NSX | Log on to NSX Manager Virtual Appliance, then go to Manage Appliance Settings and look under General Network Settings . If IPv6 is configured, this is a finding.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: password policy, single sign-on. Contains security framework guidance for authentication systems. Source: Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments."}]}
{"id": "nist_02262", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices say about Confidentiality? According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Confidentiality: The confidentiality impact level is the effect of unauthorized disclosure of contingency planning information on the ability of responsible agencies to plan for, respond to, and mitigate damaging events. Unauthorized disclosure of contingency planning information may equip an adversary with the information necessary to attack a system so that recovery is impaired. Special Factors Affecting Confidentiality Impact Determination: Unauthorized disclosure of background information that supports development of Federal contingency plans can reveal sensitive vulnerabilities, capabilities, intelligence assessments, intelligence sources, or methods employed in anti-terrorism, law enforcement, or national security activities. Depending on the information in question, the confidentiality impact can be moderate , high , or involve national security information (outside the scope of this guideline). Also, some contingency plans are themselves national security information . However, the purpose of most contingency planning information is to protect against inadvertent or accidental damaging events rather than against malicious attacks. Even so, in the case of Federal government systems, the case of hostile attacks on systems must be considered. The consequences of unauthorized disclosure of extracts from contingency plans are likely to have negligible to limited adverse effects on agency operations. In such cases, the confidentiality impact would be, at most, low . Unauthorized disclosure of the entire plan to malicious entities may have serious effects. As a result, the consequence of loss of confidentiality of comprehensive contingency plans is likely to involve serious harm to government assets, personnel, or missions. In such cases, the confidentiality impact would be, at least, moderate . Recommended Confidentiality Impact Level : The provisional confidentiality impact level recommended for contingency planning information is moderate .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_02263", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 187) policy that addresses\u2014 i. The objectives, roles, and responsibilities for the physical and environmental security program as it relates to protecting the organization\u2019s personnel and assets; and ii. The scope of the physical and environmental security program as it applies to all of the organizational staff, contractors, and third parties; and b. Procedures to address the implementation of the physical and environmental security policy and associated physical and environmental protection requirements; 2. Management commitment ensures compliance with the organization\u2019s security policy and other regulatory requirements; and 161 3. The organization ensures that the physical and environmental security policy and procedures comply with applicable federal, state, local, tribal, and territorial laws and regulations. Supplemental Guidance The organization may include the physical and environmental security policy as part of the general security policy for the organization. Requirement Enhancements None. Additional Considerations None. Impact Level Allocation Low: SG.PE-1 Moderate: SG.PE-1 High: SG.PE-1 SG.PE-2 Physical Access Authorizations Category: Common Governance, Risk, and Compliance (GRC) Requirements Requirement 1. The organization develops and maintains lists of personnel with authorized access to facilities containing smart grid information systems and issues appropriate authorization credentials (e.g., badges, identification cards); and 2. Designated officials within the organization review and approve access lists on an organization-defined frequency, removing from the access lists personnel no longer requiring access. Supplemental Guidance None. Requirement Enhancements None. Additional Considerations A1. A2. A3.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02264", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2014 Annual Report say about FEDERAL INFORMATION PROCESSING STANDARDS (FIPS) NO FINAL APPROVED FIPS RELEASED DURING FY 2014.? (Part 4) According to Computer Security Division 2014 Annual Report, FEDERAL INFORMATION PROCESSING STANDARDS (FIPS) NO FINAL APPROVED FIPS RELEASED DURING FY 2014.: for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations | | March 2014 | Attribute Based Access Control (ABAC) Definition and Considerations | | February 2014 | Framework for Improving Critical Infrastructure Cybersecurity | | January 2014 | A Profile of the Key Management Framework for the Federal Government | | December 2013 | The National Vulnerability Database (NVD): Overview | | November 2013 | ITL Releases Preliminary Cybersecurity Framework | | October 2013 | ITL Updates Federal Information Processing Standard (FIPS) for Personal Identity Verification (PIV) of Federal Employees and Contractors | ABSTRACTS OF NIST TECHNICAL SERIES PUBLICATIONS RE- L E A S E D I N F Y 2 0 1", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, key management. Contains security framework guidance for authentication systems. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_02265", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN) say about 4.5.2. Recover: Improvements Category? (Part 2) According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN), 4.5.2. Recover: Improvements Category: threats, improve technology, and address changes to the organization, the operating environment, and deficiencies encountered during plan implementation, execution, and testing. | NIST SP 800-53 Rev. 5 CP-2, CP-10, IR-4, IR-8 NIST SP 800 612 3.4 | | RC.IM-2: Recovery strategies are updated. | Evaluate the incident's characteristics and impact to determine if the recovery strategy was sufficient or appropriate (i.e., proportional to the impact) and revise the recovery strategy and corresponding plan accordingly. HSNs share lessons learned and after-action reports among partner organizations in a format and level of detail agreed upon in advance. Consider participation and sharing of lessons learned in forums such as Space ISAC. | NIST SP 800-53 Rev. 5 IR-3, IR-4, IR-8 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)."}]}
{"id": "nist_02266", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Application Container Security Guide say about C O M P U T E R S E C U R I T Y? According to Application Container Security Guide, C O M P U T E R S E C U R I T Y: \u3053\u306e\u6587\u66f8\u306f\u4ee5\u4e0b\u306e\u56e3\u4f53\u306b\u3088\u3063\u3066\u7ffb\u8a33\u76e3\u4fee\u3055\u308c\u3066\u3044\u307e\u3059 <!-- image --> \u672c\u6587\u66f8\u306f\u3001\u539f\u5178\u306b\u6cbf\u3063\u3066\u3067\u304d\u308b\u3060\u3051\u5fe0\u5b9f\u306b\u7ffb\u8a33\u3059\u308b\u3088\u3046\u52aa\u3081\u3066\u3044\u307e\u3059\u304c\u3001\u5b8c\u5168\u6027\u3001 \u6b63\u78ba\u6027\u3092\u4fdd\u8a3c\u3059\u308b\u3082\u306e\u3067\u306f\u3042\u308a\u307e\u305b\u3093\u3002 \u7ffb\u8a33\u76e3\u4fee\u4e3b\u4f53\u306f\u3001\u672c\u6587\u66f8\u306b\u8a18\u8f09\u3055\u308c\u3066\u3044\u308b\u60c5\u5831\u3088\u308a\u751f\u3058\u308b\u640d\u5931\u307e\u305f\u306f\u640d\u5bb3\u306b\u5bfe\u3057 \u3066\u3001\u3044\u304b\u306a\u308b\u4eba\u7269\u3042\u308b\u3044\u306f\u56e3\u4f53\u306b\u3064\u3044\u3066\u3082\u8cac\u4efb\u3092\u8ca0\u3046\u3082\u306e\u3067\u306f\u3042\u308a\u307e\u305b\u3093\u3002 <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Application Container Security Guide."}]}
{"id": "nist_02267", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SR-12 in NIST_SP_800-53r5_Security_Privacy_Controls? (Part 90) Control SR-12: n an information system, system security procedures, internal controls, or implementation that could be exploited or triggered by a threat source. vulnerability analysis See vulnerability assessment. vulnerability assessment [CNSSI 4009] Systematic examination of an information system or product to determine the adequacy of security measures, identify security deficiencies, provide data from which to predict the effectiveness of proposed security measures, and confirm the adequacy of such measures after implementation. T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I APPENDIX A PAGE 423 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02268", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-256 in Derived PIV Application and Data Model Test Guidelines? (Part 245) Control HA-256: ct along with the status word '90 00'. 3. From Step 4, the extended key usage extension asserts the id- PIV-content-signing OID, indicating that the certificate is authorized to sign PIV data objects. | ## 9.3.4.7 Authority Information Access Extension | Test Assertion | TA-09.03.04.07 | |----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Purpose | Verifies the authority information access extension in the Derived PIV Credential Issuer's (content signing) certificate is populated appropriately and contains the id-ad-caIssuers (1.3.6.1.5.5.7.48.2) accessMethod, which points to the location where the certificates issued to the issuer of this certificate can be found. | | DTR(s) | \u2022 DTR-07.03.04.08 | | Issuer Documentation | None. | | Precondition(s) | \u2022 A token with the Derived PIV Application is inserted into an appropriate token reader. \u2022 Suitable drivers have been loaded between the test system and an instance of the reader. \u2022 A Security Object is present within the Derived PIV Application.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_02269", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EN-1 in Guidelines for the Creation of Interoperable Software Identification (SWID) Tags? (Part 3) Control EN-1: two ways. First, the schema specifies UTF-8 as the allowed character encoding scheme for SWID tag files. Second, the schema allows the optional @xml:lang attribute to be included on all tag elements. By taking advantage of these features, a Japanese software provider could issue a SWID tag like this: ``` <SoftwareIdentity xmlns=\"http://standards.iso.org/iso/19770/-2/2015/schema.xsd\" xml:lang=\"ja-jp\" name=\" \u30b3\u30f3\u30d4\u30e5\u30fc\u30bf\u7ba1\u7406\u30b7\u30b9\u30c6\u30e0 2015\" tagId=\"jp.largecomputerco. \u30bf\u30b0\u756a\u53f7 1\" version=\"1.0\"> ``` ``` <Entity name=\" \u5927\u578b\u30b3\u30f3\u30d4\u30e5\u30fc\u30bf\u4f1a\u793e \" regid=\"largecomputerco.jp\" role=\"tagCreator softwareCreator\"/> \u2026 </SoftwareIdentity> ``` According to W3C documentation, language tags 'are used to indicate the language of text or other items in HTML and XML documents' [W3C-langtags]. By supplying the language tag ' ja-jp ' as the value of the &lt;SoftwareIdentity&gt; @xml:lang attribute, the tag creator signals to tag consumers that various language-dependent attributes, such as the &lt;SoftwareIdentity&gt; @name attribute, are provided in Japanese. Additionally, the SWID schema is designed so that any value of @xml:lang specified on any tag element is inherited by all of that element's child elements, unless explicitly overridden. As a result, the value specified for the &lt;SoftwareIdentity&gt; @xml:lang attribute will, in effect, establish the preferred language that is used for all language-dependent attributes within the tag. Knowing the preferred language of SWID tag attribute values can be very useful to tag consumers, and can relieve them of the need to attempt to perform language auto-detection. The following guideline requires that tag creators always specify the preferred language of a tag: GEN-2. The &lt;SoftwareIdentity&gt; element MUST specify an @xml:lang attribute with a non-blank value to indicate the default human language used for expressing all language-dependent attribute values. Guideline GEN-2 is directed towards both authoritative and non-authoritative tag creators.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Creation of Interoperable Software Identification (SWID) Tags."}]}
{"id": "nist_02270", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings say about 2005 PKI R&amp;D Workshop Multiple Paths to Trust? (Part 3) According to 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings, 2005 PKI R&amp;D Workshop Multiple Paths to Trust: and Implementation of LDAP Component Matching for Flexible and PKI | Design and Implementation of LDAP Component Matching for Flexible and PKI | 41 | | Secure Certificate Access in Sang Seok Lim | IBM Watson Research Center | | | PKI without Revocation Checking * Karl Scheibelhofer | Institute for Applied Information Processing and Communications, Graz | 52 | | Delegation Issuing Service for X.509 | | 66 | | David Chadwick | University of Kent, England | | * Paper was accepted, but was not presented at during the Workshop.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02271", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1.2 Purpose and Scope according to NIST Guidelines on Firewalls and Firewall Policy According to Guidelines on Firewalls and Firewall Policy, 1.2 Purpose and Scope: This document seeks to assist organizations in understanding the capabilities of firewall technologies and firewall policies. It provides practical guidance on developing firewall policies and selecting, configuring, testing, deploying, and managing firewalls.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Firewalls and Firewall Policy."}]}
{"id": "nist_02272", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Threshold Schemes for Cryptographic Primitives_ Challenges and Opportunities in Standardization and Validation of Threshold Cryptography provide? (Section 97) '85, pages 291-304. ACM, 1985. DOI:10.1145/22145.22178. - [GMW87] O. Goldreich, S. Micali, and A. Wigderson. How to Play ANY Mental Game or A Completeness Theorem for Protocols with Honest Majority . In Proc. 19th Annual ACM Symposium on Theory of Computing, STOC '87, pages 218-229. ACM, 1987. DOI:10.1145/28395.28420. - [GRJK00] R. Gennaro, T. Rabin, S. Jarecki, and H. Krawczyk. Robust and Efficient Sharing of RSA Functions . Journal of Cryptology, 13(2):273-300, Mar 2000. DOI:10.1007/s001459910011. - [Gro16] C. T. Group. NIST Cryptographic Standards and Guidelines Development Process . NISTIR 7977, March 2016. DOI:10.6028/NIST.IR.7977. - [Gue09] S. Gueron. Intel's New AES Instructions for Enhanced Performance and Security . In O. Dunkelman (ed.), Fast Software Encryption, 16th International Workshop, FSE 2009, vol. 5665 of LNCS, pages 51-66. Springer, 2009. DOI:10.1007/978-3-642-03317-9\\_4. - [HJKY95] A. Herzberg, S. Jarecki, H. Krawczyk, and M. Yung. Proactive Secret Sharing Or: How to Cope With Perpetual Leakage . In D. Coppersmith (ed.), Advances in Cryptology - CRYPT0' 95, pages 339-352. Springer Berlin Heidelberg, 1995. DOI:10.1007/3-540-44750-4\\_27. - [HM00] M. Hirt and U. Maurer. Player Simulation and General Adversary Structures in Perfect Multiparty Computation . Journal of Cryptology, 13(1):31-60, Jan 2000. DOI:10.1007/s001459910003. - [HSH + 09] J. A. Halderman, S. D. Schoen, N. Heninger, W. Clarkson, W. Paul, J. A. Calandrino, A. J. Feldman, J. Appelbaum, and E. W. Felten. Lest We Remember: Cold-boot Attacks on Encryption Keys . Commun. ACM, 52(5):91-98, May 2009. DOI:10.1145/1506409.1506429. - [IN83] K. Itakura and K. Nakamura. A public-key cryptosystem suitable for digital multisignatures . In NEC J. Res. Dev. 71, pages 1-8, Oct. 1983. - [Int18] Intel Corporation. Software Guard Extention (SGX) . https: //software.intel.com/en-us/sgx, 2018. - [ISN89] M. Ito, A. Saito, and T. Nishizeki. Secret sharing scheme realizing general access structure .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Threshold Schemes for Cryptographic Primitives_ Challenges and Opportunities in Standardization and Validation of Threshold Cryptography."}]}
{"id": "nist_02273", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does An Algorithm for Generating Very Large Covering Arrays provide? (Section 4) ut line i and resume scanning with line i +1. This procedure can normally reduce 10,000 to 100,000 tests to a several hundred, with the final reduced tests containing less than 1% 'don't care' values. Discussion: This procedure works because with many variables, each test case contains thousands of k -way combinations of variables. Another way of viewing the covering procedure is to think of each of the C = \uf8ec \uf8ec \uf8eb x v \uf8f7 \uf8f7 \uf8f8 \uf8f6 \uf8ed k n k combinations that must be covered as a separate bin. If we throw C marbles into random bins, most bins will have at least one marble. Another set of C marbles covers more bins, and so on repeated d times, until nearly all contain one or more marbles. For example, with C =20, d =8, all C combinations are covered with 99.5% probability The number of combinations produced by the algorithm is d x C , and each random combination is assigned to one of the C bins, with the total number of randomly generated combinations proportional to C ln C . With suitable values of d , at least one combination is assigned to each bin with a very high probability. The efficiency of this approach is increased by minimizing the number of duplicate combinations in each new test in step 3 Implementation notes: The algorithm can be distributed across any number of machines, but requires a common 'checkbox' to record the combinations covered. For a large number of variables, a very large amount of disk storage would be required for the blackboard, roughly <!-- image --> 8 \uf8f8 \uf8ed \uf8f8 \uf8ed k bytes. For 6-way combinations of 50 variables with 6 values each, this is approximately 9 gigabytes; large but fairly easy to implement on a cluster system. With lower interaction levels or fewer values per variable, a desktop PC is adequate for 100 variables or more. Alternatively, a disk based version of the program can be used, although this increases run time from a few minutes to hours. Calculation of d in step 3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: An Algorithm for Generating Very Large Covering Arrays."}]}
{"id": "nist_02274", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 10.3 Audit and Accountability (AU) according to NIST An Introduction to Information Security According to An Introduction to Information Security, 10.3 Audit and Accountability (AU): An audit is an independent review and examination of records and activities to assess the adequacy of system controls and ensure compliance with established policies and operational procedures. An audit trail is a record of individuals who have accessed a system as well as what operations the user has performed during a given period. Audit trails maintain a record of system activity both by system and application processes and by user activity of systems and applications. In conjunction with appropriate tools and procedures, audit trails can assist in detecting security violations, performance issues, and flaws in applications. Audit trails may be used as a support for regular system operations, a kind of insurance policy, or both. As insurance, audit trails are maintained but not used unless needed (e.g., after a system outage). As a support for operations, audit trails are used to help system administrators ensure that the system or resources have not been harmed by hackers, insiders, or technical problems. Examples of audit and accountability controls include: audit events, time stamps, nonrepudiation, protection of audit information, audit record retention, and session audit. Organizations: (i) create, protect, and retain system audit records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful, unauthorized, or inappropriate system activity; and (ii) ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: An Introduction to Information Security."}]}
{"id": "nist_02275", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RC-16 in Effective Use of Computing Technology in Vote-Tallying? (Part 22) Control RC-16: a handcarried permanent magnet if it is located no closer than about 76 millimetres (about 3 inches) to any point at which such a magnet could be placed. NBS has issued a report on this subject. ## 4. Design Specifications for Summarizers An important aspect of ballot and vote summarizers is that they are altered to specialize them for each election. Specifications should include the methods that are used to document these changes so that the documentation can become part of the election records. Audit trails are needed in these devices, just as they are in computer programs meant for stored-program computers. If summarizers are precinct-located, the capabil ity- to provide partial summations of district-wide totals following the addition of each precinct is not a pertinent requirement. Nevertheless, the other capabilities listed under VI. C. 4 Inclusion of Audit Trails are still pertinent. However, the provisions for some of these capabilities, for example for undervote storage and the computation of undervotes for offices in which more than one vote is allowed, would probably need to be implemented in hardware in these devices. The extra cost of this implementation must be weighed against the need for complete confidence in the results. ## F. Acceptance Testing of Vote-Tallying Equipment The concept of acceptance testing implies that there exists a group of identical devices, and some subset of these are to undergo a specific test determining whether design specifications are met. If those undergoing the test pass, then it is assumed that the remainder, designed identically will also pass the same test and be allowed to be used. If the number of devices is small, say ten or less, then perhaps each one may be required to undergo specific acceptance tests against design specifications. If the number of identical devices is larger, then a small number may be required to undergo extensive tests and the remainder limited to tests on the most fundamental parameters.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Effective Use of Computing Technology in Vote-Tallying."}]}
{"id": "nist_02276", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings provide? (Section 315) PKI may both potentially impact the performance of this security scheme; however, evaluating how these effects may scale to large networks is di GLYPH&lt;14&gt; cult to do analytically or empirically. In this paper, we use the tools of simulation to evaluate the impact that signatures, verification, and certificate handling have on convergence time, message size, and storage, for the principal approaches to securing BGP. By distributing and maintaining routing information, the Border Gateway Protocol (BGP) [32, 39] plays a central role in making the Internet work. However, BGP relies on hearsay information. BGP speakers trust the messages they receive and they completely trust other BGP speakers to follow the protocol specification reliably. Consequently, BGP-and the Internet it routes-is vulnerable to many potential attacks by malicious players [26]. To mitigate these risks, many researchers have proposed security mechanisms to authenticate the routing information transferred between BGP speakers [1, 8, 13, 17, 35, 40, 41]. S-BGP is the dominant scheme here. Because of the need to authenticate information passed among parties spanning a large set of domains, these se- GLYPH&lt;3&gt; contact author, zhaom@cs.dartmouth.edu (and BGP convergence) but this comes at a price, memory and message size. This Paper Section 2 reviews BGP and S-BGP. Section 3 reviews some alternate encoding and cryptographic approaches. Section 4 presents our evaluation methodology. Section 5 presents our experiments and results for path authentication. Section 6 presents our experiments and results for origin authentication. Section 7 reviews related work, and Section 8 concludes with some thoughts for future research. The Border Gateway Protocol (BGP) [32, 39] is the routing protocol for maintaining connectivity between autonomous systems (ASes) in the Internet. Each AS is assigned a unique integer as its identifier, known as its AS number .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02277", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Section 180) t: The derived keying material or an error indicator. Note: Key confirmation can be incorporated into this scheme. See Section 6.2.1.5 for details. dhHybridOneFlow is summarized in Table 15. Table 15: dhHybridOneFlow key-agreement scheme summary | | Party U | Party V | |---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------| | ( p, q, g {, SEED, counter }) | ( p, q, g {, SEED, counter }) | Domain parameters | | Static private key x U Static public key y U | Static private key x V Static public key y V | Static data | | Ephemeral private key r U Ephemeral public key t U | N/A | Ephemeral data | | 1. Compute Z s by calling FFC DH using x U and y V 2. Compute Z e by calling FFC DH using r U and y V 3. Compute Z = Z e || Z s | 1. Compute Z s by calling FFC DH using x V and y U 2. Compute Z e by calling FFC DH using x V and t U 3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}]}
{"id": "nist_02278", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Smart Card Technology_ New Methods for Computer Access Control say about 2.0 SMART CARD INTEGRATED CIRCUIT TECHNOLOGIES? According to Smart Card Technology_ New Methods for Computer Access Control, 2.0 SMART CARD INTEGRATED CIRCUIT TECHNOLOGIES: The smart card's ability to perform the computations and other functions needed in security applications depends on the development of the smart card microcomputer, which, in turn, is inherently tied to the progress of integrated circuit technologies. This chapter discusses some of the concepts and considerations involved in the production of integrated circuits.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Smart Card Technology_ New Methods for Computer Access Control."}]}
{"id": "nist_02279", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Biometric Match-on-Card Feasibility Report say about 3.1 Test Fixture? (Part 1) According to Secure Biometric Match-on-Card Feasibility Report, 3.1 Test Fixture: 3.1 Test Fixture The test fixture uses the Win32 Smart Card Application Programming Interface (API) library to communicate with DUTs and smart card readers. The library was used to acquire the following time measurements: + Average 2 time to establish a secure session + Average time to transmit the encrypted biometric data to the DUT and receive a match result + Average total time to perform a complete biometric match-on-card transaction To perform time measurements, the test fixture sends Application Protocol Data Units (APDU) to a DUT using the SCardTransmit command. The time it takes to execute a SCardTransmit command, which is obtained by computing the time difference before and after a call to SCardTransmit, is then recorded to an output file. For APDUs that require multiple calls to SCardTransmit (e.g., GET RESPONSE), the total elapsed time is determined by adding the time to execute each SCardTransmit operation. An example message sequence between a DUT and the test fixture is as follows: 1. The test fixture selects the SBMOC application on the card. 2. The test fixture performs Get Data to read the PKI certificate from the DUT and validates the certificate. 3. The test fixture requests a challenge from the DUT. The DUT responds with a challenge. 4. The text fixture and DUT generate encryption and Message Authentication Code (MAC) session keys, and finish establishing a secure session. 5. The text fixture encrypts biometric data using session key and sends it to the DUT for verification. The DUT responds with the signed match / no-match result. After running the test fixture, a Comma-Separated Values (CSV) output file is created that contains the measured times for the DUT used in the test. Table 1 lists the data recorded in the output file. A sample test fixture output appears in Appendix C. Table 1.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Secure Biometric Match-on-Card Feasibility Report."}]}
{"id": "nist_02280", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to General Server Security provide? (Section 63) ver software. The new user and new group should be independent from all other users and groups and unique. This is a prerequisite for implementing the access controls described in the following steps. During initialization, the server may have to run with root (Unix) or administrator/system (Windows) privileges; ensure that the server is configured to reduce its privileges to those of the server user after performing its initialization functions. In addition, use the server OS to limit which files can be accessed by the service processes. These processes should have read-only access to those files necessary to perform the service and should have no access to other files, such as server log files. Use server host OS access controls to enforce the following: 28 - GLYPH&lt;c=31,font=/MIJOHI+Webdings&gt; Service processes are configured to run as a user with a strictly limited set of privileges (i.e., not running as root, administrator, or equivalent). - GLYPH&lt;c=31,font=/MIJOHI+Webdings&gt; Service processes can only write to server content files and directories if necessary. - GLYPH&lt;c=31,font=/MIJOHI+Webdings&gt; Temporary files created by the server software are restricted to a specified and appropriately protected subdirectory (if possible). Access to these temporary files is limited to the server processes that created the files (if possible). It may also be necessary to ensure that the server software cannot save (or, in some cases, read) files outside the specified file structure dedicated to server content. This may be a configuration choice in the server software, or it may be a choice in how the server process is controlled by the OS. Ensure that such directories and files (outside the specified directory tree) cannot be accessed both directly and through the server software. To mitigate the effects of certain types of DoS attacks, configure the server to limit the amount of OS resources it can consume.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to General Server Security."}]}
{"id": "nist_02281", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Storage Encryption Technologies for End User Devices? (Part 37) Control ES-1: e and the user has been authenticated to the storage encryption solution, malware could access decrypted files and transfer copies of them to external hosts or extract sensitive information from them. Other examples are an attacker disabling or reconfiguring storage encryption, malware installing a keylogger that captures passwords used for storage encryption authentication, or malware acquiring a copy of a storage encryption key from the device's memory (for software-based storage encryption solutions). Organizations should also be aware that they should not rely on storage encryption technologies to protect data without regularly maintaining the encryption solution. For example, if an attacker acquires a lost, stolen, or retired device protected by storage encryption technology, and a vulnerability in the storage encryption technology is discovered in the future, the attacker may be able to exploit it to access the protected data. ## 3.3 Comparison of Storage Encryption Technologies Table 3-1 lists several characteristics of storage encryption technologies as a means for comparing the types of technologies described in this publication. 26 When multiple encryption methods are used simultaneously, the cryptographic keys used by the encryption methods are usually different. Table 3-1.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit, malware. Contains technical security guidance that could inform defensive posture. Source: Guide to Storage Encryption Technologies for End User Devices."}]}
{"id": "nist_02282", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Identity and Access Management for Electric Utilities say about Java Application? (Part 18) According to Identity and Access Management for Electric Utilities, Java Application: LOCK_USER1 ocksetAccessMode],[IPLocksetCredentialFormat],[IPLocks etAccessAlways],[RawPrimaryCredential],[LargeEncodedCa rdID],[EmbossedNumber]) VALUES (NEWID(),$UserText1,$CardNumber,$FacilityCode,$PIN,'0' ,'0','0','1',NULL,NULL,'0','0',NULL,NULL,SYSDATETIME() ,'alertent',SYSDATETIME(),'alertent','0','0',NULL,'0', '255',NULL,NULL,'Active',NULL,NULL,NULL,NULL,NULL,NULL ,'') END END; update [dbo].[Cardholders] set CardholderStatus='0' where CardholderID=$CardholderID update [dbo].[Cardholders] set CardholderStatus='1' where CardholderID=$CardholderID select CardholderID from [dbo].[Cardholders] where CardholderID =$CardholderID INSERT INTO [dbo].[CardholderAccessLevels] ( [CardholderAccessLevelID], [AccessLevelID],[LastModified],[ActivateDate],[Deactiv ateDate]) VALUES ( NEWID(), $CardholderID,(select AccessLevelID from [dbo].[AccessLevels] where AccessLevelName=$ROLE_NAME),GetUTCDate(), NULL, NULL) [CardholderID], delete from [dbo].[CardholderAccessLevels] where CardholderID=$CardholderID and AccessLevelID=(select AccessLevelID from [dbo].[AccessLevels] where AccessLevelName=$ROLE_NAME) select CardholderID from [dbo].[Cardholders] where UserText1=$UserText1 BEGIN IF $CardNumber is null BEGIN update [dbo].[Cardholders] set CardholderStatus='1' where UserText1=$UserText1 END ELSE BEGIN INSERT INTO [AIUniversal].[dbo].[Cards] ([CardID],[CardholderID],[CardNumber],[FacilityCode],[ PINNumber],[PINExempt],[APBExempt],[UseExtendedAccessT imes],[CardStatus],[ActiveDate],[ExpireDate],[UserLeve l],[UseCustomReporting],[EventInfo],[Notes],[LastModif ied],[LastModifiedByUser],[DateCreated],[CreatedByUser ],[IssueLevel],[DeactivateExempt],[VacationDate],[Vaca tionDuration],[UseCount],[TempDeactivateStart],[TempDe activateEnd],[Classification],[IPLocksetUserType],[IPL ocksetAccessMode],[IPLocksetCredentialFormat],[IPLocks etAccessAlways],[RawPrimaryCredential],[LargeEncodedCa rdID],[EmbossedNumber]) VALUES (NEWID(),(select CardholderID from [dbo].[Cardholders] where UserText1=$UserText1),$CardNumber,$FacilityCode,$PIN,' 0','0','0','1',NULL,NULL,'0','0',NULL,NULL,SYSDATETIME (),'alertent',SYSDATETIME(),'alertent','0','0',NULL,'0 ','255',NULL,NULL,'Active',NULL,NULL,NULL,NULL,NULL,NU LL,'') END END; update [AIUniversal].[dbo].[Cards] set CardStatus='0',Classification='InActive' where [CardNumber]=$CardNumber NIST SP 1800-2C: Identity and Access Management for Electric Utilities 169 f.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_02283", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Enhanced Security Requirements for Controlled Unclassified Information say about 3.10 PHYSICAL PROTECTION? According to Assessing Enhanced Security Requirements for Controlled Unclassified Information, 3.10 PHYSICAL PROTECTION: There are no enhanced security requirements for physical protection.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02284", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Glossary of Computer Security Terminology say about 2) See BELL-LAPADULA MODEL and SECURITY POLICY MODEL.? (Part 2) According to Glossary of Computer Security Terminology, 2) See BELL-LAPADULA MODEL and SECURITY POLICY MODEL.: nergy Act, as amended, and safeguarded as national security information subject to the restrictions of transmission to other countries and regional defense organizations that apply to Restricted Data. (DOE 5635.1 A) | | formulary | A technique for permitting the decision to grant or deny access to be determined dynamically at access time, rather than at the time of creation of the access list. (FIPS PUB 39) | | for official use only (FOLIO) data | Unclassified official information of a sensitive proprietary, or personal nature which must be protected against unauthorized public release as defined In AFR 12-30. (AFR 205-16; AR 380-380) | | front-end security filter | A process that Is invoked to process data according to a specified security policy prior to releasing the data outside the processing environment or upon receiving data from an external source. (DOD 5200.28-STD) | | functional testing | The portion of security testing in which the advertised features of a system are tested for correct operation.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, for official use only, national security. Contains guidance on protecting sensitive government information. Source: Glossary of Computer Security Terminology."}]}
{"id": "nist_02285", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2007 Annual Report say about Overview? (Part 2) According to Computer Security Division 2007 Annual Report, Overview: each programs. Activities in this area have historically involved, and continue to involve, large amounts of collaboration and the facilitation of relationships with other entities. Federal agencies that have collaborated recently with these activities are the Department of State, the Department of Commerce, the Department of Defense, the General Services Administration, the National Aeronautics and Space Administration, the National Security Agency, the Department of Energy, the U.S. Office of Management and Budget, the Social Security Administration, the United States Postal Service, the Department of Veterans Affairs, the Federal Aviation Administration, and NIST's National Voluntary Laboratory Accreditation Program. The list of industry entities that have worked with us in this area is long and includes the American National Standards Institute (ANSI), Oracle, Cisco Systems, Lucent Technologies, Microsoft Corporation, International Business Machines (IBM), VISA, MasterCard, Computer Associates, RSA Security, Research in Motion, Sun Microsystems, Network Associates, Entrust, and Fortress Technologies. The Division also has collaborated at the global level with Canada, the United Kingdom, France, Germany, India, Japan, and Korea in this area.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2007 Annual Report."}]}
{"id": "nist_02286", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain approved according to NIST Recommendation for Key Derivation Using Pseudorandom Functions According to Recommendation for Key Derivation Using Pseudorandom Functions, approved: An algorithm or technique for a specific cryptographic use that is specified in a FIPS or NIST Recommendation, adopted in a FIPS or NIST Recommendation, or specified in a list of NIST-approved security functions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key Derivation Using Pseudorandom Functions."}]}
{"id": "nist_02287", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Section 61) entation; list of devices requiring unique identification and authentication; device connection reports; system audit records; list of privileged system accounts; other relevant documents or records]. Interview : [ SELECT FROM: Organizational personnel responsible for system operations; organizational personnel responsible for account management; organizational personnel responsible for device identification and authentication; organizational personnel responsible for information security; system/network administrators; system developers]. Test : [ SELECT FROM: Cryptographically-based bidirectional authentication mechanisms; mechanisms supporting and/or implementing network connection policy; mechanisms supporting and/or implementing replay-resistant authentication mechanisms; mechanisms supporting and/or | | 3.5.2e | ENHANCED SECURITY REQUIREMENT Employ automated mechanisms for the generation, protection, rotation, and management of passwords for systems and system components that do not support multifactor authentication or complex account management. | ENHANCED SECURITY REQUIREMENT Employ automated mechanisms for the generation, protection, rotation, and management of passwords for systems and system components that do not support multifactor authentication or complex account management.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02288", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IR-7658 in Guide to SIMfill Use and Development? (Part 17) Control IR-7658: of records in a linear fixed file, test data may sometimes exceed those limits. To accommodate such situations, data written to a shorter field is truncated and excess records are dropped. SIMfill logs such events as a warning message for the user. The implications of the procedure used by SIMfill are important to understand when using or modifying the baseline test data provided, or creating new test data. The process allows the freedom to experiment with simple test data cases, involving only a single EF, while not affecting other EFs on a (U)SIM. However, any EF intended to be empty (i.e., erased and not populated with any test data) must be specified explicitly in the data file as a null entry. Otherwise, the content remains unchanged. Similarly, one must be aware of the field length and record number limits of (U)SIMs being populated when constructing test data. If not careful, important parts of a test case could be truncated or dropped. ## 4. Data and Schema Definitions The choice of XML as a representation for the data used by SIMfill has several advantages. XML is a well-known and well-defined standard, similar to the Hypertext Markup Language (HTML). Most users are likely to be familiar with it or with HTML, which lessens the learning curve. XML scheme definitions can also be specified for a document to exert control over its contents. Schema-sensitive XML editors are widely available, and many of them are free. With such an editor, it is fairly easy to modify existing or create new reference test data conforming to the schema definition. Changes to the XML schema definitions provided in the SIMfill distribution normally are not needed unless an error is discovered or the capabilities of SIMfill are modified to accommodate additional EFs or other types of identity modules. Nevertheless, some basic understanding is helpful, particularly if using an XML editor to modify or create test data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to SIMfill Use and Development."}]}
{"id": "nist_02289", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TG-005 in Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)? (Part 161) Control TG-005: s the integrity category [t] Similarly, any GDI has greater integrity than any UDI: however, no GDI or TP has a combined access class that is comparable to any UDI when both components are considered. What has been described so far is a system in which the individual objects of interest (GDIs and TPs) are in isolated domains, but are \"tagged\" with access classes that encode their attributes relative to the Clark/Wilson rules. In particular, the integrity component of the access class of a TP serves as the \"relation\" required by Rule El. ## Non-Discretionary Policy The non-discretionary component of the policy implicit in the Glark/Wilson requirements can be found by examining the semantics of the classes assigned to the various data objects in the context of the basic non-discretionary and program integrity rul6s. The properties listed below are global, persistent, and unconditionally maintained by the underlying security kernel, provided the security officer and certifying officials are diligent in assigning clearances and assigning labels to certified transactions correctly. An individual GDI has the \"general\" GDI integrity and disclosure category, an individual GDI category, and an individual GDI disclosure category. It, therefore, can be manipulated using only programs that have been certified to correctly manipulate that specific GDI, by personnel authorized to both read and write GDIs in general and this GDI in particular. An individual TP has the \"general\" TP and GDI integrity and disclosure categories, the integrity category of each GDI it has been certified to manipulate correctly, and an individual TP disclosure category. It, therefore, (as an executable object) can be used to manipulate any of the GDIs it has been certified for, and none of the others (it does not carry their integrity category, so program integrity will prevent it from being executed.) It may be created, modified, or deleted only by someone cleared \"[t]\" (i.e., a certifier).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)."}]}
{"id": "nist_02290", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Reference control parameter P1 according to NIST Government Smart Card Interoperability Specification, Version 2.1 According to Government Smart Card Interoperability Specification, Version 2.1, Reference control parameter P1: The reference control parameter P1 shall be used to indicate the type of requested properties information. The following P1 values are possible: 0x00: Get a GSC-IS v2.0 compatible properties response message. If this response cannot be supported by the smart card then an error (0x6A86) shall be returned. 0x01: Get all the properties. 0x02: Get the properties of the tags provided in list of tags in the command data field.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_02291", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Technology Assessment_ Methods for Measuring the Level of Computer Security say about CONTENTS? (Part 9) According to Technology Assessment_ Methods for Measuring the Level of Computer Security, CONTENTS: 5-31 | | CHAPTER | 6 | SECURITY POLICY IMPACT | | | 6.1 | SENSITIVITY DISTINCTIONS 6-1 | | | 6.2 | ACCEPTANCE CRITERIA 6-4 | | | 6.2.1 | Definition Of Acceptance Criteria 6-5 | | | 6.2.2 | Security Requirement Classes For Evaluation | | | 6.2.3 | Types Of Acceptance Criteria 6-13 6-20 | | | 6.2.4 | Conclusions | | CHAPTER | 7 | DOCUMENT OVERVIEW | | | 7.1 | INTRODUCTION 7-1 ENVIRONMENTS | | | 7.2 7.3 | V-2 CONTROLS V-2 | | | 7.3.1 | Control Groupings Or Structures 7-2 | | | 7.3.2 | Exposure Groupings Or Structures 7-3 | | | 7.4 | EVALUATION METHODOLOGIES/APPROACHES 7-3 | | 7.5 | SUMMARY OF THE STATE-OF-THE-ART 7-6 | |-------|-----------------------------------------| | 7.5.1 | Similarities And Differences 7-8 | | 7.5.2 | Approaches For Structuring Analysis 7-9 | | 7.5.3 | General Evaluation Issues 7-9 | | 7.5.4 | Conclusions 7-10 | | 7.6 | SECURITY POLICY IMPACT 7-10 | | 7.6.1 | Sensitivity Distinctions 7-10 | | 7.6.2 | Acceptance Criteria 7-11 | | 7.6.3 | Conclusions 7-11 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technology Assessment_ Methods for Measuring the Level of Computer Security."}]}
{"id": "nist_02292", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is COURSE TITLE according to Computer Security Training & Awareness Course Compendium? COURSE TITLE: Hands-On-Lans: Auditing Novell Networks Workshop COURSE LENGTH:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Training & Awareness Course Compendium."}]}
{"id": "nist_02293", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Integrating Forensic Techniques into Incident Response provide? (Section 140) 6&gt;s hard drive instead of the expected action, rebooting the system. An analyst who uses the keyboard of a computer of interest could enter keystrokes that cause unexpected actions to be performed. The best way to avoid key remapping problems is by collecting data from the computer without using its keyboard. For example, the analyst could attach a forensic workstation to a computer of interest using a crossover network cable and run scripts from the forensic workstation. Various tools and techniques can be used to support the examination process. Many of the tools and techniques discussed in Section 4.3 for examining collected data files can also be used with collected OS data. In addition, as described in Section 7, security applications, such as file integrity checkers and host IDSs, can be very helpful in identifying malicious activity against OSs. For instance, file integrity checkers can be used to compute the message digests of OS files and compare them against databases of known message digests to determine whether any files have been compromised. If intrusion detection software is installed on the computer, it might contain logs that indicate the actions performed against the OS. Another issue that analysts face is the examination of swap files and RAM dumps, which are large binary data files containing unstructured data. Hex editors can be used to open these files and examine their contents; however, on large files, manually trying to locate intelligible data using a hex editor can be a time-consuming process. Filtering tools automate the process of examining swap and RAM dump files by identifying text patterns and numerical values that might represent phone numbers, names of people, email addresses, Web addresses, and other types of critical information. Analysts often want to gather additional information about a particular program running on a system, such as the processGLYPH&lt;146&gt;s purpose and manufacturer.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: intrusion detection, incident response. Contains technical security guidance that could inform defensive posture. Source: Guide to Integrating Forensic Techniques into Incident Response."}]}
{"id": "nist_02294", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Random Bit Generator (RBG) Constructions provide? (Section 89) ding output for use by a consuming application). 5. If a reseed capability is implemented, the DRBG shall be reseeded using any healthy validated entropy source(s) used for instantiation. 6. The DRBG shall be reseeded before generating output if the DRBG has produced 2 17 or more bits of output since instantiation or the last reseeding process. 7. When instantiating and reseeding CTR\\_DRBG without a derivation function, keylen + output\\_len bits with full entropy (where keylen is the length of the key to be used by the cryptographic primitive and output\\_len is the length of its output block) or as otherwise specified in [SP\\_800-90A] shall be obtained either directly from the entropy sources or 27 See Sec. 2.8.2 and 3.1 for discussions of the Get\\_entropy\\_bitstring function. ``` , call is replaced by: Get_conditioned_input ``` . via an external vetted conditioning function that provides full-entropy output (see Sec. 3.2.2.2). 8. For CTR\\_DRBG with a derivation function, Hash\\_DRBG , or HMAC\\_DRBG , a bitstring with at least 3 s /2 bits of entropy shall be obtained from the entropy sources to instantiate the DRBG at a security strength of s bits. When reseeding is performed, a bitstring with at least s bits of entropy shall be obtained from the entropy source(s). The entropy may be obtained directly from the entropy source(s) or via an external vetted conditioning function (see Sec. 3.2.2). 9. The entropy source(s) used for the instantiation and reseeding of the DRBG within an RBG2(P) construction shall include one or more validated physical entropy sources; the inclusion of one or more validated non-physical entropy sources is optional. A bitstring that contains entropy shall be assembled and the entropy in that bitstring determined as specified in Method 1 of Sec. 2.3 (i.e., only the entropy provided by validated physical entropy sources shall be counted toward fulfilling the amount of entropy in an entropy request). 10.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Bit Generator (RBG) Constructions."}]}
{"id": "nist_02295", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices say about Implementation Tip? (Part 1) According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Implementation Tip: Implementation Tip Most government information systems access, process, and/or disseminate more than one class of information. Security objectives and impacts associated with all of the types of information and processes served by the information system need to be considered in determining the system's information security requirements. Each information type may include one or more elements. For example, benefits management information includes employee identification information, benefit plan information for insurance and other products, cost information, claims and reimbursement policy information, claims procedures, etc. In some cases, different impact levels are appropriate for different information elements. For example, elements of program monitoring information relating to remediation of information security vulnerabilities may have a different impact level than elements of program monitoring information relating to an office furniture upgrade. Each agency that processes an information type may process a distinct combination of elements. The authority and responsibilities assigned to each agency that processes an information type can affect the actual impact level associated with the information within the context of that agency's operations. In Table C-2, the existence of exceptions to provisional impact assignments are identified by displaying impact assignments in a gray font [ gray font ] and are described as applicable by security objective in the information type descriptions to follow. The specific descriptions are provided under the sub-heading 'Special Factors Affecting [Security Objective] Impact Determination.' Appendices C.2 and C.3 identify information elements and contexts that may result in variances from the basic impact level assignment. For example, some systems process information the compromise of which affect national security, critical infrastructures, or key national assets.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_02296", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Conformance Test for FDDI Medium Access Control (MAC) say about Continued from previous page.? (Part 17) According to A Conformance Test for FDDI Medium Access Control (MAC), Continued from previous page.: | | Test Case Dynamic Behaviour | Test Case Dynamic Behaviour | Test Case Dynamic Behaviour | Test Case Dynamic Behaviour | Test Case Dynamic Behaviour | |----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| | Reference : FDDI/MAC/BASIC/FrameRepeat Identifier; FrameRepeat Purpose; Test MAC Frame Repeating Defaults Reference; | Reference : FDDI/MAC/BASIC/FrameRepeat Identifier; FrameRepeat Purpose; Test MAC Frame Repeating Defaults Reference; | Reference : FDDI/MAC/BASIC/FrameRepeat Identifier; FrameRepeat Purpose; Test MAC Frame Repeating Defaults Reference; | Reference : FDDI/MAC/BASIC/FrameRepeat Identifier; FrameRepeat Purpose; Test MAC Frame Repeating Defaults Reference; | Reference : FDDI/MAC/BASIC/FrameRepeat Identifier; FrameRepeat Purpose; Test MAC Frame Repeating Defaults Reference; | | Behaviour Description | Label | Constraint Reference | V | Comments | | FrameRepeat +FDDI/INITCONNECT # # !DATA # # # * ?DATA # # # # 70THERWISE ?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Conformance Test for FDDI Medium Access Control (MAC)."}]}
{"id": "nist_02297", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cell Phone Forensic Tools_ an Overview and Analysis provide? (Section 197) reported above. (Above) The following scenarios were conducted on an unlocked Nokia 6610i GSM phone, using an ATETSI interface (i.e., AT-ETSI phone protocol plug-in, ETSI-AT phone data conversion). Connectivity and Retrieval: The password-protected device contents were successfully acquired with or without the SIM present without providing authentication. Basic subscriber and service provider information was found and reported (i.e., IMEI, ICCID). Memory size is not reported. (Meet) PIM Applications: Active phonebook entries were found and reported. No other PIM data was found. (Below) Dialed/Received Phone Calls: All dialed/received phone calls were found and reported. Deleted phone calls were not found. (Below) SMS/MMS Messaging: All active incoming and outgoing SMS messages were found and reported. Active MMS and deleted SMS/MMS messages were not found. (Below) Internet Messaging: N.A. - The Nokia 6610i does not support email. (NA) Web Applications: Visited URLs, search queries performed, textual Web content or graphical images of visited sites were not found. (Miss) Text File Formats: Data content associated with text files (i.e., . txt , . doc , . pdf ) was not found. (Miss) Graphics Files Format: Graphic files (e.g., . bmp , . jpg , . gif , . png , . tif ) were not found. (Miss) Compressed File Archive Formats: Compressed data file (i.e., . zip , . rar , . exe , . tgz ) content was not found. (Miss) Misnamed Files: Misnamed files (e.g., . txt file renamed with a . dll extension) were not found. (Miss) Peripheral Memory Cards: N.A. - The Nokia 6610i does not allow for removable media. (NA) Acquisition Consistency: N.A. - The MD5/SHA1 hashing algorithms are used to determine whether a case file has been damaged, not to verify that the acquired data has not been altered after acquisition. (NA) Cleared Devices: N.A. - A Hard Reset function is not provided by the phone.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_02298", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives say about 7.7 Ecosystem scale and interoperability? (Part 2) According to Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives, 7.7 Ecosystem scale and interoperability: ion of typically centrally administered cyber certifications, such as granting an Authority to Operate (govt) or the equivalent in commercial settings, and applicability to decentralized capabilities. - Overcoming cybersecurity practices which may result in siloing cyber knowledge in specific domains, e.g., industrial controls, space satellites. - Security and life cycle management concerns associated with dependence on open-source software [60]. Impact : The mechanics and patterns of linking traceability between blockchain solutions, for example to accommodate logistics, must ultimately stand up to the demands of multiple end operating environments and traceability ecosystems. The experience need not be the only teacher. Experiments, further proofs of concept, modeling and simulation could improve readiness and cyber resilience. By probing with adaptive models, we may anticipate constitution of transactions, in scope, identity solutions, content, vocabulary, synchronicity, and perhaps unforeseen characteristics when market forces and cyber adversaries are on the move.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives."}]}
{"id": "nist_02299", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Control according to Security and Privacy Controls for Information Systems and Organizations? Control: Employ a detonation chamber capability within [Assignment: organization-defined", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02300", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines on Electronic Mail Security provide? (Section 133) s (e.g., Windows, Linux, Unix). This arrangement introduces an added layer of complexity because that general-purpose operating system must also be secured in addition to the firewall software itself. Application layer firewalls are increasingly being deployed as appliance-based devices, which may use specialized operating systems. Routers and stateful inspection firewalls also typically run on specialized operating systems. To successfully protect a mail server using a firewall, ensure that the firewall is patched to the latest or most secure level (application and underlying operating system) and is both capable of and configured to support the following items: - GLYPH&lt;c=31,font=/HABHKN+Webdings&gt; Control all traffic between the Internet and the mail server - GLYPH&lt;c=31,font=/HABHKN+Webdings&gt; Block all inbound traffic to the mail server except that traffic which is required, such as TCP port 25 (SMTP).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_02301", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Advanced Encryption Standard (AES) say about Table of Contents? (Part 5) According to Advanced Encryption Standard (AES), Table of Contents: Expansion of a 192-bit Key | . . . . . . . . . . . . . . . . . . | 30 | | A.3 | Expansion of a 256-bit Key | . . . . . . . . . . . . . . . . . . | 32 | | Appendix B -Cipher Example | Appendix B -Cipher Example | Appendix B -Cipher Example | 34 | | Appendix C -Example Vectors | Appendix C -Example Vectors | Appendix C -Example Vectors | 36 | | Appendix D -Change Log (Informative) | Appendix D -Change Log (Informative) | Appendix D -Change Log (Informative) | 37 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Advanced Encryption Standard (AES)."}]}
{"id": "nist_02302", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control DP-10 in Computer Security_ Selected Articles? (Part 38) Control DP-10: e computer security articles and a reading list of computer security publications. This information will benefit computer security managers as well as managers and users of information technology. 12. KEY WORDS (5 TO 12 ENTRIES; ALPHASETICAL ORDER; CAPITAUZE ONLY PROPER NAMES; AND SEPARATE KEY WORDS BY SEMICOLONS) encryption; internet; local area network; risk analysis; security; viruses 13. AVAILABILITY 14. NUMBER OF PRINTED PAGES UNUMITED FOR OFFICIAL DISTRIBUTION. DO NOT RELEASE TO NATIONAL TECHNICAL INFORMATION SERVICE (NTIS). 4 3 ORDER FROM SUPERINTENDENT OF DOCUMENTS, U.S. GOVERNMENT PRINTING OFFICE, WASHINGTON, DC 20402, 15. PRICE AO 3 1 A ORDER FROM NATIONAL TECHNICAL INFORMATION SERVICE (NTIS), SPRINGFIELD, VA 22161. .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security_ Selected Articles."}]}
{"id": "nist_02303", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does User's Guide to Telework and Bring Your Own Device (BYOD) Security say about Authority? (Part 1) According to User's Guide to Telework and Bring Your Own Device (BYOD) Security, Authority: Authority This 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. \u00a7 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. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-114 Revision 1 Natl. Inst. Stand. Technol. Spec. Publ. 800-114rev1, 44 pages (July 2016) CODEN: NSPUE2 This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800-114r1 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: User's Guide to Telework and Bring Your Own Device (BYOD) Security."}]}
{"id": "nist_02304", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Non-Fungible Token Security provide? (Section 21) point of a token's transaction history and determine its origin and where it has been. The ability to validate a token's history can help a user determine whether a token is fraudulent or legitimate. A blockchain could undergo an attack (e.g., 51 % attack [25]) that enables a malicious entity to change the blockchain history, but this is unlikely for established and widely used blockchains due to the significant resources dedicated to maintenance of those chains (e.g., either mining processing power or large staked holdings). A fundamental property of a blockchain is its ability to record data in a near-permanent manner based on its decentralized storage and cryptographic mechanisms. Other than the previously referenced 51% attack [25], there are some exceptions to a blockchain's permanence. One way to sidestep the property of permanence is to 'burn' the NFT. Transferring an NFT to an address that no one can access renders any further use of the NFT impossible. For example, sending any transaction to the Ethereum address '0x0000000000000000000000000000000000000000' will effectively destroy whatever is sent because there is no known private key that resolves to this address (and it is extremely unlikely for someone to find it) so no one can access the account. Other blockchains have specific addresses that the underlying blockchain code will prevent from sending transactions but can still receive transactions. These are hard coded burn addresses, so even if someone were to discover a private key that would resolve to that address, they could not claim any asset associated with it. There may be legitimate use cases for burning an NFT, such as to provide proof of burning to receive an upgraded NFT in a different smart contract or if the NFT is a consumable object in a blockchain-based video game (i.e., a unique item that provides some benefit for the player). Even though the NFT is burned, it still technically exists in the smart contract on the blockchain.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: token, sso. Contains security framework guidance for authentication systems. Source: Non-Fungible Token Security."}]}
{"id": "nist_02305", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook provide? (Section 98) \"Computer Security Training Guidelines,' dated July 1988. 7. Federal Information Processing Standards Publication (FIPS PUB) 73, \"Guidelines for Security of Computer Applications,' dated June 1980. 8. FIPS PUB 39, \"Glossary for Computer Systems Security,' dated February 1976. 9. DOD Trusted Computer System Evaluation Criteria, DOD 5200.28-STD, dated December 1985. 10. National Computer Security Center, NCSC-TG-004, Version 1, \"Glossary of Computer Security Terms,' dated October 1988. - B. NASA MANAGEMENT INSTRUCTIONS AND HANDBOOKS 1. NMI 1152.19, \"NASA Information Security Program Committee.' 2. NMI 1200.7, \"NASA's Internal Control System.' 3. NMI 1371.3, \"Coordination of Foreign Visitor Activity.\" 4. NMI 1610.3, \"Personnel Security Program.\" 5. NHB 1610.6, \"NASA Personnel Security Handbook.\" 6. NMI 1630.2, \"Delegation of Authority to Certify for Access 5. to Restricted Data.\" 7. NHB 1640.4, \"NASA Information Security Program.\" 8. NMI 1640.7, \"Delegation of Authority to Make Determinations in Original Classification Matters.\" 9. NMI 1650.1, \"Industrial Security Policies and Procedures.\" 10. NHB 2410.1, \"Information Processing Resources Management.\" 11. NMI 2410.7, \"Assuring the Security and Integrity of NASA 11. Automated Information Resources.\" 12. NMI 2520.1, \"Communications System Management.\" 13. NMI 9810.1, \"The NASA Investigations Program.\" - C. NASA HEADQUARTERS IRM OFFICE DOCUMENTS NASA Computer Security Awareness and Training (CSAT) Guide, dated April, 1990.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook."}]}
{"id": "nist_02306", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cell Phone Forensic Tools_ an Overview and Analysis provide? (Section 65) | TULP 2G | BITpim | |------|---------------|---------------|----------------|------------|------------------|-----------|-----------------| | 8910 | | | | | | X | Audiovox | | X | | | | | | | BlackBerry 7750 | | X | | | | | | | BlackBerry 7780 | | | | X | X | | X | X | Ericsson T68i | | X | X | | | | | | Kyocera 7135 | | | | X | | | X | X | Motorola C333 | | X | | | | | | | Motorola MPX220 | | | | X | X | | X | X | Motorola V66 | | | | | X | | X | X | Motorola V300 | | | | X | | X | | | Nokia 3390 | | | | X | X | X | X | X | Nokia 6610i | | | | | X | X | | X | Nokia 6200 | | | | | X | X | | | Nokia 7610 | | X | | | | | | | Samsung i700 | | | | | | |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_02307", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Benefits of an Updated Mapping between the NIST Cybersecurity Framework and the NERC Critical Infrastructure Protection Standards provide? (Section 2) d publications, visit the Computer Security Resource Center. Information on other efforts at NIST, in the Information Technology Laboratory (ITL), and on the NIST Smart Grid Program is also available. Visit NERC for information about NERC programs, projects, and initiatives. National Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000 Email: NISTCSF-NERCCIP-Mapping@nist.gov All comments are subject to release under the Freedom of Information Act (FOIA). The final mapping between the NERC CIP standards and the NIST Cybersecurity Framework (CSF) v1.1 referenced in this white paper can be found at https://doi.org/10.18434/mds2-2348 The file named 'NIST CSF v1.1 to NERC CIP FINAL.XLSX' is the complete mapping. There is also a README file explaining the mapping data set and its background and uses. Every organization in the electricity sector knows that cybersecurity is already a major challenge. There are a variety of standards and resources that organizations are either required or encouraged to use in managing their unique cybersecurity-related risks. A recent mapping initiative between two major cybersecurity guidance documents can help organizations mature and align their compliance and security programs and better manage risks. The 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, csf, fips. General security reference material without sensitive content. Source: Benefits of an Updated Mapping between the NIST Cybersecurity Framework and the NERC Critical Infrastructure Protection Standards."}]}
{"id": "nist_02308", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Technical Capabilities Provided by Solution according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case, Technical Capabilities Provided by Solution: Microsoft Active Directory provides components of the following Technical Capabilities described in Section 6 of Volume 1: - Credential Management - Authentication and Authorization", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, credential management. Contains security framework guidance for authentication systems. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case."}]}
{"id": "nist_02309", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-05(03) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control CM-05(03): ACCESS RESTRICTIONS FOR CHANGE | SIGNED COMPONENTS [WITHDRAWN: Moved to CM-14.]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_02310", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Sample Level 2 Text according to NIST Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, Sample Level 2 Text: - C-SCRM Leads shall be responsible for: - o Representing the interests and needs of C-SCRM PMO members. - o Leading and/or coordinating the development and execution of program or business-line C-SCRM plans. This shall include ensuring that such plans are appropriately aligned to and integrated with the enterprise-level C-SCRM plan. - The mission and business process C-SCRM staff shall be responsible for: - o The primary execution of C-SCRM activities (e.g., supplier or product assessments) and - o Support for mission- and business-specific C-SCRM activities driven by non-CSCRM staff.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_02311", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Test according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, Test: [SELECT FROM: mechanisms for implementing least privilege functions]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02312", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.4 Risk Assessment according to NIST Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events According to Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events, 3.4 Risk Assessment: NIST SP 800-30 Revision 1, Guide for Conducting Risk Assessments states that risk is 'a measure of the extent to which an entity is threatened by a potential circumstance or event, and typically a function of: (i) the adverse impacts that would arise if the circumstance or event occurs; and (ii) the likelihood of occurrence.' The guide further defines risk assessment as 'the process of identifying, estimating, and prioritizing risks to organizational operations (including mission, functions, image, 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.' The NCCoE recommends that any discussion of risk management, particularly at the enterprise level, begins with a comprehensive review of NIST SP 800-37 Revision 2, Risk Management Framework for Information Systems and Organizations -material available to the public. The Risk Management Framework (RMF) guidance, as a whole, proved to be invaluable in giving us a baseline to assess risks, from which we developed the project, the security characteristics of the build, and this guide. We performed two types of risk assessments: - \uf0a7 Initial analysis of the risk factors discussed with financial, retail, and hospitality institutions: this analysis led to creation of the DI project and desired security posture. See NISTIR 8050, Executive Technical Workshop on Improving Cybersecurity and Consumer Privacy, for additional participant information. . - \uf0a7 Analysis of how to secure the components within the solution and minimize any vulnerabilities they might introduce: see Section 5, Security Characteristic Analysis.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_02313", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Conformance Test for FDDI Medium Access Control (MAC) say about FDDI MAC Conformance Test C Language Test Generated by the TTCN Translator? (Part 41) According to A Conformance Test for FDDI Medium Access Control (MAC), FDDI MAC Conformance Test C Language Test Generated by the TTCN Translator: Verdict (FAIL) ; return (TRUE) } /* line 1699 \"FDDI.MP\" [5]? TIMEOUT */ if (Timeout (\"TRT. \") ) { _level += 1; SetfVerdict (FAIL) return (TRUE) } } /* end of level [5] */ } /* line 1702 \"FDDI.MP\" [4]? OTHERWISE */ if (_buffer) { _level +' 1; SetfVerdict (FAIL) ; return (TRUE) } /* line 1705 \"FDDI.MP\" --[4]? TIMEOUT */ if (Timeout (\"TRT. \") ) { _level +' 1; SetfVerdict (FAIL) ; return (TRUE) ) /* end of level [4] */ } /* end of level [3] */ } } _level \u00bb _lastlevel; /* end of level [2] */ return (FALSE) /* end of level [1] */ /* * DetectFrameBody2 Testing MAC Frame Error Detection 8: Detecting Frame * Body 2 */ int DetectFrameBody2 () ( int _time -0; _level -1; lastlevel; ``` ``` strcpy(R, \"NONE\") Result -NONE; _timername -(char *} 0; _bufferlen --1; /* line 1713 \"FDDI.MP\" (1)+ */ /* Initializing Connection */ _lastlevel _level; if (INITCONNECT 0 return (TRUE) else if (_level > _lastlevel) { _level +-1; while (TRUE) ( /* line 1716 \"FDDI.MP\" [2]! DATA */ /* * Tester sends the frame (DA-IUT Address; a symbol (not Idle or data) in * INFO) */ pDATA -DATA_T10(); Send_PDU_DATA (pDATA) ; _level +-1; while (TRUE) { /* line 1720 \"FDDI.MP\" [3]! TOKEN */ /* followed by To)cen. */ pTOKEN \u00bb T0KEN_T1 () ; Send_PDU_TOKEN (pTOKEN) _level +-1; _timername -\"TRT.\"; while (TRUE) { /* line 1724 \"FDDI.MP\" [4]? DATA_Strip */ /* PA, SD, FC, DA, SA and Idles returned, */ pDATA_Strip -DATA_Strip_R2 () _buffer = Receive_PDU (_timername) if (Is_PDU_DATA_Strip (pDATA_Strip, _buffer) ) { _level +\u00bb 1; _timername -\"TRT.\"; while (TRUE) { /* line 1728 \"FDDI.MP\" [5]? TOKEN */ /* followed by Tolcen */ pTOKEN -T0KEN_R1 () ; _buffer ' Receive_PDU (_timername) if ( I s_PDD_TOKEN (pTOKEN, _buffer) ) { _level +-1; SetfVerdict (PASS) ; return (TRUE) ) /* line 1734 \"FDDI.MP\" --[5]? OTHERWISE */ if (_buffer) ( _level +-1; SetfVerdict (FAIL) return (TRUE) } /* line 1737 \"FDDI.MP\" [5]? TIMEOUT */ if (Timeout (\"TRT.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, token. Contains security framework guidance for authentication systems. Source: A Conformance Test for FDDI Medium Access Control (MAC)."}]}
{"id": "nist_02314", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 2017 NIST_ITL Cybersecurity Program Annual Report provide? (Section 215) The software identification (SWID) data model defined by this standard describes an XML format for software publishers to provide authoritative identification, categorization, software relationships (e.g., dependency, bundling, and patching), executable and library footprint details, and other metadata for software. This information can be used to support operational and cybersecurity use cases around managing software deployments, managing software licenses, managing software vulnerabilities and related software patches, and assessing secure software configurations. To supplement the requirements in ISO/IEC 19770-2:2015, CSD collaborated with DHS, NSA, and MITRE on the development of NISTIR 8060, Guidelines for the Creation of Interoperable Software Identification (SWID) Tags . NISTIR 8060, published in April 2016, provides an overview of the capabilities and usage of SWID tags as part of a comprehensive software lifecycle. This report introduces SWID tags in an operational context, provides guidelines for the creation of interoperable SWID tags, and highlights key usage scenarios for which SWID tags are applicable. Figure 39 illustrates several types of SWID tags (as indicated in the legend) and how these support multiple elements of the software product life cycle, including deployment, installation, patching, upgrading and removal. Figure 39: SWID Tags Support the Software Product Lifecycle <!-- image --> Additionally, in FY 2017, NIST has worked with the IETF to integrate SWID tags into the Network Endpoint Assessment (NEA) protocol, through the Software Inventory Message and Attributes (SWIMA) for PA-TNC specification (see https:/ /datatracker.ietf. org/doc/draft-ietf-sacm-nea-swima-patnc/).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02315", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Acknowledgments according to NIST Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, Acknowledgments: The authors gratefully acknowledge and appreciate the significant contributions from individuals and organizations in the public and private sectors whose constructive comments improved the overall quality, thoroughness, and usefulness of this publication. The authors also wish to thank the NIST technical editing and production staff - Jim Foti, Jeff Brewer, Eduardo Takamura, Isabel Van Wyk, Cristina Ritfeld, Derek Sappington, and Carolyn Schmidt - for their outstanding support in preparing this document for publication. Finally, a special note of thanks goes out to Kelley Dempsey for the initial research and development of the content used in the prototype CUI overlay.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_02316", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT) say about 7.7 Network Security? (Part 1) According to Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT), 7.7 Network Security: 7.7 Network Security Network security standards provide security requirements and guidelines on processes and methods for the secure management, operation and use of information, information networks, and their inter-connections. Such standards-based technologies can help to assure the confidentiality and integrity of data in motion, assure electronic commerce, and provide for a robust, secure and stable network and Internet. IoT networks are deployed using a multitude of protocols and physical links. Selecting the appropriate messaging and communication protocols depends on the use case and security requirements for each system. One characteristic of IoT is the potential for spontaneous connections (due to the networking) without a system view. Viewed in this way the IoT could not be 'planned' nor secured well using traditional approaches to security since system compositional or emergent properties would never be seen by a risk manager. The network interfaces in these loosely coupled systems represent attack surfaces. Therefore, without a system asset definition and subsequent threat analysis the security design is very unlikely to be useful. Radio Frequency (RF) connections may be based on industrial, scientific, and medical (ISM) radio band, cellular data, or other standards. RF interference should be considered as a source of risk for IoT deployments. Individual sensors may be disabled or degraded by RF interference. This could be inadvertent, e.g., use of a poorly shielded microwave oven near an IP based security camera; or malicious, e.g., use of a cell-phone jammer to prevent long-term evolution (LTE)-connected motion sensors from transmitting activity to a security officer monitoring station Annex D lists the standards of the common protocols that support IoT communications and establish the security of the underlying network connections.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_02317", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Management_ Part 1 \u2013 General provide? (Section 286) rivate signature key and corresponding public key could be generated and the public key distributed in accordance with Section 8.1.5.1 for use if the primary private signature key becomes unavailable. It is appropriate to backup or archive a public signature-verification key for as long as required in order to verify the information signed by the corresponding private signature key. In the case of a public key that has been certified (e.g., by a Certification Authority), saving the public-key certificate would be an appropriate form of storing the public key; backup or archive storage may be provided by the infrastructure (e.g., by a certificate repository). The public key should be stored in backup storage until the end of the private key's cryptoperiod and should be stored in archive storage as long as required for the verification of signed data. A symmetric authentication key is used to provide assurance of the integrity and source of information. A symmetric authentication key can be used: 1. By an originator to create a message authentication code (MAC) that can be verified at a later time to determine the integrity (and possibly the source) of the authenticated information; the authenticated information and its MAC could then be stored for later retrieval or transmitted to another entity; 2. By an entity that retrieves the authenticated information and the MAC from storage to determine the integrity of the stored information (note: this is not a communication application); 3. Immediately upon receipt by a receiving entity to determine the integrity of transmitted information and the source of that information (the received MAC and the associated authenticated information may or may not be subsequently stored); or 4.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02318", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-18(05) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control SI-18(05): PERSONALLY IDENTIFIABLE INFORMATION QUALITY OPERATIONS | NOTICE OF CORRECTION OR DELETION POTENTIAL ASSESSMENT METHODS AND OBJECTS:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_02319", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Networks of 'Things' say about 6 Summary? (Part 1) According to Networks of 'Things', 6 Summary: 6 Summary This document offers an underlying and foundational science for IoT-based technologies on the realization that IoT involves sensing , computing , communication , and actuation . We presented a common vocabulary to foster a better understanding of IoT and better communication between those parties discussing IoT. We acknowledge that the Internet is a network of networks, but we believe that focusing on restricted NoTs in a bounded way gives better traction to addressing trustworthiness problems that an unbounded Internet does not. Some may argue that every 'thing' in a NoT is ultimately a service. The primitives definitely offer services, however because of the combinatorics of mixtures of hardware and software 'things', and we prefer to distinguish. Five primitives and six elements that impact IoT trustworthiness have been presented. Primitives are the building blocks; elements are the less tangible trust factors impacting NoTs. Primitives also allow for analytics and formal arguments of IoT use case scenarios. Without an actionable and universally-accepted definition for IoT, the model and vocabulary presented here expresses how IoT, in the broad sense, behaves . Use case scenarios employing the primitives afford us quicker recommendations and guidance concerning a NoT's potential trustworthiness. For example, authentication can be used in addressing issues such as geo-location and sensor ownership, but authentication may not be relevant if an adversary owns the sensors and can obtain that information based on proximity. Encryption can protect sensor data transmission integrity and confidentiality including cloud-tocloud communication, but it might render the IoT sensors unusable due to excessive energy requirements. While fault-tolerant techniques can alleviate reliability concerns associated with inexpensive, replaceable, and defective third party 'things', they can also be insecure and induce communication overhead and increased attack surfaces.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Networks of 'Things'."}]}
{"id": "nist_02320", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Managing Information Security Risk_ Organization, Mission, and Information System View provide? (Section 57) quisite 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. A key output from the Tier 2 definition of mission/business processes is the selected risk response strategy 35 for these processes within the constraints defined in the risk management strategy. The risk response strategy includes identification of information protection needs and the allocation of those needs across components of the process (e.g., allocation to protections within information systems, protections in the operational environments of those systems, and allocation to alternate mission/business execution paths based on the potential for compromise). A significant risk-related issue regarding the ability of organizations to successfully carry out missions and business functions is the complexity of the information technology being used in information systems.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Managing Information Security Risk_ Organization, Mission, and Information System View."}]}
{"id": "nist_02321", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain DRAFT NISTIR 7275 Revision 4, Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.2 according to NIST Computer Security Division 2010 Annual Report According to Computer Security Division 2010 Annual Report, DRAFT NISTIR 7275 Revision 4, Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.2: Group: Systems and Emerging Technologies Security Research This report specifies the data model and Extensible Markup Lan\u00ad guage (XML) representation for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.2. An XCCDF document is a structured collection of security configuration rules for some set of target systems. The XCCDF specification is designed to support information interchange, document gener\u00ad ation, organizational and situational tailoring, automated com\u00ad pliance testing, and compliance scoring. The specification also defines a data model and format for storing results of security guidance or checklist compliance testing. XCCDF provides a uni\u00ad form foundation for expression of security checklists and other configuration guidance, and thereby fosters more widespread application of good security practices. Contact: Mr. David Waltermire david.waltermire@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2010 Annual Report."}]}
{"id": "nist_02322", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Study of Federal Agency Needs for Information Technology Security say about Appendix A? According to A Study of Federal Agency Needs for Information Technology Security, Appendix A: oversight for OMB/NIST/NSA - Congress needs to be kept informed", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of Federal Agency Needs for Information Technology Security."}]}
{"id": "nist_02323", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Limited Delegation for Client-Side SSL \u2217 according to NIST 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings According to 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings, Limited Delegation for Client-Side SSL \u2217: Nicholas Santos nicholas.j.santos@gmail.com Sean W. Smith sws@cs.dartmouth.edu", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_02324", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research provide? (Section 99) 800-164 Related controls: CM-2, CM-4, CM-5, CM-6, CM-9, SA-10, SI-2, SI-12 References: NIST SP 800-128 Related controls: AC-2, AC-3, AC-14, AC-17, AC-18, IA-4, IA-5, IA-8 References: HSPD-12; OMB M-04-04, 06-16, 11-11; FIPS 201; NIST SPs 800-63, 800-73, 800- 76, 800-78; Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance; idmanagement.gov Related controls: AC-2, IA-2, IA-3, IA-5, IA-8, SC-37 References: FIPS 201; NIST SPs 800-73, 800-76, 800-78 Related controls: AC-2, AC-3, AC-6, CM-6, IA-2, IA-4, IA-8, PL-4, PS-5, PS-6, SC-12, SC-13, SC-17, SC-28 References: OMB M-04-04, 11-11; FIPS 201; NIST SPs 800-63, 800-73, 800-76, 800-78; FICAM Roadmap and Implementation Guidance; idmanagement.gov 47 Security and Privacy Controls for Federal Information Systems and Organizations , Related controls: AC-17, PE-4 References: FIPS 140-2, 197; NIST SPs 800-52, 800-77, 800-81, 800-113; Committee on National Security Systems (CNSS) Policy 15; National Security Telecommunications and Information Systems Security (NSTISSI) No.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research."}]}
{"id": "nist_02325", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance) say about Required Vendor Information? According to PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance), Required Vendor Information: VE03.03.01: The vendor shall provide in its documentation a list of all the authenticators along with their tags and possible values, when applicable.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)."}]}
{"id": "nist_02326", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Process: according to NIST Recommendation for Random Bit Generator (RBG) Constructions According to Recommendation for Random Bit Generator (RBG) Constructions, Process:: 1. Obtain the current internal state of DRBG1 to get its instantiated security strength (shown as RBG1\\_DRBG1\\_security\\_strength in step 2). 2. If ( s &gt; RBG1\\_DRBG1\\_security\\_strength ) , then return ( ERROR\\_FLAG , Invalid\\_state\\_handle ) . 3. If the length of the personalization\\_string &gt; max\\_personalization\\_string\\_length , return ( ERROR\\_FLAG, Invalid\\_state\\_handle ) . 4. If ( s &gt; 192) , then s = 256 Else, if ( s \u2264 128) , then s = 128 . Else, s = 192 . 5. ( status, seed\\_material ) = DRBG\\_Generate ( RBG1\\_DRBG1\\_state\\_handle, number\\_of\\_bits\\_to\\_generate, s ) . 6. If ( status \u2260 SUCCESS) , return ( status , Invalid\\_state\\_handle ) . 7. working\\_state\\_values = Instantiate\\_algorithm ( seed\\_material, personalization\\_string ) . 8. Get the sub-DRBGx\\_state\\_handle for a currently empty internal state. If an empty internal state cannot be found, return ( ERROR\\_FLAG, Invalid\\_state\\_handle ) . Comment: See the instructions below for the value of number\\_of\\_bits\\_to\\_generate . 9. Set the internal state for the new instantiation (e.g., as indicated by sub-DRBGx\\_state\\_handle ): 2. 9.1 Record the working\\_state\\_values returned from step 7. 3. 9.2 Record any administrative information (e.g., the value of s ).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Bit Generator (RBG) Constructions."}]}
{"id": "nist_02327", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3 provide? (Section 108) ethodologies have not been incorporated as part of a cohesive security fabric. They are | | 1422 | potentially valuable checklist-style elements that can solve specific security or privacy needs. These | | 1423 | methodologies could be better integrated with risk management guidelines developed by others (e.g., | | 1424 | NIST Special Publication 800-37 Revision 1, Guide for Applying the Risk Management Framework to | | 1425 | Federal Information Systems [92], NIST Internal Report (NISTIR) 8062, An Introduction to Privacy | | 1426 | Engineering and Risk Management in Federal Systems [93], and COBIT Risk IT Framework [94]. | | 1427 | In the proposed operational taxonomy, broad considerations of the conceptual taxonomy appear as | | 1428 | recurring features. For example, confidentiality of communications can apply to governance of data at rest | | 1429 | and access management, but it is also part of a security metadata model [95]. | | 1430 | The operational taxonomy will overlap with small data taxonomies while drawing attention to specific | | 1431 | issues with Big Data [96], [97]. | c For further information, see the frameworks suggested by the Association for Information and Image Management (AIIM; http://www.aiim.org /) and the MIKE 2.0 Information Governance Association (). Figure 5: Security and Privacy Operational Taxonomy <!-- image --> - Device, User, Asset, Services, and Applications Registration: Includes registration of devices in machine to machine (M2M) and IoT networks, DRM-managed assets, services, applications, and user roles - Security Metadata Model - o The metadata model maintains relationships across all elements of a secured system. It maintains linkages across all underlying repositories.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, risk management framework, fips. General security reference material without sensitive content. Source: NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3."}]}
{"id": "nist_02328", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines on Security and Privacy in Public Cloud Computing provide? (Section 32) ce agreement are usually stipulated in multiple documents, which can typically include a Service Level Agreement (SLA), privacy policy, acceptable use policy, and terms of use [Bra10]. An SLA represents the understanding between the cloud consumer and cloud provider about the expected level of service to be delivered and, in the event that the provider fails to deliver the service at the level specified, the compensation available to the cloud consumer. The privacy policy documents information handling practices and the way consumer information is collected, used, and managed by the cloud provider, while the acceptable use policy identifies prohibited behaviors by cloud consumers. The terms of use cover other important details such as licensing of services, 2 The process to perform a risk analysis and manage risks is not discussed in this publication. For additional information, see NIST SP 800-30, Risk Management Guide for Information Technology Systems , and SP 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems , at limitations on liability, and modifications to the terms of the agreement. Privacy and security risks depend to a great extent on the terms established in the service agreement. Two types of service agreements exist: predefined non-negotiable agreements and negotiated agreements [Bra10, UCG10]. Non-negotiable agreements are in many ways the basis for the economies of scale enjoyed by public cloud computing. The terms of service are prescribed completely by the cloud provider. They are typically not written with attention to federal privacy and security requirements [CIO10a].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, risk management framework, fips. General security reference material without sensitive content. Source: Guidelines on Security and Privacy in Public Cloud Computing."}]}
{"id": "nist_02329", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST Cloud Computing Forensic Science Challenges provide? (Section 104) (Metadata) | N/A | [27], [35] | | FC-08 | Log capture | OD/BNA/RP/RE /MS | S (only applies to network logs involving dynamically assigned IP addresses) | Analysis (Metadata) | N/A | [24], [4], [34] | | FC-09 | Interoperability issues among Providers | RE | G (applies to most capabilities) | Architecture | Standards (Interoperabilit y) | [24], [4], [29], [36], [37], [38] | | FC ID | Short Title | Relevance of Essential Cloud Characteristics | Labeling of Challenge/Functional- Capabilities Correlation | Primary Category (Subcategory) | Related Category (Subcategory) | References | |---------|--------------------------------|------------------------------------------------|----------------------------------------------------------------------------------------------|----------------------------------|----------------------------------|------------------| | FC-11 | No single source for criminals | OD/BNA/RP/RE | S (only applies when multiple clouds are involved) | Architecture | Data Collection | [39], [40] | | FC-12 | Detection of the malicious act | OD/BNA/RP/RE | Q (applicability is limited to capabilities that may be vulnerable to steppingstone attacks) | Architecture | N/A | [39], [41], [15] | | FC ID | Short Title | Relevance of Essential Cloud Characteristics | Labeling of Challenge/Functional- Capabilities Correlation | Primary Category (Subcategory) | Related Category (Subcategory) | References | |---------|-------------------------------------------------------------|------------------------------------------------|--------------------------------------------------------------|----------------------------------|----------------------------------|-----------------------------------------| | FC-13 | Criminals access to low cost computing power | OD/BNA/RP/RE /MS", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Cloud Computing Forensic Science Challenges."}]}
{"id": "nist_02330", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events provide? (Section 103) | 2.30.9 Symantec DLP ...........................................................................................................481 | | 2.30.10 Cisco WSA .................................................................................................................481 | | 2.30.11 Tripwire IP360...........................................................................................................482 | | 2.30.11.1 Tripwire Log Center, Tripwire IP360, Tripwire Enterprise, and ArcSight ESM...........................................................................................................483 | | 2.30.12 FileZilla and ArcSight.................................................................................................485 | | 2.30.13 Cisco ISE and ArcSight...............................................................................................485 | | 2.30.14 Cisco WSA and ArcSight............................................................................................486 | | 2.30.15 Semperis DSP and ArcSight.......................................................................................486 | | 2.30.16 Symantec DLP and ArcSight ......................................................................................487 | .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_02331", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Policy Machine_ Features, Architecture, and Specification say about C.1 Semantic Definitions? (Part 1) According to Policy Machine_ Features, Architecture, and Specification, C.1 Semantic Definitions: C.1 Semantic Definitions The semantic description of an administrative command differs from a syntactic description or programming language representation. The semantic descriptions define the correct behavior expected of administrative commands, which is essential for maintaining the integrity of the PM as it transitions between states. The specifications should not be interpreted as programming statements, and instead should be interpreted as changes to model structures representing the authorization state, which occur when a command is correctly carried out. Behavioral aspects other than those related to access control are outside the scope of these descriptions, including other facets of security such as authentication and audit. Preconditions are defined for each administrative command. Preconditions denote requirements. They are expressed as a logical expression that must be satisfied for the command to be carried out. The preconditions for administrative commands ensure that the arguments supplied for the formal parameters of the command are of the correct type, and that the basic properties of the model are observed. The following conventions are observed in the semantic descriptions given below: - \uf0a7 The behavior of administrative commands is atomic; their effects are indivisible and uninterruptable. - \uf0a7 The main body of an administrative command specifies state changes for those model elements and relations that are affected by its conduct-the state of any unspecified element or relation is unaffected and remains unchanged. - \uf0a7 Model elements and relations, whose states are affected by the behavior of an administrative routine or command, are indicated with the prime symbol. - \uf0a7 All specified preconditions must be satisfied for the change of state described in the body of the routine or command to occur.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Policy Machine_ Features, Architecture, and Specification."}]}
{"id": "nist_02332", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2003 Annual Report say about SCALABLE QUANTUM INFORMATION NETWORK? (Part 1) According to Computer Security Division 2003 Annual Report, SCALABLE QUANTUM INFORMATION NETWORK: SCALABLE QUANTUM INFORMATION NETWORK Q uantum mechanics, the strange behavior of matter on the atomic scale, provides entirely new and uniquely powerful tools for computing and communications. This field could revolutionize many aspects of computing and secure communications, and could have enormous impacts in homeland security. Quantum computers could perform processing tasks that would take billions of years on conventional computers. They also could solve problems that conventional computers could not manage given realistic amounts of time, memory, and processing power. Exploiting quantum properties would be particularly valuable in cryptography, making codes that would be unbreakable by the best supercomputers of tomorrow, or breaking codes in seconds that could not be cracked in millions of years by the most powerful binary computers. Quantum information also can be used for remarkably secure communications. In this particular area, we are partnering closely with the Defense Advanced Research Projects Agency (DARPA). The objective of this NIST project is to develop an extensible quantum information test-bed and the scalable component technology essential to the practical realization of a quantum communication network. The test-bed will demonstrate quantum communication and quantum cryptographic key distribution with a high data rate. This test-bed, once developed, will provide a measurement and standards infrastructure that will be open to the DARPA QuIST (Quantum Information Science and Technology) community and will enable wideranging experiments on both the physical- and network-layer aspects of a quantum communication system. The infrastructure will be used to provide calibration, testing, and development facilities for the QuIST community. This project is one part of the broader Quantum Information Program at NIST.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2003 Annual Report."}]}
{"id": "nist_02333", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Identity and Risk Related Standards according to NIST Developing Trust Frameworks to Support Identity Federations According to Developing Trust Frameworks to Support Identity Federations, Identity and Risk Related Standards: - ISO/IEC 24760 Parts 1 - 3: A Framework for Identity Management. Explores core concepts of identity and identity management and their relationships and is applicable to any information system that processes identity information. http://www.iso.org/. - ISO 31000:2009: Risk management principles and guidelines . Provides principles, framework and a process for managing risk. 43170. - ISO/IEC DIS 29003: Identity Proofing and Verification . Currently under development. 62290.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Trust Frameworks to Support Identity Federations."}]}
{"id": "nist_02334", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-6 in NIST_SP_800-37r2_Risk_Management_Framework? (Part 42) Control AM-6: xisting common control providers and associated security and privacy plans; information security and privacy program plans; organization- and system-level security and privacy risk assessment results. Expected Outputs: List of common control providers and common controls available for inheritance; security and privacy plans (or equivalent documents) providing a description of the common control implementation (including inputs, expected behavior, and expected outputs). Primary Responsibility: Senior Agency Information Security Officer; Senior Agency Official for Privacy. Supporting Roles: Mission or Business Owner; Senior Accountable Official for Risk Management or Risk Executive (Function); Chief Information Officer; Authorizing Official or Authorizing Official Designated Representative; Common Control Provider; System Owner. Discussion: 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. Common controls may differ based upon a variety of factors, such as hosting location, system architecture, and the structure of the organization. The organization-wide list of common controls takes these factors into account. Common controls can also be identified at different levels of the organization (e.g., corporate, department, or agency level; bureau or subcomponent level; or individual program level).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: identity management, sso. Contains security framework guidance for authentication systems. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_02335", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Managing Information Security Risk_ Organization, Mission, and Information System View provide? (Section 26) Resources. The guidelines in this publication are applicable to all federal information systems other than those systems designated as national security systems as defined in 44 U.S.C., Section 3542. The guidelines have been broadly developed from a technical perspective to complement similar guidelines for national security systems and may be used for such systems with the approval of appropriate federal officials exercising policy authority over such systems. State, local, and tribal governments, as well as private sector organizations are encouraged to consider using these guidelines, as appropriate. This publication is intended to serve a diverse group of risk management professionals including: - Individuals with oversight responsibilities for risk management (e.g., heads of agencies, chief executive officers, chief operating officers); - Individuals with responsibilities for conducting organizational missions/business functions (e.g., mission/business owners, information owners/stewards, authorizing officials); - Individuals with responsibilities for acquiring information technology products, services, or information systems (e.g., acquisition officials, procurement officers, contracting officers); - Individuals with information security oversight, management, and operational responsibilities (e.g., chief information officers, senior information security officers, 10 information security managers, information system owners, common control providers); 9 An executive agency is: (i) an executive department specified in 5 U.S.C., Section 101; (ii) a military department specified in 5 U.S.C., Section 102; (iii) an independent establishment as defined in 5 U.S.C., Section 104(1); and (iv) a wholly owned government corporation fully subject to the provisions of 31 U.S.C., Chapter 91. In this publication, the term executive agency is synonymous with the term federal agency .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Managing Information Security Risk_ Organization, Mission, and Information System View."}]}
{"id": "nist_02336", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RS-0010 in Biometric Specifications for Personal Identity Verification? (Part 30) Control RS-0010: | | Tag | Len. | Value | | | | | | | | | 81 | 1 | Biometric type (i.e., modality, 08 = fingerprint) | 08 | | | | | | | | 82 | 1 | Biometric subtype (e.g., finger position) - These values shall be from ISO/IEC 19785-3:2007, NOT from [CARD-MIN].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Biometric Specifications for Personal Identity Verification."}]}
{"id": "nist_02337", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Architecture Design Process for Health Information Exchanges (HIEs) say about NIST Special Publications (SPs)? According to Security Architecture Design Process for Health Information Exchanges (HIEs), NIST Special Publications (SPs): NIST SP 800-25, Federal Agency Use of Public Key Technology for Digital Signatures and Authentication , October 2000. NIST SP 800-30, Risk Management Guide for Information Technology Systems, January 2002. NIST SP 800-39, Draft Managing Risk from Information Systems: An Organizational Perspective , April 2008. NIST SP 800-45, Version 2, Guidelines on Electronic Mail Security , February 2007. NIST SP 800-52, Guidelines for the Selection and Use of Transport Layer Security (TLS) Implementations , June 2005. NIST SP 800-53, Revision 3, Recommended Security Controls for Federal Information Systems and Organizations, August 2009. NIST SP 800-57, Recommendation for Key Management , March 2007. NIST SP 800-58, Security Considerations for Voice Over IP Systems , January 2005. NIST SP 800-63 Rev. 1, Draft Electronic Authentication Guide, December 2008. NIST SP 800-66, Revision 1, An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule , October 2008. NIST SP 800-77, Guide to IPsec VPNs , December 2005. NIST SP 800-92, Guide to Computer Security Log Management , September 2006. NIST SP 800-106, Randomized Hashing Digital Signatures , July 2008. NIST SP 800-111, Guide to Storage Encryption Technologies for End User Devices , November 2007. NIST SP 800-113, Guide to SSL VPNs , July 2008. NIST SP 800-122, Guide to Protecting the Confidentiality of Personally Identifiable Information (PII) , April 2010.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Security Architecture Design Process for Health Information Exchanges (HIEs)."}]}
{"id": "nist_02338", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.3.4 Pre-shared Secret Key (PSK) Authentication according to NIST Guide to IPsec VPNs According to Guide to IPsec VPNs, 3.3.4 Pre-shared Secret Key (PSK) Authentication: PSK-based authentication is often deployed because it is the easiest to configure. Each end of the communication has the identity of the other end and their PSK. It does not require generating public keys or certificates or running an EAP infrastructure. It is most commonly used for gateway-to-gateway deployments as it does not involve adding a third-party trust anchor to the VPN gateway device. Some deployments use a PSK for authentication that is shared between the VPN server and all of the remote access VPN clients. Once the PSK has been obtained by an attacker, it can be used to impersonate any client or the remote access VPN server itself. Even if the clients are using onetime passwords (OTPs), a man-in-the-middle attacker can obtain an OTP and log in as the remote user to the real remote access VPN. Therefore, group PSKs are strongly discouraged. 29 DNSSEC is a system of digital signatures to authenticate DNS content. The DNSSEC core specifications are defined in IETF RFCs 4033, 4034, and 4035. PSKs are often derived from dictionary words and are less than 32 characters long. Such insecure deployments are vulnerable to offline dictionary attacks. 30 PSKs must have a high entropy value. A good PSK is pseudorandomly created and has at least 128 bits of entropy.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to IPsec VPNs."}]}
{"id": "nist_02339", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is NOTICE according to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities? NOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities."}]}
{"id": "nist_02340", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 929) ations include policy or regulatory, technology, physical infrastructure, system component allocation, public access, scalability, common control, operational or environmental, and security objective. APPENDIX A PAGE 415 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ security [CNSSI 4009] security attribute security categorization security category [OMB A-130] security control [OMB A-130] A condition that results from the establishment and maintenance of protective measures that enable an organization to perform its mission or critical functions despite risks posed by threats to its use of systems. Protective measures may involve a combination of deterrence, avoidance, prevention, detection, recovery, and correction that should form part of the organization\u2019s risk management approach. An abstraction that represents the basic properties or characteristics of an entity with respect to safeguarding information. Typically associated with internal data structures\u2014 including records, buffers, and files within the system\u2014and used to enable the implementation of access control and flow control policies; reflect special dissemination, handling or distribution instructions; or support other aspects of the information security policy. The process of determining the security category for information or a 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. See security category.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02341", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for Derived Personal Identity Verification (PIV) Credentials say about 1.2 Purpose and Scope? (Part 1) According to Guidelines for Derived Personal Identity Verification (PIV) Credentials, 1.2 Purpose and Scope: 1.2 Purpose and Scope This document provides guidelines for cases in which the use of PIV Cards with mobile devices, using either contact card readers or NFC, is deemed impractical. This guideline specifies the use of tokens with alternative form factors to the PIV Card that may be inserted into mobile devices, such as Secure Digital (SD) cards, USB tokens, Universal Integrated Circuit Cards (UICC, the new generation of SIM cards), or that are embedded in the mobile device. The embedded tokens may be either hardware or software cryptographic modules. The use of tokens with alternative form factors greatly improves the usability of electronic authentication from mobile devices to remote IT resources, while at the same time maintaining the goals of HSPD-12 for common identification that is secure, reliable and interoperable governmentwide. The scope of the Derived PIV Credential is to provide PIV-enabled authentication services on the mobile device to authenticate the credential holder to remote systems as illustrated in Figure 1-1. This publication also includes an informative annex that provides recommendations for the inclusion of digital signature and key management keys on mobile devices. To achieve interoperability with the PIV infrastructure and its applications, public key infrastructure (PKI) technology has been selected as the basis for the Derived PIV Credential. The PKI-based Derived PIV Credentials specified in this document are issued at levels of assurance (LOA) 3 and 4. 3 <!-- image --> Figure 1-1 Use of Derived PIV Credential Derived PIV Credentials are based on the general concept of derived credential in [SP800-63], which leverages identity proofing and vetting results of current and valid credentials. When applied to PIV, identity proofing and vetting processes do not have to be repeated to issue a Derived PIV Credential. Instead, the user proves possession of a valid PIV Card to receive a Derived PIV Credential.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, key management. Contains security framework guidance for authentication systems. Source: Guidelines for Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_02342", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IA-10 in Security and Privacy Controls for Information Systems and Organizations? Control IA-10: ADAPTIVE AUTHENTICATION Control: Require individuals accessing the system to employ [Assignment: organization-defined supplemental authentication techniques or mechanisms] under specific [Assignment: organization-defined circumstances or situations]. Discussion: Adversaries may compromise individual authentication mechanisms employed by organizations and subsequently attempt to impersonate legitimate users. To address this threat, organizations may employ specific techniques or mechanisms and establish protocols to assess suspicious behavior. Suspicious behavior may include accessing information that individuals do not typically access as part of their duties, roles, or responsibilities; accessing greater quantities of information than individuals would routinely access; or attempting to access information from suspicious network addresses. When pre-established conditions or triggers occur, organizations can require individuals to provide additional authentication information. Another potential use for adaptive authentication is to increase the strength of mechanism based on the number or types of records being accessed. Adaptive authentication does not replace and is not used to avoid the use of multi-factor authentication mechanisms but can augment implementations of multi-factor authentication. Related Controls: IA-2, IA-8. Control Enhancements: None. References: [SP 800-63-3].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor. Contains security framework guidance for authentication systems. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02343", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings say about References? (Part 1) According to 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings, References: References - [1] ISO 9594-8/ITU-T Rec. X.509 (2000) The Directory: Public-key and attribute certificate frameworks - [2] ISO SC 6 N12596 'Proposed Draft Amendment on Enhancements to PublicKey and Attribute Certificates', Geneva output, March 2004 - [3] C. Adams, S. Farrell. 'Internet X.509 Public Key Infrastructure Certificate Management Protocols'. RFC 2510, March 1999 - [4] Kaliski, B., \"PKCS #10: Certificate Request Syntax, Version 1.5.\" RFC 2314, March 1998. - [5] D.W.Chadwick, A. Otenko, E.Ball. 'Role-based access control with X.509 attribute certificates', IEEE Internet Computing, March-April 2003, pp. 62-69. [6] ITU-T Recommendation X.680 (1997) | Information Technology - Abstract Syntax Notation One 6. ISO/IEC 8824-1:1998, (ASN.1): Specification of Basic Notation - [7] D.W.Chadwick, A. Otenko. 'RBAC Policies in XML for X.509 Based Privilege Management' in Security in the Information Society: Visions and Perspectives: IFIP TC11 17 th Int. Conf. On Information Security (SEC2002), May 7-9, 2002, Cairo, Egypt. Ed. by M. A. Ghonaimy, M. T. ElHadidi, H.K.Aslan, Kluwer Academic Publishers, pp 39-53. - [8] T.Parker, D.Pinkas. 'Sesame V4 Overview', Issue 1, Dec 1995. Available from 9. me/html/sesame\\_documents.html - [9] Standard ECMA-219 \"Authentication and Privilege Attribute Security Application with Related Key Distribution Functions\" Parts 1, 2 and 3, December 1994. - [10] J. Kohl, C. Neuman. 'The Kerberos Network Authentication Service (V5).' RFC 1510, Sept 1993. - [11] C. Ellison, B. Frantz, B. Lampson, R. Rivest, B. Thomas, T. Ylonen. 'SPKI Certificate Theory'. RFC 2693, Sept 1999. - [12] Ron Rivest and Butler Lampson, \"SDSI -A Simple Distributed Security Infrastructure [SDSI]\", See &lt; - [13] S. Tuecke, V. Welch, D. Engert, L. Pearlman, M. Thompson.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02344", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain B.4 Additional Properties on Existing Data Elements according to NIST Specification for Asset Identification 1.1 According to Specification for Asset Identification 1.1, B.4 Additional Properties on Existing Data Elements: The XML schema also provides extension points on most XML elements to allow for tracking metadata about Asset Identification information, such as classification level, sensitivity, or other organizationspecific data. As long as Asset Identification elements are able to validate against the core schema and conform to the requirements of this specification, these extensions and the Asset Identification elements are valid.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Specification for Asset Identification 1.1."}]}
{"id": "nist_02345", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.16.6 Policy Enforcement: Developing Policy Conditions according to NIST Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events According to Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events, 2.16.6 Policy Enforcement: Developing Policy Conditions: 1. Navigate to Policy &gt; Policy Elements &gt; Conditions &gt; Posture. 2. Expand the Posture section. This will reveal a list of categories for conditions. (Note: These conditions allow you to select or define requirements that endpoints should meet. In typical enterprises, these conditions can be used as requirements to gain network access-however, this strongly depends on the capabilities of your network device.) 3. As an example, we will require that Cisco AMP be installed on all Windows devices. If you are using a different anti-malware software, locate that instead. Click Anti-Malware Condition. <!-- image --> 4. Click Add. 5. Enter a name. 6. Enter a description if desired. 7. Select Windows All for Operating System. 8. Select Cisco Systems, Inc. for Vendor. 9. Under Products for Selected Vendor, check the box next to Cisco Advanced Malware Protection with the version number you have installed. <!-- image --> 10. Click Submit.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_02346", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Additional Information according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, Additional Information: Additional information about this publication is available at including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02347", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report of the Workshop on Cryptography in Support of Computer Security say about 4.2 Discussion? (Part 2) According to Report of the Workshop on Cryptography in Support of Computer Security, 4.2 Discussion: o suggest that the present algorithm can be used in much more secure ways, for instance cascading, which doubles the effective key. TUCHMAN: The algorithm as published is precisely what IBM submitted. The responsibility for the algorithm rests solely with IBM, not with NSA, and certainly not with NBS. We analyzed the algorithm extensively, and found no short cuts at all. The purpose of the structure in the S-boxes is to make a stronger algorithm. It is only an accident that NSA has an interest in keeping the design principles secret. There is no collusion. DIFFIE ( Stanford University): How can we have a FIPS standard based on classified design principles? HELLMAN: We have brought up many questions. When will they be addressed? I am prepared to agree that the DES is probably the best standard that could be promulgated at the present time. But I feel it necessary that the classified material involved be declassified. SCANTLIN: I would like to review with you the work that we have done privately on the algorithm. It is clear that the S-boxes are critical to the strength of the algorithm. There are many choices of S-boxes that would certainly result in a weak algorithm and it is by no means clear that the present choice is not weak. The strong potential of a trap door puts us in the place of an antagonist. Since important information was withheld, we tried to evaluate the strength of the algorithm. The results were not reassuring. The NBS position is that the algorithm resists all attacks except brute force, but we are able to reduce the work by a factor of two using analytical methods and we see much potential for further reduction. We are concerned about possible trap doors and about the short key. We feel that a standard must be completely visible. We also feel that IBM is placed at an advantage in producing the chip because it is keeping the design secret. We do not think this is proper for a standard.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, secret. Contains guidance on protecting sensitive government information. Source: Report of the Workshop on Cryptography in Support of Computer Security."}]}
{"id": "nist_02348", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications provide? (Section 44) but supplied by the testing code: - \u03b5 The sequence of bits as generated by the RNG or PRNG being tested; this exists as a global structure at the time of the function call; \u03b5 = \u03b5 1 , \u03b5 2 , \u2026 , \u03b5 n . - sobs : The absolute value of the sum of the Xi (where, Xi = 2 \u03b5 - 1 = \u00b1 1) in the sequence divided by the square root of the length of the sequence. The reference distribution for the test statistic is half normal (for large n ). (Note: If z (where z = 2 ; see Section 3.1) is distributed as normal, then | z | is distributed as half normal.) If the s obs sequence is random, then the plus and minus ones will tend to cancel one another out so that the test statistic will be about 0. If there are too many ones or too many zeroes, then the test statistic will tend to be larger than zero. - (1) Conversion to \u00b1 1: The zeros and ones of the input sequence ( \u03b5 ) are converted to values of -1 and +1 and are added together to produce Sn = X1 + X2 + \uf04c + Xn , where Xi = 2 \u03b5 i - 1. <!-- formula-not-decoded --> <!-- formula-not-decoded --> 2 For the example in this section, sobs = = .632455532. 10 <!-- formula-not-decoded --> <!-- formula-not-decoded --> If the computed P-value is &lt; 0.01, then conclude that the sequence is non-random. Otherwise, conclude that the sequence is random. Since the P-value obtained in step 3 of Section 2.1.4 is \u2265 0.01 (i.e., P-value = 0.527089), the conclusion is that the sequence is random. Note that if the P-value were small (&lt; 0.01), then this would be caused by or being large. Sn s obs Large positive values of Sn are indicative of too many ones, and large negative values of Sn are indicative of too many zeros. It is recommended that each sequence to be tested consist of a minimum of 100 bits (i.e., n \u2265 100 ).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications."}]}
{"id": "nist_02349", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2017 NIST_ITL Cybersecurity Program Annual Report say about EXTERNAL PUBLICATIONS? According to 2017 NIST_ITL Cybersecurity Program Annual Report, EXTERNAL PUBLICATIONS: The following journal articles and conference papers were published during FY 2017. For conference papers, the contributions listed below were either i) accepted for a conference held during FY 2017, or ii) accepted for a conference held prior to FY 2017 with final proceedings published in FY 2017 (and not listed in an earlier Annual Report). All NIST authors are identified using italics ; publications are arranged alphabetically by author. Links to document preprints are available at https:/ /csrc.nist.gov/publications.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02350", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2012 Annual Report say about \u0091\u0091 Enumerations:? According to Computer Security Division 2012 Annual Report, \u0091\u0091 Enumerations:: - \u0091 Common Platform Enumeration (CPE), a nomenclature anGLYPH(cmap:df00) GLYPH(cmap:df00)ictionary of harGLYPH(cmap:df00)ware, operating systems, and applications; - \u0091 Common Configuration Enumeration (CCE), a nomenclature anGLYPH(cmap:df00) GLYPH(cmap:df00)ictionary of software security configurations; anGLYPH(cmap:df00) - \u0091 Common Vulnerabilities and Exposures (CVE), a nomenclature and dictionary of security-relateGLYPH(cmap:df00) software flaws;", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_02351", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TA-0 in Guidelines for Managing the Security of Mobile Devices in the Enterprise? (Part 32) Control TA-0: ted supply chain attack against a single organization or group of individuals, choosing validated devices and software and using a vetted system integrator can help mitigate the risk of broad attacks. NIST's Cryptographic Algorithm Validation Program (CAVP) 'provides validation testing of [Federal Information Processing Standards] FIPS-approved and NIST-recommended cryptographic algorithms and their individual components [13],' while the NIST Cryptographic Module Validation Program (CMVP) validates cryptographic module implementations against the Security Requirements for Cryptographic Modules [17]. The National Security Agency's (NSA) National Information Assurance Partnership (NIAP) [7] is responsible for implementation of the internationally recognized Common Criteria. throughout the Federal Government. Products certified through the Common Criteria program are evaluated for conformance with specific security protection profiles. NIAP's product compliance list identifies evaluated products and may be searched by vendor, technology type, protection profiles, and certifying country [8]. NSA's Commercial Solutions for Classified Program (CSfC) [9][10] also 'requires specific, selectable requirements to be included in the Common Criteria evaluation' and provides a list of software or hardware systems [33], including MDM and mobile platforms, that meet these more stringent requirements. In addition, CSfC provides a Trusted Integrator List [11], which identifies companies that have met its criteria for trustworthy systems integration capabilities. Organizations are encouraged to use lists of validated products and vetted system integrators to reduce the risk of acquiring devices or software with embedded vulnerabilities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, national security. Contains guidance on protecting sensitive government information. Source: Guidelines for Managing the Security of Mobile Devices in the Enterprise."}]}
{"id": "nist_02352", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.2 Functions according to NIST Guide to Computer Security Log Management According to Guide to Computer Security Log Management, 3.2 Functions: Log management infrastructures typically perform several functions that assist in the storage, analysis, and disposal of log data. These functions are normally performed in such a way that they do not alter the original logs. 23 The following items describe common log management infrastructure functions:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Computer Security Log Management."}]}
{"id": "nist_02353", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PA-220 in Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)? (Part 211) Control PA-220: the management interface, domain name system (DNS), and network time protocol (NTP). The management interface allows the administrator to configure and implement security rules through this interface. ## 2.5.2.1 Configure Management Interface The following steps will configure the Palo Alto Networks appliance management interface. 1. In the Palo Alto Networks portal, navigate to Device &gt; Setup &gt; Interfaces. 2. On the Interfaces tab, enable the Management option; the Management Interface Setting page opens. 3. On the Management Interface Setting screen: - a. In the IP Address field, enter the IP address for the Palo Alto Networks appliance. - b. In the Netmask field, enter the netmask for the network. - c. In the Default Gateway field, enter the IP address of the router that provides the appliance with access to the internet. - d. Under Administrative Management Services: Enable the Hypertext Transfer Protocol (HTTP) , Hypertext Transfer Protocol Secure (HTTPS) , Secure Shell (SSH) , and Ping options. - e. Click OK. Figure 2-29 Palo Alto Networks Management Interface Enabled <!-- image --> Figure 2-30 Management Interface Configuration <!-- image --> 4. To verify the configuration, navigate to Palo Alto Networks Portal &gt; Dashboard; the General Information section should reflect the appliance's network configuration. Figure 2-31 Palo Alto Networks Firewall General Information <!-- image --> ## 2.5.2.2 Configure DNS and NTP 1. In the Palo Alto Networks Portal , navigate to Device &gt; Setup &gt; Services. 2. In the Services tab, select the gear icon. Figure 2-32 Palo Alto Networks Services Configuration <!-- image --> 3. On the Services &gt; Services tab: - a. For the Primary DNS Server field, enter the primary DNS server IP address. - b. For the Secondary DNS Server field, enter the secondary DNS server IP address, if applicable. 4. Select the NTP tab. Figure 2-33 DNS Configuration <!-- image --> ## 5. On the NTP tab: - a.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_02354", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-09 in A Report on the Privilege (Access) Management Workshop? (Part 24) Control AM-09: entifies a number of factors to consider when planning an enterprise's access control system. This report pays quite a bit of attention to access control even though the focus is privilege management. This is because the characteristics and features of an access control system determine the requirements for the associated privilege management system. At the same time, an organization's capabilities to perform privilege management functions, if they cannot meet those requirements, limit the capabilities of the access control system to what is feasible. Practitioners and researchers in computer security generally distinguish among access control policies, mechanisms, and models. Policies are high-level requirements that specify how access is managed, expressing who or what should be granted or denied access to what resources. Mechanisms implement policies in a system. For example, policies might be captured as rules that a policy decision point uses, in addition to attributes about the requester and the resources, to determine whether an access request should be granted or denied. Models are used to describe and, in some cases to prove, security properties of an access control system. In short, a policy specifies access control requirements, a mechanism implements the requirements, and a model proves or describes things about the system that uses that policy and mechanism. The interested reader will find extensive discussion of these points in [FERR-07]. However, for our purposes in this report, we do not need to distinguish models and mechanisms from each other; it suffices to think about access control methods-that is, ways of doing access control. So, while an access control list (ACL) is a mechanism and role-based access control (RBAC) is a model, both are methods of access control. For the remainder of this report, then, we will refer to both models and mechanisms as methods of access control.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: A Report on the Privilege (Access) Management Workshop."}]}
{"id": "nist_02355", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Metrics and Key Performance Indicators for Robotic Cybersecurity Performance Analysis say about 5 APPENDIX A - DESCRIPTION OF MEASUREMENTS AND KPI? (Part 3) According to Metrics and Key Performance Indicators for Robotic Cybersecurity Performance Analysis, 5 APPENDIX A - DESCRIPTION OF MEASUREMENTS AND KPI: | | ID | 1.2 | |-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Name | Station Timers ( \ud835\udc60\ud835\udc60 \ud835\udc43\ud835\udc43 \ud835\udc46\ud835\udc46 , \ud835\udc60\ud835\udc60 \ud835\udc39\ud835\udc39 \ud835\udc46\ud835\udc46 , \ud835\udc60\ud835\udc60 \ud835\udc3c\ud835\udc3c \ud835\udc46\ud835\udc46 ) | | Description | Accumulation of time a station is in any valid state | | Unit of measure | seconds | | Notes | Simulated machining stations have three operating states: \u2022 Processing - station is loaded and the part is being processed \u2022 Finished - station is loaded and waiting for the robot to remove the part \u2022 Idle - station is unloaded and waiting for a part to be delivered | | ID | 1.3 | |-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Name | Batch Timer ( \ud835\udc4f\ud835\udc4f \ud835\udc43\ud835\udc43 ) | | Description | Total amount of time required for the batch to be produced | | Unit of measure | seconds | | Notes | The timer is started after the operator puts the enclave into the operational state, and is stopped when enclave operations end (automatic or operator shutdown).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Metrics and Key Performance Indicators for Robotic Cybersecurity Performance Analysis."}]}
{"id": "nist_02356", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EC-62443 in 2017 NIST_ITL Cybersecurity Program Annual Report? (Part 143) Control EC-62443: with its Internet Engineering Task Force (IETF) partners, completed the design and standardization of the BGPsec Protocol Specification (RFC8205) and <!-- image --> supporting specifications. BGPsec provides the ability to use digital signatures to prevent both malicious and accidental unauthorized routing messages from effecting Internet global routing operations. <!-- image --> In addition to standards development, NIST developed and released an open source reference implementation of emerging IETF BGPsec specifications, on-line test tools to foster their adoption and measurement systems to track their operational deployment. Figure 37 is a visualization generated by one such monitoring tool that shows the current state of Route Origin Authorizations (ROAs) in the global Resource Public Key Infrastructure (RPKI). The RPKI has been designed to provide the trust infrastructure upon which Internet routing security technologies can be based. In FY 2017, as BGPsec and RPKI technology specifications and implementations matured, ITL shifted its efforts to focus on technology transition and operational issues associated with the new secure routing technologies. The ITL staff and its collaborators published research results on highspeed BGPsec implementations that attempt to minimize the operational performance impact of routing security. Figure 38 illustrates a prototype model for investigating and validating the emerging BGP security extensions and supporting protocols. Figure 37: Measurement of global networks with most BGP announcements protected by RPKI.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, pki, sso. Contains security framework guidance for authentication systems. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02357", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Review of the Advanced Encryption Standard say about 3.1 Security Requirements? (Part 1) According to Review of the Advanced Encryption Standard, 3.1 Security Requirements: 3.1 Security Requirements The AES call for submissions [41] stated that one of the factors on which algorithms would be judged is 'the extent to which the algorithm output is indistinguishable from a random permutation on the input block.' This means that AES encryption must behave as a 'pseudorandom permutation' (PRP). It is often implicit that the inverse operation (decryption) should be indistinguishable from random as well, but this requirement can be made explicit by using the term 'strong PRP' or 'super PRP.' Consider, for example, a challenge-response protocol where the challenge is the plaintext, and the response is the ciphertext of the AES operation. 1 An attacker may generate a certain number of challenges (and observe the responses) while having access to the device. If the AES output is distinguishable from random, the attacker would be able to predict the response to a new challenge with a probability higher than 2 -128 (i.e., higher than the probability of guessing a randomly generated 128-bit ciphertext). Clearly, the indistinguishability property implies that it should not be possible for the attacker to recover the secret key, which would make it trivial to compute the response to any challenge. This requires an evaluation of whether the AES key lengths (i.e., 128, 192, and 256 bits) are sufficiently long to resist exhaustive key search in the foreseeable future, taking the advent of quantum computing into consideration. To quantify security in this setting, the number of input-output pairs available to the attacker and the success probability of the attack are relevant as well. Applications may implicitly or explicitly assume that the number of input-output pairs available to the attacker is limited.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Review of the Advanced Encryption Standard."}]}
{"id": "nist_02358", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Derived Personal Identity Verification (PIV) Credentials provide? (Section 2) 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. 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-157 Natl. Inst. Stand. Technol. Spec. Publ. 800-157, 33 pages (December 2014) http://dx.doi.org/10.6028/NIST.SP.800-157 CODEN: NSPUE2 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. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. All NIST publications, other than the ones noted above, are available at ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_02359", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Framework for Emergency Response Officials (ERO)_ Authentication and Authorization Infrastructure provide? (Section 23) nication between relying parties (such as an Incident Commander) and Authoritative source of Credential (ASC) - the EMA that provides the responding EROs often takes place through these trust brokers. From a standards perspective, this communication has two characteristics: It has to use any of the standard protocol, such as de-facto federated web-based protocols such as SAML, WS-* or SOAP The credentialing schema, while it could be customized for the ERO domain, should be based on a standard data modeling scheme such as a Relational Schema, LDAP schema or XML Schema. With a customized data schema for credential repositories, a Meta Data Service that provides a common view of the syntax and semantics of various ERO capabilities may be required. As previously stated, examples of capabilities include Qualification, Training, Licensing, and Skill Certification documents for various Emergency Response functions as well as apriori deployment agreements among the ERO-AA infrastructure players such as Emergency Management Assistance Compacts (EMACs). A number of technical and procedural standards are central to specifying the components of the framework for ERO-AA infrastructure described in this document. The primary standards are: - Federal Information Processing Standard 201 - Personal Identity Verification (FIPS 201) and its companion documents : These documents specify procedures for identity proofing, the set of credentials and authentication use cases for identity verification, the standardized formats for representation of credentials, procedures for digitally signing credentials and attesting the digital signatures and credentials. and - ISO/IEC 24727- Identification Cards - integrated circuit card programming interfaces,, which provides a set of interfaces for secure, interoperability among diverse applications with normative processes for Identity, Authentication, and Signature (IAS)services.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Framework for Emergency Response Officials (ERO)_ Authentication and Authorization Infrastructure."}]}
{"id": "nist_02360", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.4.2.2. MFA Implemented at State Agency Identity Service according to NIST Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information, 3.4.2.2. MFA Implemented at State Agency Identity Service: Alternatively, agencies may seek to integrate their state portal with a dedicated identity service platform, as Fig. 12 depicts. This option will likely provide agencies with a greater level of authenticator optionality and potential for authenticator reuse. Fig. 12. Common architecture for implementing MFA at state agency identity service. <!-- image --> Agencies should consult with their vendor to determine which authenticator types -including phishing-resistant authenticators -are supported, as well as which identity federation protocols the vendor can implement. State agencies should discuss with vendors and local jurisdictions the possibility of integrating the state identity solution with local agency identity services so that local agency users accessing the state portal can reuse any MFA they have implemented at their home agency. <!-- image --> Tip: State agencies commonly manage user accounts and credentials for their state CJIS portal, serving as the IdP for users across the state. The cost of this function, both in upfront costs of procuring and implementing MFA and in ongoing costs in help desk support and authenticator lifecycle management, might be alleviated if local, tribal, and territorial agencies had the option to integrate their local identity services with the state portal using identity federation protocols. Section 3.4.2.3 details an example architecture that supports this functionality.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, mfa. Contains security framework guidance for authentication systems. Source: Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information."}]}
{"id": "nist_02361", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3 say about Selected References? (Part 2) According to NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3, Selected References: Available: | Brief Description | Safety Level 1 | Safety Level 2 | Safety Level 3 | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Support for user annotation, notification, advisories | Support for user annotation, notification, advisories | Support for user annotation, notification, advisories | Support for user annotation, notification, advisories | | To address user and enterprise safety concerns, a Big Data system should support consumer, \"user,\" subscriber natural language annotations, notifications, and explanations.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3."}]}
{"id": "nist_02362", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cell Phone Forensic Tools_ an Overview and Analysis say about Graphics Library? According to Cell Phone Forensic Tools_ an Overview and Analysis, Graphics Library: The graphics library enables examiners to examine the collection of graphics files present on the device. Each image present can be viewed internally with the Picture Window application, allowing examiners to enlarge images if necessary. Additionally, images collected can be exported and inspected with a third party tool, if necessary. Figure 33 shows a screen shot of images acquired from a Nokia 6610i. Figure 33: Graphics Library <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_02363", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Validating the Integrity of Computing Devices say about 3.6 Technologies? (Part 2) According to Validating the Integrity of Computing Devices, 3.6 Technologies: Table 3-5 Products and Technologies | Component | Product/Technology | Function/Capability | Cybersecurity Framework Subcategories | |-------------------------------------|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------| | Component or Subsystem Manufacturer | Intel Transparent Supply Chain | Tools and processes to ensure supply chain security from the manufacturer to the purchasing organization | ID.SC-4, PR.DS- 6 | | Component or Subsystem Manufacturer | Seagate EXOS X18 18 Terabyte Hard Drive | Secure device authentication, firmware attestation | ID.SC-4, PR.AC- 6, PR.DS-6, PR.DS-8 | | OEM or VAR | Dell Technologies | Manufactures computing devices and binds them to verifiable artifacts | ID.SC-4 | | OEM or VAR | Hewlett Packard Enterprise | Manufactures computing devices and binds them to verifiable artifacts | ID.SC-4 | | OEM or VAR | HP Inc.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Validating the Integrity of Computing Devices."}]}
{"id": "nist_02364", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case say about Training for Users and Managers? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case, Training for Users and Managers: Employees must perform online computer-based training or classroom-based training per management approval. Below is an example list of potential training options. Trade organization subscriptions to newsletters and magazines will offer more industry specific training classes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case."}]}
{"id": "nist_02365", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Secure Domain Name System (DNS) Deployment Guide provide? (Section 40) | | | | Guidelines on Securing Recursive Servers (Resolver) & Stub Resolvers ............ 12.1 Setting up the Recursive | Service........................................................................12-14 | | | 12.1.2 Securing the Host Platform for Recursive Servers/Resolvers................. 12.2 Guidelines for Establishing Servers....................................................................12-15 ................................................................................. | 12-14 | | | 12.2.1 Aggregate Caches | 12-15 | | | 12.3 Setting up the Root Hints 12.5 Recommendations Summary | File.............................................................................12-17 | | 13.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Domain Name System (DNS) Deployment Guide."}]}
{"id": "nist_02366", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.1.3 FIDO and Authenticator Types according to NIST Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders According to Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders, 4.1.3 FIDO and Authenticator Types: When considering MFA implementations, PSFR organizations should carefully consider organizationally defined authenticator requirements. These requirements are detailed in Section C.3 of Appendix C. FIDO provides a standard framework within which vendors have produced a wide range of interoperable biometric, hardware, and software authenticators. This will enable PSFR organizations to choose authenticators suitable to their operational constraints. The FIDO Alliance has published specifications for two types of authenticators based on UAF and U2F. These protocols operate agnostic of the FIDO authenticator, allowing PSOs to choose any FIDO-certified authenticator that meets operational requirements and to implement it with this solution. The protocols, FIDO key registration, FIDO authenticator attestation, and FIDO deployment considerations are also detailed in Section C.3 of Appendix C.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, mfa, single sign-on. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_02367", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Card Technology Developments and Gap Analysis Interagency Report say about STANDARDS MATRIX? (Part 5) According to Card Technology Developments and Gap Analysis Interagency Report, STANDARDS MATRIX: Methods - Part 5: Optical Memory Cards | Optical Data Storage | | Standard | ISO/IEC 11693 | 1993 ID Cards - Optical Memory Cards | Optical Data Storage | | Standard | ISO/IEC 11694-1 | 1994 ID Cards - Optical Memory Cards Linear recording method Part 1: Physical Characteristics | Optical Data Storage | | Standard | ISO/IEC 11694-2 | 1994 ID Cards - Optical Memory Cards Linear recording method Part 2: Dimensions and location of the accessible op | Optical Data Storage | | Standard | ISO/IEC 11694-3 | ID Cards - Optical Memory Cards Linear recording method Part 3: Optical properties and characteristics | Optical Data Storage | | Standard | ISO/IEC 11694-4 | ID Cards - Optical Memory Cards Linear recording method Part 4: Logical data structures | Optical Data Storage | E-2", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Card Technology Developments and Gap Analysis Interagency Report."}]}
{"id": "nist_02368", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Cloud Computing Forensic Reference Architecture say about cloud consumer? According to NIST Cloud Computing Forensic Reference Architecture, cloud consumer: A person or organization that maintains a business relationship with and uses service from cloud providers. [22]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Cloud Computing Forensic Reference Architecture."}]}
{"id": "nist_02369", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RA-1 in Securing Wireless Infusion Pumps in Healthcare Delivery Organizations? (Part 129) Control RA-1: reless Infusion Pumps 96 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P 1 8 0 0 - 8 . . timeout xlate 3:00:00 timeout pat-xlate 0:00:30 timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 sctp 0:02:00 icmp 0:00:02 timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00 timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00 timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute timeout tcp-proxy-reassembly 0:01:00 timeout floating-conn 0:00:00 user-identity default-domain LOCAL aaa authentication ssh console LOCAL snmp-server host-group management SNMPHOSTS poll community ***** no snmp-server location no snmp-server contact snmp-server community ***** crypto ipsec security-association pmtu-aging infinite crypto ca trustpoint _SmartCallHome_ServerCA no validation-usage crl configure crypto ca trustpool policy auto-import crypto ca certificate chain _SmartCallHome_ServerCA certificate ca 6ecc7aa5a7032009b8cebcf4e952d491 308205ec 308204d4 a0030201 0202106e cc7aa5a7 032009b8 cebcf4e9 52d49130 0d06092a 864886f7 0d010105 05003081 ca310b30 09060355 04061302 55533117 30150603 55040a13 0e566572 69536967 6e2c2049 6e632e31 1f301d06 0355040b 13165665 72695369 676e2054 72757374 204e6574 776f726b 313a3038 06035504 0b133128 63292032 30303620 56657269 5369676e 2c20496e 632e202d 20466f72 20617574 686f7269 7a656420 75736520 6f6e6c79 31453043 06035504 03133c56 65726953 69676e20 436c6173 73203320 5075626c 69632050 72696d61 72792043 65727469 66696361 74696f6e 20417574 686f7269 7479202d 20473530 1e170d31 30303230 38303030 3030305a 170d3230 30323037 32333539 35395a30 81b5310b 30090603 55040613 02555331 17301506 0355040a 130e5665 72695369 676e2c20 NIST SP 1800-8C: Securing Wireless Infusion Pumps 97 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Securing Wireless Infusion Pumps in Healthcare Delivery Organizations."}]}
{"id": "nist_02370", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Labels for Open Systems_ an Invitational Workshop provide? (Section 34) ti-(set-)labelling (N-l)-facility | 11 | | 7. Summary of (N)-Facility Support | 11 | | 8. Support of a Fixed Label-Set Association | 13 | | 9. Support of Variable or Multiple Label-Set Associations | 14 | | 9.1 Support by variable- and multi- set-labelling facilities | 14 | | 9.2 Support by single-labelling facilities | 14 | | 10. Implementation Choices and Rationale | 16 | | References | 17 | C Gray Girling - 25 April 1990 This document provides some investigation of the means to provide the access control service, given a specific requirement: that access control should be providing using security labels at the application layer. This document investigates the options visible within an endsystem for the use of security labels in the implementation of an OSI communications protocol stack. Its scope is broader than that implied by the term Open System Interconnection because that would normally address issues visible only outside an endsystem. This document categorizes the strategies within an endsystem which can be used to support labelling. Although access control is an application layer requirement, the problem is examined from the point of view of a general layer (referred to as the (N&gt;layer). The interaction between solutions chosen for separate layers is then constrained so that the combination of layer solutions can support access control at the application layer. It is required that access control be exercised on the basis of a set of partially ordered SECURITY labels. The access control mechanism is to associate security labels with transmitted data, and ranges of security labels with application-process-invocations (apis).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Security Labels for Open Systems_ an Invitational Workshop."}]}
{"id": "nist_02371", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines provide? (Section 32) Threats to software update systems primarily target the evidence generation process so as to erase the trail of updates and prevent the ability to determine whether the updates were legitimate or not. There are several types of software update systems [11]: - Package managers that are responsible for all of the software installed on a system - Application updaters that are only responsible for individual installed applications 4 See https://securityscorecards.dev/ . - Software library managers that install software that adds functionality, such as plugins or programming language libraries. The primary task performed by a software update system is to identify the files that are needed for a given update ticket and download trusted files. At first glance, it may appear that the only checks needed to establish trust in downloaded files are the various integrity and authenticity checks performed by verifying the signatures on the metadata associated with individual files or the package. However, the very process of signature generation may be vulnerable to known attacks, so software update systems require many other security measures related to signature generation and verification. The evolving framework for providing security for software update systems has incorporated many of these required security measures into its specification and prescribed some others for future specifications. A framework is a set of libraries, file formats, and utilities that can be used to secure new and existing software update systems. The framework should protect the signing operation by requiring the policy defined in Sec. 5.1.1 to be satisfied prior to performing the signing operation.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines."}]}
{"id": "nist_02372", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD) provide? (Section 54) DigiCert are also used. The logical architectures and detailed descriptions of the builds mentioned above are in Section 6 (Build 1), Section 7 (Build 2), Section 8 (Build 3), and Section 9 (Build 4). 4.2 Physical Architecture Figure 4-2 depicts the high-level physical architecture of the NCCoE laboratory environment. As depicted, the NCCoE laboratory network is connected to the internet via the NIST data center. Access to NIST SP 1800-15B: Securing Small-Business and Home Internet of Things Devices 16 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 This publication is available freeof charge from:https://doi.org/10.6028/NIST.SP.1800-15 and from the NCCoE network is protected by a firewall. The NCCoE network includes a shared virtual environment that houses an update server, a MUD file server, an unapproved server (i.e., a server that is not listed as a permissible communications source or destination in any MUD file), a Message Queuing Telemetry Transport (MQTT) broker server, and a Forescout enterprise manager. These components are hosted at the NCCoE and are used across builds where applicable. DigiCert provided the Transport Layer Security (TLS) certificate and Premium Certificate used by the MUD file server. All four builds, as depicted in the diagram, have been implemented: \uf0a7 Build 1 network components consist of a Cisco Catalyst 3850-S switch, a Cisco MUD manager, a FreeRADIUS server, and a virtualized Forescout appliance on the local network. Build 1 also requires support from all components that are in the shared virtual environment, including the Forescout enterprise manager. \uf0a7 Build 2 network components consist of a MasterPeace Solutions, Ltd. Yikes! router on the local network. Build 2 requires support from the MUD file server, Yikes! cloud, and a Yikes! mobile application that are all resident on the Build 2 cloud. The Yikes!", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_02373", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Web Transactions_ TLS Server Certificate Management provide? (Section 67) TLS server certificates is infeasible due to the large number of certificates in most enterprises. It is also not feasible for each certificate owner to create their own certificate management system. The most efficient and effective approach is for the Certificate Services team to provide a central Certificate Service that includes technology-based solutions that provide automation and that support certificate owners in effectively managing their certificates. This service should include the technology/services for CAs, certificate discovery, inventory management, reporting, monitoring, enrollment, installation, renewal, revocation, and other certificate management operations. The central Certificate Service should also provide self-service access for certificate owners so they are able to configure and operate the services for their areas without requiring significant interaction with the Certificate Services team. Furthermore, the central Certificate Service should be able to integrate with other enterprise systems, including identity and access management systems, ticketing systems, configuration management databases, email, workflow, and logging and auditing. Approved CAs should be designated and made available to certificate owners for requesting public and internal certificates. If, as is common, different CAs will be used for issuing public and internal certificates, then instructions should be provided to certificate owners to help them select the correct CA based on the purpose of the server where the certificate will be used. Establish backup CAs for both public and internal certificates, including completing contracts with backup public CAs so an immediate cutover is possible in case of a CA compromise, for business reasons, or because of some other motivation. An up-to-date inventory of deployed TLS server certificates is the foundation of an effective certificate management program.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_02374", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TE-1 in Mobile Device Security_ Bring Your Own Device (BYOD)? (Part 3) Control TE-1: .1.2.1 Privacy Risk Examples and Mitigation Methodologies The example solution contained in this guide identifies and helps to mitigate some common privacy risks that a BYOD deployment may encounter. The privacy risks and their accompanying problematic data actions were identified using NIST-developed methodologies. The NIST PRAM [9] and accompanying Catalog of Problematic Data Actions and Problems [12] (see Section 4.1.2) are standardized methodologies for identifying privacy challenges that were used to conduct our privacy risk analysis. This publication provides the results of our privacy risk analysis for a f ictional organization as an exemplar for the reader's use, as well as suggested privacy architecture enhancements. See Appendix G of the Supplement for an example of how the privacy risks for this practice guide's BYOD deployment example solution were deve loped. The following section, 4.1.3, outlines the security and privacy objectives of this publication's example solution architecture. ## 4.1.3 Security and Privacy Objectives To address the challenges stated in the previous sections, the architecture for this build addresses the high-level security and privacy objectives illustrated in Figure 4-1. Figure 4-1 Security and Privacy Objectives <!-- image --> The following are a list of security and privacy objectives (as highlighted above in Figure 4-1, with a green exclamation mark): 1. Separate organization and personal information. BYOD deployments can place organizational data at risk by allowing it to travel outside internal networks and systems when it is accessed on a personal device. BYOD deployments can also place personal data at risk by capturing information from employee devices. To help mitigate this, organizational and personal information can be separated by restricting data flow between organizationally managed and - unmanaged applications.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_02375", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control BE-4 in IT Asset Management? (Part 62) Control BE-4: ki and two Windows 2012 Active Directory servers. One serves as primary while the other serves as a backup. Puppet Enterprise Master enforces security and configuration baselines across all endpoints. Physical Security -The physical security network houses the devices that operate and manage physical security, such as badge readers and cameras, along with their management consoles. The devices include Router4, iStar Edge, CCure controller, two badge readers and two Internet Protocol (IP) cameras. Physical Asset Management -The physical asset management network contains devices that provide and collect information regarding physical assets. The devices include Router3, AssetCentral and CA Technologies IT Asset Manager. AssetCentral is a physical asset inventory and analysis system from AlphaPoint Technology. It allows users to view assets from multiple viewpoints, including building, room, floor, rack, project, collection, or owner. AssetCentral is running on CentOS Linux. CA IT Asset Manager allows users to holistically manage IT hardware assets, from planning and requisition to retirement and disposal. ## 1.2.3 Operating Systems All machines used in the build had either Windows 7 enterprise, Windows server 2012 R2, Ubuntu 14.04, RedHat Enterprise Linux 7.1 or CentOS 7 operating systems (OSs) installed. ## 1.2.3.1 Base Windows Installation and Hardening Details The NCCoE base Windows OS images are Server 2012 R2 x86\\_64 and Windows 7 Enterprise x86\\_64 Department of Defense (DoD) Security Technical Implementation Guide (STIG) images. The installation of both Windows systems was performed using installation media provided by the Defense Information Systems Agency (DISA). These images were chosen because they are standardized, hardened and fully documented. ## 1.2.3.2 Base Linux Installation and Hardening Details The NCCoE base Linux OS is CentOS 7. This OS is available as an open source image. The OS was configured to meet the DoD CentOS 6, STIG.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IT Asset Management."}]}
{"id": "nist_02376", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automation Support for Security Control Assessments_ Software Asset Management say about 2.7 SWAM Specific Roles and Responsibilities? (Part 3) According to Automation Support for Security Control Assessments_ Software Asset Management, 2.7 SWAM Specific Roles and Responsibilities: or group of devices, device managers are (for HWAM) responsible for adding/removing devices from the network, and for configuring the hardware of each device (adding and removing hardware components). The device managers are specified in the desired state inventory specification. The device manager may be a person or a group. If a group, there is a group manager in charge. In the absence of a Software Manager (SWMan), the DM may be assigned the task of removing unauthorized software. | Operational | | Auth | Authorizers | Authorizers have the responsibility of authorizing specific items (e.g., devices, software, software installers, software locations, or settings), and thereby define the desired state. In special cases they authorize people to authorize other items. The desired state manager oversees and organizes the activity of authorization. | Operational | | DSM | Desired State Managers (DSM) | Desired State Managers are needed for both the ISCM Target Network and each assessment object. The desired state managers ensure that data specifying the desired state of the relevant capability is entered into the ISCM system's desired state data and is available to guide the actual state collection subsystem and to identify defects. The DSM for the ISCM Target Network also resolves any ambiguity about which system authorization boundary has defects (if any). Authorizers share some of the responsibilities by authorizing specific items (e.g., devices, software, or settings), and thus defining the desired state, as delegated by the DSM. The DSM oversees and organizes this activity. | Operational | | ISCM- Ops | ISCM Operators (ISCM-Ops) | ISCM operators are responsible for operating the ISCM system (see ISCM-Sys).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_02377", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Secure Data Network Systems (SDNS) Key Management Documents provide? (Section 65) | A.6. State Tables 33 | A.6. State Tables 33 | A.6. State Tables 33 | A.6. State Tables 33 | n. ^;tU't.' i/UKj i! , - \u20224' OV ^ jii-3yj.;-'i'^l'^a;^ta3ifi K !.r^ '.) 'yaLj-'^O \u2022 '3 a/5.rb*S 'itlH 't ..'... f/'. ;.'0' ^ '1 :Ki3i'ts&gt;(!;ireMv3'!! b&amp;Jq ci...i,iA . ^ r . . ' bJu'.'*] I'/t , vi SaO . . bboM.gJW ' &gt;i&gt;.i,fi -'-j i-i / i&gt;f 3\u2122 h\" m % i 'le&amp;ii-- .-n Lr,m':?^OC&gt;8 .X \u2022* ^ ' ', ii\\_Li , wxjiva^iddA =,|-J ^4inU V '\\' }f'^ '\u2022'tv'i'fddA. '.hS.. jo, '' \\ 5 ( '.\u00bb 0-3-^ 'v- ' M 0. This document specifies the protocol for the services provided to the Key Management Application Process (KMAP) by an application service element - the Key Management Application Service Element (KMASE) - to support applications in a distributed open systems environment. 1. Key management provides for the generation, distribution, and updating of traffic encryption keys (TEKs). Some management capabilites for authentication and access control are provided by the KMAP. This document specifies the protocol and procedures for the Key Management Application Service Element. The KMASE services are provided in conjunction with the Association Control Service Element (ACSE) and the presentation service. 2. The KMASE procedures are defined in terms of: - a) the interactions between cooperating KMASE protocol machines through the use of the presentation service; and - b) the interactions between the KMASE protocol machine and its service user. This document specifies conformance requirements for systems implementing these procedures. | ISO 7498/1 | Information Processing Systems - Open Systems Interconnection - Basic Reference Model.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, key management. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_02378", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NSTIC Pilots_ Catalyzing the Identity Ecosystem say about Existing practice and the need for a standard:? According to NSTIC Pilots_ Catalyzing the Identity Ecosystem, Existing practice and the need for a standard:: In order to establish a more effective market that is responsive to the complicated requirements that service providers face today, standardized performance metrics and reporting procedures need to be developed. Once created, these standards would allow organizations, government agencies, and other service providers to effectively implement risk-based access solutions to meet cybersecurity needs, protect users, and ensure availability of services. In order to help establish a common understanding of KBA and remote identity proofing services, it is proposed that standardized approaches are developed to: - 1) determine the accuracy and efficacy of KBA and remote proofing techniques. This may include requirements for the currency and validity of the information used in the proofing or the development of the KBA questions; and - 2) report failure rates of KBA systems. In addition to standardizing validity criteria for data and processes used in the proofing process or KBA question development, this standard will establish reporting requirements for false acceptance, false rejections, and failure to enroll.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NSTIC Pilots_ Catalyzing the Identity Ecosystem."}]}
{"id": "nist_02379", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) provide? (Section 116) eriods for the original certificate and all renewed certificates for the same key must not exceed the cryptoperiod of the key used to apply protection (i.e., the key with the originator usage period). An FCKMS could notify the owner of a certificate when a certificate is about to expire so that the certificate could be renewed prior to the end validity date on the certificate. FR:6.34 The CKMS design shall specify how and the conditions under which a public key can be renewed. FR:6.35 For each key type, the CKMS design shall specify requirements for advance notification of the key type renewal, including which parties are notified, how they are notified, what security services are applied to the notification, and the time-frames for notification(s). | PR:6.30 | A Federal CKMS shall not renew the validity period of a public key certificate beyond the cryptoperiod of the key of the key pair used to apply cryptographic protection (i.e., the originator usage period). | |-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | PF:6.3 | A Federal CKMS could notify the owner of a public-key certificate that the certificate is about to expire. | | PF:6.4 | A Federal CKMS could provide notification to the relying parties of a public key certificate that the certificate has been renewed. | When a key is derived from other information (some of which is secret) in a non-reversible manner, the process is called key derivation. Key update is a special case of key derivation in which the secret information includes a symmetric key (K1), and the derived symmetric key (K2) replaces K1 for the next key-update process. Key updating could result in a security exposure if an adversary obtains a key and knows the update process used. Key update is not supported in this Profile.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_02380", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Small Business Information Security_ The Fundamentals say about Appendix B-References? (Part 2) According to Small Business Information Security_ The Fundamentals, Appendix B-References: rting of Cyber Incidents , version 1.0, April 2015, ccips/legacy/2015/04/30/04272015reporting-cyber-incidents-final.pdf (accessed October 7, 2016). | | [EY14] | Ernst &Young, How to Use Cybersecurity to Generate Business Value , 2014, _How_to_use_cybersecurity_to_generate_business_value/$FILE/EY-CIO- How-to-use-cybersecurity.pdf (accessed October 7, 2016). | | [FBI] | Federal Bureau of Investigation, Identity History Summary Checks [Web page] , (accessed October 7, 2016). | | [FTC] | Federal Trade Commission, Data Security [Web page] , security (accessed October 7, 2016). | | [Grady05] | Grady, Mark F. and Francesco Parisi (eds.), The Law and Economics of Cybersecurity , Cambridge University Press, November 28, 2005. | |---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [HSPD23] | The White House, Cybersecurity Policy , National Security Presidential Directive (NSPD)-54/Homeland Security Presidential Directive (HSPD)-23, January 2008. | | [InfraGard] | InfraGard [Web site], (accessed October 7, 2016). | | [ISACA] | ISACA [Web site], https://isaca.org/ (accessed October 7, 2016). | | [ISO7498-2] | International Standardization Organization/International Electrotechnical Commission (ISO/IEC), Information processing systems-Open Systems Interconnection-Basic Reference Model-Part 2: Security Architecture , ISO/IEC 7498-2:1989, February 2, 1989.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Small Business Information Security_ The Fundamentals."}]}
{"id": "nist_02381", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Section 126) ations to be changed at organizational time intervals; system component inventory; change control records; configuration management records; system audit records; other relevant documents or records]. Interview : [ SELECT FROM: Organizational personnel responsible for information security; organizational personnel responsible for changing processing and/or storage locations; system/network administrators]. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | Test : [ SELECT FROM: Mechanisms supporting and/or implementing changing processing and/or storage locations]. | |------------------------------------------------------------------------------------------------------------------| | 3.14.1e | ENHANCED SECURITY REQUIREMENT Verify the integrity of [ Assignment: organization-defined security critical or essential software ] using root of trust mechanisms or cryptographic signatures. | ENHANCED SECURITY REQUIREMENT Verify the integrity of [ Assignment: organization-defined security critical or essential software ] using root of trust mechanisms or cryptographic signatures.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02382", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about C.1. Preparing for Assessments? (Part 3) According to Assessing Security Requirements for Controlled Unclassified Information, C.1. Preparing for Assessments: ----------------------------------------------------------------------------------------------------------------| | OUTCOMES | \u2022 The objective, scope, and time frame of the assessment are determined. \u2022 Key organizational stakeholders are notified, and the necessary resources are allocated. \u2022 Assessors are identified and selected. \u2022 Artifacts are collected and provided to assessors. \u2022 Mechanisms to minimize ambiguities and misunderstandings about the security requirements, implementation issues, and weaknesses/deficiencies identified during the assessment are established. \u2022 The organization's operations, structure, objective, scope, and time frame of assessment are understood by assessors. |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02383", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control OA-3 in Best Practices for Privileged User PIV Authentication? (Part 23) Control OA-3: grace period until transitioning to products that support direct or indirect verification architectures at LOA-3 or LOA-4 is possible. Figure 2 shows a high-level depiction of the proxy architecture. The proxy is placed between the user (Claimant) and the Relying Party, so that it is only possible to gain privileged access to the Relying Party after successfully authenticating to the proxy. The proxy needs to be PIV-enabled, and it may be PIV-enabled either by acting as the Verifier itself (direct verification) or by accepting identity assertions from a separate PIV-enabled Verifier (indirect verification). Figure 2: High-Level Transitional Proxy Architecture <!-- image --> Proxy architectures will typically provide at most LOA-2 authentication, as these architectures are limited by the strength of the identity assertions made by the Verifier to the Relying Party. As such, transition away from the Proxy architecture is needed. Agencies should establish a POA&amp;M to help with the transition to a technology that supports PIV using the direct or indirect 16 SAML also supports holder-of-key assertions, which require the Claimant to prove possession of a key to the Relying Party. Holder-of-key assertions can be implemented in a way that provides up to LOA-4 to the Relying Party. verification architecture at the appropriate level of assurance (see the Section 2 introduction and Section 2.3). Implementers of the proxy architecture should ensure that they: - Isolate the Relying Party system from all untrusted systems. This includes designing and configuring network architectures so that all privileged access to the Relying Party system flows through the Proxy. - Segment internal networks to restrict the ability for a compromise of the Proxy to spread to other systems. - Authenticate and encrypt all communications between users (Claimants) and the Proxy.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, privileged access. Contains security framework guidance for authentication systems. Source: Best Practices for Privileged User PIV Authentication."}]}
{"id": "nist_02384", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PM-8200 in Cell Phone Forensic Tools_ an Overview and Analysis Update? (Part 4) Control PM-8200: | | NOKIA 6200............................................................................................................................. | 128 | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------| | SANYO PM-8200 ..................................................................................................................... | 129 | | APPENDIX E: PHONEBASE2 RESULTS............................................................................ | 131 | | ERICSSON T68I ........................................................................................................................ | 131 | | MOTOROLA V66...................................................................................................................... | 132 | | MOTOROLA V300.................................................................................................................... | 133 | | NOKIA 6610I ............................................................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis Update."}]}
{"id": "nist_02385", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Building Secure Microservices-based Applications Using Service-Mesh Architecture say about 5 Summary and Conclusions? (Part 3) According to Building Secure Microservices-based Applications Using Service-Mesh Architecture, 5 Summary and Conclusions: .getambassador.io/the-importance-of-control-planes- with-service-meshes-and-front-proxies-665f90c80b3d | | [8] | Kirschner E (2017) Proxy Based Service Mesh . Available at https://medium.com/@entzik/proxy-based-service-mesh-96cd4b74c198 | | [9] | Tiwari A (2017) A sidecar for your service mesh . Available at tiwari.com/a-sidecar-for-your-service-mesh/ | | [10] | Sridharan C (2018) The Three Pillars of Observability. Distributed Systems Observability (O'Reilly Media, Inc., Sebastopol, CA), Chapter 4. Available at observability/9781492033431/ch04.html | | [11] | Jaeger Project (2020) Jaeger: open source, end-to-end distributed tracing . Available at https://www.jaegertracing.io/ | | [12] | Zipkin Project (2020) Zipkin . Available at https://zipkin.io/ | | [13] | Leong A (2019) A guide to distributed tracing with Linkerd . Available at https://linkerd.io/2019/10/07/a-guide-to-distributed-tracing-with-linkerd/ | - [14] Stafford GA (2019) Kubernetes-based Microservice Observability with Istio Service Mesh: Part 1 (ITNEXT).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Building Secure Microservices-based Applications Using Service-Mesh Architecture."}]}
{"id": "nist_02386", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Annual Report 2018_ NIST_ITL Cybersecurity Program say about AUTOMATING CRYPTOGRAPHIC TESTING? According to Annual Report 2018_ NIST_ITL Cybersecurity Program, AUTOMATING CRYPTOGRAPHIC TESTING: Several years ago, NIST launched a project to automate much of the testing required under its cryptographic validation programs. Automated cryptographic algorithm testing was completed in 2018, and NIST is now developing methods to automate the testing of cryptographic modules. These efforts in automation are intended to provide a higher trust in the assurance claims made by the product developers in an efficient and cost-effective manner that allows the vendors' conformance efforts to keep pace with the changing IT landscape. By investing in a more robust testing infrastructure, NIST anticipates that product vendors will take advantage of this service by validating their products more often, which will produce more secure products. In FY19, NIST will put more responsibility for generating evidence of conformance in the hands of industry by leveraging automated test processes that will reduce time to market, slice costs to maintain compliance, and ensure that the Federal Government has effective and up-todate technologies.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Annual Report 2018_ NIST_ITL Cybersecurity Program."}]}
{"id": "nist_02387", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings provide? (Section 363) decision to implement a smart card-based PKI meant that many users were issued a CAC months prior to receiving a smart card reader and without any application requiring use of their new certificates. As a result, most users\u00d5 experience with PKI consisted of waiting in line to get a CAC and then using the CAC the same way they had used the ID card they had prior to the CAC. These users did not see any real benefit to the new technology. Although smart card readers are being deployed and applications are beginning to incorporate support for public key technology, the DoD PKI continues to struggle to attain widespread user acceptance. Application owners need policy, budget guidance, and a business justification for adopting public key technology. Within the DoD, funding for PKI core components and card stock is centrally managed. However, individual applications, including email, networks, and web servers, are very decentralized. Therefore, rolling out the PKI required a few decisions by policy makers, but integrating public key technology into applications requires many decisions by many application owners. These managers must consider multiple demands when determining how to allocate limited resources: Getting support from application managers requires providing managers with the information they need to make decisions including the following: - \u221e Ensure that published policy is consistent with the organization\u00d5s goals for integrating public key technology. Policy enables early adopters of new technology to justify their investments. - \u221e Provide direction for requesting funding for public key enabling as a part of the standard budget cycle. Getting out of cycle funding to meet security driven requirements is difficult and almost always means that other planned functionality must be sacrificed to meet PKI requirements.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02388", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0 say about Appendix A: Framework Core? (Part 47) According to Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0, Appendix A: Framework Core: ement agencies. | RS.CO-4: Coordination with stakeholders occurs consistent with response plans | \u2022 ISA 62443-2-1:2009 4.3.4.5.5 \u2022 NIST SP 800-53 Rev. 4 CP-2, IR-4, IR-8 | | RESPOND (RS) | Response activities are coordinated with internal and external stakeholders, as appropriate, to include external support from law enforcement agencies. | RS.CO-5: Voluntary information sharing occurs with external stakeholders to achieve broader cybersecurity situational awareness | \u2022 NIST SP 800-53 Rev. 4 PM-15, SI-5 | | RESPOND (RS) | Analysis (RS.AN): Analysis is conducted to ensure adequate response and support recovery activities. | RS.AN-1: Notifications from detection systems are investigated | \u2022 COBIT 5 DSS02.07 \u2022 ISA 62443-2-1:2009 4.3.4.5.6, 4.3.4.5.7, 4.3.4.5.8 \u2022 ISA 62443-3-3:2013 SR 6.1 \u2022 ISO/IEC 27001:2013 A.12.4.1, A.12.4.3, A.16.1.5 \u2022 NIST SP 800-53 Rev.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0."}]}
{"id": "nist_02389", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Electronic Health Records on Mobile Devices provide? (Section 30) -2 High-Level Architecture T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P . 1 8 0 0 - 1 . The use case scenario was not intended to include a complete set of components but rather to start a discussion about the issue and to provide an opportunity for vendors of security products to participate in the solution. From this use case scenario, we identified the architecture components that are likely in an organization\u2019s enterprise (see Table 3-1). The table also includes the security characteristics that we derived from the use case. These are the security characteristics that defined our problem. Table 3-1 Use Case Architecture Components Mobile Devices / Client Side Networks Back End / Server Side Secure Infrastructure mobile device Wi-Fi mobile device management client intrusion detection system firewall software certified [7] EHR system firewall storage encryption VPN gateway antivirus authentication, authorization, and accounting server intrusion detection system certificate authority and enrollment NIST SP 1800-1B: Securing Electronic Health Records on Mobile Devices 12 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P . 1 8 0 0 - 1 . Mobile Devices / Client Side Networks Back End / Server Side Secure Infrastructure provisioning system for mobile devices client healthcare mobile device application storage encryption Security Characteristics provisioning system for mobile devices server mobile device management server auditing mobile device From the use case scenarios, we derived a set of security characteristics as the high-level requirements for our build.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, certificate authority. Contains security framework guidance for authentication systems. Source: Securing Electronic Health Records on Mobile Devices."}]}
{"id": "nist_02390", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.1.2.3 Doubt: Consistency according to NIST Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS) According to Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS), 3.1.2.3 Doubt: Consistency: It was with regard to appropriateness to the first assurance step that our serious doubts first began to be raised. If a set of rules is to provide a useful basis for assurance of an invariant property, they must be clearly defined and internally consistent. We found the definition of an IVP ambiguous with regard to purpose, in that it was not clear (nor resolved in the plenary sessions) whether the IVP was to check internal consistency, external consistency, or both. We were also uncertain about logging requirement of rule C4 , in which the purpose of the log (accountability, backup, or both) was not clear. Again, this ambiguity was not resolved in the plenary session. We also felt rule E2 was possibly inconsistent with other rules. Its wording strongly implies the binding of individual names to programs while other discussions indicated that it was the organizational role (a derivative value) that should be the determinant of who may initiate a given TP. While we were not able to point out internal inconsistencies in the short time available, we noted areas of overlap in the rules that we felt could lead to such inconsistencies. We questioned the need for rule CI and the need to distinguish IVPs from TPs at this high level of abstraction. Likewise, we felt that rule C5 was subsumed by C2 , and again questioned the need for the distinction between a UDI and a GDI, or indeed the ability to state criteria which would enable us to distinguish one from another. We felt that rule El was subsumed by rule E2, and that rule E4 was an instance of rule C3 applied to the enforcement mechanism. The latter case raises the interesting question of circularity in the definitions, which we will touch upon in a later section.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)."}]}
{"id": "nist_02391", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automation Support for Security Control Assessments_ Volume 1_ Overview say about 3. Focusing Security Control Assessments on Security Results? (Part 1) According to Automation Support for Security Control Assessments_ Volume 1_ Overview, 3. Focusing Security Control Assessments on Security Results: 3. Focusing Security Control Assessments on Security Results This section introduces three abstraction layers that focus on achieving security results (as security capabilities) above the level of individual security controls/control items (see Section 3.5). The following security capability abstraction layers are introduced and are traceable 12 to security requirements and the individual security controls/control items that support them: - (1) Attack Step Layer - Desired Result: Block or delay attacks (see Section 3.2). - (2) Functional Capability Layer - Each capability is a grouping of controls and control items from SP 800-53. Desired Result: Make a broad area of the system more secure (see Section 3.3). - (3) Sub-Capability Layer - Each capability is decomposed into sub-capabilities necessary and sufficient to support the purpose of the larger capability. Each sub-capability is tested with one corresponding defect check. Desired Results: a) To support blocking of attack steps and provide functional security capability; and b) provide clearly testable outcomes (see Section 3.4). The control items themselves provide a fourth abstraction layer: - (4) Control Items Layer - see Section 3.5. The four abstraction layers serve the following purposes: - Support strong systems engineering of security capabilities; - Support guidance for control selection; - Simplify understanding of the overall protection process; - Enable assessment of security results at a higher level than individual controls; and - Improve risk management by measuring security results that are more closely aligned with desired business results. To address the purposes, NIST introduced the concept of information security capabilities in SP 800-53. Information security capabilities (discussed in more detail below) are groups of controls that work together to achieve an information security purpose and enable/protect the organization's ability to perform its mission.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Volume 1_ Overview."}]}
{"id": "nist_02392", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does The Use of Passwords for Controlled Access to Computer Resources say about Password 'transmission? (Part 3) According to The Use of Passwords for Controlled Access to Computer Resources, Password 'transmission: tect customer passwords in transit. In this application, the customer selects a 16 character password, which is then scrambled twice before reaching the computer where it is filed as a six-digit code. The scrambling, which is claimed to be irreversible, is handled by integrated circuits built into relay boxes at the terminals and computer center [NEWS 76] Branstad notes that encryption keys and authentication codes may be in effect the same item. In his proposed network access control machine, these keys are never transmitted through the network, but rather are loaded simultaneously by interface units into a primary encryption device. Thus, authentication can be considered complete at that level (at least) if a message can be encrypted, transmitted, and correctly decrypted [BRAND 73] , [BRAND 75]. In a master 's thesis on protocols, Stephen Kent distribution [RENTS 76]. transmission techniques: encryption-based protection considers encryption key He identifies two basic - o chained key changes - o two-level key distribution systems. Under the chained key system, each new key is enciphered using the last key issued. This new key is then used until another change occurs. Under the two-level distribution system, a special key is used solely for transmitting new keys to remote users. Kent describes protocols for using these two schemes and considers the use of magnetically encoded cards for distribution of keys. He presents the following example of a login sequence incorporating two-way authentication: 1. The user enables the terminal and establishes a connection to the host, 2. The host responds in cleartext confirming the connection by sending the host name. 3. The user transmits in cleartext the login identifier, and then inserts a magnetic stripped plastic card containing his or her (primary) key and enables the encryption module, 4.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: The Use of Passwords for Controlled Access to Computer Resources."}]}
{"id": "nist_02393", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Technical Guide to Information Security Testing and Assessment say about 4.5 Summary? (Part 2) According to Technical Guide to Information Security Testing and Assessment, 4.5 Summary: olations | There are risks associated with each technique and combination of techniques. To ensure that all are executed safely and accurately, each assessor should have a certain baseline skill set. Table 4-2 provides guidelines for the minimum skill set needed for each technique presented in Section 4. Table 4-2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technical Guide to Information Security Testing and Assessment."}]}
{"id": "nist_02394", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for API Protection for Cloud-Native Systems say about 1.4. Relationship to Other NIST Documents? According to Guidelines for API Protection for Cloud-Native Systems, 1.4. Relationship to Other NIST Documents: Today, most software development and integration are based on APIs. Section 1.2 articulated the close relationship between software and APIs, demonstrated that API development and deployment follow the same iterative life cycle as the software, and provided NIST guidelines on DevSecOps. Another 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Guidelines for API Protection for Cloud-Native Systems."}]}
{"id": "nist_02395", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Test Personal Identity Verification (PIV) Cards Version 2 say about Table of Contents? (Part 7) According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Table of Contents: 33 | | | D.1.1 | Self-Signed Trust Anchor Certificate ...............................................33 | | | D.1.2 | RSA 2048 Issuing CA Certificate ....................................................34 | | | D.1.4 | RSA 4096 Issuing CA Certificate ....................................................36 | | |-----|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| | | D.1.5 | ECC P-256 Issuing CA Certificate...................................................37 | | | | D.1.6 | ECC P-384 Issuing CA Certificate...................................................38 | | | | D.1.7 | RSA 2048 PIV-I Issuing CA Certificate............................................39 | | | D.2 | Content Signer Certificates | Content Signer Certificates | ..........................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_02396", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Severity - Law Enforcement: High Confidentiality Impact according to NIST Security Analysis of First Responder Mobile and Wearable Devices According to Security Analysis of First Responder Mobile and Wearable Devices, Severity - Law Enforcement: High Confidentiality Impact: Justification: This classification of this data depends on the immediate type of incident at hand. The high impact level is used since there exists the possibility of loss of life. For instance, sensitive information shared at a crime scene or an undercover officer communicating with law enforcement could lead to loss of life. It is of note that much of a law enforcement officer's traffic is routinely sent in in the clear, making this extremely situation-dependent. Source: N/A", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Analysis of First Responder Mobile and Wearable Devices."}]}
{"id": "nist_02397", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.2.7. Error Handling according to NIST Interfaces for Personal Identity Verification_ Part 2 \u2013 PIV Card Application Card Command Interface According to Interfaces for Personal Identity Verification_ Part 2 \u2013 PIV Card Application Card Command Interface, 4.2.7. Error Handling: The SW processing status is the status word of the overall secure messaging command and response processing. It indicates whether the secure messaging was performed successfully. If the processing was successful, it SHALL be '90 00'. Otherwise, it SHALL be as follows: - '68 82' - Secure messaging not supported - '69 82' - Security status not satisfied 24 - '69 87' - Expected secure messaging data objects are missing - '69 88' - Secure messaging data objects are incorrect If the command processing was unsuccessful, the card SHALL return one of the above status words without performing further secure messaging.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interfaces for Personal Identity Verification_ Part 2 \u2013 PIV Card Application Card Command Interface."}]}
{"id": "nist_02398", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide for Conducting Risk Assessments provide? (Section 68) , individuals, other organizations, or the Nation. Organizations can update risk assessments on an ongoing basis using security-related information from organizational continuous monitoring processes. 41 Continuous monitoring processes evaluate: (i) the effectiveness of security controls; (ii) changes to information systems and environments of operation; and (iii) compliance to federal legislation, regulations, directives, policies, standards, and guidance. As risk assessments are updated and refined, organizations use the results to update the risk management strategy, thereby incorporating lessons learned into risk management processes, improving responses to risk, and building a solid foundation of threat and vulnerability information tailored to organizational missions/business functions. 41 NIST Special Publication 800-137 provides guidance on information security continuous monitoring for information systems and organizations. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ The risk assessment process entails ongoing communications and information sharing among stakeholders to ensure that: (i) the inputs to such assessments are as accurate as possible; (ii) intermediate assessment results can be used, for example, to support risk assessments at other tiers; and (iii) the results are meaningful and useful inputs to the risk response step in the risk management process. The manner and form in which risks are communicated are an expression of organizational culture as well as legal, regulatory, and contractual constraints. To be effective, communication of information security risks and other risk-related information produced during the risk assessment is consistent with other forms of risk communication within organizations.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Guide for Conducting Risk Assessments."}]}
{"id": "nist_02399", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings say about \u00b7 Banking Kiosk? According to 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings, \u00b7 Banking Kiosk: A bank operates an ATM (auto-teller machine) network and requires the use of digital signatures for high-value transfers. The ATM can be deployed with finger-vein or palm-vein biometrics to serve as a stronger form of authentication. In this case, the end-user can use biometrics to authenticate to the OTPK CA (via the bank's internal ATM network) to get the certificate.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_02400", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers say about 7.1.5 Test Case MFA-4 (Accounts Automatically Locked After Failed Login Attempts)? (Part 2) According to Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers, 7.1.5 Test Case MFA-4 (Accounts Automatically Locked After Failed Login Attempts): mple implementation shall lock a purchaser's account upon detection of that account exceeding a predetermined number of failed login attempts for the cost threshold and risk engine example lab builds. | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | Test Case Field | Description | |--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Testable Requirement | (CR 4.a) Magento | | Description | Show that the MFA example implementation can lock a purchaser account if the allowed number of customer ID and password-authentication attempts is exceeded.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, mfa. Contains security framework guidance for authentication systems. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_02401", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide? (Section 288) eir use, but they can also misuse it for undesirable purposes. It is often very difficult to determine whether their use of the sytem is in accordance with the legitimate performance of their job. 12. -An employee may convert Government information to an unauthorized use; for example, he may sell privileged data about an individual to a prospective employer, credit agency, insurance company, or competitor; or he may use Government statistics for stock market transactions before their public release. 13. -A user whose job requires access to individual records in a file may manage to compile a complete listing of the file and then make unauthorized use of it (e.g., sell a listing of employees' home addresses as a mailing list). 14. -Unauthorized altering of information may be accomplished for an unauthorized end user (e.g., altering of personnel records). 15. -An authorized user may use the system for personal benefit (e.g., theft of services) . 16. -A supervisor may manage to approve and enter a fraudulent transaction. 17. -A disgruntled or terminated employee may destroy or modify records - possibly in such a way that backup records are also corrupted and useless. 18. -An authorized user may accept a bribe to modify or obtain information. 3. UNCONTROLLED SYSTEM ACCESS. Organizations expose themselves to unnecessary risk if they fail to establish controls over who can enter the ADP area, who can use the ADP system, and who can access the information contained in the system. - -Data or programs may be stolen from the computer room or other storage areas. - -ADP facilities may be destroyed or damaged by either intruders or employees. - -Individuals may not be adequately identified before they are allowed to enter - ADP area. - -Remote terminals may not be adequately protected from use by unauthorized - persons - -An unauthorized user may gain access to the system via a dial-in line and an authorized user's password.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls."}]}
{"id": "nist_02402", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance say about 2.2.1 Recommended Key Sizes and Algorithms? (Part 2) According to Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance, 2.2.1 Recommended Key Sizes and Algorithms: gorithms and key sizes are approved for use beyond the year 2013. However, a digital signature or key establishment certificate may expire at any time, depending on the organization's security policy. Table 2-1: Recommended Algorithms and Key Sizes | Key Type | Algorithms and Key Sizes | |------------------------------------------------------------------------|-------------------------------------------------------------------------| | Digital Signature keys used for authentication (for Users or Devices) | RSA (2048 bits) ECDSA (Curve P-256) | | Digital Signature keys used for non-repudiation (for Users or Devices) | RSA (2048 bits) ECDSA (Curves P-256 or P-384) | | CA and OCSP Responder Signing Keys | RSA (2048 or 3072bits) ECDSA (Curves P-256 or P-384) | | Key Establishment keys (for Users or Devices) | RSA (2048 bits) Diffie-Hellman (2048 bits) ECDH (Curves P-256 or P-384) | Note that some approved algorithms and key sizes, such as DSA 2048, are omitted to enhance interoperability. RSA and ECDSA, which are included in Table 2-1 above, have been widely deployed in PKIs. Therefore, they are recommended for use to enhance interoperability. However, DSA (2048 and 3072) as specified in [FIPS 186-4] are allowed as long as the required security strength is satisfied. For ECDSA, only the two elliptic curves listed in Table 2-1 above of the elliptic curves are recommended for use in PKIs for digital signatures [FIPS 186-4]. Similarly, Elliptic Curve Diffie-Hellman (ECDH) is recommended to support key establishment, rather than Elliptic Curve MQV. While Table 2-1 is focused on the strength of the public key contained in a certificate, the strength of the digital signature on a certificate itself is equally important.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance."}]}
{"id": "nist_02403", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Section 15) | | | D.3.1.14. Attachments.....................................................................................................................216 | | | D.3.1.15. C-SCRM Plan and Life Cycles ............................................................................................216 | | | D.4.1. C-SCRM Template ....................................................................................................................218 | | | D.4.1.1. Authority and Compliance..................................................................................................218 | | | D.4.1.2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_02404", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Considerations for Remote Electronic UOCAVA Voting provide? (Section 24) cation of voters, system operators, election officials, and system components. Issues related to the identification and authentication of voting system users and components are discussed in Section 7. These areas were chosen to break the discussion of security issues into closely related topic areas. Issues related to any one of these topic areas are closely bound to those associated with other topics. For instance, an insufficient authentication mechanism could allow an unauthorized individual to access sensitive information (a confidentiality violation) or modify key voting system records (an integrity violation). For each topic area, this report discusses the following: - \uf0a7 Potential Benefits: The move from the current mail-in absentee voting process to a remote electronic voting system can provide some benefits to security, such as in the areas of automated forms of strong authentication, timeliness of delivery, and ballot secrecy. For each of the topic areas, this report will describe the advantages of remote electronic voting. - \uf0a7 Properties: In order to facilitate discussion of threats to remote electronic voting systems, this report provides lists of desirable security properties. In general, threats identified in this report are actions that can violate one or more of those properties. The security properties identified in this report are based on properties and requirements identified in other electronic remote voting system documents including the Secure Electronic Registration and Voting Experiment (SERVE) Project documentation [10], the Common Criteria Protection Profile for online voting systems [8], and the Council of Europe's standards for online voting systems [9]. Policymakers ultimately must decide which properties must be met by voting systems to be acceptable in their jurisdictions.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Security Considerations for Remote Electronic UOCAVA Voting."}]}
{"id": "nist_02405", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PM-8200 in Cell Phone Forensic Tools_ an Overview and Analysis? (Part 32) Control PM-8200: in acquisition and examination. Table 3 highlights the key characteristics of each target device, listed roughly from devices with more capabilities to lesscapable devices, rather than alphabetically. Note that the more capable devices listed have a PDA heritage, insofar as they use Windows Mobile, Palm OS, RIM OS, and Symbian operating systems.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_02406", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results say about VI. Conclusion? (Part 1) According to Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results, VI. Conclusion: VI. Conclusion The thesis of this paper is that evidentiary issues and security requirements are two sides of the same coin. And in the realm of security \"one size\" does not fit all, just as in the law of evidence the foundational showing will vary with the particular circumstances. A simple hypothetical problem should elucidate the point. Party A sends Party B an electronic purchase order in standard EDI format. Parties Y and Z do the same. In both cases disputes arise necessitating the use of the two purchase orders as evidence. Here, however, the similarities end. Parties A and B, it turns out, are established trading partners engaged in a regular course of business involving the routine exchange of electronic purchase orders. The transaction at issue involved a standard commercial product and did not carry an extraordinary dollar value. Parties Y and Z, however, are strangers who - although they possess and utilize EDI capabilities have never done business together before. Furthermore, the transaction was of a high dollar value and was for the purchase of a custom manufactured item. Although the two EDI purchase orders were essentially identical, from an evidentiary standpoint the two transactions were totally different. The burden party A must carry in order to have its purchase order admitted into evidence is relatively light. The use of basic security techniques - password access control, generally reliable audit capability, probably the use of a VAN - should suffice to have the evidence admitted. Party Y, however, must bear a heavy evidentiary burden. The controls used by party A would probably not suffice. Strong originator authentication, message integrity, and non-repudiation - probably encryption techniques - should have been used. Likewise, from the standpoint of the Computer Security Act's risk-based standard, the two transactions bear little resemblance.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results."}]}
{"id": "nist_02407", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Digital Identity Guidelines_ Federation and Assertions say about 5.5. Discovery and Registration? (Part 2) According to Digital Identity Guidelines_ Federation and Assertions, 5.5. Discovery and Registration: anaging discovery and registration. When an RP joins the ecosystem, it registers itself with the trusted service, downloads the CSP's verification keys, and receives an identifier to use with wallets. When the CSP issues attribute bundles to the subscriber-controlled wallet, the subscriber-controlled wallet is informed where it can find the list of valid RP identifiers within the ecosystem. When the RP connects to the wallet, the wallet can verify the RP's identifier without the RP having to register itself directly with the wallet. Likewise, the RP can trust the wallet's verification keys by verifying the CSP's signature over the wallet's verification keys or identifier. - 5.6. Authentication and Attribute Disclosure The decision of whether a federation transaction proceeds and, therefore, an assertion is issued and attributes are released to the RP SHALL be determined by the subscriber acting in the role of the authorized party. The decision MAY be augmented by the use of allowlists and blocklists to allow the wallet to help the subscriber make a decision based on configured policies and trust agreements. The subscriber-controlled wallet MAY remember the subscriber's decision to allow for future actions at the same RP without separate authorization from the subscriber. The use of a stored authorization decision does not supersede the requirement for wallet activation, as discussed in Sec. 5.4. The subscriber-controlled wallet MAY provide a mechanism to remember a disclosure decision by the authorized party (i.e., the subscriber) to apply to future requests from the same RP. If such a mechanism is provided, the subscriber-controlled wallet SHALL disclose to the authorized party that the storage mechanism is in use and SHALL allow the authorized party to revoke such remembered access at a future time. The subscriber-controlled wallet SHOULD provide a means to selectively disclose a subset of the attributes in the attribute bundle from the CSP.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Digital Identity Guidelines_ Federation and Assertions."}]}
{"id": "nist_02408", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Glossary of Computer Security Terminology say about 2) See BELL-LAPADULA MODEL and SECURITY POLICY MODEL.? (Part 7) According to Glossary of Computer Security Terminology, 2) See BELL-LAPADULA MODEL and SECURITY POLICY MODEL.: s) by trying combinations of commands at random to determine their effect. Common usage today is from the press, which uses the word to describe people who \"break into\" computers for various purposes. (BBD) | |------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | handled by | The term \"handled by\" denotes the activities performed on data in an AIS, such as collecting, processing, transferring, storing, retrieving, sorting, transmitting, disseminating and controlling. (DODD 5200.28) | | handshaking | Passing control characters between two devices, to control the flow of information. (APR 205-16) | | handshaking 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. A 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) | | | 2) Synonymous with PASSWORD DIALOGUE.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Glossary of Computer Security Terminology."}]}
{"id": "nist_02409", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Management_ Part 1 \u2013 General provide? (Section 289) thority), saving the public-key certificate would be an appropriate form of storing the public key; backup or archive storage may be provided by the infrastructure (e.g., by a certificate repository). The public key may be stored in backup storage until the end of the private key's cryptoperiod and may be stored in archive storage as long as required. The private key is used to establish the identity of an entity who is participating in an authenticated communication session. The private authentication key need not be backed up if a new key pair can be generated and distributed in a timely manner in accordance with Section 8.1.5.1. However, if a new key pair cannot be generated quickly, the private key should be stored in backup storage during the cryptoperiod of the private key. The private key shall not be stored in archive storage. A symmetric data-encryption key is used to protect the confidentiality of stored or transmitted data or both. The same key is used initially to encrypt the plaintext data to be protected and later to decrypt the encrypted data (i.e., the ciphertext), thus obtaining the original plaintext. The key needs to be available for as long as any data that is encrypted using that key may need to be decrypted. Therefore, the key should be backed up or archived during this period. In order to allow key recovery, the symmetric data-encryption key should be stored in backup storage during the cryptoperiod of the key and should be stored in archive storage if required. In many cases, the key is protected and stored with the encrypted data. When archived, the key should be wrapped (i.e., encrypted) by an archive-encryption key or by a symmetric key-wrapping key that is wrapped by a protected archive-encryption key. A symmetric data-encryption key that is used only for transmission is used by an originating entity to encrypt data and by the receiving entity to decrypt the ciphertext data immediately upon receipt.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02410", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations say about REFERENCES? According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, REFERENCES: Source Controls: AC-11, AC-11(01) Supporting Publications: None", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_02411", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-200901022 in Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171? (Part 70) Control PD-200901022: | x | | | SR-2 | Supply Chain Risk Management Plan | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ TABLE C-12: SECURITY ASSESSMENT REQUIREMENT MAPPINGS | SECURITY REQUIREMENTS | Defense-in-Depth Protection Strategy | Defense-in-Depth Protection Strategy | Defense-in-Depth Protection Strategy | NIST SP 800-53 Relevant Security Controls | NIST SP 800-53 Relevant Security Controls | |-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|----------------------------------------|---------------------------------------------|-------------------------------------------------------| | | PRA | DLO | CRS | | | | 3.12.1e Conduct penetration | testing x | x | | CA-8 | Penetration Testing | | 3.12.1e Conduct penetration | [ Assignment: organization- defined frequency ], leveraging automated scanning tools and ad hoc tests using subject matter experts.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_02412", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3 say about E.5.1 Cargo Shipping? (Part 5) According to NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3, E.5.1 Cargo Shipping: | Event detection | Abnormal events such as cargo moving out of the way or being stationary for unwarranted periods can be detected. | | Fabric | Forensics | Analysis of logged data can reveal details of incidents after they occur. | 3088 3089", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3."}]}
{"id": "nist_02413", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings provide? (Section 329) of DSA optimizations. For the presentation of experiment results, we use cDSA to denote S-BGP with caching, pDSA to denote S-BGP using DSA pre-computation, and cpDSA for S-BGP with both optimizations. In our model, these Table 1: Constants and benchmarks used for simulation. RSA, DSA, and SAS algorithms are based on 1024-bit keys. | | SHA-1 hash | Attestation | S-BGP X.509 Certificate | Identifier | |----------------|--------------|---------------|---------------------------|--------------| | Length (bytes) | 20 | 110 | 600 | 4 | | | RSA | DSA | DSA (p-c) | SAS | |--------------------------|-------|-------|-------------|-------| | Verify Time ( ms ) | 2.5 | 31 | 31 | 2.5 | | Sign Time ( ms ) | 50 | 25.5 | 0.015 | 50 | | Signature Length (bytes) | 128 | 40 | 40 | 128 | | | OCSP request | CRL fetching | |----------------------------|----------------|----------------| | Operation Latency (second) | 0.5-1.0 | 0.5-1.0 | Table 2: Performance rankings for the path authentication schemes we examined | | Convergence | Message Size | Memory | |-------|---------------|----------------|----------| | S-BGP | long | moderate | best | | S-A | shortest | worst | worst | | SAS | longest | best | best | caching strategies store both validated signatures and generated signatures; we use 10 GLYPH&lt;22&gt; s (with a uniformly distributed delta of 5 GLYPH&lt;22&gt; s ) to model the lookup time. The S-A scheme will not speed up by caching hash trees with signatures, because the trees, and hence the signatures, are constantly changing even for the same route announcement (since the trees depend on the context of what else is being signed at that time).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02414", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Study of Federal Agency Needs for Information Technology Security provide? (Section 148) nts were found to be based on a higher set of environmental and policy factors and conditions. Computer security technology is applied uniquely in each situation even though there are common concerns. Because 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. For 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-dlscretionary controls, such as role-based access controls, separation of duties, separation of transactions, and user-oriented least privilege. Most organizations felt security standards should include a wide range of assurances including a 'generally accepted commercial practice\" level. This new level should minimize the cost of developing new systems or retro-fitting new security functionality in existing systems. Nearly all of those Interviewed expressed the desire to have an Independent third party give a \"stamp of approval\" with regard to the trustworthiness of the systems they were buying. However, the current evaluation and certification process (I.e., with respect to a TCSEC class) was not perceived by users as meeting their needs for a variety of reasons. Those interviewed felt that security standards have failed to emerge allowing comprehensive Implementation to integrate security across a multi-vendor environment.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of Federal Agency Needs for Information Technology Security."}]}
{"id": "nist_02415", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Specification for the Open Checklist Interactive Language (OCIL) Version 2.0 say about 1.2 Document Structure? According to Specification for the Open Checklist Interactive Language (OCIL) Version 2.0, 1.2 Document Structure: The remainder of this document is organized into the following major sections and appendices: - Section 2 defines terms used within this specification and provides a list of common acronyms and other abbreviations. - Section 3 defines the conformance rules for this specification. - Section 4 provides an overview of related specifications and standards. - Section 5 presents the primary components of the OCIL data model. - Section 6 provides requirements and recommendations for OCIL content syntax, structures, and development. - Section 7 describes OCIL document processing requirements. - Appendix A discusses possible use cases for OCIL. - Appendix B defines requirements for using OCIL as a check system for the eXtensible Configuration Checklist Description Format (XCCDF).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Specification for the Open Checklist Interactive Language (OCIL) Version 2.0."}]}
{"id": "nist_02416", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Integrity according to NIST Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Integrity: The integrity impact level is based on the specific mission and the data supporting that mission, not on the time required to detect the modification or destruction of information. The consequences of unauthorized modification or destruction of global trade information depends on whether the information is time-critical. Unauthorized modification or destruction of information affecting export promotion information may adversely affect mission operations and result in potentially serious economic repercussions. Trade agreements that have been implemented are generally matters of public record. Therefore, the specific negotiated terms, etc., must be accurately recorded. The modification of merchandise inspection information may result in significant financial consequences to an importer or exporter whose shipment is in question and may adversely affect mission operations and result in potentially serious economic repercussions. The results of completed inspections are matters of public record and must be accurately recorded. For tariffs/quotas monitoring information, the requirement for adequate means to detect data corruption is high . This information is used in policy and strategic analysis, and the accuracy of this statistical information is critical. Unauthorized modification or destruction of information affecting tariffs/quotas monitoring information may adversely affect mission operations and result in potentially catastrophic economic repercussions. Recommended Integrity Impact Level: The provisional integrity impact level recommended for global trade information is high .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_02417", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Section 67) understood | High | R1: Estimate the impact and scope of adverse events through automated (e.g., SIEM, SOAR) and/or manual means, and review and refine the estimates. | | DE.AE-06 | Information on adverse events is provided to authorized staff and tools | High | R1: Generate alerts and provide them to cybersecurity and incident response tools and staff (e.g., the SOC and incident responders). R2: Make log analysis findings accessible to incident responders and other authorized personnel at all times. R3: Consider automatically creating and assigning tickets in the organization's ticketing system when certain types of alerts occur. | | DE.AE-07 | Cyber threat intelligence and other contextual information are integrated into the analysis | High | R1: Integrate up-to-date CTI and other contextual information (e.g., asset inventories) into adverse event analysis to improve detection accuracy and characterize threat actors, their methods, and indicators of compromise. R2: Rapidly acquire and analyze vulnerability disclosures for the organization's technologies from suppliers, vendors, and third-party security advisories. N1: See [SP800-150] for guidelines on consuming, using, and storing CTIs, as well as establishing CTI relationships. | | DE.AE-08 | Incidents are declared when adverse events meet the defined incident criteria | High | R1: Apply incident criteria to known and assumed characteristics of analyzed activity, and consider known false positives to determine whether an incident should be declared. | | RS (Respond) | Actions regarding a detected cybersecurity incident are taken | High | N1: The Respond Function is at the core of incident response activities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, threat actor, incident response. Contains technical security guidance that could inform defensive posture. Source: Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile."}]}
{"id": "nist_02418", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is References according to Security and Privacy Controls for Information Systems and Organizations? References: [SP 800-12], [SP 800-30], [SP 800-39], [SP 800-100].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02419", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Securing Radio Frequency Identification (RFID) Systems provide? (Section 221) | If the risk assessment identifies risks related to human health, fuel, ordnance, or other sensitive materials (e.g., pharmaceuticals) that are not fully mitigated by the RFID usage policy, then the organization should require additional controls to prevent the associated hazard from being realized. A separate policy is needed for each hazard type (HERF/HERO/HERP/other sensitive materials) because each one has distinct issues. Organizations facing these hazards should also consult safety and regulatory experts in this area to ensure their approaches are valid and comply with legally-mandated FCC exposure limits. 79 | RF Subsystem | Recommended | | | 5 | Enhance the organization's information security policy to account for the presence of RFID systems. | The introduction of RFID technology represents a new challenge to the security of the enterprise network that should be mitigated by policy and associated technical, operational, and management controls. Elements of the network security policy that might require revision include (a) perimeter security (i.e., firewalls and extranets), (b) database security, (c) application security, and (d) wireless connections (i.e., between readers and the enterprise network). Typically a firewall separates readers from the enterprise network that hosts RFID database and application servers.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_02420", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2012 Annual Report provide? (Section 131) df00)ios, smart carGLYPH(cmap:df00)s, spacebased communications, munitions, security tokens, storage devices, and products supporting Public Key Infrastructure (PKI) and electronic commerce. A module may be a standalone product, such as a virtual private network (VPN), smart carGLYPH(cmap:df00) or toolkit, or one module may be used in several products; as a result, a small number of moGLYPH(cmap:df00)ules may be incorporateGLYPH(cmap:df00) within hunGLYPH(cmap:df00)reGLYPH(cmap:df00)s of proGLYPH(cmap:df00)ucts. Likewise, the CAVP valiGLYPH(cmap:df00)ates cryptographic algorithms that may be integrated in one or more cryptographic modules. The two valiGLYPH(cmap:df00)ation programs (the CAVP anGLYPH(cmap:df00) CMVP) provide documented methodologies for conformance testing through GLYPH(cmap:df00)efineGLYPH(cmap:df00) sets of security requirements. Security requirements for the CAVP are found in the individual validation system documents containing the validation test suites that are required to assure that the algorithm has been implemented correctly. The validation system documents are designed for each FIPS-approved and NIST-recommended cryptographic algorithm. Security requirements for the CMVP are found in FIPS 140-2, Security Requirements for Cryptographic Modules , and the associated test metrics and methods in Derived Test Requirements for FIPS 140-2. Annexes to FIPS 140-2 reference the underlying cryptographic algorithm standards or methods. Federal agencies are required to use modules that were valiGLYPH(cmap:df00)ateGLYPH(cmap:df00) as conforming to the provisions of FIPS 140-2. The CMVP developed Derived Test Requirements associateGLYPH(cmap:df00) with FIPS 140-2 to GLYPH(cmap:df00)efine the security requirements and the test metrics and methods to ensure repeatability of tests and equivalency in results across the testing laboratories.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, token, sso. Contains security framework guidance for authentication systems. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_02421", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Interview according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, Interview: [SELECT FROM: personnel with responsibilities for cryptographic key establishment or management; personnel with information security responsibilities; system administrators]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02422", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD) provide? (Section 44) le solution. However, a combination of allowing only certain device capabilities and blocking devices or domains that are considered suspicious allowed network administrators to mitigate some threats. With the evolution of internet hosts from multiuser systems to personal devices, this security posture became impractical, and the emergence of IoT has made it unsustainable. In typical networking environments, a malicious actor can detect an IoT device because it exposes its services directly to the internet. The malicious actor can launch an attack on that device from any system on the internet. Once compromised, that device can be used to attack any other system on the internet. Anecdotal evidence indicates that a new device will be detected and will experience its first attack within minutes of deployment. Because the devices being deployed often have known security flaws, the success rate for compromising detected systems is very high. Typically, malware is designed to compromise a list of specific devices, making such attacks very scalable. Once compromised, an IoT device can be used to compromise other internet-connected devices, launch attacks on any victim device on the internet, or launch attacks on devices within the local network hosting the device. 3.4.2 Vulnerabilities The vulnerability of IoT devices in this environment is a consequence of full connectivity, exacerbated by the large number of security vulnerabilities in complex software systems. Modern systems ship with millions of lines of code, creating a target-rich environment for malicious actors. Some vendors provide patches for security vulnerabilities and an efficient means for securely updating their products. However, patches are often unavailable or nearly impossible to install on many other products, including many IoT devices.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, malware. Contains technical security guidance that could inform defensive posture. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_02423", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does National Online Informative References (OLIR) Program_ Overview, Benefits, and Use say about Supportive Relationship Mapping OLIR? According to National Online Informative References (OLIR) Program_ Overview, Benefits, and Use, Supportive Relationship Mapping OLIR: An OLIR that indicates how a supporting concept can or does help achieve a supported concept, with one of the concepts being a Focal Document Element and the other a Reference Document Element.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: National Online Informative References (OLIR) Program_ Overview, Benefits, and Use."}]}
{"id": "nist_02424", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identity and Access Management for Electric Utilities provide? (Section 297) ss, as listed in Figure 9-9. T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . NIST SP 1800-2C: Identity and Access Management for Electric Utilities 177 Figure 9-9 Guardian Recon Authoritative Fields 9.3.3.2 Identity & Access > Request Categories Setup > Manual Configuration > Identity & Access > Request Categories. Select ChangeAccess Category name, and click Modify. a. On the Modify screen, make the following changes: b. In the Provisioning Actions section, un-select the Delimit User and Change Validity Dates checkboxes, if they are selected, and select the Change User option. c. Go to the Add Existing section, and select the system and Remove Role option from the Resources/Roles drop-down field. Click Save to save the configuration. Figure 9-10 Create External Provisioning Attribute Repeat Steps 1 and 2 to configure the fields listed in Figure 9-11. T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . Note: Field names are case-sensitive. NIST SP 1800-2C: Identity and Access Management for Electric Utilities 178 Figure 9-11 Field Names T h i s p u b l i c a t i o n 9.3.3.3 Identity & Access>Provisioning>Provisioning Mapping Setup > Manual Configuration > Identity & Access > Provisioning > Provisioning Mapping. Select ACCESSIT PACS, and click Configure. On the next screen, click the New button, and select UserText1 for the DB Connector Attribute Name (Figure 9-12). i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_02425", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Considerations for Remote Electronic UOCAVA Voting say about 4.5 Open Issues? (Part 1) According to Security Considerations for Remote Electronic UOCAVA Voting, 4.5 Open Issues: 4.5 Open Issues Achieving a very strict notion of ballot secrecy remains a challenging issue in remote electronic voting systems. While polling place voting systems do not store, or even learn, the identities of voters, remote electronic voting systems need to authenticate voters before allowing them to cast ballots. Cryptographic protocols exist to protect the secrecy of ballots even from those with unrestricted access to voting system equipment, but these technologies may not be ready for immediate use with remote electronic voting systems. For technical, procedural, and legal reasons, it is likely that any deployed voting system for UOCAVA voters would still have access to, and probably store, sufficient information to violate ballot secrecy. Depending on policy decisions at state and local levels, this issue may not require a technical solution beyond what is already practical. Advanced voting-specific cryptographic protocols have highly desirable properties in idealized models, but in practice, systems based on these protocols are often difficult to use and require that cryptographic keys be distributed to voters before an election. These systems also do not protect against many types of attacks, particularly if the computer used to cast votes and the voting environment are not secured. Current techniques for remote electronic voting do not solve the problems of coercion and vote selling that are inherent to unsupervised voting. Variations on these attacks are possible with mail-in absentee voting, although in that voting method, it is difficult for a single individual to impact many voters. When moving to remote electronic voting, election officials and technologists should consider whether the move makes it easier to scale these attacks. In particular, there appear to be ways that attackers could coerce or buy votes remotely. A simple attack involves selling or transferring the credentials that voters use to log into the remote voting system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Remote Electronic UOCAVA Voting."}]}
{"id": "nist_02426", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information say about B.5. VPN Integration? (Part 2) According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information, B.5. VPN Integration: sends the submitted username and password to the LDAP server to validate the credentials. The LDAP server returns a login success message. 8. The user's session with the CAD/RMS server is established. Although the officer only needs to use one username/password credential and one MFA credential, there is no SSO user experience since the user needs to enter the password twice. If MFA is not required at the CAD/RMS web app, the session is susceptible to phishing, as described in Sec. 2.5. If, on the other hand, the CAD/RMS web app enforced MFA a second time, the user would need to respond to the MFA prompt again. Repeated authentication and MFA prompts pose a burden on the user and can take focus away from the critical work they need to do.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, mfa. Contains security framework guidance for authentication systems. Source: Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information."}]}
{"id": "nist_02427", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 210) udes scanning for ports, protocols, and services that should not be accessible to users and for improperly configured or incorrectly operating information flow mechanisms. Requirement Enhancements 1. The organization employs vulnerability scanning tools that include the capability to update the list of smart grid information system vulnerabilities scanned; and 2. The organization includes privileged access authorization to organization-defined smart grid information system components for selected vulnerability scanning activities to facilitate more thorough scanning. Additional Considerations A1. A2. A3. The organization employs automated mechanisms on an organization-defined frequency to detect the presence of unauthorized software on organizational smart grid information systems and notifies designated organizational officials; The organization performs security testing to determine the level of difficulty in circumventing the security requirements of the smart grid information system; and The organization employs automated mechanisms to compare the results of vulnerability scans over time to determine trends in smart grid information system vulnerabilities. Impact Level Allocation Low: SG.RA-6 Moderate: SG.RA-6 (1) High: SG.RA-6 (1), (2) 3.23 SMART GRID INFORMATION SYSTEM AND SERVICES ACQUISITION (SG.SA) Smart grid information systems and services acquisition covers the contracting and acquiring of system components, software, firmware, and services from employees, contactors, and third parties. A policy with detailed procedures for reviewing acquisitions should reduce the introduction of additional or unknown vulnerabilities into the smart grid information system. SG.SA-1 Procedures Smart Grid Information System and Services Acquisition Policy and Category: Common Governance, Risk, and Compliance (GRC) Requirements 185 Requirement 1. The organization develops, implements, reviews, and updates on an organization-defined frequency\u2014 a.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, privileged access. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02428", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Recommended Confidentiality Impact Level according to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices? Recommended Confidentiality Impact Level: The provisional confidentiality impact level recommended for public comment tracking information is low .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_02429", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for the Secure Deployment of IPv6 say about 3.5.6 Security Ramifications? (Part 4) According to Guidelines for the Secure Deployment of IPv6, 3.5.6 Security Ramifications: ful firewalls can limit even allowed types to those that could legitimately be part of permitted traffic flows. Table 3-7 gives recommended ICMPv6 firewall settings for various possible traffic types. The -Maintenance of Communications\u2016 and -Error Messages\u2016 sections of the table assume the more sophisticated connection-association capabilities mentioned above; less-sophisticated firewalls would have to allow these messages whenever a corresponding connection could occur, based on other rules (e.g., allowed source and destination addresses).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_02430", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-2 in Computer Security Division 2004 Annual Report? (Part 68) Control HA-2: ter Security Division Information Technology Laboratory National Institute of Standards and Technology U.S. Department of Commerce Carlos M. Gutierrez, Secretary Technology Administration Phillip J. Bond, Under Secretary for Technology National Institute of Standards and Technology Hratch Semerjian, Acting Director NIST IR 7219 April 2005 Disclaimer: Any mention of commercial products is for information only; it does not imply NIST recommendation or endorsement, nor does it imply that the products mentioned are necessarily the best available for the purpose. Michael James, Design/Production The DesignPond", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2004 Annual Report."}]}
{"id": "nist_02431", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series say about cookie? According to Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series, cookie: A piece of state information supplied by a web server to a browser that is temporarily stored and returned to the server on any subsequent visits or requests.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series."}]}
{"id": "nist_02432", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-256 in Derived PIV Application and Data Model Test Guidelines? (Part 141) Control HA-256: '07' as P1 value, the command returns the transported key with status word '90 00'. Compare the test toolkit application's copy of the plaintext key to the one received in the response from the token. For algorithm reference '11' or '14' as P1 value, the command returns the shared secret Z 16 with | 15 Template '85' contains the other party's public key, a point on Curve P-256 or P-384, encoded as '04' || X || Y, without the use of point compression, as described in Section 2.3.3 of [SEC1]. 16 Z is the X coordinate of point P as defined in [SP800-56A], Section 5.7.1.2 | | status word '90 00'. Compare the shared secret computed by the token with the shared secret computed off token (using the key management public key that was returned in Step 6). | |------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Postcondition(s) | The token has newly generated private key(s). | ## 9. Test Assertions for the Derived PIV Application Data Model This section lists the test assertions used to determine conformity to the derived test requirements (DTR) listed in Section 7. The Implementation Under Test (IUT), the Derived PIV Data Objects loaded on a Derived PIV Application by an issuer, must meet the stated objective(s) of the assertion by way of a test or submission of artifacts in order to be deemed conformant to the associated DTR(s). ## 9.1 BER-TLV Conformance The following assumptions apply to the test assertions within this section. Table 1 - Encoding of Length Field | 1 | When the length of the value field is between 0 and 127 bytes, the length field should consist of a single byte where bit 8 is set to 0 and bits 7 to 1 encode the number of bytes in the value field. When the length of the value field is greater than 127 bytes, the length field consists of two or more bytes.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, token, sso. Contains security framework guidance for authentication systems. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_02433", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations provide? (Section 125) Enumeration (CWE), which is a dictionary of weaknesses that can lead to exploitable vulnerabilities (i.e., CVEs) and the Common Weakness Scoring System (CWSS) for assigning risk scores to weaknesses. SwAAP also uses the Common Attack Pattern Enumeration &amp; Classification (CAPEC), which is a publicly available catalog of attack patterns with a comprehensive schema and classification taxonomy, to provide descriptions of common methods for exploiting software and the Malware Attribute Enumeration &amp; Characterization (MAEC), which provides a standardized language for encoding and communicating information about malware based upon attributes such as behaviors, artifacts, and attack patterns. There are a number of software assurance tools and technologies that are now incorporating many of these automation specifications to provide software security throughout the software development life cycle. The implementation and effective use of software assurance technologies can assist organizations in automating the implementation, assessment, and continuous monitoring of several NIST SP 800-53 security controls including CA-7, Continuous Monitoring; SA-4, Acquisitions; SA-8, Security Engineering Principles; SA-11, Developer Security Testing; SA-12, Supply Chain Protection; SA-13, Trustworthiness; SA-14, Critical Information System Components; and SI-13, Predictable Failure Prevention. Aggregation and analysis technologies are those that have the capability to collect raw data from one or more security controls or other direct data gathering technologies and correlate, analyze, and represent the raw data in a way that provides a more meaningful perspective on the effectiveness of security control implementation across part or all of an organization than would data from any single technology. This section discusses common types of aggregation and analysis technologies and their role in supporting an ISCM capability. They include SIEM and management dashboards.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, malware. Contains technical security guidance that could inform defensive posture. Source: Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations."}]}
{"id": "nist_02434", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TE-1 in Mobile Device Security_ Bring Your Own Device (BYOD)? (Part 27) Control TE-1: ites - phishing protection risky URLs - application forensics - application binaries (Android only) - application inventory (Android only) zIPS also collects some information that cannot be disabled. These items include: - device root/jailbreak status - USB debug mode status (Android only) - developer mode status (Android only) - 3 rd party app store presence (Android only) - mobile OS-specific vulnerability status (e.g., Stagefright) - device encryption status (Android only) - device protection status - screen lock status zIPS must collect certain data items to properly communicate with the zConsole. These items include: - user credentials (email address, Zimperium-specific password) - mobile network operator - mobile network country code - device operating system - device push token - hash of local z9 database - time and name of threat detection when a threat occurs ## 4.7.3 Application Vetting: Kryptowire Kryptowire collects certain pieces of device information through the MaaS360 REST API for analytics and application association purposes. The data collected includes: - MDM device ID - MDM device name - MDM username - last MDM sync date - MDM enrollment data - enterprise and non-app store installed applications ## 4.7.4 VPN: Palo Alto Networks The Palo Alto Networks VPN uses information about the device as it establishes VPN connections.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: token, sso. Contains security framework guidance for authentication systems. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_02435", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 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 say about B . Government: Obligations of Processors of Personal Data? (Part 3) 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 , B . Government: Obligations of Processors of Personal Data: tion for and purposes of collection, the extra-agency disclosures (\"routine uses\") that may be made of the data collected, and the consequences to the individual of failing to provide the information. Personal data must be collected as much as possible directly from the record subject, and information may not ordinarily be collected about an individual's exercise of First Amendment rights ( e . q , freedom of expression, assembly, and religion). 5 U.S.C. \u00a7 552a. The 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. \u00a7 9. Many State fair information practice statutes limit the type of information that the State government can collect and maintain about individuals. See , e . q . Ark. Stat. \u00a7 16-804; Conn. Gen. Stat. \u00a7 4-190; 111. Stat. ch. 116, \u00a7 43.5; Mass. Gen. L. ch. 119, \u00a7 51E; Mass. Gen. L. ch. 66, \u00a7 17A; Ohio Rev. Code 1347.01; Va . Code 2.1-377;. 2. \u00a7 \u00a7 10. Furthermore, statutes in nearly every State limit the ability of government to disclose personal data to third parties. See Ala. Code \u00a7 41-8-10; Alaska Stat. \u00a7 09.25.140; Ark. Stat. \u00a7 16-804; Cal. Civil Code \u00a7 1798; Colo. Rev. Stat. \u00a7 24-72 . 204 (3) (a) ; Conn. Gen. Stat. \u00a7 4-190; D.C. Code \u00a7 37-106.2; Fla. Stat. \u00a7 257.261; 111. Stat. ch . 116, \u00a7 43.5; 111. Stat. ch. 81, \u00a7 1202; Ind. Code \u00a7 4-1-6; Iowa Code \u00a7 68A.7(13); Ky. Rev. Stat. \u00a7 61.870; La. Rev. Stat. \u00a7 44:13; Me. Rev. Stat. tit. 27, \u00a7 121; Me. Rev. Stat. tit. 5, \u00a7 1851; Mich. Comp. Laws \u00a7 397.603; Minn. Stat. \u00a7 13.01; Miss. Code \u00a725-53-53; Mo. Stat. \u00a7 182.817; Mont. Rev. Code \u00a7 22-1-1103; Neb. Rev. Stat. \u00a7 84-712.05; Nev. Rev. Stat.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. 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 ."}]}
{"id": "nist_02436", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Considerations for Remote Electronic UOCAVA Voting say about Property: Proper software engineering practices? According to Security Considerations for Remote Electronic UOCAVA Voting, Property: Proper software engineering practices: The voting system software is designed, implemented, tested and deployed with accepted software engineering best practices.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Remote Electronic UOCAVA Voting."}]}
{"id": "nist_02437", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Extension: according to NIST COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0 According to COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0, Extension:: Not hierarchical to any other component. Dependencies: None FPT\\_SYN-CSPP.1.1 The TSF shall support the system capability to provide the capability to synchronize distributed TSF elements and to associate audit event records produced by multiple TSF entities. Refinement (to CSPP component): See FPT\\_SYN-CSPP.1.1 in [CSPP]. Application note: This component is similar to FPT\\_STM 'Time stamps', but calls out the synchronization requirement instead of a specifying a mechanism (i.e., reliable time stamps') that could be used for that purpose.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0."}]}
{"id": "nist_02438", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Data Network Systems (SDNS) Access Control Documents say about 4.2.3 COMPARE EV AND PDU LABEL? According to Secure Data Network Systems (SDNS) Access Control Documents, 4.2.3 COMPARE EV AND PDU LABEL: Inputs: Enforcement Vector PDU Attributes Local Configuration Information Outputs: PAE Result = Pass/Fail", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Data Network Systems (SDNS) Access Control Documents."}]}
{"id": "nist_02439", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Web Transactions_ TLS Server Certificate Management say about Download a Certificate from the CertCentral Account? According to Securing Web Transactions_ TLS Server Certificate Management, Download a Certificate from the CertCentral Account: After DigiCert issues the certificate, access it from inside the CertCentral account. 1. In the CertCentral account, go to the Orders page. In the sidebar menu, click Certificates &gt; Orders. 2. On the Orders page, use the filters and advanced search features to locate the certificate to be downloaded. 3. In the Order # column of the certificate to be downloaded, click the Quick View link. 4. In the Order # details pane (on the right), using the Download Certificate As drop-down, select the certificate format to be used. - a. .crt (best for Apache/Linux) Download the certificate in a .crt format, best for Apache/Linux platforms. - b. .pb7 (best for Microsoft and Java) Download the certificate in a .pb7 format, best for Microsoft and Java platforms. 5. (OPTIONAL) In the Download Certificate As drop-down, click More Options to see more Server Platform options and File Type options or to download only the Certificate, the Intermediate Certificate, or the Root Certificate. 6. Download a Combined Certificate File In the Download Certificate window, under Combined Certificate Files, use any of these options to download the combined SSL certificate file. - a. Platform specific In the Server Platform drop-down, select the server where the SSL/TLS certificate will be installed, and then click Download.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_02440", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Methodology for Characterizing Network Behavior of Internet of Things Devices say about Abstract? According to Methodology for Characterizing Network Behavior of Internet of Things Devices, Abstract: This report describes an approach to capturing and documenting the network communication behavior of Internet of Things (IoT) devices. From this information, manufacturers, network administrators, and others can create and use files based on the Manufacturer Usage Description (MUD) specification to manage access to and from those IoT devices. The report also describes the current state of implementation of the approach and proposals for future development.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Methodology for Characterizing Network Behavior of Internet of Things Devices."}]}
{"id": "nist_02441", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-4(2) in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Control SI-4(2): Wireless Sniffing (T0887) Encrypt Network Traffic (M0808) Minimize Wireless Signal Propagation (M0806) Damage Assessment, Behavior Validation Obfuscation Obfuscation Negate, Degrade, Exert Negate, Degrade, Exert", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_02442", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Section 333) | \u2022 Authorizing Official or Authorizing Official Designated Representative | \u2022 System Owner or Common Control Provider \u2022 Information Owner or Steward \u2022 System Security Officer \u2022 System Privacy Officer \u2022 Senior Agency Information Security Officer \u2022 Senior Agency Official for Privacy | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ TABLE E-7: MONITORING TASKS, RESPONSIBILITIES, AND SUPPORTING ROLES | RMF TASKS | PRIMARY RESPONSIBILITY | SUPPORTING ROLES | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | TASK M-1 System and Environment Changes Monitor the information system and its environment of operation for changes that impact the security and privacy posture of the system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, rmf, fips. General security reference material without sensitive content. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_02443", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Management_ Part 1 \u2013 General provide? (Section 91) vice to be provided. Asymmetric algorithms are used, for example, to: 1. Provide source, identity, and integrity authentication services in the form of digital signatures, 31 and 2. Establish cryptographic keying material using key-agreement and key-transport algorithms. 32 SP 800-175B provides discussions on the use of asymmetric-key algorithms to generate digital signatures and establish keying material. Random bit generators (RBGs) (also called random number generators (RNGs)) are required for the generation of keying material (e.g., keys and IVs). RBGs generate sequences of random bits (e.g., 010011); technically, RNGs translate those bits into numbers (e.g., 010011 is translated into the number 19). However, the term 'random number generator' (RNG) is commonly used to refer to both concepts. The use of RBGs is discussed in SP 800-175B; approved RBGs are specified in the SP 800-90 series of documents. 29 For example, see FIPS 197 and SP 800-38F. 30 Sometimes, a key pair is generated by a party that is trusted by the key owner rather than by the key owner and then provided to the key owner. 31 See FIPS 186. 32 See SP 800-56A and SP 800-56B. This section classifies the different types of keys and other cryptographic information according to their uses; discusses cryptoperiods and suggests appropriate cryptoperiods for each key type; provides recommendations and requirements for other keying material; introduces assurance of domain-parameter validity, public-key validity, and private-key possession; discusses the implications of the compromise of keying material; and provides guidance on the selection, implementation, and replacement of cryptographic algorithms and key sizes according to their security strengths. There are several different types of cryptographic keys, each used for a different purpose.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02444", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain EVALUATION OF HARDWARE/SOFTWARE PRODUCT THAT PERFORMS A DIRECT COMPUTER SECURITY FUNCTION according to NIST Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out According to Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out, EVALUATION OF HARDWARE/SOFTWARE PRODUCT THAT PERFORMS A DIRECT COMPUTER SECURITY FUNCTION: - o OMB Circular A-130, Appendix III, Security of Federal Automated Information Systems - o OMB Bulletin 90-08, Guidance for Preparation of Security Plans for Federal Computer Systems that Contain Sensitive Information - o Model Framework for Management Control Over Automated Information Systems, January 1988, PCMI", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out."}]}
{"id": "nist_02445", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)? (Part 63) Control PD-12: ort contains- (i) the results of the assessment; (ii) recommendations for correcting deficiencies; and (iii) the residual risk to the organization if those deficiencies are not corrected or mitigated. The assessment report is the Assessor's statement of the results of analyzing and evaluating the issuer's implementation of controls. The sample assessment report template in Appendix E should be used as a format for documenting the results after assessing the issuer controls. ## Task 5: Assessment Documentation This task consists of the Assessor submitting the assessment report to the OIMO and the latter adding the issuer's operations plan (revised if necessary) and the corrective actions plan (CAP) to generate an authorization submission package for the DAO. In situations where the assessment report contains deficiencies, the OIMO may choose to address some deficiencies based on the recommendations by the Assessor and revise the operations plan (if needed), even before submitting the package for authorization. Subtask 5.1: Provide the OIMO with the assessment report. Responsibility: Assessor Guidance: The OIMO relies on the expertise, experience, and judgment of the Assessor to: (i) provide recommendations on how to correct deficiencies in the planned or performed operations; and (ii) to understand the potential impacts of those deficiencies. The OIMO may choose to act on selected recommendations of the Assessor before the authorization package is finalized. To optimize the utilization of resources organization-wide, any actions taken by the OIMO prior to the final authorization decision must be coordinated with the DAO. The Assessor reviews any changes made in response to the corrective actions and revises the assessment report, as appropriate. Subtask 5.2: Revise the operations plan (if necessary) and implement its new provisions.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_02446", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-3 in Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders? (Part 124) Control AC-3: cument. In the lab, local\\_policy.jar was extracted to the default location, &lt;javahome&gt;/lib/security.Network Configuration . - Check if the firewall is running or not by using the command below. If it is up, it will return a status that shows it is running: - If it is not running, activate the firewall by using the following command: - Check if the required ports, 9031 and 9999, are open by using the following command: - This command will return the following values: ``` firewall-cmd --state ``` ``` sudo systemctl start firewalld.service ``` ``` firewall-cmd --list-ports ``` 6031/tcp 9999/udp 9031/tcp 6031/udp 9998/udp 9031/udp 9999/tcp 9998/tcp 8080/tcp From the returned ports, we can determine which ports and protocols are open. - In case the required ports are not open, issue the command below. It should return success . - Reload the firewall by using the following command to make the rule change take effect: - Now, when the open ports are listed, the required ports should show up: ``` firewall-cmd --zone=public --permanent --add-port=9031/tcp success ``` ``` firewall-cmd --reload Success ``` firewall-cmd --zone=public --list-ports 6031/tcp 9999/udp 9031/tcp 6031/udp 9998/udp 9031/udp 9999/tcp 9998/tcp 8080/tcp 5000/tcp ## 3.2.3 PingFederate Installation Ping installation documentation is available at gettingStartedGuide/pf\\_t\\_installPingFederateRedHatEnterpriseLinux.html. . ## Some important points are listed below: - \uf0a7 Obtain a Ping Identity license. It can be acquired from https://www.pingidentity.com/en/account/sign-on.html. - \uf0a7 For this experiment, installation was done using the zip file. Installation was done at /usr/share . - \uf0a7 The license was updated. - \uf0a7 The PingFederate service can be configured as a service that automatically starts at system boot. PingFederate provides instructions for doing this on different OSs.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, single sign-on. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_02447", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Small Business Information Security_ The Fundamentals provide? (Section 47) able to meet their contractual agreement. Regularly assess your processes, procedures, and technology solutions according to your risks (see Section 2). Make corrections and improvements as necessary. You may want to consider conducting training or table-top exercises which simulate or run-through a major event scenario in order to identify potential weaknesses in your processes, procedures, technology, or personnel readiness. Make corrections as needed. Many incidents can be prevented by practicing safe and secure business habits. Unlike the previous section, which looked at programmatic steps you can take within your business, this section focuses on every-day activities you and your employees can do to help keep your business safe and secure. While criminals are becoming more sophisticated, most criminals still use well-known and easily avoidable methods. This section provides a list of recommended practices to help protect your business. Each employee should be trained to follow these basic practices. Get to know them and maintain contact with your employees, including any contractors your business or building may employ (e.g. for cleaning, security, or maintenance). 16 Watch for unusual activity or warning signs such as the employee mentions financial problems, begins working strange hours, asks for a lot of overtime, or becomes unusually secretive. In most cases, this activity is benign, but occasionally it can be an indicator that the employee is or may begin stealing information or money from the business, or otherwise damaging the company. Watch for unusual activity near your place of business or in your industry. Similarly, know if other businesses in your area perform any activities which may pose an environmental or safety risk. An event that affects your neighbors may affect your business as well, or indicate new risks in your area, so it is important to remain aware.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Small Business Information Security_ The Fundamentals."}]}
{"id": "nist_02448", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Derived Personal Identity Verification (PIV) Credentials say about identity management system identity proofing? (Part 1) According to Derived Personal Identity Verification (PIV) Credentials, identity management system identity proofing: identity management system identity proofing Perimeter network segment that is logically between internal and external networks. Its purpose is to enforce the internal network's information assurance policy for external information exchange and to provide external, untrusted sources with restricted access to releasable information while shielding the internal networks from outside attacks. A standardized application residing on a removable hardware cryptographic token that hosts a Derived PIV Credential and associated mandatory and optional elements An X.509 Derived PIV Authentication certificate with associated public and private key that is issued in accordance with the requirements specified in this document where the PIV Authentication certificate on the applicant's PIV Card serves as the original credential. The Derived PIV Credential (DPC) is an additional common identity credential under Homeland Security Presidential Directive-12 and Federal Information Processing Standards (FIPS) 201 that is issued by a federal department or agency and is used with mobile devices. A measure of trust or confidence in an authentication mechanism defined in publications Office of Management and Budget (OMB)-04-04 and NIST SP 800-63 in terms of four levels: - \uf0a7 Level 1: LITTLE OR NO confidence - \uf0a7 Level 2: SOME confidence - \uf0a7 Level 3: HIGH confidence - \uf0a7 Level 4: VERY HIGH confidence A standard for adoption and use by federal departments and agencies that has been developed within the Information Technology Laboratory and published by NIST. A standard in FIPS covers a specific topic in information technology to achieve a common level of quality or some level of interoperability.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, identity management, token. Contains security framework guidance for authentication systems. Source: Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_02449", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-11 in Guidelines for Smart Grid Cybersecurity? (Part 57) Control SI-11: mation voluntarily turned over to Third Parties is \"ill-suited for the digital age we live in today.\u201d Although it ruled against Golden Valley, the 9th Circuit indicated a possible new legal approach. Specifically, the court said that in some circumstances \"a company's guarantee to its customers that it will safeguard the privacy of their records might suffice to justify resisting an administrative subpoena.\"41 The Court did note that the outcome might have been different if Golden Valley had entered into a contract with its customers specifically agreeing to keep such business records confidential.42 In 2012, the first court case discussing privacy in the context of the smart grid was tried in the Maine Supreme Court. In Friedman, the Maine Supreme Court partially invalidated the Maine Public Utilities Commission\u2019s (\u201cMaine PUC\u201d) dismissal of plaintiff Friedman's objections to a Smart Meter opt-out penalty. First, the court rejected the Maine PUC\u2019s arguments that Friedman\u2019s health and safety concerns had been \u201cresolved\u201d by its opt-out investigations in another proceeding, because the Commission had explicitly declined in those proceedings to make any determination on health and safety -- instead deferring to the jurisdiction of the Federal Communications Commission (FCC). The court held the Maine PUC could not explicitly decline to make determinations on health and safety in the opt-out investigations proceedings, and then attempt to treat the issues as \u201cresolved\u201d in this proceeding. Having never determined whether the smart-meter technology is safe, it could not conclude whether the opt-out fee was \u201cunreasonable or unjustly discriminatory.\u201d Second, the Maine Supreme Court concluded that the Maine PUC had resolved the privacy, trespass, and Fourth Amendment claims against the utility, but did not state exactly how the Maine PUC concluded that was the case.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02450", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Section 72) tials for facility access. - c. Review the facility access list [ Assignment: organization-defined frequency ]. - d. Remove individuals from the facility access list when access is no longer required. A facility can include one or more physical locations containing systems or system components that process, store, or transmit CUI. Physical access authorizations apply to employees and visitors. Individuals with permanent physical access authorization credentials are not considered visitors. Authorization credentials include identification badges, identification cards, and smart cards. Organizations determine the strength of the authorization credentials consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines. Physical access authorizations may not be necessary to access certain areas within facilities that are designated as publicly accessible. Source Control: PE-02 Supporting Publications: None - a. Monitor physical access to the facility where the system resides to detect and respond to physical security incidents. - b. Review physical access logs [ Assignment: organization-defined frequency ] and upon occurrence of [ Assignment: organization-defined events or potential indications of events ]. NIST SP 800-171r3 May 2024 A facility can include one or more physical locations containing systems or system components that process, store, or transmit CUI. Physical access monitoring includes publicly accessible areas within organizational facilities. Examples of physical access monitoring include guards, video surveillance equipment (i.e., cameras), and sensor devices. Reviewing physical access logs can help to identify suspicious activities, anomalous events, or potential threats. The reviews can be supported by audit logging controls if the access logs are part of an automated system. Incident response capabilities include investigations of physical security incidents and responses to those incidents.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_02451", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector say about ACKNOWLEDGEMENTS? (Part 1) According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector, ACKNOWLEDGEMENTS: ACKNOWLEDGEMENTS We are grateful to the following individuals for their generous contributions of expertise and time. | Name | Organization | |--------------------|-----------------------------| | Dan Frechette | Microsoft | | Ian Schmertzler | Dispel | | Ben Burke | Dispel | | Chris Jensen | Tenable | | Bethany Brower | VMWare | | Dennis Hui | OSIsoft (now part of AVEVA) | | John Matranga | OSIsoft (now part of AVEVA) | | Michael A. Piccalo | Forescout | | Tim Jones | Forescout | | Yejin Jang | Forescout | | Samantha Pelletier | TDI Technologies | | Rusty Hale | TDI Technologies | | Steve Petruzzo | GreenTec-USA | | Josh Carlson | Dragos | | Alex Baretta | Dragos | The Technology Partners/Collaborators who participated in this build submitted their capabilities in response to a notice in the Federal Register. Respondents with relevant capabilities or product components were invited to sign a Cooperative Research and Development Agreement (CRADA) with NIST, allowing them to participate in a consortium to build this example solution.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector."}]}
{"id": "nist_02452", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PE-22 in Security and Privacy Controls for Information Systems and Organizations? Control PE-22: COMPONENT MARKING Control: Mark [Assignment: organization-defined system hardware components] indicating the impact level or classification level of the information permitted to be processed, stored, or transmitted by the hardware component. CHAPTER THREE PAGE 192 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ Discussion: Hardware components that may require marking include input and output devices. Input devices include desktop and notebook computers, keyboards, tablets, and smart phones. Output devices include printers, monitors/video displays, facsimile machines, scanners, copiers, and audio devices. Permissions controlling output to the output devices are addressed in AC-3 or", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02453", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PA-220 in Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)? (Part 246) Control PA-220: . 1. In the MobileIron Admin Portal, navigate to Policies &amp; Configs &gt; Compliance Actions. 2. Select Add; the Add Compliance Action dialogue opens. 3. In the Add Compliance Action dialogue: - a. In the Name field, add a description of the compliance action; we recommend indicating the kind of action taken. This example illustrates creating a compliance action that will be associated with the MTP - High Risk label. - b. Select the Enforce Compliance Actions Locally on Devices check box. - c. Select the Send a compliance notification or alert to the user check box. - d. Select the Block email access and AppConnect apps check box. - e. Select the Quarantine the device check box. - f. Deselect the Remove All Configurations check box. - g. Click Save. Figure 2-124 MTP High Risk Compliance Action <!-- image --> ## 2.7.7.3 Create MobileIron Security Policy for Lookout MES In addition to potentially defining other controls, such as password requirements, a Security Policy can map a Compliance Action to an App Control rule, enabling MobileIron to execute the configured actions whenever a device that applies the policy violates the App Control rule. The following steps will create a new Security Policy for Lookout MES High Risk devices using an existing policy as a baseline from which to apply more stringent controls. 1. In the MobileIron Admin Portal , navigate to Policies &amp; Configs &gt; Policies. 2. On the Policies page: - a. Select the security policy to use as a baseline. - b. Select More Actions &gt; Save As ; this opens the New Security Policy dialogue. - c. In the New Security Policy dialogue: - i. In the Name field, rename the policy to MTP - High Risk. - ii. In the Priority drop-down menu, select a current policy. The new policy will be prioritized based on the selection. In this example, the new policy is higher than the MTP Medium Risk policy.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_02454", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain CSD's Part in National and I nternational ISO Security Standards Processes according to NIST Computer Security Division 2015 Annual Report According to Computer Security Division 2015 Annual Report, CSD's Part in National and I nternational ISO Security Standards Processes: Figure 1 shows many of the national and international standards developing organizations (SDOs) involved in cybersecurity standardization. CSD participates in many cybersecurity standards' activities in many of these organizations, either in leadership positions or as editors and contributors, including the Biometric Application Programming Interface (BioAPI) Consortium; the Bluetooth Special Interest Group (SIG): Bluetooth Security Expert Group (BT-SEG); the International Telecommunications Union - Telecommunication Standardization Sector (ITU-T); various groups within the Institute of Electrical and Electronics Engineers (IEEE) and the Internet Engineering Task Force (IETF); the North American Security Products Organization (NASPO); the Trusted Computing Group (TCG); and Accredited Standards Committee X9, Inc. (ASC X9, Inc.) (e.g., X9F - Data &amp; Information Security Subcommittee). Many of CSD's publications have been the basis for both national and international standards projects. The following paragraphs discuss, in particular, CSD staff activities in conjunction with the InterNational Committee for Information Technology Standards (INCITS) Technical Committee Cyber Security (CS1), where CSD's Sal Francomacaro served as the CS1 Vice Chair.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2015 Annual Report."}]}
{"id": "nist_02455", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Audience according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, Audience: This publication serves a diverse group of individuals and organizations in the public and private sectors, including 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) - Acquisition or procurement responsibilities (e.g., contracting officers) - System, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers) - Security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, independent verifiers/validators, analysts) The above roles and responsibilities can be viewed from two perspectives: - Federal perspective : The entity establishing and conveying security assessment requirements in contractual vehicles or other types of agreements - Nonfederal perspective : The entity responding to and complying with the security assessment requirements set forth in contracts or agreements", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02456", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RS-0010 in Biometric Specifications for Personal Identity Verification? (Part 29) Control RS-0010: | '97' | | | | | | A1 | Var. | Biometric Header Template (BHT) conforming to ISO/IEC 19785-3:2005 | Biometric Header Template (BHT) conforming to ISO/IEC 19785-3:2005 | Biometric Header Template (BHT) conforming to ISO/IEC 19785-3:2005 | | | | | | | | | Tag | Len.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Biometric Specifications for Personal Identity Verification."}]}
{"id": "nist_02457", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Telehealth Remote Patient Monitoring Ecosystem say about E-1 Device Capabilities Mapping? (Part 45) According to Securing Telehealth Remote Patient Monitoring Ecosystem, E-1 Device Capabilities Mapping: | | PR.DS-3: Assets are formally managed throughout removal, transfers, and disposition. | N/A | N/A | 45 C.F.R. \u00a7\u00a7 164.308(a)(1)(ii)(A) 164.310(a)(2)(ii) 164.310(a)(2)(iii) 164.310(a)(2)(iv) 164.310(d)(1) 164.310(d)(2) | | PR.DS-4: Adequate capacity to ensure availability is maintained. | \uf0a7 Ability to enforce configured disk quotas. \uf0a7 Ability to provide sufficient resources to store and run the operating environment (e.g., operating systems, firmware, applications). \uf0a7 Ability to utilize file compression technologies (e.g., to protect against denial of service). | N/A | 45 C.F.R. \u00a7\u00a7 164.308(a)(1)(ii)(A) 164.308(a)(1)(ii)(B) 164.308(a)(7) 164.310(a)(2)(i) 164.310(d)(2)(iv) 164.312(a)(2)(ii) | | PR.DS-5: Protections against data leaks are implemented. | \uf0a7 Ability to control device responses to device input. \uf0a7 Ability to control output from the device. | N/A | 45 C.F.R. \u00a7\u00a7 164.308(a)(1)(ii)(D) 164.308(a)(3) 164.308(a)(4) 164.310(b) 164.310(c) 164.312(a) | | PR.DS-6: Integrity checking | \uf0a7 Ability to identify software loaded on the IoT device based on IoT device identity. | \uf0a7 Providing documentation and/or other communications describing how to | 45 C.F.R. \u00a7\u00a7 164.308(a)(1)(ii)(D) | .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_02458", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Securing Public Web Servers say about Miscellaneous Web Security Resources? According to Guidelines on Securing Public Web Servers, Miscellaneous Web Security Resources: | Resource/Title | URL | |---------------------------------------|----------------------------------------------------------------------| | dominosecurity.org | | | Honeynet Project | | | Lotus Domino Security Page | http://www-128.ibm.com/developerworks/lotus/security/ | | Microsoft Internet Explorer Home Page | http://www.microsoft.com/windows/products/winfamily/ie/default .mspx | | Mozilla Security Center | http://www.mozilla.org/security/ | | Netcraft | http://www.netcraft.com/ |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Securing Public Web Servers."}]}
{"id": "nist_02459", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Web Transactions_ TLS Server Certificate Management provide? (Section 327) ources. Examples include file servers (to store files), print servers (to manage one or more printers), network servers (to manage network traffic), and database servers (to process database queries). (NIST SP 800-47) | | Service Provider | A provider of basic services or value-added services for operation of a network; generally refers to public carriers and other commercial enterprises. (NISTIR 4734) | | Simple Certificate Enrollment Protocol (SCEP) | A protocol defined in an IETF internet draft specification that is used by numerous manufacturers of network equipment and software that are developing simplified means of handling certificates for large-scale implementation to everyday users, as well as referenced in other industry standards. | | Simple Mail Transfer Protocol | The primary protocol used to transfer electronic mail messages on the internet. (NISTIR 7387) | | Special Publication | A type of publication issued by NIST. Specifically, the Special Publica- tion 800 series reports on the Information Technology Laboratory's research, guidelines, and outreach efforts in computer security and its collaborative activities with industry, government, and academic | | | organizations. The 1800 series reports the results of National Cyber- security Center of Excellence demonstration projects.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_02460", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Training & Awareness Course Compendium say about VENDOR:? According to Computer Security Training & Awareness Course Compendium, VENDOR:: Anne Arundel Community College Engineering and Computer Technology Careers 219 101 College Parkway Arnold, MD 21012-1895 Gail Reese: (410) 541-2758 A survey of topics in data retention and control and techniques associated with data, computer systems, network and installation security. The student will obtain skills related to occupations in data libraries and data security at computer installations. NOTE: Three semester hours; prerequisite: CSI 113 or permission of department head. COURSE TITLE: COURSE LENGTH: 2 DAYS TEMPEST Program Management and Systems Engineering", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Training & Awareness Course Compendium."}]}
{"id": "nist_02461", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Section 408) ended user environment for the product or service, and supplier information. Define risk analysis and the criteria that will be utilized to assess the scoring of the product or service being assessed. Include a rubric with categorical definitions to encourage the transparency of assessment results. The C-SCRA risk exposure reflects a combined judgement based on likelihood and impact analyses. The likelihood analysis is scored via a combination of the aforementioned threat and vulnerability analysis score, as outlined in the figure below. Fig. 11. Example Likelihood Determination | Likelihood Level | Likelihood Level | Likelihood Level | Likelihood Level | Likelihood Level | Likelihood Level | |--------------------|--------------------|--------------------|--------------------|--------------------|--------------------| | Threat | Vulnerability | Vulnerability | Vulnerability | Vulnerability | Vulnerability | | Threat | | Low | Moderate | High | Critical | | Threat | Critical | Moderately Likely | Highly Likely | Very Likely | Very Likely | | Threat | High | Moderately Likely | Highly Likely | Highly Likely | Very Likely | | Threat | Moderate | Unlikely | Moderately Likely | Highly Likely | Highly Likely | | Threat | Low | Unlikely | Unlikely | Moderately Likely | Moderately Likely | The C-SCRA risk exposure is then aggregated based on that likelihood score and the impact score. If multiple vulnerabilities are identified for a given product or service, each vulnerability shall be assigned a risk level based on its likelihood and impact. Fig. 12.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_02462", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Guidelines for Storage Infrastructure provide? (Section 61) backup is sensitive to multiple failures. For example, incorrect configuration could involve a live database backup performed without applying techniques to ensure consistency or write-order fidelity. Insufficient currency or retention could mean that at least some portion of the data, old or new, will be unrecoverable. An attacker, therefore, has a high motivation to target not only a 'primary' data asset but also its backup and copies. When existing copies cannot be compromised, another viable attack strategy could be to interfere with the backup process itself, thereby gradually 'poisoning' future copies. When enough time has passed, the attacker can return to the original goal of compromising the primary data assets, knowing that the only available copies for recovery are too old. Another type of 'poisoning' strategy is to specifically infect backup copies of compute or application assets, such as OS images, software packages, firmware, or even source code repositories. This way, when an individual component or even an entire environment is rebuilt in an attempt to battle an infection, at least some portions of the malware will be included in the restored environment, allowing the attacker to quickly regain control, or inflict more damage. The reversable obfuscation and/or encryption of data results in data becoming unavailable to the user or organization unless it is recovered using a key held only by an attacker. This type of risk is commonly used in ransomware attacks - a form of malware that encrypts the victim's data and demands a ransom to restore access to the data. Although it originally targeted data or files on users' computers or enterprise servers, ransomware has evolved to also include other storage components, such as NAS and backup appliances [30]. Data obfuscation and encryption typically originate from an external source but could also potentially be inflicted by an internal one.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Security Guidelines for Storage Infrastructure."}]}
{"id": "nist_02463", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2013 Annual Report say about Contact:? According to Computer Security Division 2013 Annual Report, Contact:: Dr. Ren\u00e9 Peralta (301) 975-8702 rene.peralta@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2013 Annual Report."}]}
{"id": "nist_02464", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Status Report on the Final Round of the NIST Lightweight Cryptography Standardization Process say about 4. Benchmarking Results? According to Status Report on the Final Round of the NIST Lightweight Cryptography Standardization Process, 4. Benchmarking Results: This section summarizes the main software and hardware performance benchmarking initiatives that were considered during evaluation of the finalists. While these efforts provided crucial information on the performance of the finalists, it is important to note their limitations. Results may not present a complete picture of a finalist's potential for optimization in any particular metric. Further, not all implementations are designed with the same assumptions or goals, and there are more diverse implementations for some finalists than others. More efficient implementations are likely possible for all finalists. As such, the results of these efforts were considered as a general guide and not a strict ranking.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Final Round of the NIST Lightweight Cryptography Standardization Process."}]}
{"id": "nist_02465", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommended Criteria for Cybersecurity Labeling of Consumer Software say about 2.1.2 Terminology Conventions? According to Recommended Criteria for Cybersecurity Labeling of Consumer Software, 2.1.2 Terminology Conventions: The Descriptive Claims group defines two terms, Claimant and Label Scope: A Claimant is defined in broad terms to encompass organizations of varying sizes and functions. This allows for individual developers, developer organizations, publishers, and others to act as the entity making the claims represented in a label and allows for flexibility on the part of the scheme owner. The Label Scope refers to what a label is describing. This allows a claimant to distinguish among software that is either included or excluded from the claims backed by the label (e.g., a mobile app versus a back-end server). This is especially important to the consumer, as it is often difficult to determine where these systems begin and end - their boundaries. For brevity, the criteria in this document frequently use the term 'software' and should be understood as referring to 'software within the label scope.'", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommended Criteria for Cybersecurity Labeling of Consumer Software."}]}
{"id": "nist_02466", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-11 in Guidelines for Smart Grid Cybersecurity? (Part 366) Control SI-11: nticating communication between smart meters and an AMI head end can help ensure that an adversary cannot falsely claim to be the AMI head end and issue control commands to the meter, update firmware. Authenticating the meter to the AMI head end can help ensure that usage information is retrieved from the correct meter. 35 As utilities merge and service territories change, a utility will eventually end up with a collection of smart meters from different vendors. Meter to/from AMI head end authentication should be interoperable to ensure that authentication and authorization information need not be updated separately on different vendor\u2019s AMI systems. Demand response (DR) HAN devices should be securely authenticated to the HAN gateway and vice versa. It is important for a HAN device to authenticate any demand-response commands from the DR head end in order to prevent coordinated falsification of control commands across many HAN devices and/or at rapid rates could lead to grid stability problems. It is important that the DR head end authenticate the HAN device to ensure that commands are delivered to the correct device and that responses from that device are not forged. Interoperability of authentication is essential in order to ensure competition that will lead to low- cost consumer devices. This authentication process should be simple and user-friendly, since it will be utilized and installed by consumers who buy/rent HAN devices. HAN devices obtained by the consumer from the utility may be preprovisioned with authentication information, but HAN devices obtained from retail stores may require provisioning through an Internet connection or may receive their provisioning through the HAN gateway. Authentication and access control is important to meters and AMI access networks (e.g., neighborhood area networks (NANs) and HANs).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02467", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives say about Non-Technological? According to Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives, Non-Technological: Team spirit with a member in charge of governance. The right environment for co-innovation was set up. SITA volunteered to project manage the initiatives, induced a consortium spirit, and organized workshops where participants from all companies could brainstorm and work together face-to-face.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives."}]}
{"id": "nist_02468", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-8 in Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations? (Part 65) Control CM-8: | An organizational official responsible for the development, implementation, assessment, and monitoring of common controls (i.e., security controls inherited by information systems). | | Compensating Security Controls [NISTIR 7298] | The management, operational, and technical controls (i.e., safeguards or countermeasures) employed by an organizationin lieu of the recommended controls in the low, moderate, or high baselines described in NIST Special Publication 800-53, that provide equivalent or comparable protection for an information system. | | Comprehensive Testing [NISTIR 7298] | A test methodology that assumes explicit and substantial knowledge of the internal structure and implementation detail of the assessment object. Also known as white box testing. | | Computer Incident Response Team (CIRT) [CNSSI 4009] | Group of individuals usually consisting of Security Analysts organized to develop, recommend, and coordinate immediate mitigation actions for containment, eradication, and recovery resulting from computer security incidents. Also called a Computer Security Incident Response Team (CSIRT) or a CIRC (Computer Incident Response Center, Computer Incident Response Capability, or Cyber Incident Response Team). | | Confidentiality [44 U.S.C., Sec. 3542] | Preserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information. | | Configuration Control (or Configuration Management) [CNSSI 4009] | Process for controlling modifications to hardware, firmware, software, and documentation to protect the information system against improper modifications before, during, and after system implementation. | | Continuous Monitoring | Maintaining ongoing awareness to support organizational risk decisions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations."}]}
{"id": "nist_02469", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.2.4 Management Interfaces according to NIST Securing Web Transactions_ TLS Server Certificate Management According to Securing Web Transactions_ TLS Server Certificate Management, 5.2.4 Management Interfaces: Certificate owners and the Certificate Services team should provide user interfaces to view and manage certificates. The interfaces should be simple enough to support certificate owners who have small numbers of certificates and perform management operations infrequently. The interfaces should also offer more-sophisticated functionality to support the needs of certificate owners with large numbers of certificates and the needs of the Certificate Services team. The interfaces should provide the following characteristics and functions: - \uf0a7 Inventory view : Certificate owners should be able to view their certificates (to which they have been granted access). The Certificate Services team should be able to view the entire inventory. - \uf0a7 Searching and filtering : Certificate owners with large numbers of certificates, and the Certificate Services team, should be able to search and filter operations so they can quickly find specific certificates. - \uf0a7 Enrollment and renewal : The portal should provide a simple method to request new certificates and to renew existing certificates. Having a single interface for enrollment and renewal across all CAs reduces the retraining needed when moving CAs, resulting in better crypto-agility. - \uf0a7 Approvals : If an external system is not used for reviewing certificate requests, then the portal should provide a method for an approver to perform RA functions to review the relevant details of certificate requests and to approve/reject the requests with comments.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_02470", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-256 in Derived PIV Application and Data Model Test Guidelines? (Part 183) Control HA-256: --------------------------------------------------------------| | Purpose | Verifies that the public key algorithm used for generating the keys is as specified in Table 3-4 of [SP800-78]. | | DTR(s) | \u2022 DTR-07.03.01.03 \u2022 DTR-07.03.01.04 | | Issuer Documentation | None. | | Precondition(s) | \u2022 A token with the Derived PIV Application is inserted into an appropriate token reader. \u2022 Suitable drivers have been loaded between the test system and an instance of the reader. \u2022 A Derived PIV Authentication certificate is present within the Derived PIV Application. | | Test Scenario | 1. Send the SELECT command with \u2022 AID == 'A0 00 00 03 08 00 00 20 00 01 00' 2. Send the GET DATA command with \u2022 Data field of the command containing the tag ('5FC105') of the X.509 Certificate for Derived PIV Authentication data object 3. Extract subjectPublicKeyInfo->algorithm->algorithm field value 4. Match the algorithm value to the Table 3-4 of [SP800-78]. 5. If the algorithm is elliptic curve, ensure that the OID for Curve P-256 from Table 3-5 of [SP800-78] is populated in the subjectPublicKeyInfo->algorithm- >parameters->namedCurve field. Note: If the RSA algorithm is used, the subjectPublicKeyInfo->algorithm->parameters field will be NULL. | | Expected Result(s) | 1.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_02471", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CS-3 in U.S. Department of Energy Risk Assessment Methodology? (Part 121) Control CS-3: ware & | Communications: | Sabotage Unauthorized access Accidents | | M M M H | 3 2 1 1 | | (Hard- Software): | Lighting All | environmental threats | | M | 1 | | f) Procedures, Administration, and Management: | Storm* All environmental | threats | | M M | 1 1 | | g) Environmental Security and Safety: | Storms Fire | | | M L | 1 2 | t 4 ' ii <!-- image --> | DEPARTMENT OF ENERGY ADP SYSTEM RISK ASSESSMENT | DEPARTMENT OF ENERGY ADP SYSTEM RISK ASSESSMENT | DEPARTMENT OF ENERGY ADP SYSTEM RISK ASSESSMENT | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | PAGE 5 | PAGE 5 | |----------------------------------------------------------------|----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|----------------------------------------------------------------|----------------------------------------------------------------| | 5 , COUfiTBRMEASUfiES tDENTmCAJIONS AND WSK PROFILE ACCEPTANCE | 5 , COUfiTBRMEASUfiES tDENTmCAJIONS AND WSK PROFILE ACCEPTANCE | 5 , COUfiTBRMEASUfiES tDENTmCAJIONS AND WSK PROFILE ACCEPTANCE | 5 , COUfiTBRMEASUfiES tDENTmCAJIONS AND WSK PROFILE ACCEPTANCE | 5 , COUfiTBRMEASUfiES tDENTmCAJIONS AND WSK PROFILE ACCEPTANCE | 5 , COUfiTBRMEASUfiES tDENTmCAJIONS AND WSK PROFILE ACCEPTANCE | 5 , COUfiTBRMEASUfiES tDENTmCAJIONS AND WSK PROFILE ACCEPTANCE | | (1) SECURITY DISCIPLINE AREA | (a ) accept CURRENT RISK PROFILE (YES OR NO) | (b)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: U.S. Department of Energy Risk Assessment Methodology."}]}
{"id": "nist_02472", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N provide? (Section 45) licy is to allow access under these critical situations, a policy combining algorithm of 'permit-overrides' is used, while still denying access if only the conditions stated in Rule 1 or Rule 2 apply. ``` // Doctor Access to Medical Records // <Target> /* :Attribute-Category :Attribute ID :Attribute Value */ :access-subject :Role :doctor :access-subject :Role :intern :resource :Resource-id :medical-records :action :Action-id :read :action :Action-id :write </Target> <Rule RuleId = 'Rule 1' Effect='Deny'> <Condition> ``` ``` Function: string-not-equal ``` ``` /* :Attribute-Category :Attribute ID */ :access-subject :WardAssignment :resource :WardLocation </Condition> </Rule> <Rule RuleId = 'Rule 2' Effect='Deny'> <Condition> Function: and Function: string-equal /* :Attribute-Category :Attribute ID :Attribute Value */ :access-subject :Role :intern Function: string-equal /* :Attribute-Category : Attribute ID :Attribute Value */ :action :Action-id :write </Condition> </Rule> <Rule RuleId = 'Rule 3' Effect='Permit'> <Condition> Function: and Function: string-equal /* :Attribute-Category :Attribute ID :Attribute Value */ :access-subject :Role :doctor Function: string-equal /* :Attribute-Category :Attribute ID :Attribute Value */ :resource :PatientStatus :critical </Condition> </Rule> </Policy> ``` Together policies (PolicySets and Policies) and attribute assignments define the authorization state. Table 1 defines the authorization state for Policy 1 by specifying attribute names and values.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N."}]}
{"id": "nist_02473", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2016 NIST_ITL Cybersecurity Program Annual Report say about CONTACTS:? According to 2016 NIST_ITL Cybersecurity Program Annual Report, CONTACTS:: Ms. Elaine Barker (301) 975-2911 elaine.barker@nist.gov Mr. John Kelsey (301) 975-5101 john.kelsey@nist.gov Dr. Meltem S\u00f6nmez Turan (301) 975-4391 Dr. Kerry McKay (301) 975-4969 meltem.turan@nist.gov kerry.mckay@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02474", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls say about 3..8 Session 8. Data Bases and Data Base Management Systems? According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls, 3..8 Session 8. Data Bases and Data Base Management Systems: This, the last session of the workshop, sounds like a very well-defined area with clear limits or boundaries. In a sense it is, but this does not mean it is simple. The state of the art in Data Base Management Systems finds us coming to grips with a variety of structures. There are network, hierarchical, and relational structures with proliferations of access methods, linkages, relationships, and file inversions. There is no universal form for these, and theory and standards are sparse. The challenge to this session has two major aspects. We must deal with the problem of variety, as in most of the other sessions. The other aspect has to do with auditor independence. When an auditor uses a query language to draw information from a data base, he is dependent on the system structure. Should the auditor have an independent access path to data? I phrased this as a question rather than a position; but let me leave no doubt that auditability is, in itself, a control and we have to provide for auditability in all our workshop sessions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls."}]}
{"id": "nist_02475", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Considerations for Voice Over IP Systems say about 4.2.1.3 H.235v2 Annex D - Voice Encryption Option? (Part 3) According to Security Considerations for Voice Over IP Systems, 4.2.1.3 H.235v2 Annex D - Voice Encryption Option: cate requests | | The voice encryption option describes the master key exchange during H.225.0 call signaling and the generation and distribution of media stream keys during H.245 call control. The encryption algorithms are to be used in CBC mode. New is the support of the AES. AES and TDEA may also be used in EOFB mode. The following security mechanisms are described within the voice encryption security profile: - Encryption of RTP packets with an assortment of algorithms and modes to be taken; - Key management with key and security capability exchange; - Key update mechanism and synchronization. The following issues are not covered by this profile: - Encryption and key management for RTCP; - Authentication and integrity for RTP and RTCP (a lightweight authentication and integrity could be provided by media anti-spamming). To counter denial of service and flooding attacks on discovered RTP/UDP ports, the H.235 standard defines the media anti-spamming procedure, which provides lightweight RTP packet authentication and integrity on selected fields through a computed message authentication code (MAC). The algorithms used are tripleDES-MAC or the cryptographic one-way function SHA1. Media anti-spamming uses the padding mechanism of RTP. For this feature, no special security profile was specified in H.235 like the voice encryption security profile for the RTP encryption, but media anti-spamming may be used in combination with media encryption.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_02476", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6.1 Purpose according to NIST Report of the NIST Workshop on Digital Signature Certificate Management, December 10-11, 1992 According to Report of the NIST Workshop on Digital Signature Certificate Management, December 10-11, 1992, 6.1 Purpose: A RevocationList is created by an authority (A) to enumerate all 'active' revoked certificates issued by a set of authorities, which may or may not include A. A revoked certificate is active if it has been issued and the expiry date of the certificate it revokes has not been reached. A Revocation List provides assurance that there are no other active Revoked Certificates issued by the named authorities.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the NIST Workshop on Digital Signature Certificate Management, December 10-11, 1992."}]}
{"id": "nist_02477", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Technology Assessment_ Methods for Measuring the Level of Computer Security say about LIST OF TABLES? (Part 1) According to Technology Assessment_ Methods for Measuring the Level of Computer Security, LIST OF TABLES: LIST OF TABLES | Table | | Page | |---------|-------------------------------------------------------------------------------------------------|--------| | 2-1 2-2 | Environmental Parameter Categories , Dedicated Data Base Management System | 2-2 | | | (e.g.. Airline Reservations) | 2-4 | | 2- 3 | Environmental Influences | 2-6 | | 3- 1 | Applications Systems Controls from the Systems Auditability and Control Study | 3-3 | | 3-2 | Computer Service Center Control Structure | 3-5 | | 3-3 | Application System Development Control Structure | 3-6 | | 3-4 | AFIPS Guideline Evaluation Categories | 3-8 | | 3-5 | Control Evaluation Guide of the Canadian Institute of Chartered Accountants | 3-11 | | 3-6 | Illustrative General Control Structure | 3-21 | | 3-7 | Mutually Exclusive Exposures | 3-23 | | 3-8 | Overlapping Exposures | 3-24 | | 4- 1 | Touche Ross Application Activities Subject to Control ,.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technology Assessment_ Methods for Measuring the Level of Computer Security."}]}
{"id": "nist_02478", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Codes for Identification of Federal and Federally-Assisted Organizations? (Part 65) Control PD-12: | | | Federally Aided Organization: | | 6991 | National Railroad Passenger Corporation (AMTRAK) | ## TABLE OF ORGANIZATIONS AND CODES EXECUTIVE DEPARTMENTS ## (and their associated organizations) ## Code Organization | 2000 | TREASURY , Department of the | |--------|--------------------------------------------------------| | 2001 | Departmental Offices | | 2004 | Inspector General | | 2014 | Office of the Inspector General for Tax Administration | | 2046 | Office of the Comptroller of the Currency | | 2041 | Bureau of Engraving and Printing | | 2042 | Bureau of the Fiscal Service | | 2044 | United States Mint | | 2022 | Alcohol and Tobacco Tax and Trade Bureau | | 2026 | Financial Crimes Enforcement Network | | 2050 | Internal Revenue Service | | | Associated Federal Organizations: | | 2061 | Federal Financing Bank | | 2066 | Community Development Financial Institutions | | | Federally Aided Organizations: | | 2093 | District of Columbia | | 2094 | District of Columbia Public School | ## TABLE OF ORGANIZATIONS AND CODES EXECUTIVE DEPARTMENTS ## (and their associated organizations) ## Code Organization | 3600 | VETERANS AFFAIRS , Department of | |--------|-----------------------------------------------------------------------------------| | 3601 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Codes for Identification of Federal and Federally-Assisted Organizations."}]}
{"id": "nist_02479", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendations for Federal Vulnerability Disclosure Guidelines say about 2.1.3. Develop Technical Analysis Capability? According to Recommendations for Federal Vulnerability Disclosure Guidelines, 2.1.3. Develop Technical Analysis Capability: The FCB may develop technical vulnerability analysis and remediation capabilities to triage the importance of incoming source vulnerability reports, verify the existence of reported vulnerabilities, and assist the VDPO closest to an affected system with analysis and remediation efforts. They could be used, for example, to address severe vulnerabilities applicable to multiple VDPOs and to assist smaller VDPOs that may not have sufficient resources to assess and remediate vulnerabilities.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendations for Federal Vulnerability Disclosure Guidelines."}]}
{"id": "nist_02480", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations say about Sample Text? (Part 4) According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, Sample Text: | Establish processes to respond to identified risks and to monitor for impacts to the enterprise's supply chain | Cancelled | \u2026 | \u2026 | \u2026 | Table 16. Objective 3 - Implementation milestones to position the enterprise as an industry leader in C-SCRM | Implementation Plan Milestone | Status | Owner | Priority | Target Date | |---------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------|------------|---------------| | Coordinate and engage with national security and law enforcement to ensure rapid access to mission-critical supply chain threats | Planned | J. Doe | Do Now | XX/XX/XX | | Evaluate C-SCRM improvement opportunities, and strengthen requirements and oversight for industry-wide common solutions and shared services | Complete | \u2026 | Do Next | \u2026 | | Advocate for C-SCRM awareness and competency through training and workforce development, to include secure coding training for developers | Delayed | \u2026 | Do Later | \u2026 | | Release white papers and public guidance related to C-SCRM | Cancelled | \u2026 | \u2026 | \u2026 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_02481", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain CONTACTS: according to NIST Computer Security Division 2014 Annual Report According to Computer Security Division 2014 Annual Report, CONTACTS:: Mr. Rick Kuhn (301) 975-3337 kuhn@nist.gov Dr. Raghu Kacker (301) 975-2109 raghu.kacker@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_02482", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Note according to Security Guidance for First Responder Mobile and Wearable Devices? Note: 802.1X is still used in WPA, WPA2, and WPA3 personal protocols, however, it generally takes place within the authenticator since an authenticator server is not used in WPA personal networks.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Guidance for First Responder Mobile and Wearable Devices."}]}
{"id": "nist_02483", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) say about 4.11.7 Changing FCKMS Security Policies? (Part 2) According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS), 4.11.7 Changing FCKMS Security Policies: peration of the changed security-domain protection mechanisms; and f) Coordinate with the domain authorities of other domains with which an equivalence or compatibility has previously been determined. | |-----------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | PF:4.9 | | A Federal CKMS could support the manual configuration and/or automated negotiation of modified FCKMS Security Policies for interaction with entities in different domains that are approved by all affected Security Domain authorities. |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_02484", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Assurance Requirements for Linux Application Container Deployments provide? (Section 51) use of enterprise-grade authentication services using strong credentials and directories, and isolating containers to separate hosts based on the sensitivity level of the applications running in them. In addition to these countermeasures, the orchestration artifacts should satisfy the following security assurance requirements: - (a) Clusters should have capabilities for logging and monitoring the resource consumption patterns of individual containers to avoid unanticipated spikes in resource usage leading to non-availability of critical resources. - (b) The Orchestration platform must be usable on containerized infrastructures with more than one host OS. In other words, the orchestration tools used must be container-host OS-neutral. Using different tools for different container host OS platforms increases the probability of denial-of-service attacks in those environments since the enterprise is not able to obtain a global picture of resource usage for all running containers in the entire containerized infrastructure of the enterprise. While discussing a security solution (e.g., using mount namespace) in the context of a security objective (i.e., filesystem isolation), certain augmenting solutions are recommended since the solution under discussion cannot meet the objective by itself. However, there are some security solutions that, irrespective of any augmenting controls, impose certain limitations on the functionality and performance of certain container functions. Despite their direct impact affecting only functional and performance aspects, they may have an indirect impact on certain security parameters. For example, while setting up system call filters (with whitelist and blacklist) using Seccomp as a security solution (since system calls are not namespace-aware and thus ruling out the use of the namespaces feature), the presence of malicious processes can introduce accidental leakage between containers.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Assurance Requirements for Linux Application Container Deployments."}]}
{"id": "nist_02485", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Non-Fungible Token Security provide? (Section 11) an asset. It is a token - a record maintained by a smart contract on a blockchain. The record may point to an asset or represent some intangible asset. The person buying an NFT is then buying a token. The token may or may not convey to the purchaser any legal rights over the asset. NFTs are often represented by standard ERC-721 in smart contracts on Ethereum or a similar standard on another blockchain (see Section 5 on token standards for more details). These standards provide minimum functionality to be implemented by NFT implementations. Additional functionality is possible, even expected. For example, NFT smart contracts may have an owner role that can perform management functions (e.g., [28]). Such functionality can include upgrading to a new smart contract (e.g., [29]). Such upgrades can provide the owner arbitrary functionality, including the expiring or delisting of purchased NFTs (e.g., [29]). The following non-exhaustive set of NFT properties can be derived from this definition. Most correctly functioning and secured NFT implementations will contain these properties (see Section 3.3 for caveats to this). 1. Owned: NFTs designate ownership by recording a blockchain address. 2. Transferable: Owners and designated approved entities can transfer the ownership of NFTs to other addresses. 3. Indivisible: NFTs cannot be subdivided (although the ownership may be fractionalized). 4. Linked: NFTs have references to the asset that they represent. 5. Recorded: NFTs are smart contract data records stored on a blockchain. 6. Provenance: NFTs have their chain of ownership recorded. 7. Permanence: NFTs are normally indestructible (although some are designed to be burned). 8. Immutable: The asset that an NFT represents cannot be modified. 9. Unique: Each NFT represents a unique asset. 10. Authentic: Each NFT asset is what the NFT claims it to be (e.g., artwork from a particular artist). 11. Authorized: Each NFT asset has been authorized by an owner to be sold as an NFT.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Non-Fungible Token Security."}]}
{"id": "nist_02486", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST_SP_800-207_Zero_Trust_Architecture say about Acknowledgments? According to NIST_SP_800-207_Zero_Trust_Architecture, Acknowledgments: This document is the product of a collaboration between multiple federal agencies and is overseen by the Federal CIO Council. The architecture subgroup is responsible for development of this document, but there are specific individuals who deserve recognition. These include Greg Holden, project manager of the Federal CIO Council ZTA project; Alper Kerman, project manager for the NIST/National Cybersecurity Center of Excellence ZTA effort; and Douglas Montgomery.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-207_Zero_Trust_Architecture."}]}
{"id": "nist_02487", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.16.7 Policy Enforcement: Developing Policy Results according to NIST Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events According to Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events, 2.16.7 Policy Enforcement: Developing Policy Results: 1. Navigate to Policy &gt; Policy Elements &gt; Results &gt; Posture &gt; Requirements. 2. Click one of the black arrows next to the Edit link, and select Insert New Requirement. 3. Enter a name. 4. Select Windows All for Operating Systems. 5. Select 4.x or later for Compliance Module. 6. Select Temporal Agent for Posture. 7. Select User Defined Conditions &gt; Anti-Malware Condition &gt; Cisco AMP (substitute Cisco AMP with the name of the condition you just created). 8. Select Message Text Only for the Remediation Action. (Other remediation actions can be defined by going to Policy &gt; Policy Elements &gt; Results &gt; Posture &gt; Remediation Actions, but there is not an option for Cisco AMP to be installed, so we leave the default for now.) 9. Enter a Message to inform the user that they must install Cisco AMP. <!-- image --> 10. Click Save.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_02488", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EC-1 in A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments? (Part 2) Control EC-1: riggered by user actions, a robust identity management system is required to assign and maintain user identities and enforce robust protocols with phishing-resistant multi-factor authentication (MFA). This system should be used to issue a cryptographically verifiable runtime token that represents the user principal to the rest of the infrastructure (e.g., a JSON Web Token [JWT]), and services should authenticate the credential at each hop. Note on the above recommendation: Authenticating the user in session at every hop is impractical at scale. Therefore, NIST recommends using short-lived end user credentials (e.g., OAuth 2.0 tokens) for external users and exchanging them for a locally authenticatable token, like a JWT, that is authenticated at each hop. - ID-SEG-REC-5: End user to resource authorization - As part of each service access request, the system must ensure that the authenticated end user principal (ID-SEG-REC4) is authorized to act on the resources designated in the request. This authorization may be performed by the application itself or checked locally (e.g., by checking against a set of claims in a JWT) or externally against an authorization system's policy decision point. The JWT libraries that process the token must be enabled to both decode (base64url encoding) and verify the signature. Enforcing end user authorization via the service mesh's sidecar PEP is particularly effective [3]. Context for the application of these policy recommendations and the improved security assurance that emanates from their deployment and enforcement are explained in [2] and [3]. ## Limitations of Identity-Based Segmentation Policies for Enterprise ZTA While identity-based segmentation is powerful, purely identity-based policies cannot currently be adopted due to the following scenarios: - Identity-based segmentation policies can include access scenarios that cover all origins (e.g., users, services) and all target resources that consist of services and data.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments."}]}
{"id": "nist_02489", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-3 in Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders? (Part 31) Control AC-3: what mitigates the potential for misuse of compromised access tokens. - \uf0a7 PKCE, as explained previously, prevents interception of the authorization code by malicious applications on the mobile device. ## 5.3 Scenarios and Findings The overall test scenario on Android devices involved launching the Motorola Solutions PSX Cockpit mobile application, authenticating, and then subsequently launching additional PSX applications and validating that the applications could access the back-end APIs and reflected the identity of the authenticated user. To enable testing of the two authentication scenarios, two separate 'user organization' infrastructures were created in the NCCoE lab, and both were registered as IdPs to the test PingFederate instance acting as the PSX AS. A 'domain selector' was created in PingFederate to perform IdP discovery based on the domain of the user's email address, enabling the user to trigger authentication at one of the IdPs. . On iOS devices, two demonstration applications-a chat application and a mapping application, with corresponding back-end APIs-were developed to demonstrate SSO. The iOS demo used the same authentication infrastructure in the NCCoE lab as the Android demo. The demo consisted of launching either application and authenticating to the IdP that supported OpenID Connect and FIDO UAF, then launching the additional demo application to demonstrate SSO and access to the back-end APIs with the identity of the authenticated user. Prior to testing the authentication infrastructure, users had to register U2F and UAF authenticators at the respective IdPs. FIDO authenticator registration requires a process that provides high assurance that the authenticator is in possession of the claimed account holder. In practice, this typically requires a strongly authenticated session or an in-person registration process overseen by an administrator.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, token. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_02490", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2015 Annual Report? (Part 60) Control HA-3: ute of Technology; - Christopher Boyer, Assistant Vice President, Public Policy, AT&amp;T; - John R. Centafont, NSA Information Assurance and Cyber Defense; - David Cullinane, CEO, TruStar, LLC; - Dr. Kevin Fu, Associate Professor, The University of Michigan; - Gregory Garcia, Executive Vice President, McBee Strategic; - Jeffrey Greene, Esq., Director, Government Affairs, North America &amp; Senior Policy Counsel, Senior Policy Counsel, Cybersecurity and Identity, Symantec Corporation; - Toby Levin, Retired (formerly Senior Advisor and Director of Privacy Policy, U.S. DHS); - Edward Roback, Associate Chief Information Officer for Cyber Security, U.S. Department of Treasury; and - Gale Stone, Deputy Assistant Inspector General for Audit, Social Security Administration (SSA). During FY 2014-2015, ISPAB held three meetings, all in Washington D.C: - October 22-24, 2014; - February 11-13, 2015; and - June 10-12, 2015. In keeping with previous practices at the first meeting of each fiscal year, the Board established a work plan for FY 2015 at the meeting in October 2014. The resulting plan included the following areas of focus: - Cryptography, and specifically NIST R&amp;D; - Federally funded Research and Development Centers (FFRDCs) - internally, externally and control balance; - Metrics - success measure for security and privacy; - Trust in NIST (accountability and success); - Quantum mechanics; - Identity management (Biometrics); - Privacy technology - implementation methodology; - Medical devices - security, privacy and safety, Healthcare IT Security; 3 4 - FISMA - Continuous Diagnostics and Mitigation (CDM) and Federal Risk and Authorization Management Program (FedRAMP); - CDM - Communications Security, Reliability and Interoperability Council (CSRIC), Trusted Internet Connection (TIC); - Key ESCROW - history and lessons learned - Cybersecurity; and - Updates of other critical NIST publications.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, identity management, sso. Contains security framework guidance for authentication systems. Source: Computer Security Division 2015 Annual Report."}]}
{"id": "nist_02491", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance) provide? (Section 164) PIV_INVALID_CARD_HANDLE . | | Postcondition(s) | 1. The PIV Middleware remains in the state it had prior to the pivEstablishSecureMessaging function call. 2. The precondition states are unaffected. | | Purpose | Ensure the PIV Middleware correctly handles a secure messaging failure. | |-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Target | pivEstablishSecureMessaging | | Reference(s) | 1. SP 800-73-4 Part 3, Section 3.2.2 2. AS04.07A-R4 | | Precondition(s) | 1. Avalid PIV Card is placed within the reading range of the contactless reader. 2. There exists a valid connection between the test system and an instance of the contactless reader. 3. The client application owns a shared connection to the PIV Card Application ( sharedConnection := true ). | <!-- image --> | | 4. No other contactless card is within the proximity of the reader. 5.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)."}]}
{"id": "nist_02492", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide for Conducting Risk Assessments provide? (Section 207) - Guidance on organization-wide levels of impact needing no further consideration. - Identification of critical missions/business functions. - Exemplary set of impacts, annotated by the organization, if necessary. ( Table H-2 ) - Assessment scale for assessing the impact of threat events, annotated by the organization, if necessary. ( Table H-3 ) | No | Yes | Yes If not provided by Tier 2 | | From Tier 2: (Mission/business process level) - Impact information and guidance specific to Tier 2 (e.g., impact information related to mission/business processes, EA segments, common infrastructure, support services, common controls, and external dependencies). - Identification of high-value assets. | Yes Via RAR | Yes Via Peer Sharing | Yes | | From Tier 3: (Information system level) - Impact information and guidance specific to Tier 3 (e.g., likelihood information affecting information systems, information technologies, information system components, applications, networks, environments of operation). - Historical data on successful and unsuccessful cyber attacks; attack detection rates. - Security assessment reports (i.e., deficiencies in assessed controls identified as vulnerabilities). - Results of continuous monitoring activities (e.g., automated and nonautomated data feeds). - Vulnerability assessments, Red Team reports, or other reports from analyses of information systems, subsystems, information technology products, devices, networks, or applications. - Contingency Plans, Disaster Recovery Plans, Incident Reports.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, red team. Contains technical security guidance that could inform defensive posture. Source: Guide for Conducting Risk Assessments."}]}
{"id": "nist_02493", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AN-2011 in Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2011 NIEM XML Encoded Transactions? (Part 46) Control AN-2011: the AN-2011 standard) - \uf0b7 Modified : The Element FingerprintImageStitchedIndicator to only accept the character 'Y'. Reason : The Element was defined in the schema as a Boolean type ( true or false ). This prevented the base requirement of only allowing a single alphabetic character of 'Y' (Field 14.027 in Table 71 of the AN-2011 standard).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Test Architecture and Test Suite for ANSI_NIST-ITL 1-2011 NIEM XML Encoded Transactions."}]}
{"id": "nist_02494", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The NIST Cybersecurity Framework (CSF) 2.0 provide? (Section 17) they represent a baseline of required actions to address cybersecurity risks. Quick-Start Guides (QSGs) are brief documents on specific CSF-related topics and are often tailored to specific audiences. QSGs can help an organization implement the CSF because they distill specific portions of the CSF into actionable 'first steps' that an organization can consider on the path to improving their cybersecurity posture and management of associated risks. The guides are revised in their own time frames, and new guides are added as needed. Suggestions for new Informative References for CSF 2.0 can always be shared with NIST at olir@nist.gov. Suggestions for other resources to reference on the NIST CSF website, including additional QSG topics, should be directed to cyberframework@nist.gov. The CSF's use will vary based on an organization's unique mission and risks. With an understanding of stakeholder expectations and risk appetite and tolerance (as outlined in GOVERN), an organization can prioritize cybersecurity activities to make informed decisions about cybersecurity expenditures and actions. An organization may choose to handle risk in one or more ways - including mitigating, transferring, avoiding, or accepting negative risks and realizing, sharing, enhancing, or accepting positive risks - depending on the potential impacts and likelihoods. Importantly, an organization can use the CSF both internally to manage its cybersecurity capabilities and externally to oversee or communicate with third parties. Regardless of the CSF's utilization, an organization may benefit from using the CSF as guidance to help it understand, assess, prioritize, and communicate cybersecurity risks and the actions that will manage those risks. The selected outcomes can be used to focus on and implement strategic decisions to improve cybersecurity postures and maintain continuity of missionessential functions while taking priorities and available resources into account.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, csf, fips. General security reference material without sensitive content. Source: The NIST Cybersecurity Framework (CSF) 2.0."}]}
{"id": "nist_02495", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)? (Part 3) Control AM-1: ms risk assessment to include data and services provided externally. The HSN's prioritization effort often considers third-party relationships, agreements, and understandings between the participants. | NIST SP 800-53r5 SA-9, CP-2, AC-20, RA-2, RA-9, SA-20, SC-6 | | ID.AM-6: Cybersecurity roles and responsibilities for the entire workforce and third-party stakeholders (e.g., suppliers, customers, partners) are established. | Consider assigning cybersecurity roles and responsibilities to all participating organizations for the software, data, or components they manage. The roles and responsibilities of the external organization to the HSN are typically agreed upon in advance. Identify and resolve any inconsistencies or gaps in advance. | NIST SP 800-53r5 SA-9, CP-2, PM-2, PM-29, PS-7 ETSI TR 101 984 5.2 | ## 4.1.2. Identify: Business Environment Category The organization's mission, objectives, stakeholders, and activities are understood and prioritized; this information is used to inform cybersecurity roles, responsibilities, and risk management decisions. In the context of HSNs, identify the dependencies, obligations, and relationships between different organizations and their stakeholders to remove ambiguities and resolve any differences. The Business Environment category has five subcategories that apply to HSNs. Table 2. Business Environment Category for the Identify Function.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)."}]}
{"id": "nist_02496", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automation Support for Security Control Assessments_ Volume 1_ Overview say about 2.2.1 Terms for Referring to Assessment Objects? According to Automation Support for Security Control Assessments_ Volume 1_ Overview, 2.2.1 Terms for Referring to Assessment Objects: This document generally uses the term assessment object . The meaning of assessment object as used herein is equivalent to the glossary definition but is focused on what could potentially have a security defect. Thus, as used in this NISTIR, the term assessment object more specifically refers to the following: Anything that can have a security defect (i.e., failed or absent control). Examples include devices, software, people, credentials, accounts, privileges, and things to which privileges are granted (including data and physical facilities). Assessment object is a general concept and used where generality is implied. However, in the context of a specific capability (or group of capabilities), it may be clearer to use a more specific term. Many capabilities focus on assessment objects with defects. Hardware Asset Management (HWAM) and Software Asset Management (SWAM) are examples of capabilities with such a focus. In referring to such assessment objects, the term asset may be used (e.g., assets with defects). Most specific capabilities focus on specific assessment object types. HWAM focuses exclusively on defects in and around devices, for example. Because this volume often uses examples from the HWAM capability volume, it often uses the term devices when referring to defects in that context. For the purposes of this NISTIR, all hardware assets (assessment objects) are devices, but not all devices are assessment objects. For example, a chip on a circuit board is a device and an asset, but in the HWAM context, it is not at an abstraction level of focus. Likewise, automated security control assessment does not focus on a device's keyboard, mouse, and monitor, per se, as such mechanisms are just part of the larger device (or assessment object) being assessed. However, property systems might count them as separate assets.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Volume 1_ Overview."}]}
{"id": "nist_02497", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 say about 2.1 DEVELOPMENT APPROACH? (Part 4) According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171, 2.1 DEVELOPMENT APPROACH: _\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ organizations while under attack. The enhanced security requirements focus on the following key elements, which are essential to addressing the APT: - Applying a threat-centric approach to security requirements specification; - Employing system and security architectures that support logical and physical isolation using system and network segmentation techniques, virtual machines, and containers; 16 - Implementing dual authorization controls for the most critical or sensitive operations; - Limiting persistent storage to isolated enclaves or domains; - Implementing a comply-to-connect approach for systems and networks; - Extending configuration management requirements by establishing authoritative sources for addressing changes to systems and system components; - Periodically refreshing or upgrading organizational systems and system components to a known state or developing new systems or components; - Employing a security operations center with advanced analytics to support continuous monitoring and protection of organizational systems; and - Using deception to confuse and mislead adversaries regarding the information they use for decision-making, the value and authenticity of the information they attempt to exfiltrate, or the environment in which they are operating.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_02498", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3 Motivating Use Cases according to NIST 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings According to 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings, 3 Motivating Use Cases: In this section, we describe the use cases we wish to support with our work.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02499", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Domain Name System-Based Electronic Mail Security provide? (Section 99) nded for general use as this will result in the majority of email being deferred. It should only be used in scenarios where senders and receivers are coordinated and maintain a stable DANE deployment. Both public sector and private sector enterprises are heavily dependent on web-based technology other than email for e-commerce and other public-facing applications. Fraudulent web sites pose at least as great a security and privacy problem as fraudulent email. Further, as email becomes a more difficult medium for malicious entities to use as a penetration vector, other web-based media will be more intensively exploited. Already, emerging communications trends appear to be replacing email exchanges among individuals with other social media (e.g., Baidu, Facebook, Facebook Messenger, Google+, Instagram, LinkedIn, Pinterest, Snapchat, Tieba, Tumblr, Twitter, Viber, WhatsApp, and YouTube). Therefore, an extension of the current project that focuses on use of improved DNSSEC applications such as DANE for web applications other than mail may be justified. Additionally, the test scenarios did not include the Exchange for Office 365 MTA to demonstrate Scenario 1. Future builds might be considered to demonstrate this capability. Finally, utilities are currently under development that would provide improved support for SMIMEA and improved system notification of failed DNSSEC signature validation events. Future builds might be considered to demonstrate these capabilities as well.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_02500", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i provide? (Section 289) O'Reilly Media, 2005. He, Changhua, and Mitchell, John, 'Analysis of the 802.11i 4-Way Handshake', Proceedings of the 2004 ACM Workshop on Wireless Security , 2004. IEEE Standard 802.11, 1999 Edition. Also available at http://standards.ieee.org/getieee802/download/802.11-1999.pdf. IEEE Standard 802.11i, 2004 Edition. Also available at http://standards.ieee.org/getieee802/download/802.11i-2004.pdf. IEEE Standard 802.1X, 2004 Edition. Also available at http://standards.ieee.org/getieee802/download/802.1X-2004.pdf. Matsunaga, Yasuhiko et al, 'Secure Authentication System for Public WLAN Roaming', Proceedings of the First ACM International Workshop on Wireless Mobile Applications and Services on WLAN Hotspots , 2003. Mitsuyama, Yukio et al, 'Embedded Architecture of IEEE 802.11i Cipher Algorithms', Proceedings of the IEEE International Symposium on Consumer Electronics , 2004. O'Hara, Bob and Petrick, Al, IEEE 802.11 Handbook: A Designer's Companion , IEEE Press, 2001. Schmoyer, Tim, Lim, Yu-Xi, and Owen, Henry, 'Wireless Intrusion Detection and Response: A Case Study Using the Classic Man-in-the-middle Attack', Proceedings of IEEE Wireless Communication and Networking Conference 2004, 2004. Smyth, Neil, McLoone, M\u00e1ire, and McCanny, John, 'Reconfigurable Hardware Acceleration of WLAN Security', IEEE Workshop on Signal Processing Systems (SiPS) Design &amp; Implementation , 2004. \u0160orman, Matija, Kova \u010d , Tomislav, and Maurovi \u0107 , Damir, 'Implementing Improved WLAN Security', 46 th International Symposium Electronics in Marine , 2004. Wool, Avishai, 'A Note on the Fragility of the 'Michael' Message Integrity Code', IEEE Transactions on Wireless Communications , Vol. 3 No. 5, September 2004. You, Liyu and Jamshaid, Kamran, 'Novel Applications for 802.11x Enabled Wireless Networked Home', 2004 IEEE Consumer Communications and Networking Conference , 2004.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i."}]}
{"id": "nist_02501", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Threshold Schemes for Cryptographic Primitives_ Challenges and Opportunities in Standardization and Validation of Threshold Cryptography provide? (Section 31) eously. The secrecy of keys can be compromised by the leakage of key-dependent information during computations. This is possible even without direct physical contact with components within the device. For example, the time taken, the power consumed, and the electromagnetic radiation emanated by a device can be measured without penetrating the device enclosure. We will assume that, regardless of whether the computation is in hardware or software, the device that performs the computation consists of some circuit with wires connecting to logical gates and memory cells. Then, the attacker's view of the circuit elements may be noisy (the noisy leakage model [CJRR99]), or the attacker may be limited by the number of wires of the circuit that it can observe within a certain period of time (the probing model [ISW03]). The noisy leakage model and probing model have been unified [DDF14]. In both models, under some reasonable assumptions on the statistical distributions of sidechannel information, the complexity of a side-channel attack of a suitable implementation with an n -out-ofn secret-sharing increases exponentially with the number of shares. As such, side channel attacks on secret-shared implementations become infeasible if the number of shares is sufficiently high, and is further thwarted when the shares are refreshed before the attacker can collect enough side-channel information. Further refinements of the model take transient behavior ('glitches') of the transistors into account, which can be handled by Threshold Implementations (TI) [NRR06] or by 'lazy engineering' to just increase the number of shares [BGG + 14]. Besides the aforementioned side-channel attacks, an attacker may also obtain keydependent information by injecting a fault into the computation, and then observing the outputs [BDL97]. To inject the fault, the attacker may, for example, apply a strong external electromagnetic field.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, cui. Contains guidance on protecting sensitive government information. Source: Threshold Schemes for Cryptographic Primitives_ Challenges and Opportunities in Standardization and Validation of Threshold Cryptography."}]}
{"id": "nist_02502", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.3 Skill Statements according to NIST Workforce Framework for Cybersecurity (NICE Framework) According to Workforce Framework for Cybersecurity (NICE Framework), 2.3 Skill Statements: Skill statements relate to Task statements in that a learner is demonstrating skills in performing tasks. A learner who is not able to demonstrate the described skill would not be able to complete the Task that relies on that skill. A Skill is defined as the capacity to perform an observable action. Skill statements may describe straightforward or complex skills. Multiple Skill statements may be needed to complete a given Task. Likewise, exercising a Skill may be used to complete more than one Task. Skill statements can be simple. Example: Skill in recognizing the alerts of an Intrusion Detection System Skill statements can be complex. Example: Skill in generating a hypothesis as to how a threat actor circumvented the Intrusion Detection System. As depicted in Figure 1, Skill statements describe what the learner can do, and Task statements describe the work to be done. Therefore, it is important to separate the language used between Skill statements and Task statements and to use terms that facilitate observability and assessment of the learner.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: threat actor, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Workforce Framework for Cybersecurity (NICE Framework)."}]}
{"id": "nist_02503", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 870) s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ [SP 800-60-2] [SP 800-61] [SP 800-63-3] [SP 800-63A] [SP 800-63B] [SP 800-70] [SP 800-73-4] [SP 800-76-2] [SP 800-77] Stine KM, Kissel RL, Barker WC, Lee A, Fahlsing J (2008) Guide for Mapping Types of Information and Information Systems to Security Categories: Appendices. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-60, Vol. 2, Rev. 1. Cichonski PR, Millar T, Grance T, Scarfone KA (2012) Computer Security Incident Handling Guide. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-61, Rev. 2. https://doi.org/10.6028/NIST.SP.800-61r2 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 March 2, 2020. Grassi PA, Fenton JL, Lefkovitz NB, Danker JM, Choong Y-Y, Greene KK, Theofanos MF (2017) Digital Identity Guidelines: Enrollment and Identity Proofing. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-63A, Includes updates as of March 2, 2020. Grassi PA, Fenton JL, Newton EM, Perlner RA, Regenscheid AR, Burr WE, Richer, JP, Lefkovitz NB, Danker JM, Choong Y-Y, Greene KK, Theofanos MF (2017) Digital Identity Guidelines: Authentication and Lifecycle Management.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02504", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2009 Annual Report say about Key Management? (Part 2) According to Computer Security Division 2009 Annual Report, Key Management: xpected to be available for comment during Q2 FY2010. Further information about this project is available on the CSRC website. Contacts: Mr. Quynh Dang Ms. Elaine Barker (301) 975-3610 (301) 975-2911 qdang@nist.gov ebarker@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2009 Annual Report."}]}
{"id": "nist_02505", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services provide? (Section 97) ategy to protect the confidentiality, integrity, and availability of PNT services. In this PNT Profile, the availability and integrity of PNT services are of primary concern throughout the enterprise. PNT data that is bound or associated with personally identifiable information (PII) or other sensitive data increases confidentiality concerns. There are seven Subcategories within Data Security that apply to the PNT Profile, as summarized in the table below. Table 11. Data Security Subcategories Applicable to PNT | Protect Data Security Subcategory | Applicability to PNT | References (PNT-Specific) | |-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| | DS-1: Data at rest is protected.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_02506", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure say about 5.2.4. Information Protection and Processes Category? (Part 25) According to Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure, 5.2.4. Information Protection and Processes Category: 8-07, RQ-08-08 ISO 24089:2023 4.3.3.1, 7.3.1.3 | | IP-12 | XFC/EVSE | This may include development systems, operational systems, and IT/ICS systems. | ISA/IEC 62443-2- 1:D4E1 EVENT 1.9 | | IP-12 | Cloud/Third-Party | This may include development systems, operational systems, and IT/ICS systems. | [NIST-SP800-53r5] RA-1, RA-3, RA-5 | | IP-12 | Utility/Building Management System | This may include development systems, operational systems, and IT/ICS systems. | ISA/IEC 62443-2- 1:D4E1 EVENT 1.9 |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure."}]}
{"id": "nist_02507", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security of SQL-Based Implementations of Product Data Exchange Using STEP say about 2.4 Security Responsibilities: Non-SQL Components? According to Security of SQL-Based Implementations of Product Data Exchange Using STEP, 2.4 Security Responsibilities: Non-SQL Components: Many aspects of security in a STEP environment will take place outside the SQL processor. This section outlines these responsibilities in the following areas: application interface, SQL interface to the physical database, SQL interface to non-SQL DBMS's, and interface to remote databases.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security of SQL-Based Implementations of Product Data Exchange Using STEP."}]}
{"id": "nist_02508", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile say about 3.1 Framework Core? (Part 2) According to Cybersecurity Framework Manufacturing Profile, 3.1 Framework Core: Table 1 Cybersecurity Framework Functions and Categories | 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", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile."}]}
{"id": "nist_02509", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography? (Part 50) Control HA-3: ession of the correct static private key from a trusted third party (trusted by the recipient) either before or during a key-agreement transaction that makes use of that static public key. The methods used by a third party trusted by the recipient to obtain that assurance are beyond the scope of this Recommendation (however, see the discussion in Section 5.6.2.2.3 above). ## 5.6.2.2.3.2 Recipient Obtains Assurance Directly from the Claimed Owner (i.e., the Other Party) When two parties engage in a key-agreement transaction, there is (at least) an implicit claim of ownership made whenever a static public key is provided on behalf of a given party. That party is considered to be a claimed owner of the corresponding static key pair - as opposed to being a true owner - until adequate assurance can be obtained that the party is actually the one authorized to use the static private key. The claimed owner can provide such assurance by demonstrating its knowledge of that private key. If all the following conditions are met during a key-agreement transaction that incorporates key confirmation as specified in this Recommendation, then while establishing keying material, the recipient of a static public key may be able to directly obtain (initial or renewed) assurance of the claimed owner's (i.e., the other party's) current possession of the corresponding static private key: 1. The recipient of the static public key contributes an ephemeral public key to the keyagreement process, one that is intended to be arithmetically combined with the claimed owner's (i.e., the other party's) static private key in computations performed by the claimed owner. (If an appropriate key-agreement scheme is employed, the claimed owner will be challenged to demonstrate current knowledge of his static private key by successfully performing those computations during the transaction.) 2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}]}
{"id": "nist_02510", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings say about 9 Availability? According to 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings, 9 Availability: The component matching software is included in OpenLDAP release as a module and can be downloaded at openldap.org/software/download/ . The eSNACC ASN.1 compiler can be obtained from DigitalNet at com/knowledge/download.htm .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02511", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case say about Highlighted Performance Impacts? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case, Highlighted Performance Impacts: No performance measurement experiments were performed for network segmentation and segregation due to it being implemented on the PCS before the Manufacturing Profile implementation was initiated.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case."}]}
{"id": "nist_02512", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? (Part 233) Control HA-1: on, on the other hand, may be possible under either scheme through the use of signed authorization messages for access control. ## 6 REFERENCES [ANSI03] American National Standards Institute. Biometric Information Management and Security for the Financial Services Industry. ANSI X9.84-2003. 2003. [INCITS04] InterNational Committee for Information Technology Standards. Information Technology - Finger Pattern Based Interchange Format . January 2004. [IAB04] Interagency Advisory Board (IAB) Data Model Task Force. IAB Data Model Task Force Report v0.6 (Draft). October 2004. [ISO01] International Standards Organization. Identification cards - Contactless integrated circuit(s) cards - Proximity cards - Parts 1-4 . ISO/IEC 14443. 2000-2001. [ISO01b] International Standards Organization. Information technology - Open Systems Interconnection - The Directory: Public- key and attribute certificate frameworks. ISO/IEC 9594-8. August 2001. [ISO04] International Standards Organization. Information technology -- Biometric data interchange formats . ISO 19794. Under development, 2004. [MAM+99] M. Myers, R. Ankney, A. Malpani, S. Galperin, C. Adams. X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP . IETF RFC 2560. June 1999. [OASIS02] Organization for the Advancement of Structured Information Standards ## 4th Annual PKI R&amp;D Workshop -- Proceedings (OASIS). Guidelines for using XML Signatures with the OASIS Security Assertion Markup Language (SAML). Draft 02. September 2002. - [PAIIWG04] Government Smart Card Interagency Advisory Board's Physical Security Interagency Interoperability Working Group, Technical Implementation Guidance: Smart Card Enabled Physical Access Control Systems, Version 2.2. July 2004. - [PDR+01] Fernando Podio, Jeffrey Dunn, Lawrence Reinert, Catherine Tilton, Lawrence O'Gorman, M. Paul Collier, Mark Jerde, - Brigitte Wirtz. CBEFF: Common Biometric Exchange File Format .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02513", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2009 Annual Report say about Automated Security Testing and Test Suite Development? (Part 2) According to Computer Security Division 2009 Annual Report, Automated Security Testing and Test Suite Development: multi-block mes- sages, which require the chaining of information from one block to the next. Other types of validation testing exist to satisfy other testing requirements of cryptographic algorithms. Automated security testing and test suite development are integral components of the Cryptographic Algorithm Validation Program (CAVP). The CAVP encompasses validation testing for FIPS-approved and NIST-recommended cryptographic algorithms. Cryptographic algorithm validation is a prerequisite to the Cryptographic Module Validation Program (CMVP). All of the tests under the CAVP are handled by the 18 third-party laboratories that are accredited as CMT laboratories by NVLAP . We develop and maintain a Cryptographic Algorithm Validation System (CAVS) tool that automates the validation testing.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2009 Annual Report."}]}
{"id": "nist_02514", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management say about Appendix A-Acronyms? (Part 3) According to Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management, Appendix A-Acronyms: KRI Key risk indicator NCCIC National Cybersecurity and Communications Integration Center NCP National Checklist Program NTCTF NSA/CSS Technical Cyber Threat Framework NVD National Vulnerability Database OLIR Online Informative References OT Operational technology OVAL Open Vulnerability Assessment Language POA&amp;M Plan of Actions &amp; Milestones RDR Risk Detail Record SCAP Security Content Automation Protocol SIEM Security Incident Event Monitoring SWOT Strength, Weakness, Opportunity, and Threat Analysis TTP Tactics, Techniques, and Procedures", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management."}]}
{"id": "nist_02515", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Attribute Based Access Control (ABAC) Definition and Considerations say about Executive Summary? (Part 4) According to Guide to Attribute Based Access Control (ABAC) Definition and Considerations, Executive Summary: Further, ABAC enables object owners or administrators to apply access control policy without prior knowledge of the specific subject and for an unlimited number of subjects that might require access. As new subjects join the organization, rules and objects do not need to be modified. As long as the subject is assigned the attributes necessary for access to the required objects (e.g., all Nurse Practitioners in the Cardiology Department are assigned those attributes), no modifications to existing rules or object attributes are required. This benefit is often referred to as accommodating the external (unanticipated) user and is one of the primary benefits of employing ABAC. When deployed across an enterprise for the purposes of increasing information sharing among diverse organizations, ABAC implementations can become complex-supported by the existence of an attribute management infrastructure, machine-enforceable policies, and an array of functions that support access decisions and policy enforcement. In addition to the basic policy, attribute, and access control mechanism requirements, the enterprise must support management functions for enterprise policy development and distribution, enterprise identity and subject attributes, subject attribute sharing, enterprise object attributes, authentication, and access control mechanism deployment and distribution. The development and deployment of these capabilities requires the careful consideration of a number of factors that will influence the design, security, and interoperability of an enterprise ABAC solution.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Guide to Attribute Based Access Control (ABAC) Definition and Considerations."}]}
{"id": "nist_02516", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Batch or Rising according to Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers? Batch or Rising: Batch indexes all of the table's data every time that it runs, whereas Rising uses a checkpoint to update the data that it collects from the table. We selected Rising.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_02517", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Block Cipher Modes of Operation_ the CCM Mode for Authentication and Confidentiality say about 2 Authority? According to Recommendation for Block Cipher Modes of Operation_ the CCM Mode for Authentication and Confidentiality, 2 Authority: This document has been developed by the National Institute of Standards and Technology (NIST) in furtherance of its statutory responsibilities under the Federal Information Security Management Act (FISMA) of 2002, Public Law 107-347. NIST is responsible for developing standards and guidelines, including minimum requirements, for providing adequate information security for all agency operations and assets, but such standards and guidelines shall not apply to national security systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems, as analyzed in A-130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in A-130, Appendix III. This guideline has been prepared for use by federal agencies. It may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright. (Attribution would be appreciated by NIST.) 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. Conformance testing for implementations of the mode of operation that is specified in this Part of the Recommendation will be conducted within the framework of the Cryptographic Module Validation Program (CMVP), a joint effort of NIST and the Communications Security Establishment of the Government of Canada. An implementation of a mode of operation must adhere to the requirements in this Recommendation in order to be validated under the CMVP. The requirements of this Recommendation are indicated by the word 'shall.'", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: Recommendation for Block Cipher Modes of Operation_ the CCM Mode for Authentication and Confidentiality."}]}
{"id": "nist_02518", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Computer Security Log Management provide? (Section 90) sible. The organization can then revise its policies so that the infrastructure implementation will be less resource-intensive, while ensuring that all legal and regulatory requirements are still met. Because of the complexities of log management, it may take a few cycles of policy modification, infrastructure design, and design assessment to finalize the policy and design. When designing a log management infrastructure, organizations should consider several factors related to the current and future needs of both the infrastructure and the individual log sources throughout the organization. Major factors include the following: - GLYPH&lt;c=31,font=/APONEK+Webdings&gt; The typical and peak volume of log data to be processed per hour and day. The typical volume of log data tends to increase over time for most log sources. The peak volume should include handling extreme situations, such as widespread malware incidents, vulnerability scanning, and penetration tests that may cause unusually large numbers of log entries to be generated in a short period of time. If the volume of log data is too high, a logging denial of service may result. Many logging products rate their capacity for processing log data by the volume of events they can process in a given time, most often in events per second (EPS). - GLYPH&lt;c=31,font=/APONEK+Webdings&gt; The typical and peak usage of network bandwidth. - GLYPH&lt;c=31,font=/APONEK+Webdings&gt; The typical and peak usage of online and offline (e.g., archival) data storage. This should include an analysis of the time and resources needed to perform backups and archival of log data, as well as disposing of the data once it is no longer needed. - GLYPH&lt;c=31,font=/APONEK+Webdings&gt; The security needs for the log data. For example, if log data needs to be encrypted when transmitted between systems, this could require more processing by the systems, as well as increased usage of network bandwidth.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, malware, penetration test. Contains technical security guidance that could inform defensive posture. Source: Guide to Computer Security Log Management."}]}
{"id": "nist_02519", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-7 in Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance? (Part 76) Control CM-7: Enforce software usage and installation restrictions. | These Subcategory requirements can be met by implementing solutions that provide the Authentication and Authorization, System Use Monitoring, and Physical Access Monitoring technical capabilities. Potential solutions for meeting these Subcategory requirements include: Microsoft Active Directory, FreeIPA, Symantec Endpoint Protection, Native operating system/device capabilities, electronic access control systems, cameras, Sign in/out sheets Solutions that were implemented in use cases: Active Directory Symantec Endpoint Protection Native operating system/device capabilities Electronic access control system Sign in/out sheet | | DETECT | Security Continuous Monitoring (DE.CM) | DE.CM-4 | Low Deploy malicious code protection mechanisms throughout the manufacturing system where safe and feasible to detect and eradicate malicious code. Update malicious code protection mechanisms whenever new releases are available in accordance with the configuration management policy and procedures for the manufacturing system. | These Subcategory requirements can be met by implementing solutions that provide the Anti-virus/malware and Vulnerability Management technical capabilities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, malware. Contains technical security guidance that could inform defensive posture. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 \u2013 General Implementation Guidance."}]}
{"id": "nist_02520", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs say about Table of Contents? (Part 1) According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs, Table of Contents: Table of Contents | | Introduction ..................................................................................................................... | Introduction ..................................................................................................................... | |------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | Background: NIST Cryptographic Standards and Testing/Validation Programs ... 1 Methodology.......................................................................................................... 2 | Background: NIST Cryptographic Standards and Testing/Validation Programs ... 1 Methodology..........................................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs."}]}
{"id": "nist_02521", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-3 in Computer Security Division 2012 Annual Report? (Part 118) Control HA-3: ap:df00) GLYPH(cmap:df00)raft of FIPS 140-3. As a result, NIST requesteGLYPH(cmap:df00) additional public comments in August 2012 on several clearly iGLYPH(cmap:df00)entifieGLYPH(cmap:df00) sections. More GLYPH(cmap:df00)etails about the project anGLYPH(cmap:df00) a timetable can be founGLYPH(cmap:df00) at: nist.gov/groups/ST/FIPS140\\_3/ . During FY2013, all receiveGLYPH(cmap:df00) comments on the iGLYPH(cmap:df00)entifieGLYPH(cmap:df00) issues will be aGLYPH(cmap:df00)GLYPH(cmap:df00)resseGLYPH(cmap:df00) anGLYPH(cmap:df00) the final FIPS 140-3 GLYPH(cmap:df00)ocument will be prepareGLYPH(cmap:df00) for a final internal review anGLYPH(cmap:df00) approval by the Secretary of Commerce. nist.gov/groups/ST/FIPS140\\_3/ Contact: Dr. Michaela Iorga (301) 975-8431 michaela.iorga@nist.gov ## Personal IGLYPH(cmap:df00)entity Verification (PIV) T est CarGLYPH(cmap:df00)s Federal Information Processing Standard (FIPS) 201, Personal IGLYPH(cmap:df00)entity Verification (PIV) of FeGLYPH(cmap:df00)eral Employees and Contractors , was publisheGLYPH(cmap:df00) in February 2005 to satisfy policy GLYPH(cmap:df00)irectives specifieGLYPH(cmap:df00) in HomelanGLYPH(cmap:df00) Security PresiGLYPH(cmap:df00)ential Directive-12 (HSPD-12). The majority of feGLYPH(cmap:df00)eral workers now have Personal IGLYPH(cmap:df00)entity Verification (PIV) carGLYPH(cmap:df00)s; however , the PIV carGLYPH(cmap:df00) has not yet been embraced as a mechanism for logical access to IT resources. The unavailability of test PIV cards has been iGLYPH(cmap:df00)entifieGLYPH(cmap:df00) as an impeGLYPH(cmap:df00)iment to GLYPH(cmap:df00)eployment for this purpose. To facilitate the development of applications and miGLYPH(cmap:df00)GLYPH(cmap:df00)leware that support the PIV carGLYPH(cmap:df00), CSD GLYPH(cmap:df00)evelopeGLYPH(cmap:df00) a reference set of smart cards.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_02522", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CS-3 in U.S. Department of Energy Risk Assessment Methodology? (Part 77) Control CS-3: ed for the Classified Program. How/ever, it should be noted that selected Orders apply to both programs and are marked with an ( * ). ** NOTE; See Cross Reference List for numerical listing of Orders. | 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) | |-----------------------------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------| | OOe:;;::fi::::::.:::: OOCVMeNT NUMBER | DOE DOCMMBIT TITI^ (A\u00bb ^ | DOE DOCMMBIT TITI^ (A\u00bb ^ | BASELINE REQUIREMENT CODE | | 1000.38 | INTERNAL CONTROL SYSTEMS | INTERNAL CONTROL SYSTEMS | K, | | 1330.18 | MANAGEMENT OF AUTOMATED INFORMATION SYSTEMS AND DATA RESOURCES | MANAGEMENT OF AUTOMATED INFORMATION SYSTEMS AND DATA RESOURCES | C. | | 1360.1 A | ACQUISITON AND MANAGEMENT OF COMPUTING RESOURCES | ACQUISITON AND MANAGEMENT OF COMPUTING RESOURCES | D.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: U.S. Department of Energy Risk Assessment Methodology."}]}
{"id": "nist_02523", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-7 in Vetting the Security of Mobile Applications? (Part 6) Control CM-7: y the estimated risk as pass, warning or fail. While some standards exist for expressing risk assessment 15 and vulnerability reporting 16 the current adoption of these standards by test tools is low. To the extent possible, it is recommended that an organization use test tools that leverage vulnerability reporting and risk assessment standards. If this approach is not possible, it is recommended that the organization provide sufficient training to analysts on the interpretation of reports and risk assessments generated by test tools. ## 5.8 Compliance versus Certification For mobile application vetting, two terms are frequently used to demonstrate proof of successful implementation of mobile app security requirements. For a mobile application that has been developed to include security aimed at a particular requirement (e.g. National Information Assurance Partnership - Requirements for Vetting Mobile Apps from the Protection Profile for Application Software [7]) developers may choose to note that they are compliant or certified. The difference depends on the organization's need for compliance or certification. Compliance for mobile application security means either self-attestation or attestation from an unofficial third party that has validated the mobile app meets such security requirements. For example an enterprise may choose to use their own internally developed mobile application vetting process to validate the security and privacy of a mobile application. By going through their own internal process they approve the mobile application for use in their organization or on 15 An example standard, the Common Vulnerability Scoring System CVSS, is discussed in Section 4.2.3. 16 Examples are described in Section 2.1. their organization's mobile assets. On the other hand, certification means successful validation from the authorized validator. For example, for NIAP certification, a formal NIAP validation process must be followed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Vetting the Security of Mobile Applications."}]}
{"id": "nist_02524", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard provide? (Section 69) ime we will have to use more down to earth approaches. Human beings will be heavily involved in key management, and as in any security situation, careful steps must be taken to ensure their integrity. In practice it will be necessary to sacrifice extra complexity for the sake of smooth operation. In addition to careful planning, the chosen system should be thoroughly tested and particular attention paid to what would happen in abnormal situations such as loss of a key or recovery from a system crash. All possible eventualities should be considered and a comprehensive set of rules established. A tight discipline must then be enforced. A final reminder, if the key management scheme is not designed properly or adequately enforced, the result could not only be disastrous from a security viewpoint but the viability of the entire system may be jeopardized. Reference [1] Chambers R.P., Random Number Generation, I.E.E.E. Spectrum, February 1967. Design and Specification of Cryptographic Capabilities Interbank Card Association Carl M. Campbell, Jr. (Consultant) 8 09 Maiin Road, Newtown Square, Pa. 19073 Cryptography can be used to provide data secrecy, data authentication, and originator authentication. Non-reversible transformation techniques provide only the last. Cryptographic check digits provide both data and originator authentication, but no secrecy. Data secrecy, with or without data authentication, is provided by block encryption or data stream encryption techniques. Total systems security may be provided on a link-by-link, nodeby-node, or end-to-end basis, depending upon the nature of the application. Key words: Cryptography; data security; encryption. Up to the present, cryptography has been a relatively unknown science, used primarily to secure sensitive governmental communications.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard."}]}
{"id": "nist_02525", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does General Access Control Guidance for Cloud Systems say about 1.1 Purpose? According to General Access Control Guidance for Cloud Systems, 1.1 Purpose: Access control (AC) dictates how subjects (i.e., users and processes) can access objects based on defined AC policies to protect sensitive data and critical computing objects in the cloud systems. Considering the heterogeneity and remote nature of the cloud service models, AC and its general concepts should be revisited. In recent years, many works have focused on AC in cloud systems [23, 25, 26, 27]. However, these are primarily ad hoc solutions targeted at specific cloud applications and do not provide comprehensive views of cloud AC. This document presents a set of general AC guidance for cloud service models independent from its deployment models because it requires another layer of access control that depends on the security requirements of the business function for which the cloud system is used. As shown in Figure 3, different cloud service models require the management of access to different components of the offered service. Since such cloud service models can be considered hierarchical, the AC considerations of functional components in a lower-level (according to Figure 2) service model (e.g., networking and storage layers in the Infrastructure as a Service (IaaS) model) are also applicable to the same functional components in a higher-level service model (e.g., networking and storage in Platform as a Service (PaaS) and Software as a Service (SaaS) models). In general, AC considerations for IaaS are also applicable to PaaS and SaaS, and AC considerations for IaaS and PaaS are also applicable to SaaS. Thus, AC guidance for IaaS is applicable to PaaS and SaaS, and AC guidance for IaaS and PaaS is also applicable to SaaS. However, each service model has its own focus with regard to AC. For instance, an IaaS provider may put more effort into virtualization control, and in addition to the virtualization control, a SaaS provider needs to consider data security and the privacy of services it provides.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: General Access Control Guidance for Cloud Systems."}]}
{"id": "nist_02526", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders provide? (Section 12) work for this publication was done while at employer. The Technology Partners/Collaborators who participated in this build submitted their capabilities in response to a notice in the Federal Register. Respondents with relevant capabilities or product components were invited to sign a Cooperative Research and Development Agreement (CRADA) with NIST, allowing them to participate in a consortium to build this example solution. We worked with: | Technology Partner/Collaborator | Build Involvement | |-----------------------------------|-----------------------------------------------------------------------------| | Ping Identity | Federation Server | | Motorola Solutions | Mobile Applications | | Yubico | External Authenticators | | Nok Nok Labs | Fast Identity Online (FIDO) Universal Authentication Framework (UAF) Server | | StrongKey | FIDO Universal Second Factor (U2F) Server | NOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, single sign-on. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_02527", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain RISK MANAGEMENT according to NIST Fiscal Year 2023 Cybersecurity and Privacy Annual Report According to Fiscal Year 2023 Cybersecurity and Privacy Annual Report, RISK MANAGEMENT: Organizations must balance an evolving cybersecurity and privacy threat landscape with the need to fulfill mission and business requirements - an effort that increasingly calls for a collaborative approach to managing risks. Risk management is integrated into NIST standards and guidelines to help organizations understand, measure, manage, and reduce cybersecurity and privacy risks in a larger context.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Fiscal Year 2023 Cybersecurity and Privacy Annual Report."}]}
{"id": "nist_02528", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Common Biometric Exchange Formats Framework (CBEFF) say about Patron Format Specification? (Part 7) According to Common Biometric Exchange Formats Framework (CBEFF), Patron Format Specification: what specific CBEFF optional fields are present in the record/structure (see below). Use of this element facilitates the dynamic, automated interpretation or parsing of the information within the SBH. | Patron Format A Specific Field | Field Source | Length | Bit Location | Mandatory/ Optional | Notes | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|----------|---------------------------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Optional Fields Present Mask Subheader/Basic Structure Count PID Patron Format Identifier Index Biometric Creation Date Validity Period Biometric Type Biometric Subtype CBEFF Header Version Patron Header Version Biometric Purpose Biometric Data Type Biometric Data Quality Creator Challenge/Response Payload | Format A | 2 bytes | x'0001' x'0002' x'0004' x'0008' x'0010' x'0020' x'0040' x'0080' x'0100' x'0200' x'0400' x'0800' x'1000' x'2000' x'4000' x'8000' | Optional | Present only if 'Optional Fields Present' = 1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Biometric Exchange Formats Framework (CBEFF)."}]}
{"id": "nist_02529", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet say about AN-2013 Annex G: Mapping to the NIEM IEPD? (Part 44) According to Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet, AN-2013 Annex G: Mapping to the NIEM IEPD: | | |-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|----------------------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------| | Record Type-1: Transaction information record | Record Type-1: Transaction information record | Record Type-1: Transaction information record | Record Type-1: Transaction information record | Record Type-1: Transaction information record | Record Type-1: Transaction information record | Record Type-1: Transaction information record | Record Type-1: Transaction information record | Record Type-1: Transaction information record | Record Type-1: Transaction information record | Record Type-1: Transaction information record | Record Type-1: Transaction information record | | | | 1 | Type1- 1.005- Occurrences | EQ ( Count(FldsInRec(Rec(1), Int(5))), Int(1) ) | | M-Rec(1) | | | | T | | | | | 1 | Type1- 1.006- Occurrences | MO ( Count(FldsInRec(Rec(1), Int(6))), Set-Int([0,1]) ) | | M-Rec(1) | | | | T | | | | | 1 | Type1- 1.007- Occurrences | EQ ( Count(FldsInRec(Rec(1), Int(7))), Int(1) ) | | M-Rec(1) | | | | T | | | | | 1 | Type1- 1.008- Occurrences | EQ ( Count(FldsInRec(Rec(1), Int(8))), Int(1) ) | | M-Rec(1) | | | | T | | | | | 1 | Type1- 1.009- Occurrences | EQ ( Count(FldsInRec(Rec(1), Int(9))), Int(1) ) | | M-Rec(1) | | | | T |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet."}]}
{"id": "nist_02530", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Source Controls according to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations? Source Controls: AC-02, AC-02(03), AC-02(05), AC-02(13)", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_02531", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide? (Section 122) with security violations. The data administration area is responsible for the successful management and control of the data files and data bases necessary to support the information processing system. This area is supported by data management systems (which are intended to permit access to and retrieval from existing files, usually in response to single applications, reports generation, or simple information retrieval requirements) and/or data base management systems (which are intended to integrate and manage data in a nonredundant structure for [Processing by multiple applications). The data administrator should set policies to ensure that only properly authorized users have access to the various data and programs in the computer system. The following three definitions are important for the controls considered here: Identification is the process that enables, generally by the use of unique machine-readable names, recognition of users or resources as identical to those previously described to an ADP system. Authorization is the granting to a user, a program, or a process the right of access. Authentication is a measure designed to increase protection against fraudulent transmissions by establishing the validity of a transmission, message, station, or originator. 1. It is important that identification, authorization, and authentication are all carried out (either by the data administration area or by other components of the computer system or both) 2. Since it is possible for authorized or unauthorized users to circumvent data administration controls provided by the data base management system and thereby access data and programs either through the underlying operating system or directly, the data administration area must also be cognizant of operating system access controls and flaws and consider compensatory administrative and procedural controls. 3.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls."}]}
{"id": "nist_02532", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Dramatically Reducing Software Vulnerabilities_ Report to the White House Office of Science and Technology Policy provide? (Section 91) lysis,' is a means of assessing risks or threats [Fundamental08]. Through threat analysis, software can be designed to avoid the introduction of some vulnerabilities and reduce the severity of others. For instance, one form of threat analysis is documenting attack surfaces to understand how adversaries might use interfaces to elevate privilege. Without performing threat analysis, preferably at both the architectural and design levels, software can contain vulnerabilities that might otherwise be avoided [Shostack14]. Architectural threat analysis can significantly increase the security robustness and resilience of the architecture of software and its high-level designs to dramatically reduce the number and severity of vulnerabilities [Diamant11]. The call for a dramatic reduction in software vulnerability is heard from multiple sources, including the 2016 Cybersecurity National Action Plan. This report has identified five approaches for achieving this goal. Each approach meets three criteria: 1) have a potential for dramatic improvement in software quality, 2) could make a difference in a three to seven-year time frame and 3) are technical activities. The identified approaches use multiple strategies: - Stopping vulnerabilities before they occur, including improved methods for specifying and building software; - Finding vulnerabilities, including better testing techniques and more efficient use of multiple testing methods and - Reducing the impact of vulnerabilities by building architectures that are more resilient, so that vulnerabilities cannot be meaningfully exploited. Formal Methods. Formal methods include multiple techniques based on mathematics and logic, ranging from parsing to type checking to correctness proofs to model-based development to correct-by-construction.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Dramatically Reducing Software Vulnerabilities_ Report to the White House Office of Science and Technology Policy."}]}
{"id": "nist_02533", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Blockchain Networks_ Token Design and Management Overview provide? (Section 28) This can lead to massive data leaks and abusive data collection for users and businesses. Blockchain technology has enabled a new software paradigm for managing digital ownership in partial- or zero-trust environments. It uses tokens to conduct transactions, exchange verifiable data, and achieve coordination across organizations and on the web. Fundamental to this representation is that users can independently control token custody in digital wallets through public-key cryptography and interact with one another in a peer-to-peer manner. Blockchain networks provide secure transaction reconciliation, linkage, and storage in consolidated, integrity-protected distributed ledgers. They form mutually operated record-keeping execution environments or virtual machines. Combined with off-chain resources, blockchain-based tokens can allow for faster and cheaper transaction settlement while bolstering user-centric ownership models and interoperable data representations. Blockchain networks and the tokens that they form or support are also interchangeably referred to as cryptonetworks . Bitcoin and Ethereum introduced the technologies of blockchains and smart contracts as well as new types of global, web-native social constructs with decentralized governance. Anyone with an internet connection can view the blockchain, operate a publishing node, and submit transactions. Blockchain addresses are derived from public keys generated directly by the users who control the associated private keys' custody. Transactions are signed using these private keys before being validated and reconciled by the blockchain nodes, providing data integrity and public verifiability. More generally, the domain of permissionless blockchains brought about protocol-native tokens, or cryptocurrencies .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: token, sso. Contains security framework guidance for authentication systems. Source: Blockchain Networks_ Token Design and Management Overview."}]}
{"id": "nist_02534", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Validating the Correctness of Hardware Implementations of the NBS Data Encryption Standard say about PLAIN? According to Validating the Correctness of Hardware Implementations of the NBS Data Encryption Standard, PLAIN: 01A1D6D039776742 5CD54CA83DEF57DA 0248D43806F67172 51454B582DDF440A 42FD443059577FA2 059B5E0851CF143A 0756D8E0774761D2 7625].4B829BF486A 3BDD119049372802 26955F6835AF609A 164D5E404F275232 6B056E18759F5CCA 004BD6EF09176062 480D39006EE762F2 437540C8698F3CFA 072D43A077075292 02FE55778117F12A 1D9D5C5018F728C2 305532286D6F295A CIPHER 690F5B0D9A26939B 7A389D10354BD271 868EBB51CAB4599A 7178876E01F19B2A AF37FB421F8C4095 86A560F10EC6D85B 0CD3DA020021DC09 EA676B2CB7DB2B7A DFD64A815CAF1A0F 5C513C9C4886C088 0A2AEEAE3FF4AB77 EF1BF03E5DFA575A 88BF0DB6D70DEE56 A1F9915541020B56 6FBF1CAFCFFD0556 2F22E49BAB^CA1AC 5A6B612CC26CCE4A 5F4C038ED12B2E41 63FAC0D034D9F793", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validating the Correctness of Hardware Implementations of the NBS Data Encryption Standard."}]}
{"id": "nist_02535", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-11 in Guidelines for Smart Grid Cybersecurity? (Part 378) Control SI-11: individuals are characterized by multi- decade experience and history in their companies. Examples include distribution operations departments, field operations, and distribution engineering/planning. In terms of personnel security, it may be worthwhile considering \u201ctwo-person integrity,\u201d or \u201cTPI,\u201d a security measure to prevent single-person access to key management mechanisms. This practice comes from national security environments but may have some applicability to the smart grid where TPI security measures might be thought of as somewhat similar to the safety precaution of having at least two people working in hazardous environments. Another area of concern related to personnel issues has to do with not having a backup to someone having a critical function; in other words, a person (actor) as a single point of failure (SPOF). 7.3.4 Security Levels A security model should be built with different security levels that depend on the design of the network/system architecture, security infrastructure, and how trusted the overall system and its elements are. This model can help put the choice of technologies and architectures within a security context and guide the choice of security solutions. 7.3.5 Distributed vs. Centralized Model of Management There are unique issues associated with how to manage a system as distributed as the smart grid, yet maintain efficiency and reliability factors that imply centralization. Many grid systems are highly distributed, geographically isolated, and require local autonomy\u2014as commonly found in modern substations. Yet these systems need to have a measure of centralized security management in terms of event logging/analysis, authentication, etc. There should be a series of standards in this area that can strike the right balance and provide for the \u201chybrid\u201d approach necessary for the smart grid.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02536", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS) say about 2.1 Demonstration of Invariant Properties? (Part 1) According to Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS), 2.1 Demonstration of Invariant Properties: 2.1 Demonstration of Invariant Properties The first step in the process is to postulate a set of properties, or invariants, that the system must exhibit: things that happen with suitably small (approximating \"never\") or large (approximating \"always\") probability. The desirability of these properties is seldom in dispute when they are discussed in general terms (e.g., \"safety,\" \"security,\" or \"integrity\"). An example is the midair failure of a commercial airliner's structure (an instance of \"safety\") . The specified probability of this occurrence is so small that it should \"never\" happen within the service life of a given aircraft. Once a property is selected and a definition established (e.g., the actual allowed probability of structural failure) then the system to be constructed is modelled in some suitable mathematical notation, and a mathematical argument is presented that the model exhibits the properties. Continuing our commercial aircraft analogy, this first step is the stress analysis of the structure, which is based on an abstract representation of the aircraft. The step in no sense guarantees a safe airplane because people do not fly in abstract representations. Weaknesses can be introduced in later development steps through errors in detailed design, poor materials, or shoddy workmanship. The level of assurance at this point is that the aircraft is not inherently unsafe in a way that no amount of skill in detail design or construction can overcome. The output of this step is a specification for the entity to be constructed which is consistent in the sense that it does not contradict itself and is relevant in the sense that it describes a useful and feasible system. The importance of this first step should not be underestimated. Without this step, the project runs the risk of building an inappropriate system that is entirely correct (in the sense that the implementation meets the specifications) , but does not perform any useful function.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)."}]}
{"id": "nist_02537", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Workshop on Enhancing Security of Devices and Components Across the Supply Chain say about 2.2.1. Speaker Viewpoints? (Part 2) According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain, 2.2.1. Speaker Viewpoints: ives), 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. Jason 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 security architecture during the specification and planning phases. The dynamic nature of the IC development process may impact the metrics that need to be developed, and a security metric that is suitable for the register-transfer level (RTL) may not be appropriate at the gate or physical level. He noted that time-to-market constraints still run on an approximately six- to nine-month cycle, but complexity has increased, leading to the need for automation in security, reliability, and testing. This increased complexity also increases the number of assets to protect and the number of potential vulnerabilities to mitigate. Regardless of what security techniques and associated security metrics are used early in the development life cycle (i.e., pre-silicon), verification is still needed during the physical layout and post-silicon stages.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Workshop on Enhancing Security of Devices and Components Across the Supply Chain."}]}
{"id": "nist_02538", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Trustworthy Email provide? (Section 219) validity of information transmitted. Authenticity protection includes, for example, protecting against man-in-themiddle attacks/session hijacking and the insertion of false information into sessions. The information system only allows the use of [ Assignment: organization-defined certificate authorities ] for verification of the establishment of protected sessions. Supplemental Guidance: Reliance on certificate authorities (CAs) for the establishment of secure sessions includes, for example, the use of Secure Socket Layer (SSL) and/or Transport Layer Security (TLS) certificates. These certificates, after verification by their respective CAs, facilitate the establishment of protected sessions between web clients and web servers. Justification : Prior to establishing a TLS connection for SMTP transmission of email, a sending MTA should authenticate the certificate provided by the receiving MTA. This authentication could be PKIX, or an alternative method ( e.g., DANE, SMTP-STS, etc.). See Section 5.2 for details. Control: The organization employs a detonation chamber capability within [ Assignment: organization-defined system, system component, or location ]. Supplemental Guidance: De tonation chambers, also known as dynamic execution environments, allow organizations to open email attachments, execute untrusted or suspicious applications, and execute Universal Resource Locator (URL) requests in the safety of an isolated environment or a virtualized sandbox. These protected and isolated execution environments provide a means of determining whether the associated attachments or applications contain malicious code. While related to the concept of deception nets, this control is not intended to maintain a long-term environment in which adversaries can operate and their actions can be observed.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, sso. Contains security framework guidance for authentication systems. Source: Trustworthy Email."}]}
{"id": "nist_02539", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control UI-64 in Guidelines for the Secure Deployment of IPv6? (Part 291) Control UI-64: peration of a dual stack or mixed IPv6/IPv4 environment. One of the most difficult challenges facing the operations staff in a mixed IPv6/IPv4 environment is keeping the two environments synchronized. When operations makes changes to security controls such as firewall rule sets, access control lists, and IDS signatures, they must ensure the change occurs on both the IPv4 and IPv6 networks. Rules and signatures must be translated between IPv4 and IPv6 syntax and deployed as a single coordinated process. If strict change control is not followed, the two environments will have non-overlapping protections. In a dual stack environment, the physical topologies of the equipment are the same, but the logical topologies can be very different. Configuration changes can have unpredictable or unforeseen consequences. Configuration management controls should be structured to prevent configuration changes on IPv4 or IPv6 networks that affect the other network. Organizations should manage and monitor their IPv4, IPv6, and dual stack environment as a single environment. ## 6.9.5 Disposition Phase A migration from IPv4 to IPv6 results in displacement or retirement of equipment. Some equipment does not support IPv6 and is retired, while other equipment is transferred to IPv4 islands or to other organizations. Organizations must plan for the secure disposition of this obsolete equipment, ensuring that no confidential data is released. Organizations place themselves at great risk for exposing confidential information when disposing of obsolete equipment. A key decision concerning sanitization is whether the equipment is planned for reuse or retirement. Often, equipment is reused to conserve an organization's resources. Equipment should be sanitized before it is reused or retired. Most organizations have policies, regulations or standards that require the proper disposition of obsolete equipment. It is important that these processes be followed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_02540", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Peripheral Memory Cards according to Cell Phone Forensic Tools_ an Overview and Analysis Update? Peripheral Memory Cards: N.A. - The Motorola V300 does not allow for removable media. (NA)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis Update."}]}
{"id": "nist_02541", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 902) ephen Florida Power and Light Cox Software Architects Jennic LTD Tennessee Valley Authority State of Michigan LC RISQ & Associates Microchip Technology Czaplewski, John Northrup Grumman Corp. Dagle, Jeff Dalva, Dave Danahy, Jack Pacific Northwest National Laboratory Stroz Friedberg Bochman & Danahy Research Danezis, George Microsoft Dangler, Jack Das, Subir Davis, Scott Davison, Brian De Petrillo, Nick Delenela, Ann DeLoach, Tim DePeppe, Doug di Sabato, Mark Dieffenbach, Dillon Dienhart, Mary Dierking, Tim Dillon, Terry Dinges, Sharon Dion, Thomas Do, Tam Dodd, David Dodson, Greg Don-Arthur, George Doreswamy, Rangan Doring, Ernest Dorn, John Dougherty, Steven Downum, Wesley Dransfield, Michael Applied Communication Sciences Sensus Public Utility Commission of Texas Industrial Defender Ercot IBM Global Business Services i2IS Cyberspace Solutions Ernst & Young Xcel Energy Aclara Power-Line Systems, Inc. APS Trane Dept of Homeland Security Southwest Research Institute pbnetworks Dominion Resources Services, Inc. Alterium LLC Verisign, Inc. Pacific Gas & Electric Accenture IBM Telcordia National Security Agency 170 Drgon, Michele Drozinski, Timothy Drummond, Rik Dubrawsky, Ido Duffy, Paul Duggan, Pat Dulaney, Mike Dunfee, Rhonda Dunphy, Mary Dunton, Benjamin Dupper, Jeff Duren, Michael Dutta, Prosenjit Earl, Frank Eastham, Bryant Edgar, Tom Eggers, Matthew Eigenhuis, Scott M Ellison, Mark Emelko, Glenn Engels, Mark Ennis, Greg Enstrom, Mark Eraker, Liz Erickson, Dave Ersue, Mehmet Estefania, Maria Eswarahally, Shrinath Evans, Bob Ewing, Chris Fabela, Ronnie Fabian, Michael Faith, Doug Faith, Nathan Famolari, David DataProbity Florida Power & Light Company Drummond Group Itron Cisco Systems ConEd Arxan Technologies, Inc.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02542", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Data Integrity_ Recovering from Ransomware and Other Destructive Events provide? (Section 35) rs need to be defined and developed within the capability that look for specific events. For example, it may be very normal for end users to have encrypted files they develop during operational hours. But if every file on the end user's workstation begins to be encrypted, or an encryption begins to happen on the end user machine at hours outside of normal operational hours, these could be identifiable actions noted in the log files indicating a ransomware attack. For an enterprise, these triggers need to be defined appropriately and thoroughly to have a successful Corruption Testing capability. The Backup Capability component supports the ability to back up each component within the enterprise as well as perform a restore that uses backup data. The configuration of this component needs to align with the tempo of the enterprise. For example, if an enterprise is performing thousands of transactions per hour per day, then a backup solution that only performs a backup once a day may not provide adequate recovery capability for the enterprise. This type of configuration would allow for a potentially large data loss. If backups occur every morning and a loss of DI happened at the end of the day, then a full day's worth of transactions would be lost. The decision on what the correct configuration is determined by an organization's risk tolerance. More information pertaining to this decision can be found in Section 5.1.1.3. The Virtual Infrastructure component straddles the line between being part of the enterprise and part of the DI architecture. It provides virtual capabilities to the enterprise as well as backup and restoration capabilities to support the DI architecture. The backup and restoration capabilities are for the virtual infrastructure itself. For data that is produced on individual virtual machines (VMs), either the VM infrastructure can provide the file-level restoration or the backup component can provide this capability.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Recovering from Ransomware and Other Destructive Events."}]}
{"id": "nist_02543", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cell Phone Forensic Tools_ an Overview and Analysis provide? (Section 102) Table 11: Results Matrix | | Device | Device | Device | Device | Device | |-----------------------------|---------------|---------------|--------------|------------|-------------| | Scenario | Ericsson T68i | Motorola C333 | Motorola V66 | Nokia 3390 | Nokia 6610i | | Connectivity and Retrieval | Meet | Meet | Meet | Meet | Meet | | PIM Applications | Below | Meet | Below | Below | Below | | Dialed/Received Phone Calls | Below | Below | Below | Below | Below | | SMS/MMS Messaging | Below | Meet | Meet | Below | Below | | Internet Messaging | Miss | NA | NA | NA | NA | | Web Applications | Miss | NA | NA | Miss | Below | | Text File Formats | NA | NA | NA | NA | Below | | Graphics File Formats | Miss | NA | NA | NA | Below | Figure 27: Text-Based Report Excerpt | | Device | Device | Device | Device | Device | |---------------------------------|---------------|---------------|--------------|------------|-------------| | Scenario | Ericsson T68i | Motorola C333 | Motorola V66 | Nokia 3390 | Nokia 6610i | | Compressed Archive File Formats | NA | NA | NA | NA", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_02544", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control GG-23 in Security Labels for Open Systems_ an Invitational Workshop? (Part 42) Control GG-23: 1038) was deemed acceptable to BLACKER designers (NSA). - Thus, BLACKER and DoD hosts that interface to BLACKER are built to support these internet Protocol Security Option (IPSO) labeling standards. ## MITRE ## DoD IP DATAGRAM TRANSITING PHASE I BFE MITRE <!-- image --> ## Format of Basic Security Option <!-- image --> ## MITRE ## DDN-BLAC K E R Access Control MITRE | MAC Communities | CENSER | SIOP-ESI | SCI | NSA | |-------------------|---------------------|-----------------------|------------------|------------------| | Top Secret | Top Secret CENSER | Top Secret SIOP-ESI | Top Secret SCI | Top Secret NSA | | Secret | Secret GENSER | Secret SIOP-ESI | Secret SCI | Secret NSA | | Confidential | Confidential GENSER | Confidential SIOP-ESI | Confidential SCI | Confidential NSA | | Unclassified | Unclassified GENSER | Unclassified SIOP-ESI | Unclassified SCI | Unclassified NSA | | IP THE AD PROCESSES | AND THE AD'S CRITERIA CLASS D | AND THE AD'S SECURITY OPERATING MODE D | THEN THE DAC GROUP D | AND EMERGENCY MODE ENTRY D | |-----------------------|-------------------------------------|------------------------------------------|-------------------------------|------------------------------| | CENSER lsfonnatios | Minimtm of Cl (DDN EaeLroameat) | System High or Msltilevel | Trosted/Opea or DAA-depeadeal | DAA Discretioa | | CENSER lsfonnatios | Not Miilmia of Cl (DDN Eaeifoameat) | Dedicated | DAA-depeadeat | Prohibited | DoD/GOSIP/X.25 UNITS TRANSITING PHASE III BFE MTTRE <!-- image --> ## Summary of BLACKER Labeling Functionality - Labeling functionality used to identify security level of packet to BLACKER System.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, secret, top secret. Contains guidance on protecting sensitive government information. Source: Security Labels for Open Systems_ an Invitational Workshop."}]}
{"id": "nist_02545", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-1 in Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers? (Part 99) Control CM-1: mmerce) security; internet shopping security; multifactor authentication (MFA) ## ACKNOWLEDGMENTS We are grateful to the following individuals for their generous contributions of expertise and time. | Name | Organization | |------------------|-----------------------| | Greg Dicovitsky | RSA | | Leonardo Andrade | RSA | | Adam Cohn | Splunk | | Arshad Noor | StrongKey | | Kamil Kreiser | TokenOne | | Derek Hanson | Yubico | | David Coley | Dominion Tea | | Brian Abe | The MITRE Corporation | | Lorrayne Auld | The MITRE Corporation | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | Name | Organization | |--------------------|-----------------------| | Lura Danley | The MITRE Corporation | | Sallie Edwards | The MITRE Corporation | | Charles Jones, Jr. | The MITRE Corporation | | Joshua Klosterman | The MITRE Corporation | | Jay Vora | The MITRE Corporation | | Mary Yang | The MITRE Corporation | The Technology Partners/Collaborators who participated in this build submitted their capabilities in response to a notice in the Federal Register. Respondents with relevant capabilities or product components were invited to sign a Cooperative Research and Development Agreement (CRADA) with NIST, allowing them to participate in a consortium to build these example implementations.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, mfa, token. Contains security framework guidance for authentication systems. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_02546", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Data Integrity_ Recovering from Ransomware and Other Destructive Events provide? (Section 74) (CR 2.b) Backup Capability | | Description | Show that the DI solution can recover from a DI attack that destroys data via a malware attack. | | Associated test cases | N/A | | Associated CSF Subcategories | PR.DS-1, PR.IP-4, PR-DS-6, PR.PT1 | | Preconditions | User downloads a malicious executable that modifies critical data. | Procedure 1. Open the Tripwire Enterprise interface. 2. Click on the Tasks Section, enable the associated rule box, and click Run. 3. Open HPE ArcSight ESM. 4. Under Events, select Active Channels , then select Audit Events. 5. Find the Tripwire event logs associated with the event. Select Fields in the Customize dropdown and enable the following fields: - a. End Time - b. Attacker Address - c. File Name - d. Device Action - e. Source User Name - f. Device Custom String 6. Open IBM Spectrum Protect. 7. Click on Restore. 8. Select missing files and click Restore to original location. | Expected Results (pass) | Provide file integrity monitor (CR 2.a). | |---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | Modified files are correctly identified. | | | Recovery complete (CR 2.b). | | | System was restored to pre-DI event version. | | Actual Results | Details of the event were understood and the moment of last known good was identified for the file in question. All the files affected within that timeframe were correctly identified, and a full and successful restore was executed.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Recovering from Ransomware and Other Destructive Events."}]}
{"id": "nist_02547", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Trust Model for Security Automation Data 1.0 (TMSAD) say about 6.2.4 References? (Part 1) According to Trust Model for Security Automation Data 1.0 (TMSAD), 6.2.4 References: 6.2.4 References References are an essential part of an XML digital signature. This section contains requirements specific to the construction of references. These requirements apply to a &lt;dsig:Reference&gt; that is a child of either &lt;dsig:SignedInfo&gt; or &lt;dsig:Manifest&gt; . If the document that contains the signature is referenced, it SHOULD be referenced by setting the @URI attribute on &lt;dsig:Reference&gt; to the empty string (i.e., @URI =''). When referencing items in the signature that have an attribute of type xs:ID such as &lt;dsig:Object&gt; , &lt;dsig:Manifest&gt; , or &lt;dsig:SignatureProperties&gt; , they SHOULD be referenced using a URI fragment (e.g., @URI='#referenceIdentifier' ). ``` When referencing a <dsig:Object> , <dsig:Manifest> , or <dsig:SignatureProperties> from a <dsig:Reference> , the @Type attribute MUST be specified, and it MUST contain http://www.w3.org/2000/09/xmldsig#Object , http://www.w3.org/2000/09/xmldsig#Manifest , or http://www.w3.org/2000/09/xmldsig#SignatureProperties , respectively. ``` When specifying XPath transforms, content authors SHOULD use only XPath Filter 2.0 [XPath Filter-2], which is consistent with XML Digital Signature best practices [XMLDSIG-BEST]. Due to the more limited support of XPath 2.0, XPath transforms SHOULD use only XPath 1.0 [XPath] expressions. When referencing the root node of an XML document, if an ID exists on the root node that is not of type xs:ID , then the reference SHOULD specify an [XPath Filter-2] transform targeting the root node by ID. For example, if the root node of a document is &lt;root-node id='root123'&gt; , then the [XPath Filter-2] expression would be ' root-node[@id = 'root123'] ' with a @Filter attribute value of ' intersect '. This approach is preferable because if the signed document is later included as a child node within another XML document, the signature can still be valid (unless there is an ID conflict). Unnamed XSLT transforms SHOULD be avoided.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Trust Model for Security Automation Data 1.0 (TMSAD)."}]}
{"id": "nist_02548", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Security and Privacy in Public Cloud Computing say about 7. References? (Part 22) According to Guidelines on Security and Privacy in Public Cloud Computing, 7. References: ees of Multi-tenancy, ZDNET News and Blogs, June 16, 2008, &lt;URL: - [Wal10] Hannah Wald, Cloud Computing for the Federal Community, IAnewsletter, Vol. 13, No. 2, Information Assurance Technology Analysis Center, Spring 2010. - [Wei09] Jinpeng Wei, Xiaolan Zhang, Glenn Ammons, Vasanth Bala, Peng Ning, Managing Security of Virtual Machine Images in a Cloud Environment, ACM Cloud Computing Security Workshop (CCSW'09) , Chicago, Illinois, November 13, 2009. - [Wei11] Thilo Weichert, Cloud Computing and Data Privacy, The Sedona Conference, Working Group on International Electronic Information Management, Discovery &amp; Disclosure, February 2011, &lt;URL: - [Whi09] Lance Whitney, Amazon EC2 Cloud Service Hit by Botnet, Outage, December 11, 2009, CNET News, &lt;URL: - [Wil10] Matt Williams, All Eyes are on Los Angeles as City Deploys Cloud-Based E-Mail, Government Technology, February 10, 2010, &lt;URL: - [Xen08] Xen Architecture Overview, Version 1.2, Xen Wiki Whitepaper, February 13, 2008, &lt;URL: et=Xen+Architecture\\_Q1+2008.pdf&gt;. - [You07] Greg Young, Neil MacDonald, John Pescatore, Limited Choices are Available for Network Firewalls in Virtualized Servers, Gartner, Inc., ID Number: G00154065, December 20, 2007, &lt;URL: - [You08] Lamia Youseff, Maria Butrico, Dilma Da Silva, Toward a Unified Ontology of Cloud Computing, Grid Computing Environments Workshop (GCE08), held in conjunction with SC08, November 2008, &lt;URL: ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Security and Privacy in Public Cloud Computing."}]}
{"id": "nist_02549", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Publication History according to NIST Building a Cybersecurity and Privacy Learning Program According to Building a Cybersecurity and Privacy Learning Program, Publication History: Approved by the NIST Editorial Review Board on 2024-08-09 Supersedes NIST SP 800-50 (October 2003) https://doi.org/10.6028/NIST.SP.800-50 ; Supersedes NIST SP 800-16 (April 1998) https://doi.org/10.6028/NIST.SP.800-16", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Building a Cybersecurity and Privacy Learning Program."}]}
{"id": "nist_02550", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events say about 2.18.2 Import the CSV File to Symantec ICA? According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events, 2.18.2 Import the CSV File to Symantec ICA: 1. On the Symantec ICA web console, navigate to Gear Icon &gt; Integration. 2. Click the Data Sources tab. 3. Select User Defined for Choose Data Source. 4. Click Create Data Source. 5. Select File System IW for the Data Source Type. 6. Enter a name for the data source for Data Source Label. 7. Enter the hostname of the Symantec ICA server for Server Name. 8. Select Windows/Active Directory for the Authentication Mode. 9. Enter the location for the downloaded CSV file for Download Directory (relative to the Symantec ICA server). 10. Enter the location for the CSV file to be downloaded from for Source Folder (relative to the Symantec ICA server). <!-- image --> <!-- image --> 11. Click Save. 12. Right-click the newly created data source and select Create Query. 13. Enter a Query Name and Query Description. <!-- image --> <!-- image --> 14. If you specified the Source Folder correctly, you will see the CSV file listed. 15. Check the box next to any CSVs to import. 16. Click Save. <!-- image --> <!-- image --> 17. Click OK. 18. If desired, set a schedule for this import. 19. Click Save. <!-- image --> <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events."}]}
{"id": "nist_02551", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities provide? (Section 43) higher the vulnerability score. Each organization must determine for itself the precise meaning of 'slight,' 'moderate,' 'significant,' and 'catastrophic' in the organization's environment. Table 12. Collateral Damage Potential Scoring Evaluation | Metric Value | Description | |------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | None (N) | There is no potential for loss of life, physical assets, productivity or revenue. | | Low (L) | Successful exploitation of this vulnerability may result in slight physical or property damage or loss. Or, there may be a slight loss of revenue or productivity. | | Low-Medium (LM) | Successful exploitation of this vulnerability may result in moderate physical or property damage or loss. Or, there may be a moderate loss of revenue or productivity. | | Medium-High (MH) | Successful exploitation of this vulnerability may result in significant physical or property damage or loss. Or, there may be a significant loss of revenue or productivity. | | High (H) | Successful exploitation of this vulnerability may result in catastrophic physical or property damage or loss. Or, there may be a catastrophic loss of revenue or productivity. | | Not Defined (ND) | Assigning this value to the metric will not influence the score. It is a signal to the equation to skip this metric. The default value is None. | The Confidentiality Requirement, Integrity Requirement, and Availability Requirement metrics enable the analyst to customize the environmental score depending on the importance of the affected IT asset to an organization, measured in terms of confidentiality, integrity, and availability.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities."}]}
{"id": "nist_02552", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Module-Lattice-Based Key-Encapsulation Mechanism Standard provide? (Section 2) ess a quantum computer. This standard specifies three parameter sets for ML-KEM. In 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. Published: August 13, 2024 Effective: August 13, 2024 Federal 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). In a KEM, the computation of the shared secret key begins with Alice generating a decapsulation key and an encapsulation key . Alice keeps the decapsulation key private and makes the encapsulation key available to Bob. Bob then uses Alice's encapsulation key to generate one copy of a shared secret key along with an associated ciphertext .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Module-Lattice-Based Key-Encapsulation Mechanism Standard."}]}
{"id": "nist_02553", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PM-8200 in Cell Phone Forensic Tools_ an Overview and Analysis? (Part 40) Control PM-8200: Table 5: SIMs | SIM | Phase | Network | Services | |-------|-------------------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1604 | 2 - profile download required | AT&T | Abbreviated Dialing Numbers (ADN) Fixed Dialing Numbers (FDN) Short Message Storage (SMS) Last Numbers Dialed (LND) Group Identifier Level 1 (GID1) Group Identifier Level 2 (GID2) Service Dialing Numbers (SDN) General Packet Radio Service (GPRS) | | 1144 | 2 - profile download required | AT&T | Abbreviated Dialing Numbers (ADN) Fixed Dialing Numbers (FDN) Short Message Storage (SMS) Last Numbers Dialed (LND) General Packet Radio Service (GPRS) | | 8778 | 2- profile download required | Cingular | Abbreviated Dialing Numbers (ADN) Fixed Dialing Numbers (FDN) Short Message Storage (SMS) Last Numbers Dialed (LND) Group Identifier Level 1 (GID1) Group Identifier Level 2 (GID2) Service Dialing Numbers (SDN) General Packet Radio Service (GPRS) | | SIM | Phase | Network | Services | |-------|-------------------------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 7202 | 2 - profile download required | T-Mobile | Abbreviated Dialing Numbers (ADN) Fixed Dialing Numbers (FDN) Short Message Storage (SMS) Last Numbers Dialed (LND) Group Identifier Level 1 (GID1) General Packet Radio Service (GPRS) | | 5343 | 2 - profile download required | T-Mobile | Abbreviated Dialing", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_02554", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Security-Focused Configuration Management of Information Systems say about GLOSSARY? (Part 19) According to Guide for Security-Focused Configuration Management of Information Systems, GLOSSARY: ser [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. | | 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. | | 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. | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | United States government configuration baseline (USGCB) 33 | The United States Government Configuration Baseline (USGCB) provides security configuration baselines for Information Technology products widely deployed across the federal agencies. The USGCB baseline evolved from the federal Desktop Core Configuration mandate. The USGCB is a Federal government-wide initiative that provides guidance to agencies on what should be done to improve and maintain effective configuration settings focusing primarily on security.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_02555", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cloud Computing Synopsis and Recommendations say about 4.4 The On-site Community Cloud Scenario? (Part 2) According to Cloud Computing Synopsis and Recommendations, 4.4 The On-site Community Cloud Scenario: l using a standard such as XACML [Mos05], or following a security model such as role-based access control [Fer92] or attribute-based access control [Kar09]) might be used to express sharing policies. Besides controlling access to resources, identity management [Oid11, Rag08, Oix10] is important in this scenario since clients from multiple participant organizations access a common pool of resources. As with the on-site private cloud and the outsourced private cloud, although the general statements remain true for the on-site community scenario, the on-site community cloud scenario also allows for a more detailed understanding of some of the general statements as well as additional statements that organizations considering the use of an on-site community cloud should consider: - \uf06e Network Dependency (on-site community). As with the on-site private scenario, where the organization spans multiple sites, the consumers in an on-site community cloud need to either provision controlled inter-site communication links or use cryptography over a less controlled communications media (such as the public Internet). The reliability and security of the community cloud will depend on the reliability and security of the communication links. Dedicated leased network connections can also be used to support enhanced performance, reliability, and security. In the on-site community case, in addition, care should be taken to understand the actual dependencies between member organizations since there are multiple organizations participating and any subset of them could suffer a cloud infrastructure failure (e.g., going offline). Additionally, local clouds will probably 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. - \uf06e Consumers still need IT skills (on-site-community).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, identity management. Contains security framework guidance for authentication systems. Source: Cloud Computing Synopsis and Recommendations."}]}
{"id": "nist_02556", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does General Procedures for Registering Computer Security Objects say about Table of Contents? (Part 4) According to General Procedures for Registering Computer Security Objects, Table of Contents: | C.1.3 Tag-Specific Information | 13 | | C.1.4 Security Object Usage | Rules and Handling Instructions 14 | | C.2 Security Tag Registration Rules | 14 | | C.2.1 Special Rules for Bit | Map Tags 15 | | C.2.2 Special Rules for Enumerated Tags | 15 | | C.2.3 Special Rules for Range Tags | 15 | | C.2.4 Special Rules for Free Form Tags | 15 | 1.0", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: General Procedures for Registering Computer Security Objects."}]}
{"id": "nist_02557", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out say about APPENDIX H: SAMPLE TEXT ON ENVIRONMENT CONSIDERATIONS FOR SOWs? (Part 2) According to Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out, APPENDIX H: SAMPLE TEXT ON ENVIRONMENT CONSIDERATIONS FOR SOWs: ive, physical, environmental, and telecommunications safeguards; - o statement on the continuity of operation of all information systems that support mission-essential/critical organization functions. This section should also cover the location, source, and contact for any other information that the Contractor may need to know in order to perform the tasks in the SOW. This includes the results of any previous audits, reviews, studies, certifications, analyses, etc. that address the computer security of the system(s) for which the SOW applies. <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out."}]}
{"id": "nist_02558", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AN-2011 in Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record? (Part 9) Control AN-2011: demonstrate that products meet the technical requirements specified in the standards.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Requirements and Conformance Test Assertions for ANSI_NIST-ITL 1-2011 Record Type 18 - DNA Record."}]}
{"id": "nist_02559", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PS-15413 in Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations? (Part 424) Control PS-15413: orking Group (v3), August 2021, This report leveraged the 2015 version of the NIST SP 800-161. | Threat Sources | Threat | Examples | |--------------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Systemic Economic Risks | Business failure of a key supplier leads to supply chain disruption | Economic risks stem from threats to the financial viability of suppliers and the potential impact to the supply chain resulting from the failure of a key supplier. Other threats to the supply chain that result in economic risks include vulnerabilities to cost volatility, reliance on single-source suppliers, the cost to swap out suspect vendors, and resource constraints due to company size.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_02560", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-6 in NIST_SP_800-37r2_Risk_Management_Framework? (Part 318) Control AM-6: being managed by an ongoing authorization process). ## REAUTHORIZATION Reauthorization actions occur at the discretion of the authorizing official in accordance with federal or organizational policy. 156 If a reauthorization action is required, organizations maximize the use of security and privacy risk information produced as part of the continuous monitoring processes currently in effect. Reauthorization actions, if initiated, can be either time-driven or event-driven. Time-driven reauthorizations occur when the authorization termination date is reached (if one is specified). If the system is under ongoing authorization, 157 a time-driven reauthorization may not be necessary. However, if the continuous monitoring program is not sufficiently comprehensive to fully support ongoing authorization, a maximum authorization period can be specified by the authorizing official. Authorization termination dates are guided and informed by federal and organizational policies and by the requirements of authorizing officials. Under ongoing authorization, a reauthorization may be necessary if an event occurs that produces risk above the acceptable organizational risk tolerance. A reauthorization may be warranted, for example, if there is a breach/incident or failure of or significant problems with the continuous monitoring program. Reauthorization actions may necessitate a review of and changes to the continuous monitoring strategy which may in turn, affect ongoing authorization. For security and privacy assessments associated with reauthorization, organizations leverage security and privacy information generated by the continuous monitoring program and fill in gaps with manual assessments. Organizations may supplement automatically-generated assessment information with manually-generated information in situations where an increased level of assurance is needed.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_02561", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ID-19 in Securing Telehealth Remote Patient Monitoring Ecosystem? (Part 9) Control ID-19: O engages with a telehealth platform provider that is a separate entity from the HDO and patient. The telehealth platform provider manages a distinct infrastructure, applications, and set of services. The telehealth platform provider coordinates with the HDO to provision, configure, and deploy the RPM components to the patient home and assures secure communication between the patient and clinician. The NCCoE analyzed RPM ecosystem risk factors by applying methods described in the NIST Risk Management Framework. The NCCoE also leveraged the NIST Cybersecurity Framework, NIST Privacy Framework, and other relevant standards to identify measures to safeguard the ecosystem. In collaboration with healthcare, technology, and telehealth partners, the NCCoE built an RPM ecosystem in a laboratory environment to explore methods to improve the cybersecurity of an RPM. Technology solutions alone may not be sufficient to maintain privacy and security controls on external environments. This practice guide notes the application of people, process, and technology as necessary to implement a holistic risk mitigation strategy. This practice guide's benefits include helping organizations assure the confidentiality, integrity, and availability of an RPM solution, enhancing patient privacy and limiting HDO risk when implementing an RPM solution. ## KEYWORDS access control; authentication; authorization; behavioral analytics; cloud storage; data privacy; data security; encryption; HDO; healthcare; healthcare delivery organization; remote patient monitoring; RPM; telehealth; zero trust ## ACKNOWLEDGMENTS We are grateful to the following individuals for their generous contributions of expertise and time.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_02562", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Secure Hash Standard (SHS) say about 3.1 Bit Strings and Integers? (Part 1) According to Secure Hash Standard (SHS), 3.1 Bit Strings and Integers: 3.1 Bit Strings and Integers The following terminology related to bit strings and integers will be used. 1. A hex digit is an element of the set { 0, 1,\u2026, 9, a,\u2026, f }. A hex digit is the representation of a 4-bit string. For example, the hex digit ' 7 ' represents the 4-bit string ' 0111 ', and the hex digit ' a ' represents the 4-bit string ' 1010 '. 2. A word is a w -bit string that may be represented as a sequence of hex digits. To convert a word to hex digits, each 4-bit string is converted to its hex digit equivalent, as described in (1) above. For example, the 32-bit string 1010 0001 0000 0011 1111 1110 0010 0011 can be expressed as ' a103fe23 ', and the 64-bit string ``` 1010 0001 0000 0011 1111 1110 0010 0011 0011 0010 1110 1111 0011 0000 0001 1010 ``` can be expressed as ' a103fe2332ef301a '. Throughout this specification, the 'big-endian' convention is used when expressing both 32- and 64-bit words, so that within each word, the most significant bit is stored in the left-most bit position. 3. An integer may be represented as a word or pair of words. A word representation of the message length, \uf06c , in bits, is required for the padding techniques of Sec. 5.1. An integer between 0 and 2 32 -1 inclusive may be represented as a 32-bit word. The least significant four bits of the integer are represented by the right-most hex digit of the word representation. For example, the integer 291=2 8 + 2 5 + 2 1 + 2 0 =256+32+2+1 is represented by the hex word ' 00000123' . The same holds true for an integer between 0 and 2 64 -1 inclusive , which may be represented as a 64-bit word. If Z is an integer, 0 \uf0a3 Z &lt; 2 64 , then Z =2 32 X + Y , where 0 \uf0a3 X &lt; 2 32 and 0 \uf0a3 Y &lt; 2 32 . Since X and Y can be represented as 32-bit words x and y , respectively, the integer Z can be represented as the pair of words ( x , y ). This property is used for SHA-1, SHA224 and SHA-256.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Hash Standard (SHS)."}]}
{"id": "nist_02563", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Viewing Detailed Analyzer Data according to NIST Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events, Viewing Detailed Analyzer Data: 1. The desired field data can be exported to either a .csv or Microsoft Excel format, by clicking on the Export button in the details tab. 2. Charts can be added or removed using the Charts dropdown menu near the top of the analyzer. 3. Any data in the Field List on the right side can be added to or removed from the view and will be automatically incorporated into its relevant rows or columns. 4. The entire view format can be exported as a .json file from the Open View option. <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events."}]}
{"id": "nist_02564", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PM-8200 in Cell Phone Forensic Tools_ an Overview and Analysis Update? (Part 114) Control PM-8200: Table 25: Results Matrix | | Device | Device | Device | Device | Device | Device | |-----------------------------|---------------|-----------------|--------------|---------------|------------|-------------| | Scenario | Ericsson T68i | Motorola MPX220 | Motorola V66 | Motorola V300 | Nokia 6200 | Nokia 6610i | | Connectivity and Retrieval | Meet | Meet | Meet | Meet | Meet | Meet | | PIM Applications | Below | Below | Below | Below | Below | Below | | Dialed/Received Phone Calls | Below | Below | Below | Below | Below | Below | | SMS/MMS Messaging | Below | Below | Below | Below | Below | Below | | | Device | Device | Device | Device | Device | Device | |---------------------------------|---------------|-----------------|--------------|---------------|------------|-------------| | Scenario | Ericsson T68i | Motorola MPX220 | Motorola V66 | Motorola V300 | Nokia 6200 | Nokia 6610i | | Internet Messaging | Miss | Below | NA | Below | NA | NA | | Web Applications | Miss | Miss | NA | Miss | Miss | Miss | | Text File Formats | NA | Miss | NA | Miss | Miss | Miss | | Graphics File Formats | Miss | Below |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis Update."}]}
{"id": "nist_02565", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-002 in Guidelines for Smart Grid Cybersecurity? (Part 244) Control IP-002: s, but there is a question about how a root organization becomes a root organization, how they verify the identity for those requiring certificates, and even what identity actually means for a device. 4.2.2.2 Single Sign On Many smart grid components, such as wireless devices (e.g., AMI), are low-processing-power devices with wireless interface (e.g., Zigbee) and are often connected to the backhaul networks with low bandwidth links. These components are typically equipped with 4 kB to 12 kB of RAM and 64 kB to 256 kB of flash memory. The link characteristics can also vary, depending upon the wireless radio features, such as the sleeping or idle mode of operation. For example, the advanced metering system may periodically be awakened and synced with the network to save power, rather than remain always active. Additional device requirements include (1) the support of multi-hop networks using mesh topology (e.g., to extend the backhaul reach back), and (2) support of multiple link layer technologies. Advanced meters can also be used for other purposes besides simple metering data. For example, ANS C12.22 [\u00a74.4-17] allows using advanced meters peering via relay or concentrators. Other 235 applications should be able to run simultaneously on a single meter. For security requirements, each application needs to be authenticated and needs to preserve the integrity of the data provided to the system (e.g., billing system). In such scenarios, the protocol overhead and performance must be optimized, and performance must be taken into account for these low- processing power components. From a key management perspective, optimization on the amount of exchanges and the footprint to execute peer authentication, key establishment, key update, and key deletion have to be considered for each communication layer and protocol that is used by smart grid components that need to be secured.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02566", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-1 in Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector? (Part 183) Control AC-1: | NIST SP 800-53 Rev. 5 | |--------------------------------------------|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| | | | manufacturer's supporting entities. \uf0a7 Providing communications and documentation detailing how to perform recommended local and/or remote maintenance activities. \uf0a7 Providing the details necessary to enable IoT device customers to monitor onsite and offsite IoT device maintenance activities. \uf0a7 Providing the details necessary for maintaining records for nonlocal IoT device maintenance and diagnostic activities. \uf0a7 Providing the details necessary to implement management and operational controls for IoT device maintenance personnel and associated authorizations, and record-keeping of maintenance organizations and personnel.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector."}]}
{"id": "nist_02567", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Stateless Hash-Based Digital Signature Standard say about 3. Overview of the SLH-DSA Signature Scheme? (Part 1) According to Stateless Hash-Based Digital Signature Standard, 3. Overview of the SLH-DSA Signature Scheme: 3. Overview of the SLH-DSA Signature Scheme SLH-DSA is a stateless hash-based signature scheme that is constructed using other hash-based signature schemes as components: (1) a few-time signature scheme, forest of random subsets (FORS), and (2) a multi-time signature scheme, the eXtended Merkle Signature Scheme (XMSS). XMSS is constructed using the hash-based one-time signature scheme Winternitz One-Time 2 Signature Plus (WOTS + ) as a component. Conceptually, an SLH-DSA key pair consists of a very large set of FORS key pairs. 3 The few-time signature scheme FORS allows each key pair to safely sign a small number of messages. An SLH-DSA signature is created by computing a randomized hash of the message, using part of the resulting message digest to pseudorandomly select a FORS key, and signing the remaining part of the message digest with that key. An SLH-DSA signature consists of the FORS signature and the information that authenticates the FORS public key. The authentication information is created using XMSS signatures. XMSS is a multi-time signature scheme that is created using a combination of WOTS + one-time signatures and Merkle hash trees [13]. An XMSS key consists of 2 \u210e \u2032 WOTS + keys and can sign 2 \u210e \u2032 messages. The WOTS + public keys are formed into a Merkle hash tree, and the root of the tree is the XMSS public key. (The Merkle hash tree formed from the WOTS + keys is also referred to as an XMSS tree.) An XMSS signature consists of a WOTS + signature and an authentication path within the Merkle hash tree for the WOTS + public key. In Figure 1, triangles represent XMSS trees, squares represent the WOTS + public keys, and circles represent the interior nodes of the hash tree. Within an XMSS tree, the square and circles that are filled in represent the authentication path for the WOTS + public key needed to verify the signature. The authentication information for a FORS public key is a hypertree signature.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Stateless Hash-Based Digital Signature Standard."}]}
{"id": "nist_02568", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management say about 2.2.4 Determining Potential Impact? (Part 1) According to Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management, 2.2.4 Determining Potential Impact: 2.2.4 Determining Potential Impact The final prerequisite for creating a practical list of risk scenarios for the risk register is the determination of the potential impact of the threats and vulnerabilities described above. The section below describes the completion of part D of the CSRM Risk Description column (Figure 11.) Figure 11: Adverse Impact Inclusion in Risk Scenario Identification (Part D) <!-- image --> Discovery activities throughout Section 2.2 may have already highlighted potential adverse impacts to explore. Description of the impact is a key element for enterprise stakeholders and represents the connection between cybersecurity risks and the enterprise objectives that would be affected by those risks. Reviewing the key enterprise objectives, as identified in scoping, and 26 Information about the NIST SCAP is available at https://csrc.nist.gov/projects/security-content-automation-protocol/. 27 More information about the DHS AWARE scoring method is available at armed with a broad list of potential threats and vulnerabilities, personnel can develop a list of realistic scenarios. While some types of impact may not be immediately apparent, the long-term effects can be significant. For example, consider a situation where a criminal has gained unauthorized access to an enterprise system and has exfiltrated a large amount of confidential data. If that criminal is cautious, there may not be any disruption of operations. In fact, sometimes cyber criminals actually try to improve the health of a victim's technology to ensure that it will be available for their malicious activity. In this case, the system may seem to be working fine - even better than ever - and then later, the enterprise realizes that a catastrophic loss has occurred. Notably, impact scenarios can be considered as a continuum rather than as a binary state.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management."}]}
{"id": "nist_02569", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Telehealth Remote Patient Monitoring Ecosystem say about C-6 Vulnerabilities? (Part 1) According to Securing Telehealth Remote Patient Monitoring Ecosystem, C-6 Vulnerabilities: C-6 Vulnerabilities Below is a customized application on identifying vulnerabilities that aggregates vulnerabilities identified in NIST SP 800-30 Revision 1 [9]. As noted in the document, a vulnerability is a deficiency or weakness that a threat source may exploit, resulting in a threat event. The document further describes that vulnerabilities may exist in a broader context, i.e., that they may be found in organizational governance structures, external relationships, and mission/business processes. The following table enumerates those vulnerabilities, using a holistic approach, and represents those vulnerabilities that this project identified and for which it offers guidance. For further description, readers should reference NIST SP 800-30 Revision 1 [9]. Table C-8 Vulnerability Taxonomy | Vulnerability Description | Vulnerability Severity | Predisposing Condition | Pervasiveness of Predisposing Condition | |---------------------------------------------|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| | out-of-date software | high | Systems may not have patches deployed in a timely fashion, or software may not be validated to assure that applications may operate appropriately should the underlying operating system receive new updates.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_02570", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services say about 4.1.6. Supply Chain Risk Management Category? (Part 4) According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services, 4.1.6. Supply Chain Risk Management Category: 5 PM-9, RA-3, SR-2, SR-3, SR-5, SR-6 USG FRP 1.7 | | Identify Supply | Applicability to PNT | References (PNT Specific) | |-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| | Chain Risk Management Subcategory | about the PNT system and introduce hardware, software, or firmware that could cause the disruption or manipulation of the PNT data as well as any dependencies that may be easier to subvert.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_02571", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Overview and Considerations of Access Control Based on Attribute Encryption say about 1. Introduction? (Part 2) According to Overview and Considerations of Access Control Based on Attribute Encryption, 1. Introduction: traditional PKE schemes, which allows it to be an efficient and flexible attribute-based access control method. The main features of ABE access control include: - A one-to-many authorization scheme. - Fine-grained access control based on user (i.e., subject) attributes or resource (i.e., object) attributes. - Message sending without obtaining public-key certificates from public-key infrastructure. - Data decryption without evaluating permissions from access control policy. - Collusion-resistance so that a user who holds multiple keys cannot combine different keys to access data that are only allowed to be accessed by one key. These fine-grained and collusion-resistant features support the physical resources and performance demands of systems like the cloud, the Internet of Things (IoT), disrupt-tolerant networks, wireless sensor networks, mobile ad hoc networks, and public search service systems [ELT][SW]. This document is organized as follows: - Section 1 is the introduction. - Section 2 provides an overview of the fundamental theories that ABE is built on, including elliptic-curve cryptography, bilinear pairing, and bilinear pairing for elliptic curve cryptography. - Section 3 introduces identity-based encryption (IBE). - Section 4 illustrates ABE algorithms for Ciphertext-Policy Attribute-Based Encryption (CP-ABE) and Key-Policy Attribute-Based Encryption (KP-ABE). - Section 5 describes considerations for the applications of ABE from the perspectives of security, performance, access control policies, and support models. - Section 6 is the conclusion. - Appendix A identifies changes that have been made to this publication.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Overview and Considerations of Access Control Based on Attribute Encryption."}]}
{"id": "nist_02572", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings say about 3 Disadvantages of a SEM approach? According to 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings, 3 Disadvantages of a SEM approach: One of the drawbacks of SEM approach is that it is vulnerable to Denial-ofService (DoS) attacks, as pointed in [3]. There are three types of DoS attack:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02573", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is https according to Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)? https: //nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-147B.pdf.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_02574", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Considerations for Voice Over IP Systems provide? (Section 113) lay protection for the RTP traffic as well as RTCP (Real-time Transport Control Protocol). SRTP was being standardized at the IETF in the AVT working group. It was released as RFC 3711 in March 2004. SRTP provides a framework for encryption and message authentication of RTP and RTCP streams. SRTP can achieve high throughput and low packet expansion. SRTP is independent of a specific RTP stack implementation and of a specific key management standard, but Multimedia Internet Keying (MIKEY) has been designed to work with SRTP. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ AES in counter mode is the default algorithm, if encryption is desired. AES-f8 mode is an option for UMTS applications. The pre-defined authentication transform is HMAC-SHA1. The default session authentication key-length is 160 bits, the default authentication tag length is 80 bits. The key derivation function is AES in counter mode with a 128-bit master key from the key management. Interface for hardware-crypto support (e.g. IP phones). In comparison to the security options for RTP there are some advantages to using SRTP. The advantages over the RTP standard security and also over the H.235 security for media stream data are listed below. - Confidentiality for RTP as well as for RTCP by encryption of the respective payloads; - Integrity for the entire RTP and RTCP packets, together with replay protection; - The possibility to refresh the session keys periodically, which limits the amount of cipher text produced by a fixed key, available for an adversary to cryptanalyze; - An extensible framework that permits upgrading with new cryptographic algorithms; - A secure session key derivation with a pseudo-random function at both ends; - The usage of salting keys to protect against pre-computation attacks; - Security for unicast and multicast RTP applications.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_02575", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Telehealth Remote Patient Monitoring Ecosystem say about E-2 Device Capabilities Supporting Functional Evaluations? (Part 5) According to Securing Telehealth Remote Patient Monitoring Ecosystem, E-2 Device Capabilities Supporting Functional Evaluations: ID.RA-1 ID.RA-4 ID.RA-5 ID.RA-6 | | \uf0a7 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. \uf0a7 Providing the details necessary for the installation of IoT devices and associated systems security-relevant software updates within an organizationally defined time period from the vendor release of the updates. \uf0a7 Providing education describing the operational impacts of the anti-malware activities on mission critical processes in the system where the IoT device is used. \uf0a7 Providing education explaining the responsibilities of IoT device customers to perform their own risk assessments, using information provided by the manufacturer, to determine the risks the IoT device will bring into the IoT device customer's systems. | | RPM-3 Identity Management, Authentication, and | \uf0a7 Ability to uniquely identify the IoT device logically. \uf0a7 Ability to uniquely identify a remote IoT device. | \uf0a7 Providing details for how to establish unique identification for each IoT device associated with the system and critical system components within which it is used. | .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, zero-day. Contains technical security guidance that could inform defensive posture. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_02576", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.3.4 Generic Container Provider Virtual Machine Card Edge Interface according to NIST Government Smart Card Interoperability Specification, Version 2.1 According to Government Smart Card Interoperability Specification, Version 2.1, 5.3.4 Generic Container Provider Virtual Machine Card Edge Interface: Table 5-22 shows the Generic Container Provider VM APDUs. As described in Chapter 8, containers accessed by these APDUs are split into two buffers: a TL buffer containing Tag and associated Length values, and a V buffer containing the values identified by the corresponding Tags and Lengths. Table 5-22: Generic Container VM APDUs | Card Function | CLA | INS | P1 | P2 | L c | Data | L e | |-----------------|------------|-------|-------|-------|-------|---------------------------------|-------| | READ BUFFER | 0x80 | 0x52 | Off/H | Off/L | 0x02 | Buffer and number bytes to read | - | | UPDATE BUFFER | 0x80, 0x84 | 0x58 | Off/H | Off/L | L c | Buffer and data to update | - |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_02577", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1. Introduction according to NIST Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, 1. Introduction: Executive Order (EO) 13556 [1] established a government-wide program to standardize the way the executive branch handles Controlled Unclassified Information (CUI). 1 EO 13556 required that the CUI program emphasize openness, transparency, and uniformity of government-wide practices and that the program implementation take place in a manner consistent with Office of Management and Budget (OMB) policies and National Institute of Standards and Technology (NIST) standards and guidelines. As the CUI program Executive Agent, the National Archives and Records Administration (NARA) provides information, guidance, policy, and requirements on handling CUI [4]. This includes approved CUI categories and descriptions, the basis for safeguarding and dissemination controls, and procedures for the use of CUI. 2 The CUI federal regulation [5] provides guidance to federal agencies on the designation, safeguarding, marking, dissemination, decontrolling, and disposition of CUI; establishes self-inspection and oversight requirements; and delineates other facets of the program. The CUI regulation requires federal agencies that use federal information systems 3 to process, store, or transmit CUI to comply with NIST standards and guidelines. The responsibility of federal agencies to protect CUI does not change when such information is shared with nonfederal organizations. 4 Therefore, a similar level of protection is needed when CUI is processed, stored, or transmitted by nonfederal organizations using nonfederal systems. 5 To maintain a consistent level of protection, the security requirements for safeguarding CUI in nonfederal systems and organizations must comply with Federal Information Processing Standards (FIPS 199) publication [6] and FIPS 200 [7]. The requirements are derived from the controls in NIST Special Publication (SP) 800-53 [8].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_02578", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Personal Identity Verification (PIV) of Federal Employees and Contractors provide? (Section 57) ocedure, for example by authenticating the cardholder with an associated derived PIV credential or by confirming reset via email to the on-record government-issued email address. The remote PIN reset operation SHALL satisfy the requirements for remote, postissuance updates specified in Section 2.9.2. Regardless of the PIN reset procedure used, the chosen PIN SHALL meet the activation requirements specified in Section 4.3.1. Both fingerprints used for OCC SHALL be replaced during an OCC reset. OCC reset MAY be performed in person at an issuing facility or a supervised remote identity proofing station: When OCC reset is performed in person at the issuing facility, before the reset, the issuer SHALL perform a biometric verification of the cardholder to the biometric data records in the PIV enrollment record. 16 If the biometric verification decision is negative or no alternative biometric data records are available, the cardholder SHALL provide the PIV Card to be reset and another primary identity source document (as specified in Section 2.7). An attending operator SHALL inspect these and compare the cardholder with the electronic facial image retrieved from the enrollment data record and the photograph printed on the PIV Card. OCC reset at a supervised remote identity proofing station combines the assurance of an in-person reset with the convenience of a kiosk reset. All protections and requirements of Section 2.7.1 SHALL be observed during the procedure. The 16 If OCC is being reset due to epidermal damage on a specific finger, it may be prudent to perform the biometric comparison with a different finger or different biometric characteristic.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Personal Identity Verification (PIV) of Federal Employees and Contractors."}]}
{"id": "nist_02579", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-11 in Guidelines for Smart Grid Cybersecurity? (Part 464) Control SI-11: create a communications network between end systems at customer premises (including meters, gateways, and other equipment) and diverse business and operational systems of utilities and third parties. AMI systems provide the technology to allow the exchange of information between customer end systems and those other utility and Third Party systems. In order to protect this critical infrastructure, end-to-end security must be provided across the AMI systems, encompassing the customer end systems as well as the utility and Third Party systems that are interfaced to the AMI systems. Scenario Description This use case describes a batch instruction send to meters as a multicast transaction in an open loop situation. The open loop situation means that Advanced metering Infrastructure (AMI) Head End System (HES) does not expect a response for each packet sent to a meter. A Utility requires actions from a set of meters, which may or may not result in a change to the power state of the grid. These include at least meter reading, and certain configuration changes. The meter Reading and Control (MRC) determines the need to send batch instructions to more than one meter. MRC looks up the meter associated with the customer and then instructs the Advanced metering Infrastructure (AMI) Head End system (HES) to queue up and execute the instructions. The AMI Head End can determine the instruction needs to be split into packets, schedules the sending of the packets and continues to send the packets to the meters until all instruction packets have been sent. The meter(s) receive the instruction(s) and determines if the instruction is permitted. After execution, the meter(s) send the instruction result to the HES. The HES will then send the instruction result to the MRC. If the instruction result is energy usage information, the MRC will then forward the energy usage information onto the meter Data Management System (MDMS).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02580", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i? (Part 151) Control ES-1: Questions for Identifying an Appropriate EAP Method | Question | Analysis | |----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Does the WLAN solution need to support guest users?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i."}]}
{"id": "nist_02581", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Guideline #3: Configure the Recording of Events in a Log according to NIST Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems According to Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems, Guideline #3: Configure the Recording of Events in a Log: A log of cybersecurity-relevant activities that is stored in another location can help identify the factors that led to an unexpected event, recover from the compromise, and determine how to prevent such compromises in the future. Logs should contain information about the operation of the smart inverter (e.g., normal or anomalous values of system parameters) when an event is detected and enable reviewers to understand the chain of events with a degree of fidelity. Event logging supports troubleshooting for smart-inverter issues as well as responses to cyber events. In addition to system parameters, logs should also contain cybersecurity-relevant information, such as: - Creation or removal of user accounts - Successful and unsuccessful user authentication, including the identity associated with the authentication - Changes to smart-inverter configuration settings, including previous and new values and the identity of the user or system making changes to enabled/disabled features, assigned user roles, and role permissions - Enabling previously disabled features - Records of software and firmware updates, including how the update was initiated (e.g., by a user, automatically), the source of the update, and any update integrity information (e.g., checksums, hashes) - Communications events, such as network connections or loss of connectivity - Actions performed directly from the smartinverter's control panel As shown in Fig. 5, logging capabilities should be configured and enabled by the installer during solar energy system setup. During operations and maintenance, the owner or maintenance technician should verify that information is being collected and stored in logs as intended. Fig. 5. Guideline #3 life cycle phase <!-- image -->", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems."}]}
{"id": "nist_02582", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AU-2 in Hardware-Enabled Security_ Container Platform Security Prototype? (Part 5) Control AU-2: X | X | X | | | | | | | | | PR.IP-3 | | | | | | X | X | X | | | | | | | PR.IP-5 | | PR.IP-12 | | | | | | | | | | X | X | X | | | X | | X | | | | | X | X | X | | | | PR.PT-1 | | RS.MI-1 | | | | | | | | | | X | X | X | | | RS.MI-2 | | | | | | | | | | | X | X | | ## Appendix F-Acronyms and Other Abbreviations Selected acronyms and abbreviations used in the report are defined below.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Hardware-Enabled Security_ Container Platform Security Prototype."}]}
{"id": "nist_02583", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Personal Identity Verification (PIV) of Federal Employees and Contractors say about Match? According to Personal Identity Verification (PIV) of Federal Employees and Contractors, Match: . Comparison decision stating that the biometric probe(s) and the biometric reference are from the same source. Match is a possible result of a Comparison . The opposite of a match is a non-match. SOURCE: [ISO 2382-37, adapted]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Personal Identity Verification (PIV) of Federal Employees and Contractors."}]}
{"id": "nist_02584", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case provide? (Section 94) ct X Asset Criticality The resulting risk score (1 to 100) is then used for determining the overall risk level (adapted from NIST SP 800-30 30 ) which is utilize for prioritizing remediation efforts. | Risk Level | Description | Risk Score | |--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| | Very High | Very high risk means that the identified vulnerability could be expected to have multiple severe or catastrophic adverse effects on organizational operations, organizational assets, or individuals. | 96 to100 | | High | High risk means that the identified vulnerability could be expected to have a severe or catastrophic adverse effect on organizational operations, organizational assets, or individuals. | 80 to 95 | | Medium | Moderate risk means that the identified vulnerability could be expected to have a serious adverse effect on organizational operations, organizational assets, or individuals. | 21 to 79 | | Low | Low risk means that the identified vulnerability could be expected to have a limited adverse effect on organizational operations, organizational assets, or individuals. | 5 to 20 | | Very Low | Very low risk means that the identified vulnerability could be expected to have a negligible adverse effect on organizational operations, organizational assets, or individuals. | 0 to 4 | The resulting risk information is then entered into the risk management log for tracking and for coordinating remediation.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case."}]}
{"id": "nist_02585", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Study of OSI Key Management say about 9.8.1 Algorithm choice? According to A Study of OSI Key Management, 9.8.1 Algorithm choice: There are three different possibilities for two KMSAs to establish the algorithms to use: - The KMSAs have a priori agreements; - The KMSAs have prior agreements but need to initialize cryptographic variables; - The KMSAs negotiate about the algorithms to use. The protocol uses the Kirq and Kirs PDUs to establish the algorithms. ``` Kirq ::= SEQUENCE { protocolVersion ProtocolVersion, secServGrpProp [0] IMPLICIT SecServGrpProp OPTIONAL, keyEchGrpProp CHOICE { [1] IMPLICIT AsymmKeyExchGrpProp, [2] IMPLICrT SymmKeyExchGrpProp } OPTIONAL } ``` - Kirs ::= SEQUENCE { stateResult StateResult, protocolVersion ProtocolVersion, secServGipAcc [0] IMPLICIT SecServGrpAcc OPTIONAL keyEchGrpAcc CHOICE { [1] IMPLICIT AsyminKeyExchGipAcc, [2] IMPLICrr SymmKeyExchGrpAcc } OPTIONAL) SecServGrpProp ::= SEQUENCE { confAlgs SEQUENCE OF Algorithmidentifier, icvAlgs SEQUENCE OF Algorithmidentifier) SecServGrpAcc ::= SEQUENCE { confAlg Algorithmidentifier, icvAlg Algorithmidentifier) - AsymmKeyExchGrpProp ::= SEQUENCE { keyExchMethods SEQUENCE OF Algorithmidentifier - possibly more declarations have to be put in) AsymmKeyExchGrpAcc ::= SEQUENCE { keyExchMethod Algorithmidentifier - possibly more declarations have to be put in)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of OSI Key Management."}]}
{"id": "nist_02586", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Section 126) | x | | | CM-8(2) | System Component Inventory Automated Maintenance | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ TABLE C-5: IDENTIFICATION AND AUTHENTICATION REQUIREMENT MAPPINGS | | SECURITY REQUIREMENTS | Defense-in-Depth Protection Strategy | Defense-in-Depth Protection Strategy | Defense-in-Depth Protection Strategy | NIST SP 800-53 Relevant Security Controls | NIST SP 800-53 Relevant Security Controls | |--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------|---------------------------------------------|----------------------------------------------------------------------------------------------| | | | PRA | DLO | CRS | | | | 3.5.1e | Identify and authenticate [ Assignment: organization- defined systems and system components ] before establishing a network connection using bidirectional authentication that is cryptographically based and replay resistant.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_02587", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does U.S. Department of Justice Simplified Risk Analysis Guidelines say about 6. STEP 2. AIS SECURITY INFORMATION .? According to U.S. Department of Justice Simplified Risk Analysis Guidelines, 6. STEP 2. AIS SECURITY INFORMATION .: - a. In Step 2 of the risk analysis, security related information for the AIS or application is obtained and documented. The system security measures in effect are identified and documented with a brief evaluation of their effectiveness. Security measures are required even if nonsensitive information is processed to protect the equipment and integrity of the data. However, central to the determination of the need for additional security measures is the type of information processed, whether classified (National Security Information) , sensitive (Limited Official Use) or nonsensitive information, and the threats to this information. This information is important in determining which minimum security requirements are applicable. The Appendix contains a list of the factors that should be carefully considered during this step, including a list of security measures (Table 2) and application system data sensitivity and criticality considerations (Table 3 and Work Form 5) - 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. The information obtained during Step 2 should be documented using Work Forms 2, 3, 4, and 5. Additional information required by this step includes the number and geographical disparity of AIS users, the frequency of use of the system, and the method of accessing the system.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, national security. Contains guidance on protecting sensitive government information. Source: U.S. Department of Justice Simplified Risk Analysis Guidelines."}]}
{"id": "nist_02588", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification say about 4.8 Secret Shared Between Card Issuer and Physical Token? (Part 2) According to A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification, 4.8 Secret Shared Between Card Issuer and Physical Token: ings established by each of them and the primitive authentication mechanisms that verifies each of those bindings that are discussed in Sec. 4.2 through Sec. 4.8 above are summarized in Table 1 below. Table 1: Smart Card Objects, Bindings and Verifying Authentication Mechanisms | Card Object Name - Description | Binding Established/Embodied | Primitive Authentication Mechanism (verifying the bindings) | |-----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|------------------------------------------------------------------------------------------------| | Card Holder Unique Identifier (CHUID) Object- An Object containing the Unique Person Identifier that is usually digitally signed by the Card Issuer | Card Issuer - Person Identifier Binding (Strong) | PUM-1: Person Identifier's origin and integrity checked using its associated digital signature | | Card Authentication Certificate | Card Issuer - Token Secret | PUM-2.1 : Establishing Trust in | | Object - A digital certificate issued by a CA trusted by Card Issuer that attests to the presence of a cryptographic secret held by the token.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token, sso. Contains security framework guidance for authentication systems. Source: A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification."}]}
{"id": "nist_02589", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AN-2013 in Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet? (Part 169) Control AN-2013: | | | | subfield which contains a minimum of one information item. | 1 | 1.007-DAI- InfoItemCou nt | EQ ( Count(InfoItemsIn(SubFld(1.007.1))), Int(1) ) | | M-Fld(1.007) | | | | T | | RT1.39 - Fie | 8.1.7, | This mandatory field shall contain the | 1 | 1.007-DAI- | ReturnResult | | M-Fld(1.007) | | | | B | | Req. # - ID | Ref. in Base Std. | Requirement Summary | L e v e l | Assertion ID | Test Assertion | N o t e s | Imp.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet."}]}
{"id": "nist_02590", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NSTIC Pilots_ Catalyzing the Identity Ecosystem provide? (Section 56) er that promotes confidence, privacy, choice, and innovation. 67 See '2015-NIST=NSTIC-02,' Grants.gov, March 26, 2015, available at http://www.grants.gov/web/grants/view-opportunity.html?oppId=275464. AAAE American Association of Airport Executives AAMVA The American Association of Motor Vehicle Administrators ACT-IAC American Council for Technology - Industry Advisory Council AP Attribute provider AXN Attribute Exchange Network COI Community of interest COPPA Children's Online Privacy Protection Act COTS Commercial off the shelf CSDII The Cross Sector Digital Identity Initiative CSP Credential Service Provider DHS Department of Homeland Security DMV Department of Motor Vehicles FFO Federal funding opportunity FICAM Federal Identity and Access Management FIPS Federal information processing standards FNS Food and Nutrition Services FTC Federal Trade Commission FY Fiscal Year GP Guiding Principles GSA General Services Administration GTRI Georgia Tech Research Institute IDESG Identity Ecosystem Steering Group IDEF Identity Ecosystem Framework IdP Identity provider ITL Information Technology Laboratory KBA Knowledge-based authentication LoA Level of assurance MFA Multi-factor authentication NCRIC Northern California Regional Intelligence Center NIEF National Identity Exchange Federation NIST National Institute of Standards and Technology NSTIC National Strategy for Trusted Identities in Cyberspace NPO National Program Office OIDC OpenID Connect OMB Office of Management and Budget PDS Personal Data Store PIV Personal Identity Verification PKI Public key infrastructure PRIVO Privacy Vaults Online RNS Resilient Network Systems RP Relying party SAML Security Assertion Markup Language SCC Standards Coordination Committee SP Special Publication TFP Trust framework provider TFS Trust Framework Solutions TSCP Transglobal Secure Collaboration Participation, Inc.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, mfa. Contains security framework guidance for authentication systems. Source: NSTIC Pilots_ Catalyzing the Identity Ecosystem."}]}
{"id": "nist_02591", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PS-140 in Computer Security Division 2003 Annual Report? (Part 8) Control PS-140: Their IP-based infrastructures enable operators to control who can-and cannot-use the network. Another influential element in the ongoing Internet-telephony evolution is the VoIP gateway. As these gateways evolve from PC-based platforms to robust embedded systems, each will be able to handle hundreds of simultaneous calls. Consequently, corporations may deploy large numbers of them in an effort to reduce the expenses associated with high-volume voice, fax, and videoconferencing traffic. The economics of placing all trafficdata, voice, and video-over an IP-based network may pull companies in this direction, simply because IP will act as a unifying agent, regardless of the underlying architecture (i.e., leased lines, frame relay, or Asynchronous Transfer Mode (ATM)) of an organization's network. VoIP presents challenges from several dimensions. They are: the technology of call processing, a need to interface with legacy PBX (private branch exchange) systems, making the existing security solutions fit into the VoIP environment, and security for the new applications enabled by the switchover to VoIP from legacy voice systems. NIST is looking into security issues arising from each of these dimensions and plans to develop assurance metrics and testing methodologies for several VoIP configurations. To achieve these goals, we also plan to leverage the large knowledgebase already available for various types of attacks against IP components and entities like routers, web servers, domain name servers, and so on. Contact: Dr. Ramaswamy Chandramouli (301) 975-5013 chandramouli@nist.gov ## AUTOMATED SECURITY TESTING I ndependent security functional testing of a product is very rarely performed in many security evaluations due to cost and technical complexity, except in the case of high assurance products.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2003 Annual Report."}]}
{"id": "nist_02592", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AN-2011 in ANSI_NIST-ITL 1-2011 Requirements and Conformance Test Assertions? (Part 181) Control AN-2011: 11- Compressio n Algorithm Metadata 8.15.11, Table 69, 7.7.9.1 For each of these fields, the entry corresponds to the appropriate Label entry in Table 12: Field 15.011: Compression algorithm / CGA. 1 M 15.011-CGA {15.011} MO [ASCII(NONE, JPEGB, JPEGL, JP2, JP2L, PNG, WSQ)] 8.15.11, Table 69 <The CGA is verified by checking the image metadata for the compression type signature if compression is used.> 2 M IF {15.011} EQ ASCII(JPEGB) OR ASCII(JPEGL) THEN Present(SOI -JPEG,JPEGL) 15.011- CGAMetad ata JPEGB,JPEG L 2 M 15.011-CGA Metadata JP2, JP2L 2 M 15.011-CGA Metadata PNG IF {15.011} EQ ASCII(JP2) OR ASCII(JP2L) THEN Present(SigBox) IF {15.011} EQ ASCII(PNG) THEN Present(PNGSig) 2 M 15.011-CGA IF {15.011} EQ ASCII(WSQ20) THEN 142 t-12 t-11 t-12 t-11 t-12 t-98 t-11 t-11 t-11 t-11 B B B B B B B B B B Field: 15.012-Bits Per Pixel Value Field: 15.012- Bits Per Pixel Metadata 8.15.12, Table 69, 7.7.8.6 8.15.12, Table 69 This field shall contain an entry of \u201c8\u201d for normal grayscale values of \u201c0\u201d to \u201c255\u201d. Any entry in this field greater than \u201c8\u201d shall represent a grayscale pixel with increased proportion. <The BPX is verified by checking the image metadata for the compression type signature if compression is used.> Metadata WSQ Present(SOI-WSQ) M 15.012-BPX <See Requirement ID \u201cField: Image BPX Value\u201d > t-2 2 M 15.012-BPX Metadata JPEGB,JPEG L 2 M 15.012-BPX Metadata JP2, JP2L {15.012} EQ {BPX-JPEG, JPEGL} {15.012} EQ {BPX-JP2,JP2L} 2 M 15.012-BPX {15.012} EQ {BPX-PNG} Metadata PNG 15.012-BPX Metadata WSQ <Not Tested.> Field: 15.013- Friction Ridge Generalized Position Value Field: 15.014, 15.015- Reserved Field: 15.016- Scanned Horizontal Pixel Scale Value Field: 15.017- Scanned Vertical Pixel Scale Value Field: 15.018, 15.019- See Section 7.7.4.2 for details.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: ANSI_NIST-ITL 1-2011 Requirements and Conformance Test Assertions."}]}
{"id": "nist_02593", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is cpe according to Common Platform Enumeration_ Naming Specification Version 2.3? cpe: /a:hp:openview_network_manager:7.51::~~~linux~~", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Platform Enumeration_ Naming Specification Version 2.3."}]}
{"id": "nist_02594", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Status Report on the Second Round of the SHA-3 Cryptographic Hash Algorithm Competition say about TABLE OF CONTENTS? (Part 14) According to Status Report on the Second Round of the SHA-3 Cryptographic Hash Algorithm Competition, TABLE OF CONTENTS: | ....................................................................................................... 24 | | 4.14.2 | Performance................................................................................................ 24 | | 4.14.3 | Discussion................................................................................................... 24 | | Conclusion and the Final | Round................................................................................... 24 | References .............................................................................................................................. 25", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Second Round of the SHA-3 Cryptographic Hash Algorithm Competition."}]}
{"id": "nist_02595", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-16 in Assessing Security and Privacy Controls in Information Systems and Organizations? Control AC-16: SECURITY AND PRIVACY ATTRIBUTES", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_02596", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case say about Highlighted Performance Impacts? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case, Highlighted Performance Impacts: No performance measurement experiments were performed for the use of the Graylog due to its typical installation and usage location (i.e., external to the manufacturing system).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 \u2013 Process-based Manufacturing System Use Case."}]}
{"id": "nist_02597", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet provide? (Section 143) | | RT1.14 - Fie ld: 1.003- FRC-Value | 8.1.3 | The first information item (first record category code / FRC) within this subfield shall be '1'. This indicates that the first record in the transaction is a Type-1 record consisting of header information | 1 | 1.003-FRC- Value | EQ ( {InfoI(1.003.FRC)}, Int(1) ) | | M- InfoI(1.003.F RC) | | | | B | | RT1.15 - Fie ld: 1.003- FRC- CharType | 8.1, Table 22, 8 | Section 8.1 and Table 22 specify the Character Type for each field. Numeric values shall not contain leading zeros unless indicated by the standard text.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Conformance Testing Methodology Framework for ANSI_NIST-ITL 1-2011 Update_ 2013, Data Format for the Interchange of Fingerprint, Facial & Other Biomet."}]}
{"id": "nist_02598", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Benefits according to Security Guidance for First Responder Mobile and Wearable Devices? Benefits: Complete defense against wireless attacks may be a challenge to the public safety organization but utilizing the concepts of defense-in-depth, proper user training and situational awareness may greatly reduce the chances of a Wi-Fi attack. The benefits of user training also improve overall security posture within the public safety organization. Individuals that receive cybersecurity briefings often reconsider their actions when utilizing technology.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Guidance for First Responder Mobile and Wearable Devices."}]}
{"id": "nist_02599", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-09 in A Report on the Privilege (Access) Management Workshop? (Part 36) Control AM-09: ust be capable of enabling compliance with the Federal Information Security Management Act (FISMA), the Health Insurance Portability and Accountability Act (HIPAA), and Sarbanes Oxley (SOX) standards. - \uf0b7 The expression of policy in digital form must support reconciliation of policies in a federated environment. Federated organizations need to have the protections on their data enforced by member organizations that they share their data with. For example, a person might be disallowed from accessing the contents of a file by the owning organization, but might still be able to gain access to the file's contents indirectly through another organization unless policies have been reconciled. As noted earlier, XACML may fall short in this regard. Other languages, such as Attempto, Semantic Web, and RuleML should be assessed for their suitability to address the reconciliation issue. - \uf0b7 Harmonization of the attributes used in shared or intersecting policies among organizations may not be easy to achieve, or it may not be feasible to harmonize all of those attributes. Automated support for harmonization and a method for dealing with attributes that cannot be harmonized are needed. - \uf0b7 Federated data base management systems are within the state of the practice. In theory, they could provide capability for managing and accessing attributes at the enterprise level. However, their greater capabilities can involve high cost and complexity of administration and management. A product study would benefit organizations attempting to implement enterprise-level access control systems; the study should determine whether vendor offerings, such as federated directories, could directly meet the need. - \uf0b7 Research is needed to address the issues associated with multiple values of attributes having the same name. Although a complete solution may not be possible, improvements to the current situation should be possible.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: A Report on the Privilege (Access) Management Workshop."}]}
{"id": "nist_02600", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RA-5 in Automation Support for Security Control Assessments_ Software Vulnerability Management? (Part 20) Control RA-5: th [Assignment: organization-defined personnel or roles] to help eliminate similar vulnerabilities in other information systems related to this control item might be the cause of the defect; i.e., ... | |------------------------------|----------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | RA-5(e){1} | VUL-F01 | Vulnerable Software | \u2026the presence of software vulnerabilities (CVEs or equivalent). | | RA-5(e){1} | VUL-L01 | Poor coding practices | \u2026the presence of software with poor coding practices (CWEs or equivalent). | 32 As written, defect checks VUL-F01 and VUL-L01 assume that there is an automated dashboard to which personnel or roles designated for sharing vulnerability scanning information already have access. To be more thorough, the organization could verify that: 1) the dashboard displays scan results, 2) the organization-defined personnel or roles have access, and/or 3) the organization-defined personnel or roles are using the access. Such verifications could be done either manually or through automation, in each case by comparing what is desired (sharing information on vulnerability scan results with the organization-defined personnel or roles) to what is observed (whether the information is actually shared and reviewed by defined personnel or roles). ## 3.3.3.7 Control Item SI-2(a): FLAW REMEDIATION ## Control Item Text Control: The organization: - a.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Vulnerability Management."}]}
{"id": "nist_02601", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 7.2 User Authentication Tokens\" according to NIST Security for Dial-Up Lines According to Security for Dial-Up Lines, 7.2 User Authentication Tokens\": The first group of devices belonging to the two-end challenge-response approach perform highly secure authentication of system users. Ihe ten devices falling", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Security for Dial-Up Lines."}]}
{"id": "nist_02602", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Interfaces for Personal Identity Verification_ Part 1 \u2013 PIV Card Application Namespace, Data Model and Representation provide? (Section 41) V Card Application data object names in the CardApplicationURL in the CCC of the PIV Card Application, the NIST RID ('A0 00 00 03 08') SHALL be used and the card application type SHALL be set to '00'. Each of the data objects in the PIV Card Application has been provided with a BER-TLV tag and an ASN.1 OID from the NIST personal identity verification arc. These object identifier assignments are given in Table 3 . 10 The exception does not apply to the BIT Group template, the Discovery Object, or the Application Property Template (APT) since these objects use interindustry tags from ISO/IEC 7816-6. A data object SHALL be identified on the PIV client-application programming interface using its OID. An object identifier on the PIV client-application programming interface SHALL be a dotdelimited string of the integer components of the OID. For example, the representation of the OID of the CHUID on the PIV client-application programming interface is '2.16.840.1.101.3.7.2.48.0.' A data object SHALL be identified on the PIV Card Application card command interface using its BER-TLV tag. For example, the CHUID is identified on the card command interface to the PIV Card Application by the three-byte identifier '5FC102'. Table 2 lists the ACRs of the thirty-six PIV Card Application data objects. Table 3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interfaces for Personal Identity Verification_ Part 1 \u2013 PIV Card Application Namespace, Data Model and Representation."}]}
{"id": "nist_02603", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security provide? (Section 41) anaged only from trusted hosts by authorized administrators. VPN gateways and portals can run many services and applications, such as firewalls, antimalware software, and intrusion detection software. Organizations should carefully consider the security of any solutions that involve running a remote access server on the same host as other services and applications. Such solutions may offer benefits, such as equipment cost savings, but a compromise of any one of the services or applications could permit an attacker to compromise the entire remote access server. Placing the remote access server on a separate, dedicated host reduces the likelihood of a remote access server compromise and limits its potential impact. Using a separate host may also be advisable if the remote access server is likely to place other services and applications at significantly increased risk. An organization should also consider using multiple remote access solutions if its remote access users have vastly different security needs, such as one group accessing typical low-risk resources and another group accessing mission-critical confidential data. The security of stored data is another important consideration for remote access server security. For portal servers that may temporarily store sensitive user data, wiping such data from the server as soon as it is no longer needed can reduce the potential impact of a compromise of the server. The need to wipe sensitive data from remote access servers should be determined based on a risk assessment. Major factors organizations should consider when determining where to place a remote access server include the following: - \uf03c Device Performance. Remote access services can be computationally intensive, primarily because of encryption and decryption. Providing remote access services from a device that also provides other services may put too high of a load on the server during peak usage, causing service disruptions.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security."}]}
{"id": "nist_02604", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-03(06) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control CM-03(06): CONFIGURATION CHANGE CONTROL | CRYPTOGRAPHY MANAGEMENT ASSESSMENT OBJECTIVE: Determine if:", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_02605", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Interfaces for Personal Identity Verification_ Part 1 \u2013 PIV Card Application Namespace, Data Model and Representation say about Appendix C. PIV Algorithm Identifier Discovery? According to Interfaces for Personal Identity Verification_ Part 1 \u2013 PIV Card Application Namespace, Data Model and Representation, Appendix C. PIV Algorithm Identifier Discovery: Relying parties interact with many PIV Cards with the same native key type implemented by different key sizes and algorithms. 34 For example, a relying party performing the authentication mechanism described in Appendix B.1.2 CAN expect to perform a challenge and response cryptographic authentication with a 3072-bit or a 2048-bit RSA key or an ECDSA (Curve P-256 or Curve P-384) key. This appendix describes recommended procedures for key size and algorithm discovery (PIV algorithm ID discovery) to facilitate cryptographic authentication initiated by the relying party to make appropriate decisions for granting access to logical networks and systems as well as physical access control systems. The discovery procedure is defined in terms of asymmetric and symmetric cryptographic authentication.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Interfaces for Personal Identity Verification_ Part 1 \u2013 PIV Card Application Namespace, Data Model and Representation."}]}
{"id": "nist_02606", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Standard Security Label for GOSIP_ an Invitational Workshop provide? (Section 58) ntermediaries to validate that communications between two end systems is authorized. This decision is based on a combination of knowledge of the end systems and the values in the CLNP Security Option. [The Blacker Front End (BFE) is one example of such a trusted device.] These devices may receive CLNP PDUs which are in range for the intermediate device^ but are either not within the accredited range for the source or the destination. In the former case, \u00b7 the PDU should be treated as described in Paragraph 6.6. In the latter case, a CLNP Error Report PDU should be sent to the originating CLNP entity. The first octet of the Reason for Discard parameter should be set to 1101 0010. This code indicates to the originating CLNP entity that communication with the end system is administratively prohibited (refer to Table 6.1) The security range of the interface on which the reply will be sent determines whether a reply is allowed and at what security level it should be sent ( Presentation \"Security Labels at the Transport Layer' Slides) , Wayne A. Jansen (NIST) m t'ir- % i\u00bb :, - m ' a* -^-i' J A \u00ab 5 . ,^:^Ssit&lt;3 &gt; slM pm^ rf\u00ab'i 3\u00bb''&lt;)|iwii;iv 4 \u00bb' '\u2022\u2022t**,'\u00bb&gt;\u00bb '''-*^-'''!K 5fc i , , W'-: ^#is*s^iiir ^:T:W ' V:\u20ac'*:\"' i .'* J. J .:./\"T; 4i i-U' 'il^^fa-, c ^ CO?J Act ;jl\u00ab \\^\u00abn .' mtyit 1 * 01^15 uwp Id: % \u2022 1 **' int\u00abirae^laiXeMJi^' ,trid ' aysted^ iOt W^nwi^i %UCh ; A' rfi^-. Cup^tecijrity ^U '\u2022ruicfi ith*a r \\_\\_ aire rio;^^i '#^:fcin4\".' ^ tvr. \" TT&amp;iri'iS^'^ -\u00bbm0~ -s-pn, . ^ iragi ^ wl;, #til^i4 Th- hill \\_X. yJ - '5^:' 13}'' ^1i&lt;M3i ,^w' i B\u00abi'i v vi'. y 'V ' k;, : R\u00ab6:4 ^'.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Standard Security Label for GOSIP_ an Invitational Workshop."}]}
{"id": "nist_02607", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.6.3 Organization Identity Management Official (OIMO) according to NIST Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI) According to Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI), 2.6.3 Organization Identity Management Official (OIMO): The Organization Identity Management Official is responsible for implementing policies of the organization, assuring that all PIV processes of the issuer are being performed reliably, and providing guidance and assistance to the issuing facilities. The OIMO implements and manages the operations plan; ensures that all roles are filled with capable, trustworthy, knowledgeable, and trained staff; makes certain that all services, equipment, and processes meet FIPS 201-2 requirements; monitors and coordinates activities with Issuing Facility Manager(s); and supports the authorization process. 10 Organizations may define other significant roles (e.g., PIV System liaisons, operations managers) to support the authorization process.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, identity management. Contains security framework guidance for authentication systems. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_02608", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events say about 2.10 Semperis Directory Services Protector? According to Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events, 2.10 Semperis Directory Services Protector: This section details the installation of Semperis Directory Services Protector (DSP), a tool used for monitoring Active Directory environments. This installation requires both a copy of SQL Server Express as well as the Semperis Wizard. See the Semperis DS Protector v2.5 Technical Requirements document for specifics on the requirements. For a Windows Server 2012 R2 installation, simply meet the following requirements: - .NET Framework Version 3.5 SP1 - .NET Framework Version 4.5.2 or later - joined to the Active Directory domain it is protecting - either the installer for SQL Express Advanced or connection information and credentials for a full version of Microsoft SQL (MSSQL)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_02609", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain ENHANCED SECURITY REQUIREMENT according to NIST Assessing Enhanced Security Requirements for Controlled Unclassified Information According to Assessing Enhanced Security Requirements for Controlled Unclassified Information, ENHANCED SECURITY REQUIREMENT: Conduct [ Assignment: organization-defined enhanced personnel screening ] for individuals and reassess individual positions and access to CUI [ Assignment: organization-defined frequency ].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02610", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)? (Part 113) Control PD-12: | SP 800-79-2, Section 2.6 - Issuer Roles and Responsibilities | | IAT = Organizational Preparedness | IAT = Organizational Preparedness | IAT = Organizational Preparedness | IAT = Organizational Preparedness | |-------------------------------------|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------| | Authorization Focus Area | Identifier | Issuer Control | Source | | | RR-4 | The organization has appointed the role of Assessor.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_02611", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AU-2 in Security and Privacy Controls for Information Systems and Organizations? (Part 2) Control AU-2: emergency situations. Dynamic privilege management includes the effects of privilege changes, for example, when there are changes to encryption keys used for communications. Related Controls: AC-16. (7) ACCOUNT MANAGEMENT | PRIVILEGED USER ACCOUNTS (a) Establish and administer privileged user accounts in accordance with [Selection: a role- based access scheme; an attribute-based access scheme]; (b) Monitor privileged role or attribute assignments; (c) Monitor changes to roles or attributes; and (d) Revoke access when privileged role or attribute assignments are no longer appropriate. CHAPTER THREE PAGE 21 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 . I NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ Discussion: Privileged roles are organization-defined roles assigned to individuals that allow those individuals to perform certain security-relevant functions that ordinary users are not authorized to perform. Privileged roles include key management, account management, database administration, system and network administration, and web administration. A role-based access scheme organizes permitted system access and privileges into roles. In contrast, an attribute-based access scheme specifies allowed system access and privileges based on attributes. Related Controls: None. (8) ACCOUNT MANAGEMENT | DYNAMIC ACCOUNT MANAGEMENT Create, activate, manage, and deactivate [Assignment: organization-defined system accounts] dynamically.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02612", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Engineering Trustworthy Secure Systems say about E.5. Commensurate Rigor? According to Engineering Trustworthy Secure Systems, E.5. Commensurate Rigor: Principle: The rigor associated with the conduct of an engineering activity provides the confidence required to address the most significant adverse effect that can occur. Note: Rigor determines the scope, depth, and detail of an engineering activity. Rigor is a means of providing confidence in the results of a completed engineering activity. Generally, an increase in rigor translates to an increase in confidence in the results of the activity. Further, increased confidence reduces the uncertainty that can also reduce risk or provide a better understanding of what to address to achieve risk reduction. The relationship between rigor and the criticality of data and information used to make decisions is recognized by systems analysis practices [4]. The principle of commensurate rigor helps to ensure that the concept of rigor is included as an equal factor in the trade space of capability, adverse effect, cost, and schedule in the planning and conduct of engineering activities, method and tool selection, and personnel selection. An increase in rigor may translate into an increase in the cost of personnel, methods, and tools required to complete rigorous engineering activities or an increase in schedule to accomplish the activities with the expected rigor. Any increased cost that may occur can be justified by acquiring confidence about system performance to limit loss while also addressing the system's ability to deliver the capability. Therefore, the rigor associated with an engineering activity should be commensurate with the significance of the most adverse effect associated with the activity.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_02613", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Automation Support for Security Control Assessments_ Software Asset Management provide? (Section 150) included with other capabilities, as appropriate. The literal text of the control item follows the heading Control Item Text . There may be one or more determination statements for each control item. Each determination statement is documented in a table, noting the: - determination statement ID (Control Item ID concatenated with the Determination Statement Number, where Determination Number is enclosed in curly brackets); - determination statement text; - implemented by (responsibility); - assessment boundary; - assessment responsibility; - assessment method; - selected column (TBD by the organization); - rationale for risk acceptance (thresholds) (TBD by the organization); - frequency of assessment; 27 and - impact of not implementing the defect check (TBD by the organization). The determination statement details are followed by a table showing the defect checks (and related sub-capability) that might be caused to fail if the control being tested fails. The resulting text provides a template for the organization to edit, as described in Section 3.1. This section includes security control items selected in the SP 800-53 Low, Moderate, and High baselines and that support the SWAM capability. For convenience, the control items are presented in three sections as follows: - (1) Low Baseline Control Items (Section 3.3.3). Security control items in the low baseline, which are required for all systems. - (2) Moderate Baseline Control Items (Section 3.3.4). Security control items in the moderate baseline, which are also required for the high baseline. - (3) High Baseline Control Items (Section 3.3.5). Security control items that are required only for the high baseline. Table 7 illustrates the applicability of the security control items to each baseline. 27 While automated tools may be able to assess as frequently as every 3 to 4 days, organizations determine the appropriate assessment frequency in accordance with the ISCM strategy.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_02614", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Conformance Test for FDDI Medium Access Control (MAC) say about FDDI MAC Conformance Test TTCN Machine Processable Form? (Part 1) According to A Conformance Test for FDDI Medium Access Control (MAC), FDDI MAC Conformance Test TTCN Machine Processable Form: FDDI MAC Conformance Test TTCN Machine Processable Form ' I I i ) 1 r 1 I t if mfi c I * 1. f 4 f t *i HI B [S\\_X4 Iv I ^ cr J^&amp; i S ! 1 3 xlbrF^:\u00bbr\u00bb^. if'F'd! ; u 7 , 4 - san.iMiotnoC? iO^R j :3#2\u00abLaoor^'^mri3\u20aci^ ^ f I '^'' *0'J^ IriOTT ``` $Suite $SuiteIci FDDI $Begin_SuiteOverview $SuiteId FDDI $StanciardsRef FDDI MAC (X3T9 . 5/ 88-139 ) ; $PICSRef Test Suite for FDDI MAC Conformance Verification $PIXITRef Test Suite for FDDI MAC Conformance Verification $HowUsed Test Suite for FDDI MAC Conformance Verification $TestMethods The Remote Test Method $Comment Test Suite for FDDI MAC Conformance Verification $SuiteIndex $ Test Case Index $End_TestCaseIndex $TestStepIndex $End_TestStepIndex $Defaultindex $End_Defaultindex $End_SuiteIndex $End_SuiteOverview $Declarations $UserTYPEdefs $Begin_TTCN_TYPEdef $TTCN_TYPEdef $UserTypeId Symbol $Base BITSTRING $TypeDef BITSTRING [5] $Comment The smallest signaling element used by MAC. $End_TTCN_TYPEdef $TTCN_TYPEdef $UserTypeId Sstring $Base BITSTRING $TypeDef ('llllO'B, 'OlOOl'B, 'lOlOO'B, 'lOlOl'B, 'OlOlO'B, 'OlOll'B, 'OlllO'B, 'Ollll'B, '1C $Comment Symbolstring (Sstring) is the TTCN new type defined by user. $End_TTCN_TYPEc $End_TTCN_TYPEdefs $End_UserTYPEdef $ Be gi n_TS_PARdc1 $TS_PARdcl $TS_PARid IUT_Address $TS_PARtype INTEGER $PICS_PIXIT $Comment The address of Station Under Test. $End_TS_PARdcl $TS_PARdcl $TS_PARid Tester_Address $TS_PARtype INTEGER $PICS_PIXIT $Comment The address of Tester. Get this value from Tester. $End_TS_PARdcl $TS_PARdcl $TS_PARid TTRT $TS_PARtype INTEGER (4000 TO 167772) $PICS_PIXIT $Comment The operative Target Token Rotation Time. $End_TS_PARdcl $TS_PARdcl $TS_PARid T_Req_Tester $TS_PARtype INTEGER (4000 TO 167772) $PICS_PIXIT $Comment Tester's Requested TTRT. $End_TS_PARdcl $TS_PARdcl $TS_PARid T_Req_IUT $TS_PARtype INTEGER (4000 TO 167772) $PICS_PIXIT $Comment lUT' s Requested TTRT.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, token. Contains security framework guidance for authentication systems. Source: A Conformance Test for FDDI Medium Access Control (MAC)."}]}
{"id": "nist_02615", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments say about Table of Contents? (Part 9) According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments, Table of Contents: 1. Enterprise infrastructure layer for uniform policy deployment.......................................... | Fig. 1. Enterprise infrastructure layer for uniform policy deployment.......................................... | 7 | | Fig. 2. Flexibility provided by multi-tier policies .........................................................................10 | Fig. 2. Flexibility provided by multi-tier policies .........................................................................10 | | | Fig. 3. Multi-tier Policies for a Hybrid Application Environment .................................................13 | Fig. 3. Multi-tier Policies for a Hybrid Application Environment .................................................13 | | | Fig. 4. An Istio Authorization Policy that allows Service 1 to Service 2 on port 443 but only allows it to execute the GET HTTP verb on the '/public' path........................................15 Fig. 5.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments."}]}
{"id": "nist_02616", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Index of Automated System Design Requirements as Derived from the OMB Privacy Act Implementation Guidelines say about Foreword? (Part 105) According to Index of Automated System Design Requirements as Derived from the OMB Privacy Act Implementation Guidelines, Foreword: ming Organ. Report No. - y. rcKrUKMllNU UK(jAIN i/.A 1 1(JIN MAMt AND AUUKboo NATIONAL BUREAU OF STANDARDS DEPARTMENT OF COMMERCE WASHINGTON, D.C. 20234 10. Project/Task/Work Unit No. 600 1101 11. Contract/Grant .No. 0^1 ce of ADP Standards Managemerrt^ InH^tute for Computer Sclerveef^d Technology NationS'K&amp;uxiiea.u-ef-^SnHar^ Washington, D.C. 20234 13. Type of Report &amp; Period Covered Final - 14, Sponsoring Agency Code 15. SUPPLEMENTARY NOTES 16. ABSTRACT (A 200-word or less factual summary of most sigrtificant information. If document includes a significant bibliography or literature survey, mention it here.) This 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. 17. KEY WORDS (six to twelve entries; alphabetical order; capitalize only the first letter of the first key word unless a proper name; separated by semicolons Computer; data processing/ index; information processing; privacy; requirements definition; systems design; security 18. AVAILABILITY Unlimited r~! For Official Distribution. Do Not Release to NTIS I ! Order From Sup. of Doc, U.S. Government Printing Office Washington, D.C. 20402, SD Cat. No. CU I Order From National Technical Information Service (NTIS) Springfield, Virginia 22151 19. SECURITY CLASS (THIS REPORT) UNCL ASSIFIED 20. SECURITY CLASS (THIS PAGE) UNCLASSIFIED 21. NO.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Index of Automated System Design Requirements as Derived from the OMB Privacy Act Implementation Guidelines."}]}
{"id": "nist_02617", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Attribute-based Access Control for Microservices-based Applications using a Service Mesh provide? (Section 63) (2017) Linear Time Algorithms to Restrict Insider Access using Multi-Policy Access Control Systems. Journal of Wireless Mobile - Networks, Ubiquitous Computing, and Dependable Applications 8(1):4-25. https://doi.org/10.22667/JOWUA.2017.03.31.004 - [13] Ferraiolo D, Chandramouli R, Hu V, Kuhn R (2016) A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications: Extensible Access Control Markup Language (XACML) and Next Generation Access Control (NGAC) (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-204A. https://doi.org/10.6028/NIST.SP.800-178 - [14] Agarwal G (2020) Enable Mutual TLS Authentication between your Kubernetes Workloads Using Istio (Medium.com). Available at https://medium.com/betterprogramming/enable-mutual-tls-authentication-between-your-kubernetes-workloadsusing-istio-65338c8adf82 - [15] Envoy (2021) External Authorization . Available at \\_filter#arch-overview-ext-authz - [16] Envoy (2021) JWT Authentication . Available at n\\_filter#config-http-filters-jwt-authn - [17] Hu VC, Ferraiolo DF, Kuhn DR, Schnitzer A, Sandlin K, Miller R, Scarfone K (2014) Guide to Attribute Based Access Control (ABAC) Definitions and Considerations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800162.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Attribute-based Access Control for Microservices-based Applications using a Service Mesh."}]}
{"id": "nist_02618", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 1 \u2013 General say about 8.3.1 Key Archive and Key Recovery Functions? (Part 2) According to Recommendation for Key Management_ Part 1 \u2013 General, 8.3.1 Key Archive and Key Recovery Functions: rior to the end of the key's cryptoperiod. For example, it may be prudent to archive the key when it is activated. When no longer required, the key shall be destroyed in accordance with Section 8.3.4. The confidentiality of archived key information is provided by an archive-encryption key (one or more encryption keys that are used exclusively for the encryption of archived key information), by another key that has been archived, or by a key that may be derived from an archived key. Note that the algorithm with which the archive-encryption key is used may also provide integrity protection for the encrypted information. When the archive-encryption key and its associated algorithm do not also provide integrity protection for the encrypted information, integrity protection shall be provided by a separate archive-integrity key (i.e., one or more authentication or digital-signature keys that are used exclusively for the archive) or by another key that has been archived. When the confidentiality and integrity protection of the archived key information are provided using separate processes, the archive-encryption key and archive-integrity key shall be different from each other (e.g., independently generated) and shall be protected in the same manner as their key type (see Section 6.1.1). Note that these two services could also be provided using authenticated encryption, which uses a single cryptographic algorithm operation and a single key. Tables 9 and 10 indicate the appropriateness of archiving keys and other cryptographically related information. An 'OK' in column 2 (Archive?) indicates that archiving is permissible but not necessarily required. Column 3 (Retention period) indicates the minimum time that the key should be retained in the archive. Additional advice on the storage of keying material in archive storage is provided in Appendix B.3.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02619", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems say about Table of Contents? (Part 10) According to A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems, Table of Contents: | Public Registries and Reputation Management Implications ........................ | Public Registries and Reputation Management Implications ........................ | 27 | | 4.6 | System Governance ..................................................................................... | System Governance .....................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems."}]}
{"id": "nist_02620", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations say about (3) CONTINUOUS MONITORING | TREND ANALYSES? According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, (3) CONTINUOUS MONITORING | TREND ANALYSES: Supplemental C-SCRM Guidance: The information gathered during continuous monitoring/trend analyses serves as input into C-SCRM decisions, including criticality analysis, vulnerability and threat analysis, and risk assessments. It also provides information that can be used in incident response and potentially identify a supply chain cybersecurity compromise, including an insider threat. Level(s): 3", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, incident response. Contains technical security guidance that could inform defensive posture. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_02621", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Symmetric Key Injection onto Smart Cards provide? (Section 21) ard holder, verification of MAC KPACS ensures that the session key was created by the smart card and not by a separate device, such as a desktop computer, that is under the control of the card holder. Second, when combined with the validation of the PACS's key management certificate and the verification that the key management key used by the smart card to encrypt the session key is the same as the public key in the PACS's key management certificate, the CMS helps to protect against man-in-the-middle attacks. This section presents an alternative key injection protocol, which differs from the protocol presented in Section 5 in that the PIV Card does not connect to the PACS prior to connecting with its CMS. The result of this difference is that the PACS cannot authenticate the PIV Card at all and so must completely rely on the PIV Card's CMS to ensure that symmetric key that it provides can only be obtained by the PIV Card. 1. The card holder connects to the CMS over a two-way authenticated TLS session in which client authentication is performed using the PIV Authentication key from the PIV Card. 2. The PIV Card's CMS establishes a two-way authenticated TLS session with the PACS. 3. The CMS obtains the PACS's RSA key management certificate, validates it, and then sends the public key from the certificate, KKM,PACS , to the PIV Card. 4. PIV Card generates a random session key, Ks , and a nonce, Ns . 3 5. PIV Card sends the following data to the CMS: - a. encrypted session key and nonce: ( Ks || Ns ) KKM,PACS . - b. MAC KPACS = MAC[ KCM , ( Ks || Ns ) KKM,PACS || KKM,PACS ], where KCM is the symmetric card management key that the PIV Card shares with its CMS. 6. The CMS verifies that Ks and Ns were created by the PIV Card and that the PIV Card used the correct key to encrypt Ks and Ns by verifying that MAC[ KCM , ( Ks || Ns ) KKM,PACS || KKM,PACS ] = MAC KPACS . 7. The CMS sends the following data to the PACS over the TLS protected channel: - a.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Symmetric Key Injection onto Smart Cards."}]}
{"id": "nist_02622", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CA-7 in A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)? (Part 14) Control CA-7: ange a key and its metadata without violating (or altering) either domain's FCKMS security policy. | | Component | Any hardware, software, and/or firmware required to construct a CKMS. | |--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Compromise (noun) | The unauthorized disclosure, modification, substitution, or use of sensitive data (e.g., keys, metadata, or other security-related information) or the unauthorized modification of a security- related system, device or process in order to gain unauthorized access. | | Compromise (verb) | To reduce the trust associated with a key, its metadata, a system, device or process. | | Compromise recovery | The procedures and processes of restoring a system, device or process that has been compromised back to a secure or trusted state, including destroying compromised keys, replacing compromised keys (as needed), and verifying the secure state of the recovered system. | | Compromised state | A lifecycle state for a key that is known or suspected of being known by an unauthorized entity. | | Computer Security Policy | The high-level policy for the security services that are to be supported by a computer for protecting its applications, stored data, and communications, and the rules to be followed in verifying user identities and authorizing their requests before they are granted. | | Confidentiality | The property that sensitive information is not disclosed to unauthorized entities. | | Configurable | A characteristic of a system, device, or software that allows it to be changed by an entity authorized to select or reject specific capabilities to be included in an operational, configured version.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)."}]}
{"id": "nist_02623", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessment of Access Control Systems say about 1.1 Authority? According to Assessment of Access Control Systems, 1.1 Authority: The National Institute of Standards and Technology (NIST) developed this document in furtherance of its statutory responsibilities under the Federal Information Security Management Act (FISMA) of 2002, Public Law 107-347. NIST is responsible for developing standards and guidelines, including minimum requirements, for providing adequate information security for all agency operations and assets, but such standards and guidelines shall not apply to national security systems. This document 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: Assessment of Access Control Systems."}]}
{"id": "nist_02624", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-384 in NIST Test Personal Identity Verification (PIV) Cards Version 2? (Part 13) Control HA-384: [NISTIR7870] | Cooper DA (2012) NIST Test Personal Identity Verification (PIV) Cards. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 7870. https://doi.org/10.6028/NIST.IR.7870 | | [PIV-I] | Federal PKI Certificate Policy Authority (2018) X.509 Certificate and Certificate Revocation List (CRL) Extensions Profile for Personal Identity Verification Interoperable (PIV-I) Cards. Available at: x509-cert-profiles-pivi.pdf | | [RFC4556] | Zhu L, Tung B (2006) Public Key Cryptography for Initial Authentication in Kerberos (PKINIT). (Internet Engineering Task Force (IETF) Network Working Group), IETF Request for Comments (RFC) 4556. https://doi.org/ 10.17487/RFC4556 | | [SP800-73] | Cooper DA, Ferraiolo H, Mehta KL, Francomacaro S, Chandramouli R, Mohler J (2015) Interfaces for Personal Identity Verification. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-73-4, Includes updates as of February 8, 2016. https://doi.org/10.6028/NIST.SP.800-73-4 | | [SP800-76] | Grother PJ, Salamon WJ, Chandramouli R (2013) Biometric Specifications for Personal Identity Verification. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-76-2. https://doi.org/10.6028/NIST.SP.800-76-2 | | [SP800-78] | Polk WT, Dodson DF, Burr WE, Ferraiolo H, Cooper DA (2015) Cryptographic Algorithms and Key Sizes for Personal Identity Verification. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-78-4.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_02625", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Weaknesses: according to NIST Guidelines for Securing Radio Frequency Identification (RFID) Systems According to Guidelines for Securing Radio Frequency Identification (RFID) Systems, Weaknesses:: - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; A system of digital signatures requires a public key infrastructure (PKI), including registration and certification authorities, revocation functions, and associated policies and practice statements. Successfully implementing and operating a PKI requires careful planning and considerable expertise. In addition, readers or middleware need to support digital signature and other PKI functionality that is not commonly found in current RFID technology. - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Digital signatures systems require more memory than found on many current tags. For example, NIST recommends that RSA signatures have a length of 1024 bits, and a length of 2048 bits after 2010. 55 Additional memory is required to store identifying information related to the transaction. Providing chain of custody evidence requires storing a digital signature and related identifying information for each transaction. 55 Elliptic curve cryptography can reduce the size of signatures. Elliptic curve methods provide comparable assurance to 1024bit RSA signatures with 163 bits, and to 2048-bit RSA signatures with 224 bits. This approach combined with greater memory on tags may alleviate storage concerns over time. - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; Digital signatures that are not generated by the tag are subject to replay attacks. An adversary could query a tag to obtain its evidence of authenticity (i.e., the digital signature created by a previous reader) and then replicate that data on a cloned tag. - GLYPH&lt;c=31,font=/MCAMJE+Webdings&gt; The use of digital signatures to support authentication of readers to tags would require tags to support relatively complex cryptographic functions beyond the capacity of most common tag designs. Consequently, password or symmetric key authentication systems likely will support tag access control, as opposed to tag authenticity verification, for the foreseeable future.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, pki. Contains security framework guidance for authentication systems. Source: Guidelines for Securing Radio Frequency Identification (RFID) Systems."}]}
{"id": "nist_02626", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report) say about APPENDIX G APPLICABLE LAWS AND REGULATIONS AS REPORTED BY CSPPs? (Part 4) 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), APPENDIX G APPLICABLE LAWS AND REGULATIONS AS REPORTED BY CSPPs: ry Flexibility Act Resource Planning Act Right to Financial Privacy Act Securities Act of 1933 Securities Exchange Act of 1934 Small Business Act Social Security Act Supp. for Pollution Abatement Sur. Mining Cont & Reclam Act Tariff act of 1930 Tax Reform Act The Staggers Act of 1975 Toxic Substances Control Act Trade and Tariff act of 1984 Trade agreements act of 1979 Trade Secrets Act of 1905 Trade Act of 1974 Traffic Act of 1930 Treasury Rules and Regs Treaty on Narcotic Drugs Trust Indenture Act of 1939 US Grain Standards Act USDA ADP Security Manual VA ADP Policies and Handbooks Welfare Laws Wire & Ele Com Interception Witness Security Reform Act of 1984. Witness Protection Act 10 USC 60 12 USC 95a, 22 USC 5315 13 USC (Nat. sec. Info.) 15 USC 1151-1157 15 USC 176a 18 CFR 128, 161, 250, 284, 18 USC 1906 18 USC 2351 18 USC 2510 18 USC 1902 18 CFR 35.13, 270, 273, 18 CFR 154.38, 154.63, 521 18 CFR 157, 260, 385, 388 18 USC 1030 ``` ``` 154.310 18 USC 2071 18 USC 1905, 1906 18 USC 641 18 USC 1343 18 USC 3500, 3521 18 USC 751-75 18 CFR 11, 154.301, 18 USC 1030(A)(4) 18 USC 2511 26 USC 6103 28 USC 569. 31 USC 5311 35 USC Sec. 181-188 36 CFR Subchapter E 38 USC 4 CFR 81, 83 40 USC 483(b) 44 CFR Chapter 22 44 USC 3501 44 USC Section 3508 44 USC 3501-3520 49 CFR Part 12, 44 5 USC 301 5 CFR Part 351 MP-1, MP-2, MP-3, MP-4 MP-1-76, MP-6 MP1 PT1 5 MPl PT2 13 NMI 1382.17 NMI 1382. 17B NMI 1620.7 NMI 2410. 7A NCSC 11 NSDD 145 NSDD 97 NTIS #2 NTISS # 2 NTISS # 200 NTISS 3005 NTISSP 2, 200 , MP-5 ```", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)."}]}
{"id": "nist_02627", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SR-12 in NIST_SP_800-53r5_Security_Privacy_Controls? (Part 47) Control SR-12: ntrol inheritance Augmentation of a security or privacy control to build in additional but related functionality to the control, increase the strength of the control, or add assurance to the control. A situation in which a system or application receives protection from security or privacy controls (or portions of controls) that are developed, implemented, assessed, authorized, and monitored by entities other than those responsible for the system or application; entities either internal or external to the organization where the system or application resides. See common control. control parameter See organization-defined control parameter. controlled area controlled interface Any area or space for which an organization has confidence that the physical and procedural protections provided are sufficient to meet the requirements established for protecting the information and/or information system. An interface to a system with a set of mechanisms that enforces the security policies and controls the flow of information between connected systems. APPENDIX A PAGE 399 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ controlled unclassified information [32 CFR 2002] counterfeit [SP 800-161] countermeasures [FIPS 200] covert channel [CNSSI 4009] Information that the Government creates or possesses, or that an entity creates or possesses for or on behalf of the Government, that a law, regulation, or Government-wide policy requires or permits an agency to handle using safeguarding or dissemination controls.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02628", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2015 Annual Report say about Small and Medium Size Business (SMB) Cybersecurity Workshop Outreach? (Part 2) According to Computer Security Division 2015 Annual Report, Small and Medium Size Business (SMB) Cybersecurity Workshop Outreach: overview of cybersecurity threats, vulnerabilities, and corresponding protective tools and techniques, with a special emphasis on information that small business personnel can apply directly. In FY 2015, six SMB outreach workshops were provided in Reno, Nevada; Fresno, California; Modesto, California; Fairmont, West Virginia; Pittsburgh, Pennsylvania; and McHenry, Maryland. Additionally, the SMB Cybersecurity Outreach Program was briefed to the InfraGard National Congress. In collaboration with the SBA and the FBI, planning is underway to identify locations and plan cybersecurity workshops in FY 2016.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2015 Annual Report."}]}
{"id": "nist_02629", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers provide? (Section 117) they need to replicate the multifactor authentication (MFA) for electronic commerce (e-commerce) example implementations. These reference designs are modular and can be deployed in whole or in parts. This guide contains three volumes: - \uf0a7 NIST SP 1800-17A: Executive Summary - \uf0a7 NIST SP 1800-17B: Approach, Architecture, and Security Characteristics - what we built and why - \uf0a7 NIST SP 1800-17C: How-To Guides - instructions for building the example implementations (you are here) Depending on your role in your organization, you might use this guide in different ways: Business decision makers, including chief security and technology officers, will be interested in the Executive Summary , NIST SP 1800-17A , which describes the following topics: - \uf0a7 challenges that enterprises face in implementing MFA to reduce online fraud - \uf0a7 example implementations built at the NCCoE - \uf0a7 benefits of adopting one or more of these example implementations Technology or security program managers who are concerned with how to identify, understand, assess, and mitigate risk will be interested in NIST SP 1800-17B , which describes what we did and why. The following sections of Volume B will be of particular interest: - \uf0a7 Section 3.4, Risk Assessment, provides a description of the risk analysis we performed. - \uf0a7 Appendix A, Mapping to Cybersecurity Framework, maps NIST and consensus security references to the Cybersecurity Framework Subcategories that are addressed in this practice guide. Additionally, work roles in NIST SP 800-181, National Initiative for Cybersecurity Education \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ (NICE) Cybersecurity Workforce Framework that perform the tasks necessary to implement those cybersecurity Functions and Subcategories were identified.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, mfa. Contains security framework guidance for authentication systems. Source: Multifactor Authentication for E-Commerce_ Risk-Based, FIDO Universal Second Factor Implementations for Purchasers."}]}
{"id": "nist_02630", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Performance Assurance and Data Integrity Practices provide? (Section 59) to express the proportion of records in a given file likely to be read for processing in a given run. Expressed as a percentage of the records read divided by the total number of records in the file. Appi ication -An adjective, as in application program or application system, describing custom written code to fill a specific local information processing need. (Contrast with Software.) Binding -The process, performed during program preparation, where flexibility and ambiguity are systematically removed from a computer program until an executable object program results. Binding takes place in stages starting with the programmer's original conception of the problem solution through compilation, loading, and the dynamic setting of absolute actual machine addresses immediately prior to an instruction's execution. Different types of variables are bound at different stages along the spectrum of binding time. In general, earlier binding means less flexibility and more (machine) efficiency. Later binding means flexibility at the cost of machine cycles. (Note: Each instruction must be completely bound at the instant it is executed. Commercial -An adjective, as in commercial computer, meaning a system offered for sale and listed in the GSA catalog. Contrast with special purpose, custom hardware prepared for military, space, or special industrial purposes at negotiated prices. A commercial computer is capable of performing both business and engineering processes. In some segments of the computer community, the word commercial is used as an adjective to modify the phrase \"data processing\". In this context commercial data processing is used synonymously with business data processing, and in juxtaposition to scientific data processing. Throughout this report, the unadorned phrase \"data processing\" is used to denote all of these contexts and the word commercial is used to denote the manufacturer's stock price book offering.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Performance Assurance and Data Integrity Practices."}]}
{"id": "nist_02631", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Digital Identity Guidelines_ Federation and Assertions say about Table of Contents? (Part 3) According to Digital Identity Guidelines_ Federation and Assertions, Table of Contents: . . . . . . . . . . . . . . 13 | | | 3.3.1. | Trust Agreement Management . . . . . . . . . . . . . . . . . . 13 | | | 3.3.2. . . . . . . | Authorized Party . . . . . . . . . . . . . . . . . . . . 14 | | | 3.3.3. | Proxied Federation . . . . . . . . . . . . . . . . . . . . . . . . . 14 | | | 3.3.4. | Fulfilling Roles and Functions of a Federation Model . . . . . . . 16 | | 3.4. | Federated Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 17 | | | 3.4.1. | Pairwise Pseudonymous Identifiers (PPI) . . . . . . . . . . . . . 18 | | 3.5. | Trust Agreements . . . . . . . . . . | . . . . . . . . . . . . . . . . . . . 19 | | | 3.5.1. . | Bilateral Trust Agreements . . . . . . . . . . . . . . . . . . . . 22 | | | 3.5.2. | Multilateral Trust Agreements . . . . . . . . . . . . . . . . . . . 23 | | | 3.5.3. . . . | Redress Requirements . . . . . . . . . . . . . . . . . . . . 25 | | 3.6. | Identifiers and Cryptographic Key Management for CSPs, IdPs, and RPs | .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Digital Identity Guidelines_ Federation and Assertions."}]}
{"id": "nist_02632", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Profile for Liquefied Natural Gas say about Prioritized Cybersecurity Framework Categories by Mission Objective? (Part 4) According to Cybersecurity Framework Profile for Liquefied Natural Gas, Prioritized Cybersecurity Framework Categories by Mission Objective: ---| | RECOVER | | | Recovery Planning (RC.RP) | Table 10. Prioritized CSF Categories for Mission Objective-4: Monitor, Detect, and Respond to Anomalous Behavior. | Function | High Priority | Medium Priority | Starred Priority | |------------|------------------------------|---------------------------|---------------------------------------------------------| | IDENTIFY | | Asset Management (ID.AM) | | | PROTECT | | | Information Protection Processes and Procedures (PR.IP) | | DETECT | Anomalies and Events (DE.AE) | | | | RESPOND | | Response Planning (RS.RP) | | | RECOVER | | | Recovery Planning (RC.RP) | Table 11. Prioritized CSF Categories for Mission Objective-5: Safeguard the Environment.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, csf, fips. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Liquefied Natural Gas."}]}
{"id": "nist_02633", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AT-1 in Building a Cybersecurity and Privacy Learning Program? (Part 87) Control AT-1: and privacy-related assets. It often consists of instructor-led and online courses, exercises, or other methods that inform learners of the acceptable uses of and risks to the organization's systems. Note: This is referred to as 'literacy' training in the SP 800-53r5 [11] Awareness and Training (AT) control family. Also see training . ## certification A designation earned to ensure qualifications to perform a job or task. Often issued by a professional organization, industry vendor, or employer to signify an achievement following a course of study. ## Chief Artificial Intelligence Officer A senior executive responsible for coordinating their agency's use of artificial intelligence (AI), promoting AI innovation in their agency, and managing risks from their agency's use of AI. ## Chief Data Officer A senior executive responsible for the utilization and governance of data across the agency or organization. ## Chief Financial Officer A senior member responsible for managing the financial actions of an agency or organization. ## Chief Learning Officer A senior-level executive who oversees all learning and employee development programs within an agency or organization. ## Chief Privacy Officer A senior official designated by the head of each agency to have agency-wide responsibilities for privacy, including the implementation of privacy protections; compliance with federal laws, regulations, and policies related to privacy; the management of privacy risks at the agency; and a central policy-making role in the agency's development and evaluation of legislative, regulatory, and other policy proposals. ## competency An individual's ability to complete a task or tasks within the context of a work role. From OPM: 'A competency is a measurable pattern of knowledge, skills, abilities, behaviors, and other characteristics that an individual needs to perform work roles or occupational functions successfully.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, control family, security control. General security reference material without sensitive content. Source: Building a Cybersecurity and Privacy Learning Program."}]}
{"id": "nist_02634", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Smart Card Technology_ New Methods for Computer Access Control provide? (Section 52) , however, that the user may have to type at least two seven-digit numbers for each log-on procedure. NBS will continue researching improved computer security methods as new products become available. The prototype systems already implemented at NBS illustrate some access control techniques which are now technologically possible. What will be possible in terms of cost, efficiency, ease of use, and other practical issues, is yet to be determined. The smart card is still in a relatively early stage of development, and its technological, economic, and social impact has not yet been realized. As researchers continue to explore smart card integrated circuit technologies, financial and government organizations are initiating test trials and limited prototype systems in order to examine the practical applications of the smart card. In 1985, MasterCard International began a test project in which 70,000 customers in Maryland and Florida were issued smart cards. [GLZR 86, p. 34] The Agricultural Stabilization and Conservation Service of the U.S. Department of Agriculture has implemented a smart card program to enhance record-keeping for 56,000 American peanut farmers. [CASA2 87, p.34] Results of such projects have generally been positive; however, further study will be required before smart cards can be put into wider use in the U.S. The acceptability of smart cards to a diverse group of users and the costs associated with developing smart card systems are among the factors which still need to be considered. Smart cards have the potential for preventing tremendous financial losses due to weaknesses in current authentication and access control procedures. However, the initial costs of incorporating smart cards and their associated reader/writer devices into a security system is often an important concern. One source predicts that smart cards will undergo an immense growth in popularity and that manufacturers will \"tap the economy of scale of mass production.\" [SVGL 85, p.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, sso. Contains security framework guidance for authentication systems. Source: Smart Card Technology_ New Methods for Computer Access Control."}]}
{"id": "nist_02635", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Automation Support for Security Control Assessments_ Volume 1_ Overview provide? (Section 100) volumes explain the specific purposes to be achieved by each sub-capability and the supporting controls as the sub-capabilities and supporting controls relate to the capability covered in that volume. The defect checks are designed to provide a valid measure of whether (and to what extent) the purpose of the sub-capability is being achieved. The measures described previously are of little value unless the data collected are both complete and timely. The data quality checks use letter prefix \"Q\" in their ID code. Completeness means the extent to which the security-related information includes assessment of all relevant defects on all assessment objects (within a defined scope such as a capability). Relevant defects are defects that produce significant risk, e.g., the top two orders of magnitude. Incomplete metrics tend to bias the results by underestimating total risk. Timeliness means the extent to which the security-related information has been refreshed within the last X hours or days (as determined/required by the organization. Data must be collected (and defects mitigated) faster than the attacker(s) can act, in order to be able to stay ahead of their ability to compromise a system. 23 If metrics for completeness and timeliness are not adequate, the assessment is not reliable because the results may be inaccurate.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Volume 1_ Overview."}]}
{"id": "nist_02636", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EG-21 in Guidelines for Access Control System Evaluation Metrics? (Part 17) Control EG-21: authentication, entitlement, and attribute information | | Function | Authentication | | Provider/Specification | OASIS / OASIS Security Service(SAML) TC | | Format/Schema | XML | | SCA (Service Component Architecture) Policy Framework | SCA (Service Component Architecture) Policy Framework | | Description | Allows policies and policy subjects specified using WS-Policy, as well as with other policy languages to be associated with SCA components.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, sso. Contains security framework guidance for authentication systems. Source: Guidelines for Access Control System Evaluation Metrics."}]}
{"id": "nist_02637", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Securing Web Transactions_ TLS Server Certificate Management? (Part 221) Control HA-1: eliminating time-intensive replacement procedures and human error. This facilitates industry best practices such as short-lived certificates (usually 90-day validity or less) and regular key rotation. An organization's CertCentral account can have as many users as needed, with each one having assigned preset or customizable roles. A user can be limited to what certificates they can request (by certificate type/identity), for which legal organizations/divisions they can make requests, and whether they can approve requests on their own or require an administrator/other approval. This gives users control to issue and manage their own certificates without affecting operations of other divisions within the organization. CertCentral supports two-factor authentication and single sign-on, which are potential requirements for specific roles or users. Further capabilities and settings of CertCentral are described in the DigiCert Getting Started guide. ## 4.3.9 Load Balancer The architecture includes a load balancer that acts as a reverse proxy. It receives client requests at its front end and evenly distributes these requests across a group of back-end TLS servers, which all use the same TLS server certificate and private key. ## 4.3.9.1 F5 Networks BIG-IP Local Traffic Manager Businesses depend on applications. Whether the applications help connect businesses to their customers or help employees do their jobs, making these applications available and secure is the main goal. F5 BIG -IP LTM helps enterprises deliver their applications to users in a reliable, secure, and optimized way. It provides the extensibility and flexibility of application services, with the programmability enterprises need to manage their physical, virtual, and cloud infrastructure. With BIG -IP LTM, enterprises can simplify, automate, and customize applications quickly and predictably.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, single sign-on. Contains security framework guidance for authentication systems. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_02638", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance provide? (Section 32) ng private key. The issuer is known as a Certificate Authority (CA). In many cases, the CA will delegate responsibility for the verification of the subject's identity to a Registration Authority (RA). The certificate is used to distribute the user's public key to other interested parties, known as relying parties, since they rely on the assurances provided by the PKI and the certificate creation process. CAs generally issue a self-signed certificate called a root certificate (sometimes also called a trust anchor ); this is used by applications and protocols to validate the certificates issued by a CA. CA certificates play a key role in many protocols and applications, and are generally kept in what is often called a root certificate store . Much of the business of properly configuring applications and protocols consists of ensuring that only appropriate root certificates are loaded into the root certificate store. In Microsoft Windows operating systems, there are root certificate stores that are maintained by the operating system for various purposes 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. Some 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 6 The various Mozilla browsers and e-mail clients, and the Apache web servers are examples. Microsoft Internet Explorer, Outlook and Internet Information Server all use the Windows root certificate store; Apple Safari and Mail use the Keychain; and Mozilla Firefox, Thunderbird and SeaMonkey all have their own root certificate stores, and they also can share a root certificate store from Mozilla's Network Security Services (NSS) utility. Certificates are generally issued in accordance with a certificate policy .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, certificate authority, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance."}]}
{"id": "nist_02639", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control CM-6 in Security and Privacy Controls for Information Systems and Organizations? (Part 1) Control CM-6: CONFIGURATION SETTINGS Control: a. Establish and document configuration settings for components employed within the system that reflect the most restrictive mode consistent with operational requirements using [Assignment: organization-defined common secure configurations]; b. c. Implement the configuration settings; Identify, document, and approve any deviations from established configuration settings for [Assignment: organization-defined system components] based on [Assignment: organization- defined operational requirements]; and d. Monitor and control changes to the configuration settings in accordance with organizational policies and procedures. Discussion: Configuration settings are the parameters that can be changed in the hardware, software, or firmware components of the system that affect the security and privacy posture or functionality of the system. Information technology products for which configuration settings can be defined include mainframe computers, servers, workstations, operating systems, mobile devices, input/output devices, protocols, and applications. Parameters that impact the security posture of systems include registry settings; account, file, or directory permission settings; and settings for functions, protocols, ports, services, and remote connections. Privacy parameters are parameters impacting the privacy posture of systems, including the parameters required to satisfy other privacy controls. Privacy parameters include settings for access controls, data processing preferences, and processing and retention permissions. Organizations establish organization-wide configuration settings and subsequently derive specific configuration settings for systems. The established settings become part of the configuration baseline for the system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02640", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1. Maintain Personnel Safety according to NIST Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case, 1. Maintain Personnel Safety: - Safety Programmable Logic Controller (PLC) - The workcell has a safety-rated PLC to terminate operations when an emergency condition is detected. Industry standard emergency stop buttons and light curtains are used to protect operators from entering the work area while the workcell is active. Each station has the ability to send emergency stop commands to the safety PLC.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case."}]}
{"id": "nist_02641", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2 provide? (Section 32) accomplished irrespective of how references are made within a given component. The following is a stripped down example of the source data stream. The details are covered later in this specification. ``` <ds:data-stream-collection id=\"dsc1\" schematron-version=\"1.0\"> <ds:data-stream id=\"ds1\" scap-version=\"1.2\" use-case=\"CONFIGURATION\"> <ds:dictionaries> <ds:component-ref id=\"ref1\" xlink:href=\"#dict1\"> <cat:catalog> <cat:uri name=\"dict-oval.xml\" uri=\"#ref3\"/> </cat:catalog> </ds:component-ref> </ds:dictionaries> <ds:checklists> <ds:component-ref id=\"ref2\" xlink:href=\"#xccdf1\"> <cat:catalog> <cat:uri name=\"sample-oval.xml\" uri=\"#ref3\"/> ``` ``` </cat:catalog> </ds:component-ref> </ds:checklists> <ds:checks> <ds:component-ref id=\"ref3\" xlink:href=\"#oval1\"/> </ds:checks> </ds:data-stream> <ds:component id=\"xccdf1\"> <xccdf:Benchmark> <xccdf:Rule> <xccdf:check system=\"http://oval.mitre.org/XMLSchema/oval-definitions-5\"> <xccdf:check-content-ref href=\"sample-oval.xml\" name=\"oval:gov.nist:def:1\"/> </xccdf:check> </xccdf:Rule> </xccdf:Benchmark> </ds:component> <ds:component id=\"oval1\"> <oval-def:oval_definitions>...</oval-def:oval_definitions> </ds:component> <ds:component id=\"dict1\"> <cpe2-dict:cpe-list> <cpe2-dict:cpe-item name=\"cpe:/a:oracle:database_server:11.1.0.6.0::enterprise\"> <cpe2-dict:check href=\"dict-oval.xml\" system=\"http://oval.mitre.org/XMLSchema/oval-definitions-5> oval:gov.nist:def:2</cpe2-dict:check> <cpe2-dict-ext:cpe23-item name=\"cpe:2.3:a:oracle:database_server:11.1.0.6.0:-:-:-:enterprise:-:-:-\"/> </cpe2-dict:cpe-item> </cpe2-dict:cpe-list> </ds:component> </ds:data-stream-collection> ``` The design of the SCAP source data stream is important for the following reasons: 1. Individual components may be developed outside of an SCAP data stream where the binding to other components is not necessarily known at the time the component is created. 2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2."}]}
{"id": "nist_02642", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Digital Identity Guidelines provide? (Section 62) marily supports attribute exchange. Users have access to classified or highly sensitive information or services that could result in a breach that would constitute a major incident under OMB guidance. 37 NIST SP 800-63-4 July 2025 Digital Identity Guidelines Initial Assurance Level Selection 3.3.3. Organizations SHALL develop and document a process and governance model for selecting initial assurance levels and controls based on the potential impacts of failures in the digital identity system. The following subsections provide guidance on the major elements to consider in the process for selecting initial assurance levels. The overall impact level for each user group is used as the basis for selecting the initial assurance level and related technical and process controls for the online service under assessment based on the impacts of failures within the digital identity functions. The initial assurance levels and controls can be further assessed and tailored in the next step of the DIRM process. Although the initial impact assessment (see Sec. 3.2) and the combined impact level determination for each user group (see Sec. 3.2.4) do not differentiate between identity proofing, authentication, and federation risks, the selected initial xALs may still be different. For example, the initial impact assessment may be low impact and indicate IAL1 and FAL1 but may also determine that personal information is accessible and therefore requires AAL2. Similarly, the impact assessment may determine that no proofing is required, resulting in no IAL regardless of the baselines for authentication and federation. Further changes may result from the tailoring process as discussed in Step 4: Tailoring. The output of this step is a set of initial xALs that are applicable to the online service for each user group. Selecting Initial IAL 3.3.3.1. Before selecting an initial assurance level, RPs must determine whether identity proofing is needed for the users of their online services.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Digital Identity Guidelines."}]}
{"id": "nist_02643", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations say about 16. Key Management Appendix? (Part 1) According to Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations, 16. Key Management Appendix: 16. Key Management Appendix - The Identification of the Keying Material Manager : The keying material manager should report directly to the organization's chief executive officer, chief operations executive, or chief information systems officer. The keying material manager is a critical employee who should have capabilities and trustworthiness commensurate with its responsibility for maintaining the authority and integrity of all formal electronic transactions and the confidentiality of all information that is sufficiently sensitive to warrant cryptographic protection. - The Identification of the Management Entity(ies) Responsible for Certification Authority (CA) and Registration Authority (RA) Functions and Interactions: Where public key cryptography is employed, either the keying material manager or his/her immediate superior should be designated as the organization's manager responsible for CA and RA functions. This section shall include references to any cloud computing or other shared services employed. - The Identification of the Management Entity (ies) Responsible for Symmetric Key Center Functions and Interactions: Where a symmetric key center is employed, either the keying material manager or his/her immediate superior should be designated as the organization's manager responsible key center functions. This section shall include references to any cloud computing or other shared services employed - Key Management Organization: The identification of job titles, roles, and/or individuals responsible for the following functions: - a. Key generation or acquisition; - b. Agreements with partner organizations regarding the cross-certification of any PKI keying material or sharing of keying material between symmetric key centers; - c. Key establishment and revocation structure design and management; - d. Establishment of cryptoperiods; - e.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations."}]}
{"id": "nist_02644", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Enhanced Security Requirements for Controlled Unclassified Information say about GLOSSARY? (Part 5) According to Assessing Enhanced Security Requirements for Controlled Unclassified Information, GLOSSARY: irector of the Information Security Oversight Office (ISOO). | | CUI program [32 CFR 2002] | The executive branch-wide program to standardize CUI handling by all federal agencies. The program includes the rules, organization, and procedures for CUI, established by Executive Order 13556, 32 CFR Part 2002, and the CUI Registry. | | CUI registry [32 CFR 2002] | The online repository for all information, guidance, policy, and requirements on handling CUI, including everything issued by the CUI Executive Agent other than 32 CFR Part 2002. Among other information, the CUI Registry identifies all approved CUI categories and subcategories, provides general descriptions for each, identifies the basis for controls, establishes markings, and includes guidance on handling procedures. | | cyber-physical system | Interacting digital, analog, physical, and human components engineered for function through integrated physics and logic. | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | cyber resiliency [SP 800-160-2] | The ability to anticipate, withstand, recover from, and adapt to adverse conditions, stresses, attacks, or compromises on systems that use or are enabled by cyber resources. Cyber resiliency is intended to enable mission or business objectives that depend on cyber resources to be achieved in a contested cyber environment.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02645", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 750) ing toward utilizing IP-based transport protocols for energy utility information and operational services. As IP-based nodes propagate, more opportunities for exploitation by adversaries are evolving. If a network component can be probed and profiled as part of the smart grid or other critical infrastructures, it is most likely to be targeted for some form of intrusion by adversaries. This is especially relevant with the growing use of wireless IP communications. 8.6.6.2 DoS/DDoS Attacks Denial of Service and Distributed Denial of Service (DoS/DDoS) attacks have become an effective tool to take advantage of vulnerabilities. The attack objective is to take actions that deprive authorized individuals access to a system, its resources, information stored thereon, or the network to which it is connected. A simple DoS attack attempts to consume resources in a specific application, operating system, or specific protocols or services, or a particular vendor\u2019s implementation of any of these targets to deny access by legitimate users. It may also be used in conjunction with other actions (attacks) to gain unauthorized access to a system, resources, information, or network. The DDoS attack seeks to deplete resource capacity, such as bandwidth or processing power, in order to deny access to authorized users and can be levied against the infrastructure layer or the application layer. This technique utilizes a network of attack agents to amass a large, simultaneous assault of messages on the target. As with the DoS attack, DDoS may be combined with other techniques for malicious purposes. IP-based networks are vulnerable to other attacks due to deficiencies of underlying protocols and applications. A man-in-the-middle, session-based hijack, or other technique may accompany the DoS/DDoS attack to inflict further damage on the target.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02646", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974 say about Is Network Security Possible?? (Part 2) According to Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974, Is Network Security Possible?: em. This places a heavy burden on the overall security mechanisms to control the spread of information, or its misrouting to the wrong user. 4. The complexity vulnerability has already been mentioned. The more extensive the network, the greater the probability of system error and vulnerability to rational intrusion. 5. Another problem also refers to size and scope. It is virtually impossible to verify that any large software system is completely free of errors and anomalies. Also, the state of design is such that frequent changes to the system can be expected. Errors, compounded by frequent changes, can cause frightful security problems when multiplied over a large network, in which there are multitudes of large systems, all interconnected and reliant on another large system (the interfacing processors and communications protocol) to tie them all together. The obvious question is that with so much going against it, is there really any hope for adequate protection in such systems? As we shall explore, there is some hope not only in the future, but even now, with today's systems. Much of the hope depends on what the user or owner can do on his own. The first step toward achieving any kind of security in a resource shared system is to apply those principles of protection that would be normally put in a local, batch, stand-alone system. If the basic principles of physical and administrative security, as well as adequate audit trails and backup are followed, then the necessary groundwork will have been laid for implementation of protection throughout the network. It is imperative, however, that each location submit to the rudimentary standards of security. Such standards must be a top management concern, because nothing will defeat a security program faster than to have an independent and recalcitrant appendage off in the boondocks thumbing his nose at all the controls floating down from above.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974."}]}
{"id": "nist_02647", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Building a Cybersecurity and Privacy Learning Program say about competency? According to Building a Cybersecurity and Privacy Learning Program, competency: An individual's ability to complete a task or tasks within the context of a work role. From OPM: 'A competency is a measurable pattern of knowledge, skills, abilities, behaviors, and other characteristics that an individual needs to perform work roles or occupational functions successfully. Competencies specify the 'how' of performing job tasks, or what the person needs to do the job successfully.' [18]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Building a Cybersecurity and Privacy Learning Program."}]}
{"id": "nist_02648", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.1 Specification of Key-Derivation Functions according to NIST Recommendation for Key-Derivation Methods in Key-Establishment Schemes According to Recommendation for Key-Derivation Methods in Key-Establishment Schemes, 4.1 Specification of Key-Derivation Functions: A family of one-step key-derivation functions is specified as follows: ). Function call: KDM( Z , OtherInput", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key-Derivation Methods in Key-Establishment Schemes."}]}
{"id": "nist_02649", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Contingency Planning Guide for Federal Information Systems provide? (Section 95) nate site and with the backup media. Storing a copy of the plan at the alternate site ensures its availability and good condition in the event local plan copies cannot be accessed because of disaster. The ISCP Coordinator should maintain a record of copies of the plan and to whom they were distributed. Other information that should be stored with the plan includes contracts with vendors (SLAs and other contracts), software licenses, system user manuals, security manuals, and operating procedures. Changes made to the plan, strategies, and policies should be coordinated through the ISCP Coordinator, who should communicate changes to the representatives of associated plans or programs, as necessary. The ISCP Coordinator should record plan modifications using a record of changes, which lists the page number, change comment, and date of change. The record of changes, depicted in Table , should be integrated into the plan as discussed in Section 4.1. Table 3-7: Sample Record of Changes | Record of Changes | Record of Changes | Record of Changes | Record of Changes | |---------------------|---------------------|---------------------|---------------------| | Page # | Change Comment | Date of Change | Signature | The ISCP Coordinator should coordinate frequently with associated internal and external organizations and system POCs to ensure that impacts caused by changes within any organization will be reflected in the contingency plan. Strict version control must be maintained by requesting old plans or plan pages to be returned to the ISCP Coordinator in exchange for the new plan or plan pages. The ISCP Coordinator also should evaluate supporting information to ensure that the information is current and continues to meet system requirements adequately.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Contingency Planning Guide for Federal Information Systems."}]}
{"id": "nist_02650", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Study of Federal Agency Needs for Information Technology Security provide? (Section 92) nal wording of the candidate need and a rewording that might have avoided some possible confusion: Original version as it appeared in the agency security needs study: \"[PR], [S] satisfying national ! international criteria\" (Further Description: \"Products and systems satisfying national / international criteria for protection of data and systems and that address integrity and availability in addition to confidentiality'') \"[PR], [S], [TA] for trusted technology that consider a wider range of functionality appropriate for unclassified, sensitive systems than now covered in NSA's TCSEC (\"Orange Book\"), and which satisfy national ! international \"criteria\" (Further Description: \"Products, standards, and technical assistance for trusted technology that consider a wider range of functionality appropriate for unclassified, sensitive systems than now covered in NSA's Trusted Computer Systems Evaluation Criteria, \"Orange Book,\" (Le., for protections of data and systems that more directly address integrity and availability in addition to confidentiality), and which satisfy national ! international \"criteria.\" International computer security criteria is used to develop trusted IT products that can be used to help protect important information of the government, whether it is sensitive or classified. This type of criteria helps to broaden the market for these products making them more available to potential buyers. International criteria also increases the number of COTS products available for various computer security needs. \") The study team found lack of awareness of available help and resources to be a major Issue. It is an area that represents lost or untapped potential for federal agencies. While clearly there are not existing answers to many of the needs expressed, the study team came across many situations in which those interviewed were not aware of existing solutions, products, and answers.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of Federal Agency Needs for Information Technology Security."}]}
{"id": "nist_02651", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-224 in Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance? (Part 74) Control HA-224: s, remote execution of commands, forwarded TCP/IP connections, and forwarded X11 connections [X11] can be run simultaneously over an established SSH Transport Layer and User Authentication connection. ## 10.2 Security and Compliance Issues ## 10.2.1 TLP Issues ## 10.2.1.1 Algorithm Negotiation In this step of the TLP, the algorithms to be used for the key exchange (i.e., key agreement), public key authentication, data encryption and message authentication are selected. 1. The SSH server and client should choose the same NIST-approved cryptographic algorithms for both communication directions (data streams) for a particular cryptographic service. For example, the same encryption algorithm and MACgeneration algorithm should be used for both communication directions to provide confidentiality and integrity protection, respectively. Note: The cryptographic algorithms selected for use depend on the algorithms that are supported by both the server and the client, and by the client's preference levels for these algorithms in each of its algorithm lists offered in the negotiation; the client's preference level is indicated by the order in which the algorithms are listed. See [RFC 4253, Sec. 7.1] for the defined procedure for selecting the cryptographic algorithms. 2. Suite B cryptographic algorithms are recommended for use when supported by both the client and server systems. Suite B cryptographic algorithms are specified in [RFC 6239]. They are: 2. \uf0b7 Key agreement (key exchange): ecdh-sha2-nistp256 and ecdh-sha2-nistp384 (see Section 10.2.1.2). 3. \uf0b7 Public key algorithm (for server and client authentications): x509v3-ecdsasha2-nistp256 and x509v3-ecdsa-sha2-nistp384 (see Section 10.2.1.3). The public keys are conveyed in X.509 version 3 certificates. 4. \uf0b7 Encryption and MAC: AEAD\\_AES\\_128\\_GCM and AEAD\\_AES\\_256\\_GCM (see Sections 10.2.1.4 and 10.2.1.5).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance."}]}
{"id": "nist_02652", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Security Strategies for Microservices-based Application Systems provide? (Section 21) re features in many deployments. As already stated, many of these features can be implemented either stand-alone or bundled together in architectural frameworks such as an API gateway or service mesh. Even within the API gateway, these features can be implemented through service composition or direct implementation within the code base. These features include but are not limited to authentication, access control, service discovery, load balancing, response caching, applicationaware health checks, and monitoring [2]. A brief description of these features [5] includes: - Authentication and access control: Authentication and access policy may vary depending on the type of APIs exposed by microservices-some may be public APIs; some may be private APIs; and some may be partner APIs, which are available only for business partners. - Service Discovery: In legacy distributed systems, there are multiple services configured to operate at designated locations (IP address and port number). In the microservicesbased application, the following scenario exists and calls for a robust service discovery mechanism: - a) There are a substantial number of services and many instances associated with each service with dynamically changing locations. - b) Each of the microservices may be implemented in VMs or as containers, which may be assigned dynamic IP addresses, especially when they are hosted in an Infrastructure as a Service (IAAS) or Software as a Service (SAAS) cloud service. - c) The number of instances associated with a service can vary based on the load fluctuations using features such as autoscaling. - Security monitoring and analytics - To detect attacks and identify factors for degradation of services (which may impact availability), it is necessary to monitor network traffic into and out of microservices with analytics capabilities in addition to routine logging features.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, sso. Contains security framework guidance for authentication systems. Source: Security Strategies for Microservices-based Application Systems."}]}
{"id": "nist_02653", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Acronyms according to NIST Assessing Information Security Continuous Monitoring (ISCM) Programs_ Developing an ISCM Program Assessment According to Assessing Information Security Continuous Monitoring (ISCM) Programs_ Developing an ISCM Program Assessment, Acronyms: Selected acronyms and abbreviations used in this publication are defined below. | AO | Authorizing Official | |--------|--------------------------------------------------| | CISA | Cybersecurity and Infrastructure Security Agency | | CISO | Chief Information Security Officer | | CIO | Chief Information Officer | | CSF | Cybersecurity Framework | | FISMA | Federal Information Security Modernization Act | | ISCM | Information Security Continuous Monitoring | | ISSO | Information System Security Officer | | NCCoE | National Cybersecurity Center of Excellence | | NIST | National Institute of Standards and Technology | | NISTIR | NIST Interagency or Internal Report | | RE(f) | Risk Executive (function) | | RMF | Risk Management Framework | | OA | Ongoing Authorization | | OMB | Office of Management and Budget | | SAISO | Senior Agency Information Security Officer | | SIEM | Security Information and Event Management | | SISO | Senior Information Security Officer |", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Assessing Information Security Continuous Monitoring (ISCM) Programs_ Developing an ISCM Program Assessment."}]}
{"id": "nist_02654", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SC-38 in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? (Part 2) Control SC-38: , and individuals that depend on systems containing cyber resources. This cyber risk arises in several ways. For example, cyber resources and the systems that incorporate those 104 See Section 2.1.3. APPENDIX C PAGE 82 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 1 6 0 v 2 r 1 I . NIST SP 800-160, VOL. 2, REV. 1 DEVELOPING CYBER-RESILIENT SYSTEMS _________________________________________________________________________________________________ resources are increasingly complex, so their behavior and properties in the presence of adversity (or even under expected levels of stress) can be difficult to predict. Software generally includes vulnerabilities and weaknesses, which can make it fragile and subject to exploitation by an adversary. Additionally, the presence of resources in cyberspace exposes them to cyber- attacks.105 Cyber resiliency solutions are intended to reduce the risk of depending on systems that contain cyber resources by reducing the extent of the harm from threat events,106 the likelihood of the occurrence of threat events, and the likelihood that threat events will cause harm.107 The risk model for cyber resiliency identifies the types of threat events and the classes of harm of interest to systems security engineers concerned with cyber resiliency. The extent of potential risk mitigation due to a cyber resiliency solution can be analyzed and assessed in the context of that risk model. The risk model for cyber resiliency builds on risk models for security, cybersecurity, resilience engineering, and survivability. However, the cyber resiliency risk model emphasizes the APT and the effects on missions and organizations of malicious cyber activities or of harm to systems that include cyber resources.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, adversary. Contains technical security guidance that could inform defensive posture. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_02655", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation provide? (Section 158) -----------------------------|----------------------|------------------| | CR-1.3 | | The advertised route is initially evaluated as valid . The single ROA that had made the route valid is removed from the RPKI. There is another ROA that covers the route, but its maximum prefix length is less than the prefix length of the route, so the route is re- evaluated as invalid . | | | | CR-1.3.1 | | | IPv4 address type | SIDR- ROV- 1.3.1 | | CR-1.3.2 | | | IPv6 address type | SIDR- ROV- 1.3.2 | | CR-1.4 | | The advertised route is initially evaluated as valid . An ROA that had made the route valid is removed from the RPKI; there remains another ROA that matches the route, so the route still evaluates as valid .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_02656", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to LTE Security say about 2 Overview of LTE Technology? (Part 2) According to Guide to LTE Security, 2 Overview of LTE Technology: development organization. Implementations of LTE networks are being deployed across the globe and installations continue to increase as the demand for high-speed mobile networks is constantly rising. Within Technical Specification (TS) 22.278 [9], 3GPP defines a number of high-level goals for LTE systems to meet, including: - Provide increased data speeds with decreased latency, - Build upon the security foundations of previous cellular systems, - Support interoperability between current and next generation cellular systems and other data networks, - Improve system performance while maintaining current quality of service, and - Maintain interoperability with legacy systems. The following sections explain the fundamental concepts of LTE technology and architecture, network protocols, and the evolution of the 3GPP security.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to LTE Security."}]}
{"id": "nist_02657", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Technology Assessment_ Methods for Measuring the Level of Computer Security provide? (Section 130) <!-- image --> | | | CONCLUSION | EXPLANATION AUDIT | | | |------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------------------------|------------|------------| | Nl | Assess the eiFectiTe- ness of the separation of the EDP depart- ment from non-com- patible functions within the organiza- tion, and of the segre- gation of duties within the EDP | | Compensating audit procedures | | | | S'1-1 | There is a separation of the functions of (i) initiation and authorization of transactions ; (ii) recording of transac- tions; and (Hi) cus- tody of assets. | | Verification techniques | | | | Nl-2 | Access to critical forms is restricted to individuals respon- sible for the initiation fi<nctwn. | | | | | | Nl-3 | Access to the com- puter and computer files and programs is restricted to desig- nated employees. | | | | | | | Other | | | | | | N2 | Assess the methods used to ensure that only authorized data is processed and that input documents bear evidence of authoriza- tion and are reviewed by the control group for such evidence.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Technology Assessment_ Methods for Measuring the Level of Computer Security."}]}
{"id": "nist_02658", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Considerations for Voice Over IP Systems say about A.3 Availability and Denial of Service? According to Security Considerations for Voice Over IP Systems, A.3 Availability and Denial of Service: Availability refers to the notion that information and services be available for use when needed. Availability is the most obvious risk for a switch. Attacks exploiting vulnerabilities in the switch software or protocols may lead to deterioration or even denial of service or functionality of the switch. For example: if unauthorized access can be established to any branch of the communication channel (such as a CCS link or a TCP/IP link), it may be possible to flood the link with bogus messages causing severe deterioration (possibly denial) of service. A voice over IP system may have additional vulnerabilities with Internet connections. Because intrusion detection systems fail to intercept a significant percentage of Internet based attacks, attackers may be able to bring down VOIP systems by exploiting weaknesses in Internet protocols and services. Any network may be vulnerable to denial of service attacks, simply by overloading the capacity of the system. With VOIP the problem may be especially severe, because of its sensitivity to packet loss or delay.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: exploit, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_02659", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Trustworthy Email provide? (Section 80) hing, spear phishing). | Loss of reputation, valid email from enterprise may be blocked as possible spam/phishing attack. | UBE and/or email containing malicious links or attachments may be delivered. Users may inadvertently divulge sensitive information or PII. | Deployment of domain-based authentication techniques (see Section 4). Use of digital signatures over email (see Section 6). DNS Blacklists (see Section 7). | | Email modified in transit. | Leak of sensitive information or PII. | Leak of sensitive information, altered message may contain malicious information. | Use of TLS to encrypt email transfer between servers (see Section 5). Use of end-to-end email encryption and/or digital signatures (see Section 7). Use of DKIM to id entify message mods (see Section 4.5). | | Disclosure of sensitive information (e.g., PII) via monitoring and capturing of email traffic . | Leak of sensitive information or PII. | Leak of sensitive information. | Use of TLS to encrypt email transfer between servers (see Section 5). Use of end-to-end email encryption (see Section 7). | | Disclosure of metadata of email messages. | Possible privacy violation. | Possible privacy violation. | Use of TLS to encrypt email transfer between servers (see Section 5).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Trustworthy Email."}]}
{"id": "nist_02660", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Security for Full Virtualization Technologies say about 5.3 Implementation? (Part 1) According to Guide to Security for Full Virtualization Technologies, 5.3 Implementation: 5.3 Implementation After the virtualization solution has been designed, the next step is to implement and test a prototype of the design before putting the solution into production. Aspects of the solution that should be evaluated include the following: - \uf06e Physical to Virtual Conversion. Existing servers and desktops may need to be migrated to guest OSs. Most hypervisors provide tools for doing this quickly and automatically. It is important to verify that the tools are compatible with the OSs running on the physical and the virtual machines. There 4 For more information on incident handling, see NIST SP 800-61 Revision 1, Computer Security Incident Handling Guide . may also be problems with loading the guest OS (e.g., boot device errors) or communicating properly with the hypervisor. - \uf06e Introspection. Determine whether the virtualization solution gives the necessary capability to monitor security events occurring within the guest OSs. If not, deploying additional security monitoring, such as with security devices, may need to be added and tested before the overall system is deployed. - \uf06e Authentication. Authentication is required at each of the appropriate solution layers and cannot be readily compromised or circumvented. If token-based authentication is needed in virtualized systems, test whether or not the tokens work in the emulated hardware. - \uf06e Connectivity. Users can connect to all of the resources that they are permitted to and cannot connect to any other resources. Each traffic flow is protected, if necessary, in accordance with the organization's established requirements. - \uf06e Applications. The virtualization solution does not interfere with the use of applications or servers within the guest OSs. - \uf06e Networking. The internal networking offered by the virtualization solution can be configured to conform to the organization's security policy. This includes the ability to monitor communications between guest OSs and to block particular types of traffic.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: Guide to Security for Full Virtualization Technologies."}]}
{"id": "nist_02661", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide for Security-Focused Configuration Management of Information Systems? (Part 115) Control ES-1: 800-167] | Sedgewick A, Souppaya MP, Scarfone KA (2015) Guide to Application Whitelisting. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-167. | | [SP 800-171] | Ross RS, Dempsey KL, Viscuso P, Riddle M, Guissanie G (2016) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-171, Rev. 1, Includes updates as of June 7, 2018. | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | [SP 800-171A] | Ross RS, Dempsey KL, Pillitteri VY (2018) Assessing Security Requirements for Controlled Unclassified Information. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-171A. | |-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [SP 800-175B] | Barker EB (2016) Guideline for Using Cryptographic Standards in the Federal Government: Cryptographic Mechanisms. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-175B.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Guide for Security-Focused Configuration Management of Information Systems."}]}
{"id": "nist_02662", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 1 \u2013 General say about 3 Security Services? According to Recommendation for Key Management_ Part 1 \u2013 General, 3 Security Services: Cryptography may be used to provide or support several basic security services: confidentiality, identity authentication, integrity authentication, source authentication, authorization, and nonrepudiation. These services may also be required to protect a key and other key information related to that key. In addition, there are other cryptographic and non-cryptographic mechanisms that are used to support these security services. In general, a single cryptographic mechanism may provide more than one service (e.g., the use of digital signatures can provide integrity authentication and source authentication) but not all services.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02663", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RC-20 in Blockchain Networks_ Token Design and Management Overview? (Part 42) Control RC-20: taries with a multi-signature contract. ## 4.2 Transaction Submission Transaction submission is either open to anyone or restricted to particular privileged users or roles via multilevel permissions. Access control can be implemented at the smart contract layer using conditions on function calls to accept or reject transactions according to protocol-defined rules or directly in the blockchain protocol at the base layer. As discussed in Section 2.1.3, token owners can give approvals and special authorizations to let other accounts submit transactions that directly affect their tokens. These authorizations can take the form of capability-based delegations to particular accounts or keys issued with specific usage conditions (e.g., spending limits). Such approval and authorization mechanisms can be used to implement payment requests, such as for pull payments and split payments , in which a group of users accepts a common payment request. Additionally, payment protocols can be designed to send payment acknowledgments and provide refund addresses [61]. Note that off-chain messaging schemes are generally needed to enable incoming and outgoing payment notifications. ## 4.2.1 Meta Transactions Signing transactions is free but submitting and broadcasting them on the blockchain can involve fees or tips with users bidding for storage (i.e., to get their transactions included on the blockchain). Those fees can depend on how data intensive transactions are. There may also be transaction fees at the smart contract layer, depending on the protocol. Meta transactions (or fee delegation ) make it possible for transaction fees to be paid by third parties on behalf of users. Similar to prepaid 'transaction envelopes,' this enables users to submit fee-free transactions . Thus, users do not have to own protocol-native tokens of a given token-based network to interact with it.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization, token. Contains security framework guidance for authentication systems. Source: Blockchain Networks_ Token Design and Management Overview."}]}
{"id": "nist_02664", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Summary according to NIST 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings According to 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings, Summary: The security design, implementation and deployment considerations of CDC's Public Health Information Network Messaging System (PHINMS) were discussed herein.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02665", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories say about 4.6 Uses of Categorization Information? (Part 1) According to Guide for Mapping Types of Information and Information Systems to Security Categories, 4.6 Uses of Categorization Information: 4.6 Uses of Categorization Information The results of system security categorization can and should be used by, or made available to, appropriate agency personnel to support agency activities including: - Business Impact Analysis (BIA): Agency personnel should consider the cross-utilization of security categorization and BIA information in the performance of each activity. Their common objectives enable agencies to mutually draw from them, thus, providing checks and balances to ensure accuracy for each information system. Conflicting information and anomalous conditions, such as a low availability impact and a BIA three-hour recovery time objective, should trigger a reevaluation by the mission and data owners. - Capital Planning and Investment Control (CPIC) and Enterprise Architecture (EA): Just as no IT investment should be made without a business-approved architecture, 21 the security categorization that begins the security life cycle is a business-enabling activity directly feeding the enterprise architecture and CPIC processes for new investments, as well as migration and upgrade decisions. Specifically, the security categorization can provide a firm basis for justifying certain capital expenditures and also can provide analytical input to avoid unnecessary investments. - System Design: Understanding and designing the system architecture with varying information sensitivity levels in mind may assist in achieving economies of scale with security services and protection through common security zones within the enterprise. For example, an information system containing privacy information may be located in one security zone with other information systems containing similar sensitive information. Each zone may have varying levels of security. For instance, the more critical zones may require 3-factor authentication where the open area may only require normal access controls.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: Guide for Mapping Types of Information and Information Systems to Security Categories."}]}
{"id": "nist_02666", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog say about (VMG) Vulnerability Management Options? (Part 5) According to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog, (VMG) Vulnerability Management Options: | | [FIPS-140] | National Institute of Standards and Technology (2002) Security Requirements for Cryptographic Modules. (U.S. Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) 140-3. https://doi.org/10.6028/NIST.FIPS.140-3 | | [FIPS-180] | National Institute of Standards and Technology (2015) Secure Hash Standard (SHS). (U.S. Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) 180-4. https://doi.org/10.6028/NIST.FIPS.180-4 | | [FIPS-201] | National Institute of Standards and Technology (2013) Personal Identity Verification (PIV) of Federal Employees and Contractors. (U.S. Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) 201-2. https://doi.org/10.6028/NIST.FIPS.201-2 | | [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, DC), Federal Information Processing Standards Publication (FIPS) 202.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog."}]}
{"id": "nist_02667", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments say about 1.4 Logical Architecture Summary? (Part 1) According to Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments, 1.4 Logical Architecture Summary: 1.4 Logical Architecture Summary At a high level, the trusted cloud architecture has three main pieces: a private cloud hosted at the NCCoE, an instance of the public IBM Cloud Secure Virtualization (ICSV), and an Internet Protocol Security (IPsec) virtual private network (VPN) that connects the two clouds to form a hybrid cloud. The private on-premises cloud at the NCCoE consists of the following components: - \uf0a7 Hardware Security Module (HSM) for storing keys by Gemalto - \uf0a7 server, storage, and networking hardware by Dell EMC - \uf0a7 Intel processors in the Dell EMC servers - \uf0a7 compute, storage, and network virtualization capabilities by VMware - \uf0a7 asset tagging and policy enforcement, workload and storage encryption, and data scanning by HyTrust - \uf0a7 multifactor authentication, network traffic monitoring, and dashboard and reporting by RSA The ICSV instance consists of the following components: - \uf0a7 IBM-provisioned servers with Intel processors - \uf0a7 compute, storage, network virtualization with VMware components - \uf0a7 asset tagging and policy enforcement, and workload and storage encryption with HyTrust components The IPSec VPN established between the two clouds allows them to be part of the same management domain, so that each component can be managed and utilized in the same fashion, which creates one hybrid cloud. The workloads can be shifted or live-migrated between the two sites. Figure 1-1 shows the high-level architecture. It depicts the four main components that comprise the build: - \uf0a7 HSM component : This build utilizes HSMs to store sensitive keys within the environment. - \uf0a7 Management component : Identical functional management components are instantiated within each cloud instance. At a minimum, each management component includes VMware running the virtualization stack, HyTrust providing the asset tagging policy enforcement aspect, and RSA providing network-visibility, dashboard, and reporting capabilities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments."}]}
{"id": "nist_02668", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control UM-1 in A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification? (Part 49) Control UM-1: Strengths for TWIC Authentication Use Cases We now assign intrinsic authentication strengths (in terms of the number and type of verified bindings) to TWICAuthentication Use Cases based on SCIV-ALM. In order to accomplish this, we examine the protocols involved in each Authentication Use Case and map them directly to the primitive authentication mechanisms of our methodology and their associated verified bindings (along with their types) as shown in Table B.3 below. This approach is possible because of the granularity of description of each TWIC Authentication Use Case in the TWIC specification document. Table B.3.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification."}]}
{"id": "nist_02669", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements provide? (Section 52) information available about the proposed IoT device. Figure 6 shows how information about an IoT device will flow into the updated risk assessment of the system in which the IoT device is integrated. The resulting updated risk assessment may require the organization to allocate new security controls to the information system to effectively manage the anticipated risk. The organization may identify certain security controls that apply to the IoT device, or that must be provided by the IoT device specifically. Ultimately, it is important for organizations to identify all security controls required to reduce information system risk to an acceptable level. Section 3.3 will focus on using the identified security controls to determine the technical and non-technical capabilities needed from the IoT device and/or other system elements. Figure 6: Effects on Risk Assessment due to IoT Device Informs the Risk Assessment of the Entire System. <!-- image --> Device cybersecurity requirements should be based on the security capabilities and security requirements of the system and organization while also accounting for considerations like those highlighted in Section 3.1 and updates to the system risk assessment that may be necessary as discussed in Section 3.2. Figure 7 below illustrates this process and how it will draw on the considerations and guidance from the prior sections to inform the device cybersecurity requirements. Figure 7: Organizations Can Gather Information to Update the System Risk Assessment and Determine Device Cybersecurity Requirements <!-- image --> Determining IoT device cybersecurity requirements may be challenging for some use cases. To assist organizations in selecting IoT device cybersecurity requirements, this section presents several NIST publications and resources.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements."}]}
{"id": "nist_02670", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control MP-08(03) in Assessing Security and Privacy Controls in Information Systems and Organizations? Control MP-08(03): MEDIA DOWNGRADING | CONTROLLED UNCLASSIFIED INFORMATION ASSESSMENT OBJECTIVE: Determine if:", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_02671", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain pe of the Single Finger View Record shall be either 0 or 2. AS05.02.14: The Impression Ty according to NIST PIV Data Model Test Guidelines According to PIV Data Model Test Guidelines, pe of the Single Finger View Record shall be either 0 or 2. AS05.02.14: The Impression Ty: VE05.02.14.01: The vendor shall specify if the live or non-live scane images were used. TE05.02.14.01: The tester shall verify the value is either 0 or 2 and is consistent with vendor reporting.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_02672", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-06(05) in Assessing Security Requirements for Controlled Unclassified Information? (Part 6) Control AC-06(05): d with individuals are discovered. A.03.01.01.g.01: account managers and designated personnel or roles are notified within &lt;A.03.01.01.ODP[02]: time period&gt; when accounts are no longer required. A.03.01.01.g.02: account managers and designated personnel or roles are notified within &lt;A.03.01.01.ODP[03]: time period&gt; when users are terminated or transferred. A.03.01.01.g.03: account managers and designated personnel or roles are notified within &lt;A.03.01.01.ODP[04]: time period&gt; when system usage or the need-to-know changes for an individual. A.03.01.01.h: users are required to log out of the system after &lt;A.03.01.01.ODP[05]: time period&gt; of expected inactivity or when the following circumstances occur: &lt;A.03.01.01.ODP[06]: circumstances&gt; .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02673", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Security Considerations for Voice Over IP Systems? (Part 22) Control HA-1: nals and events in media streams is the same in MEGACO as in MGCP. - -The concept of packages containing event and signal definitions that permits easy extension to the protocol is borrowed from MGCP. - -The MEGACO specification for transport of messages over UDP is the same as specified in MGCP. The three-way-handshake and the computation of retransmission timers described in MGCP are also described within the ALF definition specified in Annex E of MEGACO. MEGACO/H.248 introduces several enhancements compared with MGCP, including the following: - -Support of multimedia and multipoint conferencing enhanced services - -Improved syntax for more efficient semantic message processing - -TCP and UDP transport options - -Allows either text or binary encoding (to support IETF and ITU-T approach) - -Formalized extension process for enhanced functionality - -Expanded definition of packages MEGACO is described as Gateway Control Protocol Version 1 within the RFC 3525. ## 6.2.2 System Architecture MEGACO/H.248 (see Figure 8) has basically the same architecture as MGCP. MEGACO/H.248 commands are similar to MGCP commands. However, the \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ protocol models are quite different. MEGACO specifies a media gateway connection model that has two entities: Terminations (source or sink for (one or more) media streams), and context (grouping of terminations connected in a call). In contrast, MGCP uses the following two entities: Endpoints (source or sink of data), and Connection: (association between two endpoints). Taking a multipoint conference as an example, MEGACO simplifies the connection setup by adding terminations to a context, whereas MGCP has to establish several connections to the conference server. The context in this scenario may cover multiple media streams for enhanced multimedia services.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Considerations for Voice Over IP Systems."}]}
{"id": "nist_02674", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations say about 03.04.12 System and Component Configuration for High-Risk Areas? According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, 03.04.12 System and Component Configuration for High-Risk Areas: - a. Issue systems or system components with the following configurations to individuals traveling to high-risk locations: [ Assignment: organization-defined system configurations ]. - b. Apply the following security requirements to the systems or components when the individuals return from travel: [ Assignment: organization-defined security requirements ]. NIST SP 800-171r3 May 2024", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_02675", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Block Cipher Modes of Operation_ Methods for Format-Preserving Encryption say about Abstract? According to Recommendation for Block Cipher Modes of Operation_ Methods for Format-Preserving Encryption, Abstract: This Recommendation specifies two methods, called FF1 and FF3, for format-preserving encryption. Both of these methods are modes of operation for an underlying, approved symmetric-key block cipher algorithm.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Block Cipher Modes of Operation_ Methods for Format-Preserving Encryption."}]}
{"id": "nist_02676", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.11 RISK ASSESSMENT according to NIST Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171, 3.11 RISK ASSESSMENT: Enhanced Security Requirements - 3.11.1e Employ [ Assignment: organization-defined sources of threat intelligence ] as part of a risk assessment to guide and inform the development of organizational systems, security architectures, selection of security solutions, monitoring, threat hunting, and response and recovery activities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_02677", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-5 in Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control? (Part 60) Control PD-5: uipment that interfaces with the space segment and third-party partners. In the hosted payload scenario, third-party partnerships between the PCC and the MOCvary widely and are coordinated in advance. | Protect: Awareness and Training Category The organization's personnel and partners are provided cybersecurity awareness education and trained to perform their cybersecurity-related duties and responsibilities consistent with related policies, procedures, and agreements. The awareness and training category is not unique to the satellite industry. The focus is on privileged users who operate, monitor, and maintain equipment that interfaces with the space segment and third-party partners. In the hosted payload scenario, third-party partnerships between the PCC and the MOCvary widely and are coordinated in advance. | Protect: Awareness and Training Category The organization's personnel and partners are provided cybersecurity awareness education and trained to perform their cybersecurity-related duties and responsibilities consistent with related policies, procedures, and agreements. The awareness and training category is not unique to the satellite industry. The focus is on privileged users who operate, monitor, and maintain equipment that interfaces with the space segment and third-party partners. In the hosted payload scenario, third-party partnerships between the PCC and the MOCvary widely and are coordinated in advance. | | PR.AT-1 : All users are informed and trained. | Organizations should provide awareness education and training for all ground segment personnel for the bus and payload.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control."}]}
{"id": "nist_02678", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 2017 NIST_ITL Cybersecurity Program Annual Report provide? (Section 208) rea of work is focused on evolving security automation specifications to integrate with existing transport protocols to provide for the secure, interoperable exchange of security automation data. Additional work is focused on evolving security metrics and providing consensus guidance on security automation approaches. Through the definition and adoption of security automation standards and guidelines, IT vendors will be able to provide standardized security solutions to their customers. These solutions support continuous monitoring and automated, dynamic network defense capabilities, based on the analysis of data from operational and security data sources and the collective action of security components. Additionally, CSD is working with the vulnerability community to enable the automated analysis of metrics such as the Common Vulnerability Scoring System (CVSS), establishing a baseline of the minimum information needed to properly inform the vulnerability management process, and facilitating the sharing of vulnerability information across language barriers. To assist in this work, a public draft of NISTIR 8138, Vulnerability Description Ontology (VDO): A Framework for Characterizing Vulnerabilities, was created to foster a conversation and collect feedback on the best mechanisms to improve the degree of automation within vulnerability management processes. CSD is planning to develop this document iteratively by releasing additional drafts in FY 2018 to ensure participation from as many stakeholders in the vulnerability community as possible. Security automation standardization work has been focused in three areas: the evolution and international adoption of the Security Content Automation Protocol (SCAP), the development of software asset management standards to support operational and cybersecurity use cases, and the development of security automation consensus standards.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, continuous monitoring. General security reference material without sensitive content. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02679", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog say about Reports on Computer Systems Technology? According to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog, Reports on Computer Systems Technology: 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog."}]}
{"id": "nist_02680", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Management_ Part 1 \u2013 General provide? (Section 261) Measures necessary to mitigate the consequences of a suspected unauthorized access to protected data or processes and to reduce the probability or frequency of future compromises should be undertaken. Where secret (symmetric) keys or private (asymmetric) keys are used to protect only a single entity's local information or communications between a single pair of entities, the compromise recovery process can be relatively simple and inexpensive. Damage assessment and mitigation measures are often local matters. On the other hand, when a key is shared by or affects a large number of entities, damage can be widespread, and recovery is both complex and expensive. Some examples of keys, the compromise of which might be particularly difficult or expensive to recover from, include the following: 1. A CA's private signature key, especially if it is used to sign a root certificate in a publickey infrastructure; 2. A symmetric key-wrapping key shared by a large number of entities; 3. A master/key-derivation key used in the derivation of keys by a large number of entities; 4. A symmetric data-encryption key used to encrypt data in a large distributed database; 5. A symmetric key shared by a large number of communications network participants; and 6. A key used to protect a large number of stored keys. In all of these cases, a large number of key owners or relying parties (e.g., all parties authorized to use the secret key of a symmetric-key algorithm or the public key of an asymmetric-key algorithm) need to be immediately notified of the compromise. The inclusion of the key identifier on a Compromised Key List (CKL) or the certificate serial number on a Certificate Revocation List (CRL) to be published at a later date might not be sufficient. This means that a list of (the most likely) affected entities might need to be maintained, and a means for communicating the news of a compromise would be required.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02681", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations say about Abstract? According to Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations, Abstract: Transport Layer Security (TLS) provides mechanisms to protect data during electronic dissemination across the Internet. This Special Publication provides guidance to the selection and configuration of TLS protocol implementations while making effective use of Federal Information Processing Standards (FIPS) and NIST-recommended cryptographic algorithms. It requires that TLS 1.2 configured with FIPS-based cipher suites be supported by all government TLS servers and clients and requires support for TLS 1.3 by January 1, 2024. This Special Publication also provides guidance on certificates and TLS extensions that impact security.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations."}]}
{"id": "nist_02682", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Management_ Part 1 \u2013 General provide? (Section 271) orkin 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 | |-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | SP800-56A | https://doi.org/10.6028/NIST.SP.800-52r2 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. | | SP800-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 | | SP800-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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02683", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Data Confidentiality_ Detect, Respond to, and Recover from Data Breaches provide? (Section 43) ough there may be clues as to its existence - a user with account troubles and traffic going to a domain name very similar to the organization's domain might be enough to send up red flags if noticed. Regardless, the organization will need to deal with a privileged user account being used to download malware and hold the confidentiality of sensitive files ransom. | | Detect | The Monitoring capability for this scenario includes network monitoring, which can detect unauthorized data exfiltration out of the network and any irregular access or changes to existing data. Any exfiltration or data encryption actions would also be included in logs forwarded to the tools used for Reporting and Logging capabilities. | | Respond | The Mitigation capability for this scenario will allow for rapid disabling and secure re-enabling of compromised accounts once the relevant member accounts are detected. The Reporting capability is designed to quickly notify security teams of necessary actions, such as isolating the system from the network and securing any data not yet attacked by the ransomware. | |-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Recover | The scenario build doesn't possess any technical capabilities for literal recovery of the stolen data, as the scenario predicates the data has already been successfully stolen, but the Logging capabilities should allow a detailed review of what was taken. This will allow for post-incident review of security flaws and notification of anyone inside or outside the organization affected by the security breach.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, ransomware. Contains technical security guidance that could inform defensive posture. Source: Data Confidentiality_ Detect, Respond to, and Recover from Data Breaches."}]}
{"id": "nist_02684", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Extension: according to NIST COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0 According to COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0, Extension:: FAU\\_GEN.1-CSPP.3 When the TSF provides application support it shall support an application program interface (API) that allows a privileged application to append data to the security audit trail or to an application-specified alternative security audit trail. Refinement: See text in FAU\\_GEN.1.1 and FAU\\_GEN.1.2", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0."}]}
{"id": "nist_02685", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Section 183) | Examples: policies, plans, procedures, system requirements, designs. | | Objects | Mechanisms | Examples: functionality implemented in hardware, software, firmware. | Examples: functionality implemented in hardware, software, firmware. | | Objects | Activities | Examples: system operations, administration, management, exercises. | Examples: system operations, administration, management, exercises. | | Attributes | Depth | Addresses the rigor of and level of detail in the examination process. | Addresses the rigor of and level of detail in the examination process.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02686", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 336) s: something you know (e.g., a personal identification number [PIN]), something you have (e.g., a physical authenticator such as a cryptographic private key), or something you are (e.g., a biometric). Multi-factor authentication solutions that feature physical authenticators include hardware authenticators that provide time-based or challenge-response outputs and smart cards such as the U.S. Government Personal Identity Verification (PIV) card or the Department of Defense (DoD) Common Access Card (CAC). In addition to authenticating users at the system level (i.e., at logon), organizations may employ authentication mechanisms at the application level, at their discretion, to provide increased security. Regardless of the type of access (i.e., local, network, remote), privileged accounts are authenticated using multi-factor options appropriate for the level of risk. Organizations can add additional security measures, such as additional or more rigorous authentication mechanisms, for specific types of access. Related Controls: AC-5, AC-6. (2) IDENTIFICATION AND AUTHENTICATION (ORGANIZATIONAL USERS) | MULTI-FACTOR AUTHENTICATION TO NON-PRIVILEGED ACCOUNTS CHAPTER THREE PAGE 132 T h s i p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p s : / / d o i . o r g / 1 0 . 6 0 2 8 / N S T S P . 8 0 0 - 5 3 r 5 I . NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ Implement multi-factor authentication for access to non-privileged accounts. Discussion: Multi-factor authentication requires the use of two or more different factors to achieve authentication.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor. Contains security framework guidance for authentication systems. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02687", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 6.1 Assumptions and Limitations according to NIST Data Integrity_ Recovering from Ransomware and Other Destructive Events According to Data Integrity_ Recovering from Ransomware and Other Destructive Events, 6.1 Assumptions and Limitations: The security characteristic evaluation has several limitations: - \uf0a7 It is not a comprehensive test of all security components, nor is it a red team exercise. - \uf0a7 It cannot identify all weaknesses. - \uf0a7 It does not include the lab infrastructure. It is assumed that devices are hardened. Testing these devices would reveal only weaknesses in implementation that would not be relevant to those adopting this reference architecture.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: ransomware, red team. Contains technical security guidance that could inform defensive posture. Source: Data Integrity_ Recovering from Ransomware and Other Destructive Events."}]}
{"id": "nist_02688", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Secure Web Services? (Part 128) Control ES-1: ation into the registry. The publishing is restricted, so publishers must be authenticated. Authentication can be performed using a username/password combination, SAML, Kerberos, or some other method. - An inquiry API provides read-only access to the registry. The inquiry API allows Web services to search for organization details, services offered, and binding information for the services. This API is usually publicly accessible. In UDDI v2, the inquiry API does not support authentication, but in UDDI v3, authentication can be required for inquiries-limiting access to the registry only to trusted Web services. - UDDI v3 introduces a new subscription API that provides notifications about additions or updates to the registry. The subscription API is also restricted, requiring authentication by the registry. In addition to the SOAP-based APIs, many implementations of UDDI registries provide a Web interface for publishing to and searching the registry. Because this is not part of the UDDI standard and is not implemented by all UDDI registry vendors, these UDDI Web interfaces are not covered in this guide. ## 3.9.3 Secure Access to the Registry As described in Section 3.9.2, some portions of the UDDI API require authentication. SOAP over HTTPS is usually required to make certain that publisher credentials cannot be intercepted during transmission. In addition, all publishers should be designated as Tier 1 publishers. In UDDI v2, Tier 1 publishers have defined restrictions for what services they can publish to the registry. In a private registry, these restrictions can vary based on the needs of the organization. In contrast, the specification does not require restrictions on a Tier 2 publisher. Some UDDI registries provide the ability to restrict publishers' activities at the account level, which provides some control over Tier 2 publishers. UDDI v3 provides the ability to define policies, which provide finer control over publishers than the Tier model available in v2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Secure Web Services."}]}
{"id": "nist_02689", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Can Great Seneca Accounting stop someone from turning on a camera or microphone? according to NIST Mobile Device Security_ Bring Your Own Device (BYOD) According to Mobile Device Security_ Bring Your Own Device (BYOD), Can Great Seneca Accounting stop someone from turning on a camera or microphone?: Malicious actors with access (authorized or unauthorized) to device sensors (microphone, camera, gyroscope, Global Positioning System receiver, and radios) can use them to conduct surveillance. It may be directed at the user, as when tracking the device location, or it may be applied more generally, as when recording any nearby sounds. Captured sensor data may be immediately useful to a malicious actor, such as a recording of an executive meeting. Alternatively, the attacker may analyze the data in isolation or in combination with other data to yield sensitive information. For example, a malicious actor can use audio recordings of on-device or proximate activity to probabilistically determine user inputs to touchscreens and keyboards, essentially turning the device into a remote keylogger.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_02690", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations say about A.2.9. FAMILY: IDENTIFICATION AND AUTHENTICATION? According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, A.2.9. FAMILY: IDENTIFICATION AND AUTHENTICATION: [FIPS200] specifies the Identification and Authentication minimum security requirement as follows: 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. NIST SP 800-161, Supply Chain Risk Management Practices for Federal Information Systems and Organizations, expands the identification and authentication control family to include the identification and authentication of components in addition to individuals (users) and processes acting on behalf of individuals within the supply chain network. Identification and authentication are critical to C-SCRM because they provide for the traceability of individuals, processes acting on behalf of individuals, and specific systems/components in an enterprise's supply chain network. Identification and authentication are required to appropriately manage cybersecurity risks throughout the supply chain to both reduce the risk of supply chain cybersecurity compromise and to generate evidence in case of supply chain cybersecurity compromise. [FIPS200]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, control family. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_02691", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EP-67 in Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)? (Part 57) Control EP-67: modification, loss, and destruction. Keys shall not be stored in the Cloud, but maintained by the cloud consumer or trusted key management provider. Key management and key usage are separated duties. Page 462, Sections under category 10 | | | IEEE 1363- 2000 | IEEE | traditional public-key cryptography | Approved Standard | Cryptographic Techniques: Techniques and mechanisms and their associated standards are used to provide: confidentiality; entity authentication; non-repudiation; key management; data integrity; trust worthy data platforms; message authentication; and digital signatures.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management, sso. Contains security framework guidance for authentication systems. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_02692", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI) say about Table G.2: Controls and Assessment Procedures for Derived PIV Credential Issuers (DPCIs)? (Part 17) According to Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI), Table G.2: Controls and Assessment Procedures for Derived PIV Credential Issuers (DPCIs): | DPCI | Commonly accepted security readiness measures | | IAT = Organizational Preparedness | IAT = Organizational Preparedness | IAT = Organizational Preparedness | IAT = Organizational Preparedness | IAT = Organizational Preparedness | |-------------------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-----------------------------------------------| | Authorization Focus Area | Identifier | Issuer Control | Applicability | Source | | | FP(DC)-8 | All pre-personalized removable (non-embedded) hardware cryptographic tokens (e.g., SD Card, UICC, USB) received from token vendors are received only by authorized personnel who ensure that these tokens are stored, handled and disposed off securely at the issuing facility.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, token. Contains security framework guidance for authentication systems. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_02693", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings say about 6th Annual PKI R&amp;D Workshop - Proceedings? According to 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings, 6th Annual PKI R&amp;D Workshop - Proceedings: Figure 4 Admin UI for trust level management <!-- image --> may be desirable to have a common set of trust levels across multiple institutions, however, so that a client or a service can interpret the trust level associated with a CA correctly. In that case, a standard for trust levels should be accepted by the community and made available in a common repository or distributed to each GTS instance. Note that having a common set of trust levels does not require each GTS instance to assign the same trust level to the same CA. A GTS instance may assign a higher level of trust to a CA than another GTS instance. However, a common set of trust levels allows a client to interpret the trust level assigned by each GTS instance correctly and determine whether or not to trust the corresponding CA.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, sso. Contains security framework guidance for authentication systems. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_02694", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TG-005 in Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)? (Part 200) Control TG-005: 1155 Sixteenth St., NW., Washington, DC 20056. Building Science Series -Disseminates technical information developed at the Institute on building materials, components, systems, and whole structures. The series presents research results, test methods, and performance criteria related to the structural and environmental functions and the durability and safety characteristics of building elements and systems. Technical Notes -Studies or reports which are complete in themselves but restrictive in their treatment of a subject. Analogous to monographs but not so comprehensive in scope or definitive in treatment of the subject area. Often serve as a vehicle for final reports of work performed at NIST under the sponsorship of other government agencies. Voluntary Product Standards -Developed under procedures published by the Department of Commerce in Part 10, Title 15, of the Code of Federal Regulations. The standards establish nationally recognized requirements for products, and provide all concerned interests with a basis for common understanding of the characteristics of the products. NIST administers this program as a supplement to the activities of the private sector standardizing organizations. Consumer Information Series -Practical information, based on NIST research and experience, covering areas of interest to the consumer. Easily understandable language and illustrations provide useful background knowledge for shopping in today's technological marketplace. Order the above NISTpublications from: Superintendent of Documents, Government Printing Office, Washington, DC 20402. Federal Information Processing Standards Publications (FIPS PUB)Publications in this series collectively constitute the Federal Information Processing Standards Register. The Register serves as the official source of information in the Federal Government regarding standards issued by NIST pursuant to the Federal Property and Administrative Services Act of 1949 as amended.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Invitational Workshop on Integrity Policy in Computer Information Systems (WIPCIS)."}]}
{"id": "nist_02695", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Hardware Security Failure Scenarios_ Potential Hardware Weaknesses say about CWE References? (Part 9) According to Hardware Security Failure Scenarios_ Potential Hardware Weaknesses, CWE References: https://cwe.mitre.org/data/definitions/1274.html - [CWE-1276] Fern N (2020) CWE-1276: Hardware Child Block Incorrectly Connected to Parent System. (The MITRE Corporation). Submission date 2020-02-24. Available at https://cwe.mitre.org/data/definitions/1276.html - [CWE-1277] Wortman PA (2020) CWE-1277: Firmware Not Updateable. (The MITRE Corporation). Submission date 2020-02-24. Available at https://cwe.mitre.org/data/definitions/1277.html - [CWE-1278] Fern N (2020) CWE-1278: Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques. (The MITRE Corporation). Submission date 2020-02-24. Available at https://cwe.mitre.org/data/definitions/1278.html - [CWE-1279] Kanuparthi A, Khattri H, Manna PK, Mangipudi NKV (2020) CWE-1279: Cryptographic Operations are run Before Supporting Units are Ready. (The MITRE Corporation). Submission date 2020-02-24. Available at https://cwe.mitre.org/data/definitions/1279.html - [CWE-1280] Kanuparthi A, Khattri H, Manna PK, Mangipudi NKV (2020) CWE-1280: Access Control Check Implemented After Asset is Accessed. (The MITRE Corporation). Submission date 2020-02-24. Available at https://cwe.mitre.org/data/definitions/1280.html - [CWE-1281] Fern N (2020) CWE-1281: Sequence of Processor Instructions Leads to Unexpected Behavior. (The MITRE Corporation). Submission date 2020-02-24. Available at https://cwe.mitre.org/data/definitions/1281.html - [CWE-1282] Fern N (2020) CWE-1282: Assumed-Immutable Data is Stored in Writable Memory. (The MITRE Corporation). Submission date 2020-02-24. Available at https://cwe.mitre.org/data/definitions/1282.html - [CWE-1283] Kanuparthi A, Khattri H, Manna PK, Mangipudi NKV (2020) CWE-1283: Mutable Attestation or Measurement Reporting Data. (The MITRE Corporation). Submission date 2020-02-24. Available at https://cwe.mitre.org/data/definitions/1283.html - [CWE-1290] Kanuparthi A, Khattri H, Manna PK (2020) CWE-1290: Incorrect Decoding of Security Identifiers .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Hardware Security Failure Scenarios_ Potential Hardware Weaknesses."}]}
{"id": "nist_02696", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Note according to Domain Name System-Based Electronic Mail Security? Note: Thunderbird automatically adds other people's S/MIME certificates to the Other People's tab of a user's Certificate Manager when he or she receives from them a digitally signed message with a valid signature and with an S/MIME certificate issued by a recognized and trusted CA. CA certificates that appear in Thunderbird's Authorities tab are recognized, and may also be trusted. CA certificates that do not appear in that tab are considered unrecognized . An S/MIME certificate that was issued by an unrecognized CA will not be automatically added to the Other People's tab of the user's Certificate Manager. If the user attempts to manually import an S/MIME certificate that was issued by an unrecognized CA, nothing will happen--literally. Thunderbird will not even display an error dialog. It will just not import the S/MIME certificate. This is generally not a problem when receiving an S/MIME certificate that was issued by a trusted CA, but could be a problem for a certificate that was issued by an unrecognized or untrusted CA, or for a certificate that is self-signed (i.e., it has no CA other than itself). So, before a user can import an S/MIME certificate that is issued by an unrecognized CA or is self-signed, he or she must first acquire and import the certificate for the issuing CA. In the case of a self-signed certificate, a .cer file needs to be acquired from the individual whose certificate the user wishes to add.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_02697", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 7.2 Securing DNS Software according to NIST Secure Domain Name System (DNS) Deployment Guide According to Secure Domain Name System (DNS) Deployment Guide, 7.2 Securing DNS Software: Protection approaches for DNS software include choice of appropriate version, installation of patches, running it with restricted privileges, restricting other applications in the execution environment, dedicating instances for each function, controlling the set of hosts where software is installed, placement within the network, and limiting information exposure by logical/physical partitioning of zone file data or running two name server software instances for different client classes.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Domain Name System (DNS) Deployment Guide."}]}
{"id": "nist_02698", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.2.5. Compromise of Shared L7 Proxy (TR-5) according to NIST Service Mesh Proxy Models for Cloud-Native Applications According to Service Mesh Proxy Models for Cloud-Native Applications, 5.2.5. Compromise of Shared L7 Proxy (TR-5): Threat Description : A co-tenant exploits an L7 traffic processing vulnerability in a shared proxy and affects the confidentiality, integrity, or availability of traffic to and from another workload that runs on the same node. Proxy Function Impacted : By limiting the per-node functionality to L4 processing, the attack surface is significantly reduced. Impact Score = 1 : The application workload itself is unaffected. The proxy is a separate deployment. As long as the L7 proxy is not shared with the compromised application, there is no impact. Likelihood Score = 1 : The likelihood is as likely as in TR-4 (see Sec. 5.2.4).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Service Mesh Proxy Models for Cloud-Native Applications."}]}
{"id": "nist_02699", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach say about 4.2.1 Introduction? (Part 2) According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach, 4.2.1 Introduction: potential audit coverage for each AIS developmental phase. The modules each contain the following segments: 1. Audit participation - Brief introduction of the phase and relevant audit involvement. 2. Primary audit objectives - Overall purpose for audit coverage during phase. 3. Overview - Description of the phase and its AIS life cycle matrix responsibilities and deliverables. 4. Audit survey - Initial background analysis and pertinent survey technique(s). 5. Customized audit objectives - AIS phase developments impacting scope of subsequent audit coverage. 6. Detailed audit testing - Specific audit objectives, tests, and techniques. 7. Assessment of audit results - Analyses for developing and reporting phase audit test results and planning future AIS audit coverage. 8. Questionnaires/Matrices - Tools for soliciting and assimilating pertinent phase information.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach."}]}
{"id": "nist_02700", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices say about Integrity? According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, Integrity: The integrity impact level is based on the specific mission and the data supporting that mission, not on the time required to detect the modification or destruction of information. The consequences of unauthorized modification or destruction of higher education information would have, at most, a limited adverse effect on agency operations, agency assets, or individuals. Unauthorized modification or destruction of information affecting external communications (e.g., web pages, electronic mail) may adversely affect operations and/or public confidence in the agency, but the damage to the mission would usually be limited Special Factors Affecting Integrity Impact Determination : Exceptions that might result in more serious consequences are based on the mission supported by the higher education activity (e.g., undetected modification of weapons training information at a service academy where the modification could result in harm to the student or other individuals). In such cases, the impact is determined by the information associated with the supported mission. This can result in assignment of a moderate or high impact level to such information. Recommended Integrity Impact Level: The provisional integrity impact level recommended for higher education information is low .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_02701", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2010 Annual Report say about Internet Security? (Part 2) According to Computer Security Division 2010 Annual Report, Internet Security: and the root zone distributor. CSD continues its collaboration with the Advanced Network Technologies Division to support the development of security enhancements for routing protocols. The goal of this work is to develop protocols that allow for the validation of Internet routing information in order to prevent attacks against the infrastructure that are intended to misroute Internet traffic or cause denial of service. Other ongoing activities are focused on key management and cryptographic agility to support the authentication of routing components (e.g., to support the Border Gateway Protocol). Contacts: Mr. William Polk (301) 975-3348 william.polk@nist.gov Dr. David Cooper (301) 975-3194 david.cooper@nist.gov", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Computer Security Division 2010 Annual Report."}]}
{"id": "nist_02702", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Secure Virtual Network Configuration for Virtual Machine (VM) Protection provide? (Section 29) ng availability, so any network configuration for achieving this can be looked upon as an integral part of network-based protection for VMs. This section discusses options for configuring these paths. The physical network configuration in a data center is largely unaffected by the presence of virtualized hosts, except for some tasks such as VLAN configuration of ports in the physical switches connecting to the virtualized hosts, and configuration of the associated links as trunk links. The configuration options discussed in this section relating to network path redundancy for VMs are confined to the virtual network inside the virtualized hosts including their pNICs. The virtual network configuration features provided in most hypervisor offerings involve a combination of load balancing and failover policy options. From a network path redundancy perspective, only failover policy options are of interest. Hypervisor offerings provide a configuration feature called network interface card (NIC) teaming. NIC teaming allows administrators to combine multiple pNICs into a NIC team for NIC failover capabilities in a virtualized host. 1 The members of the NIC team are connected to the different uplink ports of the same virtual switch. Failover capability requires at least two pNICs in the NIC team. One of them can be configured as 'active' and the other as 'standby'. If an active pNIC fails or traffic fails to flow through it, the traffic will start flowing (or be routed) through the standby pNIC, thus maintaining continuity of network traffic flow from all VMs connected to that virtual switch. This type of configuration is also called active-passive NIC bonding . Some hypervisor offerings allow NIC teaming functionality to be defined at the VM level. A NIC teaming feature at the VM level enables administrators to create a NIC team using vNICs of a VM.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Secure Virtual Network Configuration for Virtual Machine (VM) Protection."}]}
{"id": "nist_02703", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to Security and Privacy Controls for Information Systems and Organizations? Discussion: For example, if the MTTF for a system component is 100 days and the MTTF", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02704", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Framework for Designing Cryptographic Key Management Systems say about Appendix B: Glossary of Terms? (Part 14) According to A Framework for Designing Cryptographic Key Management Systems, Appendix B: Glossary of Terms: ents so as to provide assurance that the key and its metadata are properly associated, originate from a particular source, have not been modified, and have been protected from unauthorized disclosure. | | Unlinkability | Assurance that two or more related events in an information processing system cannot be associated with each other in CKMS-supported communications. | | Unobservability | Assurance that an observer is unable to identify or make inferences about the parties involved in a transaction in CKMS- supported communications. | | User | An individual authorized by an organization and its policies to use an information system, one or more of its applications, its security procedures and services, and a supporting CKMS. | | Validate | To test cryptographic parameters or modules and confirm the test results to obtain assurance that the tested implementation is appropriate for use. | | Validity Period | The lifespan of a public key certificate. | SP 800-130 August 2013", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_02705", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Policy Machine_ Features, Architecture, and Specification say about 8. Related Work? (Part 2) According to Policy Machine_ Features, Architecture, and Specification, 8. Related Work: trust relationships, PolicyMaker and its successor KeyNote utilize public key infrastructure environments, certificate-based trust, and binding of cryptographic keys to actions [Bla98, Bla99]. Five basic components can be identified: a mechanism for identifying principals, a language for describing security-critical actions, a language for specifying application policies, a language for specifying delegation credentials, and a compliance checker that factors all of the above in its decisions. Unlike other access control approaches focused mainly on centralized operating environments, trust management is particularly suited for situations where security policy is decentralized and distributed across a network, such as multisystem applications and data services that cross departmental and organizational boundaries [Bla99]. In this regard, it is similar to the PM framework. A family of usage control (UCON) models was devised as a conceptual framework for access control [Par04]. The UCON models offer a broad and diverse scope of coverage that encompasses digital rights management and other modern access control models. The complete family of models is collectively termed UCONABC, since to provide a richer and finer decision capability, decision-related factors are delineated into three categories: Authorizations (A), oBligations (B), and Conditions (C). Authorizations concern the evaluation of authorization rules and usage rights together with subject and object attributes in reaching a usage decision. Attributes are used to represent key characteristics of subjects and objects, such as identities, security labels, properties, and capabilities. Obligations are treated as requirements that subjects have to perform before or during (or even after, in case of a global obligation) obtaining or exercising usage rights.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization, sso. Contains security framework guidance for authentication systems. Source: Policy Machine_ Features, Architecture, and Specification."}]}
{"id": "nist_02706", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessment of Access Control Systems say about - SQL-RBAC? (Part 2) According to Assessment of Access Control Systems, - SQL-RBAC: cation of privileges and control over creation of new relations and views. SQL2 fixes some of these shortcomings. However, SQL2's GRANT and REVOKE instructions apply only to database users. This is extended in SQL3 by considering that these instructions also apply to roles as suggested in the RBAC model. In the meantime, some vendors have implemented RBAC; other vendors have started to deliever products incorporating mandatory access controls for multilevel security. There is a recognition that SQL needs to evolve to take some of these developments into consideration. If it does, stronger and better access controls can be expected in future products.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Assessment of Access Control Systems."}]}
{"id": "nist_02707", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Fiscal Year 2023 Cybersecurity and Privacy Annual Report say about RISK MANAGEMENT? According to Fiscal Year 2023 Cybersecurity and Privacy Annual Report, RISK MANAGEMENT: Organizations must balance an evolving cybersecurity and privacy threat landscape with the need to fulfill mission and business requirements - an effort that increasingly calls for a collaborative approach to managing risks. Risk management is integrated into NIST standards and guidelines to help organizations understand, measure, manage, and reduce cybersecurity and privacy risks in a larger context.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Fiscal Year 2023 Cybersecurity and Privacy Annual Report."}]}
{"id": "nist_02708", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control WE-1000 in Hardware Security Failure Scenarios_ Potential Hardware Weaknesses? (Part 63) Control WE-1000: for Outbound Error Messages and Alert Signals * - CWE-1323 B Improper Management of Sensitive Trace Data * - CWE-1334 B Unauthorized Error Injection Can Degrade Hardware Redundancy * - CWE-285 C Improper Authorization - o CWE-1256 B Improper Restriction of Software Interfaces to Hardware Features * - o CWE-1297 B Unprotected Confidential Information on Device is Accessible by OSAT Vendors * - o CWE-1328 B Security Version Number Mutable to Older Versions * - o CWE-732 C Incorrect Permission Assignment for Critical Resource - \uf0a7 CWE-276 B Incorrect Default Permissions * - o CWE-862 C Missing Authorization - \uf0a7 CWE-1314 B Missing Write Protection for Parametric Data Values * - o CWE-863 C Incorrect Authorization - \uf0a7 CWE-1244 B Internal Asset Exposed to Unsafe Debug Access Level or State * - CWE-287 C Improper Authentication - o CWE-306 B Missing Authentication for Critical Function - \uf0a7 CWE-288 B Authentication Bypass Using an Alternate Path or Channel - CWE-1299 B Missing Protection Mechanism for Alternate Hardware Interface * - CWE-923 C Improper Restriction of Communication Channel to Intended Endpoints - o CWE-420 B Unprotected Alternate Channel - \uf0a7 CWE-1299 B Missing Protection Mechanism for Alternate Hardware Interface * ## Appendix", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Hardware Security Failure Scenarios_ Potential Hardware Weaknesses."}]}
{"id": "nist_02709", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Maintenance Testing for the Data Encryption Standard say about 2.1 The Permutations and E Operator? According to Maintenance Testing for the Data Encryption Standard, 2.1 The Permutations and E Operator: The role of the permutation P is to mix thoroughly the data bits. The operator E expands its 32 bit input to . a 48 bit output that is added mod 2 to the round key. The permutations in the key-schedule, PCI and PC2, intermix the key bits among the round keys in such a way as to equalize keybit utilization. No key bit is used more than 15 tines nor less th^n 12 times. The initial and final permutations, IP and IP , are byte oriented for efficient hardware implementation . Each permutation is a linear operator, and so can be thought of as an n x m matrix and can be validated completely if it operates correctly on an appropriate maximal linearly independent set of input vectors, i. e., a suitable basis.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Maintenance Testing for the Data Encryption Standard."}]}
{"id": "nist_02710", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector say about Contents? (Part 1) According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector, Contents: Contents | 1.2.1 | Relevant Standards and Guidance.............................................................................4 | |---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| | 3.4.1 | Threats .............................................................................................................. 10 | | 3.4.2 | Vulnerabilities......................................................................................................... 11 | | 3.4.3 | Risk .............................................................................................................. 12 | | 4.5.1 | Build 1 .............................................................................................................. 26 | | 4.5.2 | Build 2 .............................................................................................................. 29 | | 4.5.3 Build 3 ..............................................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector."}]}
{"id": "nist_02711", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST_SP_800-37r2_Risk_Management_Framework say about GLOSSARY? (Part 33) According to NIST_SP_800-37r2_Risk_Management_Framework, GLOSSARY: es (e.g., people, hardware, software, policies, procedures) and the capabilities in place to comply with applicable privacy requirements and manage privacy risks and to react as the situation changes. | | privacy program plan [OMB A-130] | A formal document that provides an overview of an agency's privacy program, including a description of the structure of the privacy program, the resources dedicated to the privacy program, the role of the Senior Agency Official for Privacy and other privacy officials and staff, the strategic goals and objectives of the privacy program, and the program management controls and common controls in place or planned for meeting applicable privacy requirements and managing privacy risks. | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | privacy requirement | A requirement that applies to an information system or an organization that is derived from applicable laws, executive orders, directives, policies, standards, regulations, procedures, and/or mission/business needs with respect to privacy. Note: The term privacy requirement can be used in a variety of contexts from high-level policy activities to low-level implementation activities in system development and engineering disciplines.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_02712", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2010 Annual Report say about Table of Contents? (Part 4) According to Computer Security Division 2010 Annual Report, Table of Contents: 39 | | Laboratory Accreditation Algorithm Validation Program Automated Security Testing andTest Suite Development ISO Standardization of Cryptographic ModuleTesting | | Automated Vulnerability Management | | | CryptographicTechnology Group | | Security Metrics | | | | 19 | Technical Vulnerability Measurement and Scoring | 40 | | | 19 | | 40 | | Cryptographic Standards Toolkit Hash Algorithms and the Secure Hash Standard | 19 | Network Security Analysis Using Attach | 40 | | Competition Block Cipher Modes of Operation | 20 20 | Graphs Infrastructure Services, Protocols, and Applications | | | | | Internet Protocol Version 6 and Internet Protocol | 41 41 | | Key Management | | Security Securing the Domain Name System | 41 | | Transitioning of Cryptographic Algorithms and Key Lengths Internet Security | 21 21 | CSD's Part in National and International IT Security Standards | | | | | Processes | 42 | | Quantum Computing | 22 | Honors and Awards | 47 | | Authentication | | Computer Security Division Publications Released | | | | 22 | | | | | | in FY2010 & Abstracts | 48-60 | | Security Aspects of Electronic Voting", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Computer Security Division 2010 Annual Report."}]}
{"id": "nist_02713", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.1 Objects on Smart Identity Tokens according to NIST A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification According to A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification, 4.1 Objects on Smart Identity Tokens: The following are the common set of electronic objects (as opposed to the visual printed objects) in a smart card used as identity tokens along with their classifiers:", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification."}]}
{"id": "nist_02714", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain SDNS SECURITY MANAGEMENT USING BUILT-IN SYSTEM MANAGEMENT FUNCTIONS according to NIST Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992 According to Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992, SDNS SECURITY MANAGEMENT USING BUILT-IN SYSTEM MANAGEMENT FUNCTIONS: - EVENT REPORTING - CONTROLS TRANSMISSION OF EVENT REPORTS - INCLUDES DESTINATION AND BACKUP ADDRESSES FOR REPORTS - LOG CONTROL - PRESERVES INFORMATION ABOUT EVENTS FROM MULTIPLE SYSTEMS - SERVES AS A BASIS FOR DISTRIBUTED AUDITING - ACCESS CONTROL - ALLOWS REPRESENTATION OF ACCESS CONTROL INFORMATION - ALLOWS AN ARBITRARY ACCESS CONTROL POLICY TO BE SPECIFIED II ^ <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992."}]}
{"id": "nist_02715", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IR-6462 in COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0? (Part 285) Control IR-6462: trols will be implemented and (2) the CSPP-OS requirement does not specify a specific set of procedures, this component is within the range of best commercial practice and should be a part of CSPP-OS. | | ADO_IGS.1 | Installation, generation, and start- up procedures | It is necessary and reasonable to expect an IT security product to include guidance to the user on secure installation, generation, and start-up. Therefore this must be a part of an effective CSPP-OS. | | ADV_HDL.1 | Descriptive high-level design | If using best commercial practice, the vendor can be expected to have the high- level design for the TOE required by this component. Since it is a reasonable expectation, it should be included in CSPP-OS. | | ATE_IND.2 (EAL1 has IND.1) | Independent testing - sample | Having the evaluator execute a sample of the vendor tests, as a check on their validity, is a low-cost, reasonable action well within the bounds of the basic goals for CSPP-OS assurance.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0."}]}
{"id": "nist_02716", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2015 Annual Report provide? (Section 237) ectives for Cybersecurity, provides additional background on international cybersecurity standardization. This document describes a privacy risk management framework for federal information systems. The framework provides the basis for the establishment of a common vocabulary to facilitate a better understanding of and communication about privacy risks and the effective implementation of privacy principles in federal information systems. This publication focuses on the development of two key pillars to support the application of the framework: privacy engineering objectives and a privacy risk model. This guidance provides an overview of the capabilities and usage of Software Identification (SWID) tags as part of a comprehensive software life cycle. As instantiated in the International Organization for Standardization (ISO)/ International Electrotechnical Commission (ISO/IEC) 197702 standard, SWID tags support numerous applications for software asset management and information security management. This report introduces SWID tags in an operational context, provides guidelines for the creation of interoperable SWID tags, and highlights key usage scenarios for which SWID tags are applicable. The Security Content Automation Protocol (SCAP) is a suite of specifications that standardize the format and nomenclature by which software flaw and security configuration information is communicated, both to machines and humans. SCAP version 1.2 requirements are defined in SP 800-126 Revision 2. Over time, certain stylistic conventions regarding the authoring of SCAP 1.2 content have become best practices. While these best practices are not required, they improve the quality of the SCAP content in several ways, such as improving the accuracy and consistency of results, avoiding performance problems, reducing user effort, lowering content maintenance burdens, and enabling content reuse.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: risk management framework, fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2015 Annual Report."}]}
{"id": "nist_02717", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 say about STANDARDS, GUIDELINES, AND REPORTS? (Part 4) According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171, STANDARDS, GUIDELINES, AND REPORTS: PR, Millar T, Grance T, Scarfone KA (2012) Computer Security Incident Handling Guide. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-61, Rev. 2. https://doi.org/10.6028/NIST.SP.800-61r2 | | [SP 800-63-3] | 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 March 2, 2020. | | [SP 800-83] | Souppaya MP, Scarfone KA (2013) Guide to Malware Incident Prevention and Handling for Desktops and Laptops. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-83, Rev. 1. https://doi.org/10.6028/NIST.SP.800-83r1 | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | [SP 800-86] | Kent K, Chevalier S, Grance T, Dang H (2006) Guide to Integrating Forensic Techniques into Incident Response. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-86.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_02718", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 1 \u2013 General say about 5.3.3.1 Communications versus Storage? According to Recommendation for Key Management_ Part 1 \u2013 General, 5.3.3.1 Communications versus Storage: Keys that are used for confidentiality protection of communication exchanges may often have shorter cryptoperiods than keys used for the protection of stored data. Cryptoperiods are generally made longer for stored data because the overhead of generating new keys and re-encrypting all data that was encrypted using the old keys may be burdensome.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02719", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Random Number Generation Using Deterministic Random Bit Generators say about CTR\\_DRBG Instantiate Process:? According to Recommendation for Random Number Generation Using Deterministic Random Bit Generators, CTR\\_DRBG Instantiate Process:: 1. temp = len ( personalization\\_string ). Comment: Ensure that the length of the personalization\\_string is exactly seedlen bits. Note that in Section 9.1, processing step 3 obtained an entropy\\_input of seedlen bits using Table 3 to define the minimum and maximum lengths, which are both equal to seedlen bits. 2. If ( temp &lt; seedlen ), then personalization\\_string = personalization\\_string || 0 seedlen temp . 3. seed\\_material = entropy\\_input \u2295 personalization\\_string . - Key = 0 keylen 4. - . Comment: keylen bits of zeros. - V = 0 blocklen 5. . Comment: blocklen bits of zeros. 6. ( Key , V ) = CTR\\_DRBG\\_Update ( seed\\_material , Key , V ). 7. reseed\\_counter = 1. 8. Return ( V , Key , reseed\\_counter ).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Number Generation Using Deterministic Random Bit Generators."}]}
{"id": "nist_02720", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog say about Related SP 800-53 Rev. 5 Controls: CP-9? According to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog, Related SP 800-53 Rev. 5 Controls: CP-9: Requirements that may be necessary: 1. Provide training explaining how to create and restore from IoT device data backups. Education and supporting materials that may be necessary to provide include details and actions such as: - a. Providing education to IoT device customers covering the instructions and details necessary for them to create accurate backups, and to recover the backups when necessary. - b. Providing education to IoT device customers that includes instructions describing how to back up data from systems where IoT device data is stored. - c. Providing awareness reminders and tips to IoT device customers (e.g., directly in person, in videos, in an online webinar) for various aspects involved with backing up the IoT device data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog."}]}
{"id": "nist_02721", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guidelines on Electronic Mail Security? (Part 88) Control ES-1: | Completed | Action | |-------------|--------------------------------------------------------------------------------------------------------------------| | | Limit privileges for most system-related tools to authorized system administrators | | | Install and configure additional security controls | | | Select, install, and configure additional software to provide needed controls not included in the operating system | | | Test the security of the operating system | | | Test operating system after initial install to determine vulnerabilities | | | Test operating system periodically to determine new vulnerabilities | ## 6. Securing Mail Servers and Content Hardening mail server applications is an important step in protecting mail servers from compromise. This section provides recommendations for securely installing mail servers and configuring operating system and mail server access controls. Another important part of mail security is protecting the email content that traverses the server, which includes content filtering, malware scanning, and spam prevention. Securing access to mailboxes by encrypting communications, including Web-based mail access, is also addressed in this section. Email content security can also involve email encryption to preserve confidentiality and digital signatures to support integrity and non-repudiation; these are discussed in Section 3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_02722", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is NOTICE according to A Security Perspective on the Web3 Paradigm? NOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. 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.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Security Perspective on the Web3 Paradigm."}]}
{"id": "nist_02723", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for the Use of PIV Credentials in Facility Access provide? (Section 26) mechanisms. In other words, the PACS has to support at least one PIV authentication mechanism that is supported by all PIV Cards. 8 The interoperability goal of a PIV-enabled PACS can be stated: 1. Any PIV Card can provide verification of identity to the PACS (access is granted only if the identity is so authorized). 2. After a successful authentication, the authentication mechanism provides the cardholder's authenticated identity (see Section 6.1) to the relying party. + The PACS supports at least one PIV authentication mechanism that is supported by all PIV Cards. For example, a PACS may use the PKI-AUTH authentication mechanism to authenticate all cardholders. Alternatively, the PACS may use the BIO authentication mechanism to authenticate most cardholders but use the PKI-AUTH authentication mechanism to authenticate those cardholders from whom fingerprints could not be collected. + A relying PACS application needs to support all acceptable algorithms, key lengths, and key material that could be presented, either by a PIV Card or by the PIV infrastructure. For PIV Card, these data objects and keys are placed on a PIV Card during issuance and use specific cryptographic algorithms selected from the acceptable algorithms in [SP800-78], Cryptographic Algorithms and Key Sizes for Personal Identity Verification . The PACS application interrogates the card to learn which algorithms are used. 5. o If the PKI-CAK authentication mechanism is performed by a PACS application, the PACS should support all of the asymmetric algorithms permitted for the asymmetric Card Authentication key, as specified in Table 3-1 of [SP800-78], i.e., RSA 2048 and ECDSA P-256, and the PACS should accept all valid Card Authentication certificates. 8 Section 4.2 indicates which authentication mechanisms can be implemented using only data objects that are mandatory under FIPS 201-2.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Guidelines for the Use of PIV Credentials in Facility Access."}]}
{"id": "nist_02724", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services? (Part 190) Control AM-1: system lifecycle. A PNT system lifecycle can include the consideration of the acquisition, integration, deployment, operations and maintenance, repair, and replacement of PNT components and services. A comprehensive, well-documented, and disciplined risk management process for PNT systems allows for continuous monitoring of threats, likelihoods, and impacts, in order to provide efficient identification and analysis of risks and effectiveness of the controls applied to manage those risks. Equally important, an agile risk management approach enables continuous adaptation to evolving threats through adoption of innovative and rapid advances in technology and current best practices. Organizations evolve the operational reliability and effectiveness throughout a PNT system's lifecycle by continuously monitoring risks and assessing risk mitigation strategies, such as: - new techniques and technologies to improve the ability to identify, protect, detect, respond, and recover from PNT system attacks - the emergence of exploitable PNT vulnerabilities - methods to mitigate vulnerabilities and operational impacts - operational environment changes in which the PNT-dependent system is deployed to determine if updates are required to the system's cybersecurity controls Table 26 illustrates how the PNT Profile can be used by a notional organization to address example scenarios and apply the five functions of the CSF to manage the risk to PNT systems. Equipment manufacturers and end users can address the scenarios through resiliency and redundancy. Table 26.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, csf, fips. General security reference material without sensitive content. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_02725", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Electronic Mail Security say about 4. Planning and Managing Mail Servers? According to Guidelines on Electronic Mail Security, 4. Planning and Managing Mail Servers: The most critical aspect of deploying a secure mail server is careful planning before installation, configuration, and deployment. Careful planning will ensure that the mail server is as secure as possible and in compliance with all relative organizational policies. Many mail server security and performance problems can be traced back to a lack of planning or management controls. The importance of management controls is difficult to overstate. In many organizations, the information technology support structure is highly fragmented. This fragmentation leads to inconsistencies, and these inconsistencies can lead to security vulnerabilities.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_02726", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2016 NIST_ITL Cybersecurity Program Annual Report say about CONTACT:? According to 2016 NIST_ITL Cybersecurity Program Annual Report, CONTACT:: Dr. Morris Dworkin (301) 975-2354 morris.dworkin@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2016 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02727", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 1 \u2013 General say about 8.2.2.2 Key Recovery Function? According to Recommendation for Key Management_ Part 1 \u2013 General, 8.2.2.2 Key Recovery Function: Keying material that is in active memory or stored in normal operational storage may sometimes be lost or corrupted (e.g., from a system crash or power fluctuation). Some of the keying material is needed to continue operations and cannot easily be replaced. An assessment needs to be made of which keying material needs to be preserved for possible recovery at a later time. The decision as to whether key recovery is required should be made on a case-by-case basis. The decision should be based on: 1. The type of key (e.g., private signature key or symmetric data-encryption key); 2. The application in which the key will be used (e.g., interactive communications or file storage); 3. Whether the key is 'owned' by the local entity (e.g., a private key), by another entity (e.g., the other entity's public key), or is shared (e.g., a symmetric data-encryption key shared by two entities); 4. The role of the entity in a communication (e.g., sender or receiver); and 5. The algorithm or computation in which the key will be used (e.g., does the entity have the necessary information to perform a given computation if the key were to be recovered). 100 The factors involved in a decision for or against key recovery should be carefully assessed. The trade-offs are concerned with the continuity of operations versus the risk of possibly exposing the keying material and the information it protects if control of the keying material is lost. If it is determined that a key needs to be recovered, and the key is still active (e.g., the cryptoperiod of the key has not expired, and the key has not been compromised), then the key may need to be replaced in order to limit the exposure of the data protected by that key (see Section 8.2.3). Issues associated with key recovery and discussions about whether or not different types of cryptographic material need to be recoverable are provided in Appendix B.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02728", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2015 Annual Report say about Conference Papers? (Part 5) According to Computer Security Division 2015 Annual Report, Conference Papers: luate the degree to which a group of countries can disconnect two other countries, isolate a set of countries from the Internet, or even break the Internet up into non-communicative clusters. To do this, we create an interconnectivity map of the worldwide Internet routing infrastructure at a country-level of abstraction. We then examine how groups of countries may use their pieces of routing infrastructure to filter out the traffic of other countries (or to block entire routes). Overall, bounds analysis indicates that the ability of countries to perform such disruptions to connectivity has diminished significantly between 2008 and 2013. However, we show that the majority of the gains in robustness go to countries that had already displayed significant robustness to the types of attacks that we consider. The countries that displayed higher initial vulnerability to such attacks did not become significantly more robust over the time period of analysis. D. Moody, R. Perlner and D. Smith-Tone, 'An Asymptotically Optimal Structural Attack on the ABC Multivariate Encryption Scheme,' 6th International Workshop on Post-Quantum Cryptography (PQCrypto 2014), Waterloo, Ontario, Canada, October 1-3, 2014. In Lecture Notes in Computer Science 8772, Post-Quantum Cryptography, M. Mosca, ed., Berlin: Springer International, 2014, pp. 180-196. doi: 10.1007/978-3319-11659-4\\_11. <!-- image --> Historically, multivariate public key cryptography has been less than successful at offering encryption schemes that are both secure and efficient. At PQCRYPTO '13 in Limoges, Tao, Diene, Tang, and Ding introduced a promising new multivariate encryption algorithm based on a fundamentally new idea: hiding the structure of a large matrix algebra over a finite field. We present an attack based on the subspace differential invariants inherent to this methodology.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2015 Annual Report."}]}
{"id": "nist_02729", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance say about Appendix B: Acronyms? (Part 2) According to Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance, Appendix B: Acronyms: d PKI Public Key Infrastructure PRF Pseudorandom Function PVM Path Validation Module RA Registration Authority RFC Request for Comment RR Resource Record RSA Rivest, Shamir, and Adleman. S/MIME Secure/Multipart Internet Mail Extensions SA Security Association SEP Secure Entry Point SHA Secure Hash Algorithm SMTP Simple Mail Transfer Protocol SSL Secure Socket Layer TCG Trusted Computing Group TDEA Triple Data Encryption Algorithm TEK Traffic Encryption Key TGS Ticket Granting Service TLS Transport Layer Security TPM Trusted Platform Module TS Target Server TSIG Transaction Signature URL Uniform Resource Locator VPN Virtual Private Network XOR Exclusive-Or operation ZSK Zone Signing Key", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance."}]}
{"id": "nist_02730", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 5.2 Cryptographic Key Management Systems according to NIST Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms According to Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms, 5.2 Cryptographic Key Management Systems: Several publications have been developed for the development of key-management systems: SP 800-130 74 (see Section 5.2.1), SP 800-152 75 (see Section 5.2.2), and documents relating to the Public Key Infrastructure used for asymmetric-key cryptography (see Section 5.2.3). A Cryptographic Key Management System (CKMS) includes policies, procedures, components, and devices that are used to protect, manage, and distribute key information. A CKMS includes all devices or subsystems that can access a key or the other information associated with it. The devices could be computers, cell phones, tablets, or other smart devices, such as cars, alarm systems, or even refrigerators.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms."}]}
{"id": "nist_02731", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Card Technology Developments and Gap Analysis Interagency Report provide? (Section 129) sts to verify their compliance with the standards. Nevertheless any new technology will have such early tweaking requirements and adding a new technology on a card will require monitoring for a while. D-38 Presentation: Migration Strategies Presented By: Michael L. Davis, OmniTek File Size: 227 KB PDF File Capabilities: In the access control marketplace, contactless with smart cards are the ideal medium for access control and as proof of that, we now use a technology called Prox which enjoys a very large penetration rate. But it's an older technology and it's very prevalent. But with the new contactless smart cards, we wish to talk about some migration strategies. Lessons Learned : If you're starting from scratch, that's always a much better solution. That applies to almost any endeavor that one takes. But unfortunately, there's a lot of product out there now and we have to make it seamless for the end users and the community to move to a new technology. Technology/Capabilities/Standards/Limitations : So Prox, as it's talked about in the United States, is actually 125 kilohertz. And it's basically, a nice technology, very reliable, very mature. But it suffers from some negatives. The biggest negative is that it's read only typically. You can write cards. But you can't do them on the fly. You can't actually present them and rewrite the data. And the security is pretty low. You can actually find the data sheets for the manufacturers, the chips used inside right on the Internet. And there's no ISO standard. And, of course, the biggest significant factor is it's not multiapplication. Comparison: So we're all experts in here about contactless smart cards. But as you can see, it shares many of the same features as Proxs, but it adds some new ones like larger memory, multi-application, very high security, true read/write and extremely high security again when compared to Proxs and it's ISO standardized.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Card Technology Developments and Gap Analysis Interagency Report."}]}
{"id": "nist_02732", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TR-2997 in Standard Security Label for GOSIP_ an Invitational Workshop? (Part 3) Control TR-2997: ecurity Labels Jon Graff, Ph.D. ## I. Security Policies Security Policies form the foundation for the architecture and design of a Trusted Computer Base (TCB) or a Trusted Computer system or network. The policy defines the philosophy and methods for obtaining and assuring security of the information and processes within the system. The security policies set forth in the DoD Trusted Computer System Evaluation Criteria (Orange Book) and the DoD Trusted Network Interpretation (Red Book) arc based on the trusted \"reference monitor\" concept. The reference monitor's function is to ensure that access is only permitted when the subject's and object's label meet the requirements set forth in the security policy. TTie concept calls for the trusted reference monitor to examine \"labels\" to determine if a \"subject\" (an active agent, such as a calling program or a human) has permission to access an \"object\" (passive resource such as a piece of data). The subject's label indicates the characteristics that an object must have in order for a subject to be permitted to access the object. The object's label identifies what characteristics the subject must have in order to be permitted to access the object. ## A. The Bell and LaPadula Family of Security Policies The Bell and LaPadula family of security policies (BLFSP) are based on a reference monitor that requires sensitivity-levels as a mechanism for policy inforcement. The model is based on the environment in which multiple subjects may have access to multiple objects. The reference monitor adjudicates the access control between subjects and objects by comparing their \"sensitivity labels\" according to the Mandatory Access Control (MAC) policy. The reference monitor permits a subject to access an object only if the subject's and object's sensitivity labels fulfill the requirements of the security policy. The important point of this discussion is that sensitivity labeling is a required pan of maintaining the BLFSP. ## B.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Standard Security Label for GOSIP_ an Invitational Workshop."}]}
{"id": "nist_02733", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Review of U.S. and European Security Evaluation Criteria provide? (Section 37) nge Book; Red Book; security evaluation criteria, trust; trusted computer system 13. AVAILABIUTY UNUMITED FOR OFFICIAL DISTRIBUTION. DO NOT RELEASE TO NATIONAL TECHNICAL INFORMATION SERVICE (NTIS). JL ORDER FROM SUPERINTENDENT OF DOCUMENTS, U.S. GOVERNMENT PRINTING OFFICE, WASHINGTON, DC 20402. ORDEP FROM NATIONAL TECHNICAL INFORMATION SERVICE (NTIS), SPRINGFIELD, VA 22161. 14. NUMBER OF PRINTED PAGES 29 - IS. PRICE A03 1. PUBUCATION OR REPORT NUMBER NISTIR 4774 2. PERFORMINQ ORGANIZATION REPORT NUMBER 3. PUBUCATION DATE MARCH 1992 'oi'(ft3i''''o-&gt; ocieuS niSH' s. ; &lt;t&gt;x 3 4'} c^'i- . 0 \u2022''4 ';\u00bb ^.iiX'i'iV.y . '7 vy S-'~- \u2022 - \\ . '&gt;\\ iVv % -T V,. ^ ' i, ' ' -\u2022&gt;'&lt;f'\u00bb/'' v'', \u2022 '' 5SI Jfi. vy?v v-^yryw m iiiA: mn", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Review of U.S. and European Security Evaluation Criteria."}]}
{"id": "nist_02734", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.6.2 Configure Stealthwatch to Forward Events according to NIST Data Confidentiality_ Detect, Respond to, and Recover from Data Breaches According to Data Confidentiality_ Detect, Respond to, and Recover from Data Breaches, 2.6.2 Configure Stealthwatch to Forward Events: 1. Log on to the Stealthwatch Management Console web interface. 2. Navigate to Configure &gt; Response Management . 3. Click the Actions tab. 4. Click the three dots next to Send to Syslog and click Edit . 5. Set the action to Enabled . 6. Enter the address of the Helix Communications Broker. 7. Enter the port that you selected earlier. <!-- image --> 8. Click Save . 9. Click the Rules tab. 10. On the Actions tab, you can use some of the existing rules or create your own. 11. To create your own, click Add New Rule . For the purposes of this example, we select FlowCollector System Alarm . 12. Enter a name for the rule. 13. Ensure the rule is Enabled . 14. Click the plus sign under 'Rule is triggered if'. You can select conditions for the rule to trigger, based on severity, processing time, and type. <!-- image --> <!-- image --> 15. Enable Send to Syslog in the Associated Actions section. You can enable syslog messages for when the alarm becomes active and inactive. 16. You can also configure email alerts through this interface to improve the response time for incidents (this is a separate Action that needs to be edited on the Actions tab). 17. Click Save . <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Data Confidentiality_ Detect, Respond to, and Recover from Data Breaches."}]}
{"id": "nist_02735", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN) say about 4.1.6. Identify: Supply Chain Risk Management? (Part 1) According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN), 4.1.6. Identify: Supply Chain Risk Management: 4.1.6. Identify: Supply Chain Risk Management The organization's priorities, constraints, risk tolerances, and assumptions are established and used to support risk decisions associated with managing supply chain risk. The organization has established and implemented processes to identify, assess, and manage supply chain risks. Supply chain risk management (SCRM) is typically an intra-organization function. In the context of HSNs, organizations may consider the partner's SCRM so that the impacts of any risk inherited by partners are understood and within the level of the organization's tolerance. The Supply Chain Risk Management category has five subcategories that apply to HSNs. Table 6. Supply Chain Risk Management Category for the Identify Function. | Subcategory | Applicability to HSNs | Informative References | |----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|---------------------------------------------------------------------------| | ID.SC-1: Cyber supply chain risk management processes are identified established, assessed, managed, and agreed to by organizational stakeholders. | Applicable, no HSN-specific considerations. | NIST SP 800-53 Rev.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)."}]}
{"id": "nist_02736", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities provide? (Section 34) he pathway for the exploita/t\\_i.ligaon of a vulnerability. - A security failure is a viola/t\\_i.ligaon of a system security requirement caused by the exploita/t\\_i.ligaon of a security vulnerability. The BF security concept de/uniFB01ni/t\\_i.ligaons are contextually visualized in Fig. 7. Following the blue solid ini/t\\_i.ligaal arrow, a security vulnerability may start with a so/f\\_t.ligaware or /uniFB01rmware security bug (i.e., a code or speci/uniFB01ca/t\\_i.ligaon defect within an opera/t\\_i.ligaon). Following the green dashed arrow, a vulnerability chain may also start from a hardware defect-induced fault . For more details, refer to the forthcoming SP 800-231A, Bugs Framework: Security Concepts . Fixing the bug or hardware defect-induced fault will resolve the vulnerability, as well as any other vulnerability with the same root cause. Fixing a propagated fault, including the cause of the /uniFB01nal error at the sink, will only mi/t\\_i.ligagate the vulnerability. Occasionally, several vulnerabili/t\\_i.ligaes must converge at their /uniFB01nal errors for an exploit to be harmful. Fixing the bug or star/t\\_i.ligang fault of at least one of the chains would avoid the failure. An exploit of a vulnerability may result in a fault star/t\\_i.ligang a new faults-only vulnerability. Fixing the bug or star/t\\_i.ligang fault of the /uniFB01rst vulnerability will resolve the en/t\\_i.ligare chain of vulnerabili/t\\_i.ligaes. Fig. 7. BF security concepts <!-- image --> The BF security bugs and related faults landscape covers the opera/t\\_i.ligaons (i.e., the BF opera/t\\_i.ligaons) in so/f\\_t.ligaware, /uniFB01rmware, and hardware execu/t\\_i.ligaon phases at appropriate levels of abstrac/t\\_i.ligaon. A BF opera/t\\_i.ligaon is the minimal input-process-output code that -because of a bug or fault -results in an error that propagates to another fault or is /uniFB01nal (see Sec. 3.1).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities."}]}
{"id": "nist_02737", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-002 in Guidelines for Smart Grid Cybersecurity? (Part 235) Control IP-002: the level of module physical security required. 4.2.2 Key Management Systems for Smart Grid 4.2.2.1 Public Key Infrastructure 4.2.2.1.1 Background Certificates are issued with a validity period. The validity period is defined in the X509 certificate with two fields called \u201cnotBefore\u201d and \u201cnotAfter.\u201d The notAfter field is often referred to as the expiration date of the certificate. As will be shown below, it is important to consider certificates as valid only if they are being used during the validity period. If it is determined that a certificate has been issued to an entity that is no longer trustworthy (for example the certification was issued to a device that was lost, stolen, or sent to a repair depot), the certificate can be revoked. Certificate revocation lists are used to store the certificate serial number and revocation date for all revoked certificates. An entity that bases its actions on the information in a certificate is called a Relying Party (RP). To determine if the RP can accept the certificate, the RP needs to check the following criteria, at a minimum: 1. The certificate was issued by a trusted CA. (This may require the device to provide or the RP to obtain a chain of certificates back to the RP\u2019s trust anchor.) 2. The certificates being validated (including any necessary chain back to the RP\u2019s trust anchor) are being used between the notBefore and notAfter dates. 3. The certificates are not in an authoritative CRL. 4. Other steps may be required, depending on the RP\u2019s local policy, such as verifying that the distinguished name of the certificate subject or the certificate policy fields are appropriate for the given application for which the certificate is being used. This section focuses primarily on steps 2 and 3.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02738", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-256 in PIV Data Model Test Guidelines? (Part 164) Control HA-256: icate expiration date value is earlier than or equal to the sunset date specified in Table 3-3 of SP80078 for the ithm from Step 4. that field is populated with SHA-256 (OID = 2.16.840.1.101.3.4.2.1). For the other RSA algorithms, the pulated with NULL. For ECDSA, the d is absent. algor 3. From Step 4: If the algorithm value is id-RSASSA-PSS, verify the signature->parameters parameters fiel parameters fiel d is po | ## 11.1.1.2 Verify subject public key algorithm | Purpose | Co firms that the public key algorithm used for generating the keys is n as specified in Table 3-5 of SP80078. | |--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Reference(s) | 1. 3. SP80078, Section 3.2.1 2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: PIV Data Model Test Guidelines."}]}
{"id": "nist_02739", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Security strategies for preventing credential abuse and stuffing attacks (MS-SS-11): according to NIST Security Strategies for Microservices-based Application Systems According to Security Strategies for Microservices-based Application Systems, Security strategies for preventing credential abuse and stuffing attacks (MS-SS-11):: - A run-time prevention strategy for credential abuse is preferable to an offline strategy. A threshold for a designated time interval from a given location (e.g., IP address) for the number of login attempts should be established; if the threshold is exceeded, preventive measures must be triggered by the authentication/authorization server. This feature must be present when a bearer token is used, to detect its reuse and enforce prevention. - A credential-stuffing detection solution has the capability to check user logins against the stolen credential database and warn legitimate users that their credentials have been stolen. - Configure IDS and boundary devices to detect the following: (a) a denial of service attack and raise an alert before the service is no longer accessible, and (b) a distributed network probe. - Configure service hosts to scan file uploads and the contents of each container's memory and file system for resident malware threats.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, token. Contains security framework guidance for authentication systems. Source: Security Strategies for Microservices-based Application Systems."}]}
{"id": "nist_02740", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does The Network Security Center_ a System Level Approach to Computer Network Security say about 4.0 THE OVERALL NETWORK SECURITY APPROACH? (Part 1) According to The Network Security Center_ a System Level Approach to Computer Network Security, 4.0 THE OVERALL NETWORK SECURITY APPROACH: 4.0 THE OVERALL NETWORK SECURITY APPROACH The network security solution approach which is advocated here is based on the usage of one or more Network Security Centers (NSCs) as global access control and auditing mechanisms, as well as a \"security interface\" between each site and the network. This interface includes a remotely keyable cryptographic device which, due to its capabilities of key management and interface protocols, is called a Network Cryptographic Device (NCD). All such encryption is end-to-end across the network, i.e., between the NCDs at the two communicating sites. In addition to the usual message protection on the communication links, end-to-end encryption has the following advantages over link-by-link encryption: - (1) Information is protected in intermediate switches as well as on the communication links. This also minimizes the verification concerns for the switches. - (2) Any misdelivered messages are unintelligible to the recipient. - (3) The ongoing (properly deciphered) communication gives implicit and continual authentication of the two communicating devices. - (4) The encryption keying mechanism can be utilized to initially authenticate the NCD (and its data processing device) to the NSC. - (5) Access control enforcement is possible by means of the keying of the two NCDs (by the NSC). Only NCDs with matching keys can communicate. The operation of the NCDs and the NSC can best be described by an example. Suppose that a user is operating a terminal which is connected to the network via an NCD. The user wishes to communicate with a host computer which is also connected to the network via an NCD.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, key management. Contains security framework guidance for authentication systems. Source: The Network Security Center_ a System Level Approach to Computer Network Security."}]}
{"id": "nist_02741", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain B.3.11 Ephemeral Key Pairs according to NIST Recommendation for Key Management_ Part 1 \u2013 General According to Recommendation for Key Management_ Part 1 \u2013 General, B.3.11 Ephemeral Key Pairs: Ephemeral key-agreement keys are generated and distributed during a single key-agreement transaction (e.g., at the beginning of a communication session) and should not be reused. These key pairs are used to establish a shared secret (often in combination with static key pairs); the shared secret is subsequently used to derive shared keying material. Not all key-agreement schemes use ephemeral key pairs, and when used, not all entities have an ephemeral key pair (see SP 800-56A).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02742", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations say about 6.2.13 Key Backup, Archiving and Recovery? According to Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations, 6.2.13 Key Backup, Archiving and Recovery: OMB Guidance to Federal Agencies on Data Availability and Encryption , 26 November 2001, states that agencies must address information availability and assurance requirements through appropriate data recovery mechanisms such as cryptographic key recovery. For each CKMS, the CKMS PS should prescribe any roles, responsibilities, facilities, and procedures necessary for all organizational elements to backup, archive and recover critical key information, with the necessary integrity mechanisms successfully verified for the stored information, in the event of the loss or expiration of the operational copy of cryptographic keys under which the data is protected. Backups support recovering the current operational keys. Archives support the recovery of keys, primarily for the recovery of information after the key's cryptoperiod has expired. Key backup, archive and recovery are normally the responsibility of the Central Oversight Authority, or its organizational equivalent, although mechanisms to support recovery may be included in other components of a CKMS. Part 1, Appendix B.5, contains general key recovery recommendations that should be included in or referenced by the CKMPS. Examples of key recovery policies include the Key Recovery Policy for The Department of the Treasury Public Key Infrastructure (PKI) , Federal Public Key Infrastructure Key Recovery Policy, and Key Recovery Policy for External Certification Authorities .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations."}]}
{"id": "nist_02743", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Status Report on the First Round of the SHA-3 Cryptographic Hash Algorithm Competition say about Second Round Candidates? According to Status Report on the First Round of the SHA-3 Cryptographic Hash Algorithm Competition, Second Round Candidates: | BLAKE | Gr\u00f8stl | Shabal | |--------------------|----------|-----------| | BLUE MIDNIGHT WISH | Hamsi | SHAvite-3 | | CubeHash | JH | SIMD | | ECHO | Keccak | Skein | | Fugue | Luffa | | In a few cases, a submitted design was selected in part for its uniqueness and elegance. NIST generally favored those designs that were based on clear design principles or otherwise illustrative of an innovative idea. NIST feels that the diversity of designs will provide an opportunity for cryptographers and cryptanalysts to expand the scope of ideas in their field, and it will also be less likely that a single type of attack will eliminate the bulk of the candidates remaining in the competition.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the First Round of the SHA-3 Cryptographic Hash Algorithm Competition."}]}
{"id": "nist_02744", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cloud Computing Synopsis and Recommendations say about Service Models:? (Part 2) According to Cloud Computing Synopsis and Recommendations, Service Models:: g network, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations. Cloud Infrastructure as a Service (IaaS). The capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications; and possibly limited control of select networking components (e.g., host firewalls).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cloud Computing Synopsis and Recommendations."}]}
{"id": "nist_02745", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.2.3.3 Round 3 Analysis according to NIST Third-Round Report of the SHA-3 Cryptographic Hash Algorithm Competition According to Third-Round Report of the SHA-3 Cryptographic Hash Algorithm Competition, 4.2.3.3 Round 3 Analysis: Naya-Plasencia et al. [39] extended their previous analysis to produce semi-free-start internal near collisions on 37 rounds of the JH compression function, with 2 352 time and 2 57.6 memory complexity, and used similar techniques to find differential characteristics for all 42 rounds of the E8 permutation, with 2 304 time and 2 57.6 memory complexity. Table 13 summarizes the cryptanalysis results on JH's Round 3 submission. Table 13. Summary of Cryptanalysis Results on JH's Round 3 Submission | Target | Attack type | Output | Variant | CF Call | Memory | Reference | |-------------|-----------------------|----------|-----------|-----------|----------|-------------| | Permutation | Differential Property | all | 42 rounds | 2 304 | 2 57.6 | [39] | | Permutation | Differential Property | all | 42 rounds | 2 352 | 2 57.6 | [39] | | CF | SFS near collision | all | 37 rounds | 2 352 | 2 57.6 | [39] | | CF | SFS near collision | all | 26 rounds | 2 112 | 2 57.6 | [39] |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Third-Round Report of the SHA-3 Cryptographic Hash Algorithm Competition."}]}
{"id": "nist_02746", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Managing Information Security Risk_ Organization, Mission, and Information System View say about 2.6.1 Establishing Trust Among Organizations? (Part 4) According to Managing Information Security Risk_ Organization, Mission, and Information System View, 2.6.1 Establishing Trust Among Organizations: use of the services/information or the participation in the partnership, is at an acceptable level; and - Recognize that decisions to establish trust relationships are expressions of acceptable risk. The degree of trust that an organization places in external organizations can vary widely, ranging from those who are highly trusted (e.g., business partners in a joint venture that share a common business model and common goals) to those who are less trusted and may represent greater sources of risk (e.g., business partners in one endeavor who are also competitors or adversaries). The specifics of establishing and maintaining trust can differ from organization to organization based on mission/business requirements, the participants involved in the trust relationship, the criticality/sensitivity of the information being shared or the types of services being rendered, the history between the organizations, and the overall risk to the organizations participating in the relationship. Appendix G provides several trust models that organizations can use when dealing with external organizations. In many situations, the trust established between organizations may not allow a full spectrum of information sharing or a complete provision of services. When an organization determines that 50 External information system services are services that are implemented outside of the system's traditional authorization boundary (i.e., services that are used by, but not a part of, the organizational information system). 51 External providers or mission/business partners can be public or private sector entities, domestic or international.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Managing Information Security Risk_ Organization, Mission, and Information System View."}]}
{"id": "nist_02747", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Malware Incident Prevention and Handling for Desktops and Laptops say about 2.2 Attacker Tools? (Part 2) According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops, 2.2 Attacker Tools: b browser plug-in provides a way for certain types of content to be displayed or executed through a web browser. Malicious web browser plug-ins can monitor all use of a browser. - \uf03c E-Mail Generators. An email generating program can be used to create and send large quantities of email, such as malware and spam, to other hosts without the user's permission or knowledge. - \uf03c Attacker Toolkits. Many attackers use toolkits containing several different types of utilities and scripts that can be used to probe and attack hosts, such as packet sniffers, port scanners, vulnerability scanners, password crackers, and attack programs and scripts. Because attacker tools can be detected by antivirus software, some people think of them as forms of malware. However, attacker tools have no infections capability on their own; they rely on malware or other attack mechanisms to install them onto target hosts. Strictly speaking, attacker tools are not malware, but because they are so closely tied to malware and often detected and removed using the same tools, attacker tools will be covered where appropriate throughout this publication.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, malware. Contains technical security guidance that could inform defensive posture. Source: Guide to Malware Incident Prevention and Handling for Desktops and Laptops."}]}
{"id": "nist_02748", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Section 507) rvices procured and implemented by organiza\ue000on; third-party creden\ue000al veri\ufb01ca\ue000on records; evidence of third-party creden\ue000als; third-party creden\ue000al authoriza\ue000ons; other relevant documents or records]. IA-08(02)-Interview [SELECT FROM: Organiza\ue000onal personnel with system opera\ue000ons responsibili\ue000es; organiza\ue000onal personnel with informa\ue000on security responsibili\ue000es; system/ network administrators; system developers; organiza\ue000onal personnel with account management responsibili\ue000es]. IA-08(02)-Test [SELECT FROM: Mechanisms suppor\ue000ng and/or implemen\ue000ng iden\ue000\ufb01ca\ue000on and authen\ue000ca\ue000on capabili\ue000es; mechanisms that accept external creden\ue000als]. T h i s p u b l i c a \ue000 o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h \ue003 p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P. 8 0 0 - 5 3 A r 5 CHAPTER FOUR PAGE 267 Reference produced from open data h\ue003ps://github.com/usnistgov/oscal-content T h i s p u b l i c a \ue000 o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h \ue003 p s : / / d o i . . o r g / 1 0 6 0 2 8 / N I S T . S P. 8 0 0 - 5 3 A r 5 NIST SP 800-53A, REV. 5 ASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS IA-08(03) IDENTIFICATION AND AUTHENTICATION (NON-ORGANIZATIONAL USERS) | USE OF FICAM-APPROVED PRODUCTS [WITHDRAWN: Incorporated into IA-08(02).] IA-08(04) IDENTIFICATION AND AUTHENTICATION (NON-ORGANIZATIONAL USERS) | USE OF DEFINED PROFILES ASSESSMENT OBJECTIVE: Determine if: IA-08(04)_ODP iden\ue000ty management pro\ufb01les are de\ufb01ned; IA-08(04) there is conformance with <IA-08(04)_ODP iden\ue000ty management pro\ufb01les> for iden\ue000ty management. POTENTIAL ASSESSMENT METHODS AND OBJECTS: IA-08(04)-Examine [SELECT FROM: Iden\ue000\ufb01ca\ue000on and authen\ue000ca\ue000on policy; system security plan; system design documenta\ue000on; system con\ufb01gura\ue000on se\ue001ngs and associated documenta\ue000on; system audit records; other relevant documents or records].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Assessing Security and Privacy Controls in Information Systems and Organizations."}]}
{"id": "nist_02749", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3 provide? (Section 130) Table 1: Draft Security Operational Taxonomy Mapping to the NBDRA Components | Activities | Description | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | System Orchestrator | | | \u2022 Policy Enforcement \u2022 Security Metadata Model \u2022 Data Loss Prevention, Detection \u2022 Data Life Cycle Management \u2022 Threat and Vulnerability Management \u2022 Mitigation \u2022 Configuration Management \u2022 Monitoring, Alerting \u2022 Malware Surveillance and Remediation \u2022 Resiliency, Redundancy, and Recovery \u2022 Accountability \u2022 Compliance \u2022 Forensics \u2022 Business Risk Model | Several security functions have been mapped to the System Orchestrator block, as they require architectural level decisions and awareness.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, malware. Contains technical security guidance that could inform defensive posture. Source: NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3."}]}
{"id": "nist_02750", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3 provide? (Section 227) Available: http://dx.doi.org/10.1109/PST.2016.7907022 | Brief Description | Safety Level 1 | Safety Level 2 | Safety Level 3 | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| | Integration of key management practices with domain models | Integration of key management practices with domain models | Integration of key management practices with domain models | Integration of key management practices with domain models | | Tokenization and key management practices are frequently central to managing proper access to systems and data, especially across enterprises.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, token. Contains security framework guidance for authentication systems. Source: NIST Big Data Interoperability Framework_ Volume 4, Security and Privacy Version 3."}]}
{"id": "nist_02751", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Derived Personal Identity Verification (PIV) Credentials say about Appendix D References? (Part 3) According to Derived Personal Identity Verification (PIV) Credentials, Appendix D References: ederal Networks and Critical Infrastructure , May 11, 2017. Available: - [17] M. Barrett et al., The Cybersecurity Framework: Implementation Guidance for Federal Agencies, Draft, NIST Interagency Report 8170, Gaithersburg, Md., May 2017. Available: - [18] C. Brown et al., Assessing Threats to Mobile Devices &amp; Infrastructure: The Mobile Threat Catalogue, Draft, NIST Interagency Report 8144, Gaithersburg, Md., Sept. 2016. Available: - [19] NIST. National Vulnerability Database. [Online]. Available: https://nvd.nist.gov/. - [20] NIST. CVE-2016-6716 Detail, National Vulnerability Database. [Online]. Available: https://nvd.nist.gov/vuln/detail/CVE-2016-6716. - [21] S. Quirolgico et al., Vetting the Security of Mobile Applications , NIST SP 800-163, Gaithersburg, Md., Jan. 2015. Available: https://doi.org/10.6028/NIST.SP.800-163 - [22] The MITRE Corporation . Common Vulnerabilities and Exposures (CVE). [Online]. Available: https://cve.mitre.org/. - [23] U.S. General Services Administration, Decision for Standard Assessment &amp; Authorization, Authorization to Operate Letter, Nov. 3, 2016. Available: \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ - [24] E. Simmon, DRAFTEvaluation of Cloud Computing Services Based on NIST 800-145, NIST SP 500-322, Gaithersburg, Md., Apr. 2017. Available: ng\\_services\\_based\\_on\\_nist\\_800-145\\_20170427clean.pdf.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, cve-. Contains technical security guidance that could inform defensive posture. Source: Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_02752", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2017 NIST_ITL Cybersecurity Program Annual Report say about Cryptographic Hash Algorithms? (Part 2) According to 2017 NIST_ITL Cybersecurity Program Annual Report, Cryptographic Hash Algorithms: ons will produce unrelated outputs. In December 2016, NIST further expanded the uses of KECCAK with the publication SP 800-185, SHA3 Derived Functions: cSHAKE, KMAC, TupleHash and ParallelHash . It provides four new types of functions, as indicated in the title, each with the same two supported security strengths: - cSHAKE128 and cSHAKE256 are XOFs that can be 'customized' for individual users or applications, so that their outputs would be unrelated to any other SHAKE variants; - KMAC128 and KMAC256 are keyed-hash functions with variable-length outputs, i.e., pseudorandom functions (PRFs); - TupleHash128 and TupleHash256 are hash functions on tuples of input strings; and - ParallelHash128 and ParallelHash256 are hash functions that can exploit parallel processing to efficiently hash long messages. NIST is currently considering the development of a parallelizable hashing mode and XOF mode for generic hash functions (e.g., SHA-2). These modes would allow the SHA-2 family to achieve some of the functionality of the SHA-3 family.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02753", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI) provide? (Section 66) tection, rather than on reliable, automated security mechanisms, makes it critical that trust and reliability assessments of management, operators, and maintenance personnel are current and upto-date. Many of the assessment procedures rely on interactions among the Assessor, issuer management, and facilities staff. Interviews with all involved personnel and observations of all PIV processes are required. On-site visits, real-time observations, and reviews of processes are essential, as the Assessor must not rely solely on documentation to determine if a given issuer control has been implemented. In order to assess the capability and reliability of an issuer, one or more assessment procedures associated with each issuer control have to be completed. An assessment procedure is carried out using one or more of the following assessment methods. (The assessment methods associated with an assessment procedure are given in parenthesis in Table G.1 and Table G.2.) - \uf0b7 Review - An evaluation of documentation that describes plans, policies, and procedures in order to verify that they are adequate, understood by management and operations personnel, and that they are in accordance with applicable policies, regulations, standards, technical guidelines, and organizational guidance. - \uf0b7 Interview - a directed conversation with one or more issuer personnel in which both preestablished and follow-on questions are asked, responses documented, discussion encouraged, and conclusions reached. - \uf0b7 Observe - a real-time viewing of PIV processes in operation, including all information system components of the issuer involved in creation, issuance, maintenance, and termination of PIV Cards or Derived PIV Credentials. - \uf0b7 Test - an evaluation of a component against a set of relevant PIV specifications using applicable test methods and metrics (as given in the associated assessment procedure in Table G.1 and Table G.2).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_02754", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters? (Part 67) Control HA-1: Glossary ## base point A fixed elliptic curve point that generates the group used for elliptic curve cryptography. ## group order Cardinality of the group. ## identity Unique group element 0 for which x + 0 = x for each group element x , relative to the binary group operator +. ## inverse For some group element x , the unique element y for which x + y is the identity element relative to the binary group operator + ( y is usually denoted as -x ). ## isogeny A (non-constant) mapping from an elliptic curve to a second elliptic curve, which preserves point addition and fixes the identity point. ## isomorphism (of elliptic curves) A bijective mapping from one elliptic curve to another, which maps addition (on the first curve) to addition (on the image curve). ## point at infinity Identity element of a Montgomery curve or a curve in short-Weierstrass form. ## point order Smallest non-zero multiple of a group element that results in the group's identity element. ## quadratic twist Certain elliptic curve related to a specified elliptic curve. ## square The property that some element x of a finite field GF( q ) can be written as x = z 2 for some element z in the same field GF( q ).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters."}]}
{"id": "nist_02755", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Identity and Access Management for Electric Utilities say about Java Application? (Part 16) According to Identity and Access Management for Electric Utilities, Java Application: a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_02756", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Automation Support for Security Control Assessments_ Software Vulnerability Management provide? (Section 16) | 6 | | | | 2.3.1 Common Vulnerabilities and Exposures (CVEs) ..................................7 | | | | | 2.3.2 Common Weakness Enumerations (CWEs).......................................10 | | | | | 2.3.3 Roles for Mitigation of CVEs and CWEs.............................................11 | | | | 2.4 Example VUL Data Requirements................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Vulnerability Management."}]}
{"id": "nist_02757", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does SHA-3 Derived Functions_ cSHAKE, KMAC, TupleHash, and ParallelHash provide? (Section 2) o copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-185 Natl. Inst. Stand. Technol. Spec. Publ. 800-185, 32 pages (December 2016) CODEN: NSPUE2 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-185 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. 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 National Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930 Email: SP800-185@nist.gov All comments are subject to release under the Freedom of Information Act (FOIA).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: SHA-3 Derived Functions_ cSHAKE, KMAC, TupleHash, and ParallelHash."}]}
{"id": "nist_02758", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3 provide? (Section 69) nition | A container for a single component. The types of components are defined in Section 3.1.2. | A container for a single component. The types of components are defined in Section 3.1.2. | A container for a single component. The types of components are defined in Section 3.1.2. | | Properties | Properties | Properties | Properties | | Name | Type | Count | Property Definition | | id | literal - ID | 1 | The identifier for the component. This identifier SHALL be globally unique (see Section 3.1.3). | | timestamp | literal - dateTime | 1 | Indicates when the <ds:component> was created or last updated.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3."}]}
{"id": "nist_02759", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TR-1 in Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1? (Part 108) Control TR-1: ----------------------------------| | Category | The subdivision of a Function into groups of cybersecurity outcomes, closely tied to programmatic needs and particular activities. Examples of Categories include 'Asset Management,' 'Identity Management and Access Control,' and 'Detection Processes.' | | Critical Infrastructure | 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 cybersecurity, national economic security, national public health or safety, or any combination of those matters. | | Cybersecurity | The process of protecting information by preventing, detecting, and responding to attacks. | | Cybersecurity Event | A cybersecurity change that may have an impact on organizational operations (including mission, capabilities, or reputation). | | Cybersecurity Incident | A cybersecurity event that has been determined to have an impact on the organization prompting the need for response and recovery. | | Detect (function) | Develop and implement the appropriate activities to identify the occurrence of a cybersecurity event. | | Framework | A risk-based approach to reducing cybersecurity risk composed of three parts: the Framework Core, the Framework Profile, and the Framework Implementation Tiers. Also known as the 'Cybersecurity Framework.' | | Framework Core | A set of cybersecurity activities and references that are common across critical infrastructure sectors and are organized around particular outcomes. The Framework Core comprises four types of elements: Functions, Categories, Subcategories, and Informative References.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, identity management. Contains security framework guidance for authentication systems. Source: Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1."}]}
{"id": "nist_02760", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EG-21 in Guidelines for Access Control System Evaluation Metrics? (Part 21) Control EG-21: The syntax is a strict subset of XACML; it is suitable for specifying a wide range of policies, including authorization, quality-of-service, quality-of protection, reliable messaging, privacy, and application-specific service options.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Guidelines for Access Control System Evaluation Metrics."}]}
{"id": "nist_02761", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Standard Security Label for GOSIP_ an Invitational Workshop provide? (Section 15) Mr. Housley added that there should be a reference in the SSL text that indicates what document provides usage rules for this label. The full text of the Xerox comments appear later in this document. Hilary Hosmer (Data Security) presented the concept of multipolicy. She pointed out that OSI security labels should be able to support co-existing security policies . Ms. Hosmer stated that allowing only one Security Level field in the SSL is a serious limitation because it makes it difficult to support multiple security policies. David Crawford (Canadian Defense) discussed Canada *s coexisting security policies. He explained the relationship between security levels that cover the equivalents to U.S. Classified and Unclassified but Sensitive. Thomas Bartee (IC Staff) presented a position paper justifying a request for an additional tag type for the Standard Security Label (SSL) . Mr. Bartee *s argument was that the tags currently specified in the SSL are geared towards indicating restriction markings. The addition of a \"reversed' bit map type would make it easier to specify permissive markings such as release indicators. He mentioned that such an approach is currently used in the Director of Central Intelligence Office (DCI) Extended IP Security Option and by the Compartmented Workstation program. Most of the second day of the workshop was devoted to discussion of issues raised in the presentations of the first day. The group listed and prioritized the different issues. This ordered list guided the discussion of the relevant topics. After discussing each issue an informal vote was taken. The position taken by the group was recorded as the workshop's output. That output is presented in the following section. The following list of issues were identified and discussed by the workshop attendees. The statements listed under each issue were subject to an informal vote and represent the group's position. This list constitutes the workshop's output.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, compartmented. Contains guidance on protecting sensitive government information. Source: Standard Security Label for GOSIP_ an Invitational Workshop."}]}
{"id": "nist_02762", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is This publication is available free of charge from according to Report on Lightweight Cryptography? This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8114", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report on Lightweight Cryptography."}]}
{"id": "nist_02763", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control BP-92049 in Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI? (Part 100) Control BP-92049: CD: POSIX Conformance Document, HP 9000 Computers, Fourth Edition, 1994. as modified by POSIX Conformance Document, HP-UX Compartment Mode Workstation Addendum, HP 9000 Computers, First Edition, 1994. GTI - Supported by Product MFS - Supported by Product MC - Supported by Product AP - Supported by Product 151-2IBM001 Issued: 03/08/94 Type: Native Product Supplier: International Business Machines Corporation Product: MVS/ESA 4.3 OpenEdition\u201c 1.0 PCD: OpenEdition MVS POSIX 1 Conformance Document, Document Number SC23-30 11-00 GTI - NOT Provided by Product MFS - Supported by Product MC - NOT Provided by Product AP - Supported by Product Computer Hardware Supplier: International Business Machines Corporation Computer Hardware Product: ES/9000-570 C Compiler: IBM SAA AD/Cycle\u00ae C/370 Version 1 Release 2 APTL 100342 Mindcraft, Inc. 151-2IBM002 Issued: 02/17/94 Type: Native Product Supplier: International Business Machines Corporation Product: AIX Version 3-2.5 for RISC System/6000 with RTFs: U423984, U424399, U424507, U424590, U425456, U424587, U425384, U425988, U425997, U426001, U426014, U425858 PCD: AIX Version 3.2 POSIX Conformance Document GTI - Supported by Product MFS - Supported by Product MC - Supported by Product AP - Supported by Product Computer Hardware Supplier: International Business Machines Corporation Computer Hardware Product: RISC System/6000, Model 590 Computer Hardware Supplier: Hewlett-Packard Company Computer Hardware Product: Series 9000 Model 770 C Compiler: XLC Version 1 , Release 3 APTL 100342 Mindcraft, Inc. C Compiler: HP C Compiler Version XI 0.1 APTL 100342 Mindcraft, Inc. 151-2HPC009 Issued: 03/02/95 Product Supplier: Hewlett-Packard Company Type: Native Product: HP-UX Release 10.00 PCD: POSIX Conformance Document, HP 9000 Computers, Third Edition, 1994.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI."}]}
{"id": "nist_02764", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-1 in Derived Personal Identity Verification (PIV) Credentials? (Part 50) Control AC-1: es an authentica- tion certificate, which is an X.509 public key certificate that has been issued in accordance with the re- quirements of NIST SP 800-157 and the X.509 Certificate Policy for the U.S. Federal PKI Common Pol- icy Framework [25] | PR.AC-1 | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | Component | Product | Version | Function | Cybersecurity Framework Subcategories | |------------------------------------------|------------------------------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------| | PKI Certificate Authority | Verizon Shared Service Pro- vider | Not appli- cable | Entity that issues an authentica- tion certificate, which is an X.509 public key certificate that has been issued in accordance with the re- quirements of NIST SP 800-157 and the X.509 Certificate Policy for the U.S.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, certificate authority. Contains security framework guidance for authentication systems. Source: Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_02765", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN) say about 4.3.1. Detect: Anomalies and Events Category? (Part 4) According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN), 4.3.1. Detect: Anomalies and Events Category: e interface activity, user reports, and administrator reports. Standards-based data formatting and serialization promotes communication, interoperability, and exchange of HSN data and supporting data. Correlate events and cross-check detected anomalies from the different data and service providers. Consider including events from external and authoritative shared resources (such as open source, | NIST SP 800-53 Rev. 5 AU-6, CA-7, CP-2, IR-4, IR-5, IR-8, SI-4 NIST SP 800-160v1 3.3.7, Appendix G.2, Appendix G.3 | | DE.AE-4: The impact of events is determined. | In addition to the impact on the organization, consider the impact on the data and service providers participating in the HSN. | NIST SP 800-53 Rev. 5 CP-2, IR-4, IR-5, IR-8, SI-4 | | Subcategory | Applicability to HSNs | Informative References | |-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| | DE.AE-5: Incident alert thresholds are established. | Discussions regarding the setting and review of thresholds should include external stakeholders.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)."}]}
{"id": "nist_02766", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-256 in Fiscal Year 2021 Cybersecurity and Privacy Annual Report? (Part 58) Control HA-256: ology (NIST) in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. \u00a7 3541. 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 be appreciated by NIST. ## HOW TO CITE THIS NIST TECHNICAL SERIES PUBLICATION O'Reilly PD, II, Rigopoulos KG, Feldman L, Witte GA (2022) Fiscal Year 2021 Cybersecurity and Privacy Annual Report. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-220. https://doi.org/10.6028/NIST.SP.800-220 ## DISCLAIMER A ny 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: Fiscal Year 2021 Cybersecurity and Privacy Annual Report."}]}
{"id": "nist_02767", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control RA-3(3) in Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Control RA-3(3): CONTROL NAME RISK ASSESSMENT | DYNAMIC THREAT AWARENESS", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_02768", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is System Supplier according to Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI? System Supplier: Sequent Computer Systems Inc.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI."}]}
{"id": "nist_02769", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings say about 6 Conclusion? According to 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings, 6 Conclusion: We have described the motivations for identity federation and for attribute-based authorization in Grids. We have described our plans for addressing these motivations through integration of Shibboleth and the Globus Toolkit in order to produce a system capable of enabling attribute-based authorization in Grids, leveraging existing campus Shibboleth infrastructure, and allowing for pseudonymity.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02770", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Digital Identity Guidelines_ Federation and Assertions provide? (Section 72) ttributes, trust agreements SHOULD use a runtime decision to control attribute release, as discussed in Sec. 4.6.1.3. When the federation transaction uses an ephemeral provisioning mechanism (see Sec. 4.6.3), the IdP SHOULD request to the RP to prevent the RP from storing or correlating information between use an ephemeral federated identifier for each authorization sessions. The IdP SHALL limit the transmission of subscriber information to only that which is necessary for the system to function and is stipulated and disclosed by the trust agreement. These functions include the following: - Identity proofing, authentication, or attribute assertions (collectively 'identity service'); - A specific subscriber request to transmit the information; - Fraud mitigation related to the identity service; or - Responding to a security incident related to the identity service. If an IdP discloses information on subscriber activities at an RP to any party or processes the subscriber's attributes for any purpose other than these cases, the IdP SHALL implement measures to maintain predictability and manageability commensurate with the privacy risks that arise from the additional processing. Measures MAY include providing clear notice, obtaining subscriber consent, or enabling the selective use or disclosure of attributes. When an IdP gathers the subscriber's consent to use information outside the identity transaction, the IdP SHALL NOT make consent for the additional processing a condition of the identity service. For example, an IdP cannot require a subscriber to consent to receiving a newsletter in order to allow the subscriber to log into an RP.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Digital Identity Guidelines_ Federation and Assertions."}]}
{"id": "nist_02771", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls say about APPLICATION SYSTEM VULNERABILITIES (Published in FIPS PUB 65, pp 22-27)? (Part 3) According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls, APPLICATION SYSTEM VULNERABILITIES (Published in FIPS PUB 65, pp 22-27): area. - -Remote terminals may not be adequately protected from use by unauthorized - persons - -An unauthorized user may gain access to the system via a dial-in line and an authorized user's password. - -Passwords may be inadvertently revealed to unauthorized individuals. A user may write his password in some convenient place, or the password may be obtained from card decks, discarded printouts, or by observing the user as he types it. - -A user may leave a logged-in terminal unattended, allowing an unauthorized - person to use it. - -A terminated employee may retain access to ADP system because his name and password are not immediately deleted from authorization tables and control lists - -An unauthorized individual may gain access to the system for his own purposes (e.g., theft of computer services or data or programs, modification of data, alteration of programs, sabotage, denial of services). - -Repeated attempts by the same user or terminal to gain unauthorized access to the system or to a file may go undetected. 4. INEFFECTIVE SECURITY PRACTICES FOR THE APPLICATION. Inadequate manual checks and controls to insure correct processing by the ADP system or negligence by those responsible for carrying out these checks results in many vulnerabilities. - -Poorly defined criteria for authorized access may result in employees not knowing what information they, or others, are permitted to access. - -The person responsible for security may fail to restrict user access to only those processes and data which are needed to accomplish assigned tasks. - -Large funds disbursements, unusual price changes, and unanticipated Inventory usage may not be reviewed for correctness. - -Repeated pajnnents to the same party may go unnoticed because there is no review. - -Sensititve data may be carelessly handled by the application staff, by the mail service, or by other personnel within the organization.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls."}]}
{"id": "nist_02772", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Intrusion Detection and Prevention Systems (IDPS) provide? (Section 210) k traffic it is monitoring must pass through it. Intrusion Detection: The process of monitoring the events occurring in a computer system or network and analyzing them for signs of possible incidents. Intrusion Detection and Prevention: The process of monitoring the events occurring in a computer system or network, analyzing them for signs of possible incidents, and attempting to stop detected possible incidents. See also 'intrusion prevention'. Intrusion Detection System Load Balancer: A device that aggregates and directs network traffic to monitoring systems, such as intrusion detection and prevention sensors. Intrusion Detection System: Software that automates the intrusion detection process. Intrusion Prevention: The process of monitoring the events occurring in a computer system or network, analyzing them for signs of possible incidents, and attempting to stop detected possible incidents. See also 'intrusion detection and prevention'. Intrusion Prevention System: Software that has all the capabilities of an intrusion detection system and can also attempt to stop possible incidents. Also called an intrusion detection and prevention system. Jamming: Emitting electromagnetic energy on a wireless network's frequencies to make them unusable by the network. Malware: 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. Management Network: A separate network strictly designed for security software management. Management Server: A centralized device that receives information from sensors or agents and manages them.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: malware, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Guide to Intrusion Detection and Prevention Systems (IDPS)."}]}
{"id": "nist_02773", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Engineering Trustworthy Secure Systems say about The Concept of an Adequately Secure System? (Part 1) According to Engineering Trustworthy Secure Systems, The Concept of an Adequately Secure System: The Concept of an Adequately Secure System Adequate security is a concept that enables meaningful judgments about the idealistic nature of security objectives. The definition of security expresses an ideal that encapsulates three essential characteristics of a secure system: - It enables the delivery of the required system capability despite intentional and unintentional forms of adversity. - It enforces constraints to ensure that only the desired behaviors and outcomes associated with the required system capability are realized while satisfying the first characteristic. - It enforces constraints based on a set of rules to ensure that only authorized human-tomachine and machine-to-machine interactions and operations are allowed to occur while satisfying the second characteristic. These characteristics are to be achieved to the extent practicable, resulting in a gap between the ideal secure system and the security performance that the system can dependably achieve. 24 The judgment that a system is adequately secure 25 requires an evidence-based determination that security performance is optimized against all other performance objectives and constraints. The scope of conditions relevant to security and the acceptable level of security are specific to stakeholder needs. To be adequately secure, the system: - Meets minimum tolerable levels 26 of security, as determined by experience, analysis, or a combination of both - Is as secure as reasonably practicable (ASARP) 21 Active entities exhibit behavior (e.g., a process in execution) while passive entities do not (e.g., data, file). 22 At the highest level of assurance, security policies are formally specified and verified. 23 Privileges are also referred to as authorizations or rights. 24 Because system security is asymmetric - that is, things can be observed to be insecure, but no observation allows one to declare an arbitrary system secure [22] - the ideal cannot be achieved without some uncertainty.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_02774", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST Test Personal Identity Verification (PIV) Cards Version 2 say about Authority Key Identifier :? According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Authority Key Identifier :: A1:A9:F2:66:2C:F8:29:F4:13:0C:7B:ED:5B:64:68:94:3D:F3:F1:BC", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_02775", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain C.2.4.2 Continuity of Operations Information Type according to NIST Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices, C.2.4.2 Continuity of Operations Information Type: Continuity of operations involves the activities associated with the identification of critical systems and processes, and the planning and preparation required to ensure that these systems and processes will be available in the event of a catastrophic event. The recommended provisional security categorization for the continuity of operations information type is as follows: Security Category = {(confidentiality, Moderate), (integrity, Moderate), (availability, Moderate)}", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices."}]}
{"id": "nist_02776", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms provide? (Section 109) (2001) Introduction to Public Key Technology and the Federal PKI Infrastructure. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-32. SP 800-32 was developed to assist agency decision-makers in determining if a PKI is appropriate for their agency and how PKI services can be deployed most effectively within a federal agency. It is intended to provide an overview of PKI functions and their applications. SP 800-38 SP 800-38A SP 800-38B SP 800-38C SP 800-38D A series of publications specifying modes of operation for block cipher algorithms (see below). Dworkin MJ (2001) Recommendation for Block Cipher Modes of Operation: Methods and Techniques. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-38A. https://doi.org/10.6028/NIST.SP.800-38A SP 800-38A defines five confidentiality modes of operation for use with an underlying symmetric-key block cipher algorithm: Electronic Codebook (ECB), Cipher Block Chaining (CBC), Cipher Feedback (CFB), Output Feedback (OFB), and Counter (CTR). When used with an approved underlying block cipher algorithm (i.e., AES or TDEA), these modes can provide cryptographic protection for sensitive computer data. Dworkin MJ (2005) 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 6, 2016. https://doi.org/10.6028/NIST.SP.800-38B SP 800-38B specifies a message authentication code (MAC) algorithm based on a symmetric-key block cipher (i.e., AES or TDEA). This block cipher-based MAC algorithm, called CMAC, may be used to provide assurance of the source and integrity of binary data.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms."}]}
{"id": "nist_02777", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Device Security_ Cloud and Hybrid Builds say about DISCLAIMER? According to Mobile Device Security_ Cloud and Hybrid Builds, DISCLAIMER: Certain commercial entities, equipment, products, 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 or NCCoE, nor is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose. National Institute of Standards and Technology Special Publication 1800-4C, Natl. Inst. Stand. Technol. Spec. Publ. 1800-4C, 109 pages, February 2019, CODEN: NSPUE2", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Cloud and Hybrid Builds."}]}
{"id": "nist_02778", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Implementation of DevSecOps for a Microservices-based Application with Service Mesh say about 3 DevSecOps - Organizational Preparedness, Key Primitives, and Implementation? According to Implementation of DevSecOps for a Microservices-based Application with Service Mesh, 3 DevSecOps - Organizational Preparedness, Key Primitives, and Implementation: DevSecOps incorporates security into the software engineering process early on. It integrates and automates security processes and tooling into all of the development workflow (or pipeline as later explained) in DevOps so that it is seamless and continuous. In other words, it can be looked upon as a combination of the three processes: Development + Security + Operations [12]. This section discusses the following aspects of DevSecOps: - Organizational preparedness for DevSecOps - DevSecOps Platform - Fundamental building blocks or key primitives for DevSecOps", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Implementation of DevSecOps for a Microservices-based Application with Service Mesh."}]}
{"id": "nist_02779", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Guidelines for Storage Infrastructure say about 4.3.3 Account Management Recommendations? (Part 1) According to Security Guidelines for Storage Infrastructure, 4.3.3 Account Management Recommendations: 4.3.3 Account Management Recommendations AC-SS-R14 - Use of accounts not associated with system users: Accounts not associated with any system user (e.g., not in Active Directory, such as 'guest,' 'anonymous,' 'nobody') should be disabled. In situations where they need to be used, they should not be mapped to any system user, and all of their default configurations (e.g., password, privileges) should be changed to conform to organization-wide policies. AC-SS-R15 - Account lockout: Users should be locked out after a certain number of unsuccessful login attempts. Certain implementations of account locking include automatic reset (account unlock) after a certain period of time or a power cycle. Automatic reset should not be allowed on sensitive storage systems. AC-SS-R16 -A local user account for emergency purposes: A single local user account should be maintained for access to storage resources in order to provide emergency-only access if the centralized authentication system is down. This account should conform to all organizational policies (e.g., password length). In addition, its usage should be allowed from a special physically protected location, and following well documented procedures that include appropriate approval of relevant stakeholders, and notification of use. AC-SS-R17 - Eliminate or disable default user accounts: The default user accounts that come with the storage system installations should be eliminated or disabled immediately, if the feature exists. When the feature to disable or eliminate does not exist or there is a justified reason to keep any of those accounts, the privileges assigned to this account should be kept to the minimum necessary. AC-SS-R18 - Limit local and default user accounts: As much as possible, eliminate the use of local and default accounts. In situations where this is not possible: - (a) Limit the use of such accounts and the privileges they have.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Security Guidelines for Storage Infrastructure."}]}
{"id": "nist_02780", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PA-5250 in Implementing a Zero Trust Architecture_ High-Level Document? (Part 7) Control PA-5250: latform, Mandiant MSV, Okta Identity Cloud, Okta Verify App, Radiant Logic RadiantOne Intelligent Identity Data Platform, SailPoint IdentityIQ, Tenable.ad, Tenable.io, Tenable NNM, and Zimperium MTD. - \uf0a7 Enterprise 2 Build 4 (E2B4) (SDP and SASE; Broadcom (with Symantec products) as PE) uses products from Broadcom (with VMware and Symantec products), Google Cloud, IBM, Mandiant, Okta, Radiant Logic, SailPoint, and Tenable. Certificates from DigiCert are also used. E2B4 components consist of Symantec Cloud Secure Web Gateway (Cloud SWG), Symantec Zero Trust Network Access (ZTNA), Symantec Cloud Access Security Broker (CASB), Symantec Endpoint Security Agent, VMware Workspace ONE UEM, Symantec DLP Cloud Detection Service, Symantec ZTNA Connector, Okta Identity Cloud, Okta Verify App, Radiant Logic RadiantOne Intelligent Identity Data Platform, SailPoint IdentityIQ, IBM Security QRadar XDR, Tenable.io, Tenable.ad, Tenable NNM, Mandiant MSV, Google Cloud, and DigiCert CertCentral. - \uf0a7 Enterprise 3 Build 4 (E3B4) (SDP; F5 as PE) uses products from F5, Forescout, Mandiant, Microsoft, Palo Alto Networks, and Tenable. Certificates from DigiCert are also used. E3B4 components consist of F5 BIG-IP, F5 NGINX Plus, F5 Access App, Microsoft AD, Microsoft Azure AD, Microsoft Azure AD Identity Governance, Microsoft Intune, Microsoft Sentinel, Tenable.io, Tenable.ad, Tenable NNM, Mandiant MSV, Forescout eyeControl, Forescout eyeExtend, Forescout eyeSight, Forescout eyeSegment, Microsoft Azure (IaaS), and DigiCert CertCentral. - \uf0a7 Enterprise 4 Build 4 (E4B4) (SDP; Microsegmentation, and EIG; Broadcom (with VMware products) as PE) uses products from Broadcom (with VMware products), IBM, Mandiant, and Tenable. Certificates from DigiCert are also used.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Implementing a Zero Trust Architecture_ High-Level Document."}]}
{"id": "nist_02781", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is EMS Data according to Cell Phone Forensic Tools_ an Overview and Analysis Update? EMS Data: Active and deleted incoming EMS Messages that exceed 160 characters were found and reported. An EMS message containing an embedded picture was found. However, the image was not correctly decoded and presented, though the text was. (Below)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis Update."}]}
{"id": "nist_02782", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Securing Property Management Systems? (Part 159) Control AM-1: he enterprise. <!-- image --> Remediant SecureONE is the privileged access management solution within the reference architecture. Additionally, it maps to the Security Analytics component of the ZTA. ## 2.6.1 Privileged Access Management System-Remediant SecureONE-Overview Remediant SecureONE provides detection and response capabilities for violations of privileged access within the enterprise. In the PMS reference design, SecureONE was deployed as a prebuilt VM appliance from the vendor. We configured the appliance with parameters necessary for our environment. The network security in place in the architecture relies on the appropriate authentication of privileged users. Once that authentication is secured, it is trusted. It is the purview of the PAM solution to prevent abuse of this trust. The location of the PAM system in the reference architecture is highlighted in Figure 2-5 below. Figure 2-5 Privileged Access Management System in the Reference Architecture <!-- image --> ## 2.6.2 Privileged Access Management System-Remediant SecureONERequirements The following subsections document the software, hardware, and network requirements for the PAM system Remediant SecureONE. Both the hardware and software requirements were included in the managed deployment provided by Remediant. ## 2.6.2.1 Hardware Requirements for the Privileged Access Management System This installation occurred on a machine with 4 CPUs, 8 GB of memory, and 100 GB of storage. ## 2.6.2.2 Software Requirements for the Privileged Access Management System This build utilized an Ubuntu 14.04 OS for the SecureONE server. ## 2.6.2.3 Network Requirements for the Privileged Access Management System Network connectivity must be available to the web server hosted on the Remediant SecureONE device. Please note that a zero trust networking solution such as CryptoniteNXT can limit availability of network resources when improperly configured.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, privileged access. Contains security framework guidance for authentication systems. Source: Securing Property Management Systems."}]}
{"id": "nist_02783", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Enhanced Security Requirements for Controlled Unclassified Information say about 3.14.6e? (Part 7) According to Assessing Enhanced Security Requirements for Controlled Unclassified Information, 3.14.6e: | The correctness of <3.14.7e_ODP[1]: security critical or essential software components> is verified using <3.14.7e_ODP[4]: verification methods or techniques> . | | | 3.14.7e[b] | The correctness of <3.14.7e_ODP[2]: security critical or essential firmware components> is verified using <3.14.7e_ODP[4]: verification methods or techniques> .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Enhanced Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02784", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Recommendation for Key Management_ Part 1 \u2013 General provide? (Section 180) rovided by a FIPS 140-validated cryptographic module at a security level that is consistent with the FIPS 199 impact level associated with the data to be protected by the key (see SP 800-152). -OR- 3. Physical protection provided by secure storage with controlled access (e.g., a safe or protected area). Keying material is used with a given cryptographic mechanism (e.g., to generate a digital signature or establish keys) or with a particular application. Protection shall be provided to ensure that the keying material is not used incorrectly (e.g., not only must the usage or application be associated with the keying material, but the integrity of this association must be maintained). This protection can be provided by separating the keying material from that of other mechanisms or applications or by the use of appropriate metadata associated with the keying material. Section 6.2.3 addresses the metadata associated with keys. Some key information needs to be correctly associated with another entity (e.g., the key source or an entity that owns or uses the key), and the integrity of this association shall be maintained. For example, a secret symmetric key used for the encryption of key information or the computation of a MAC needs to be associated with the other entity (or entities) that share the key. Public keys need to be correctly associated (e.g., cryptographically bound) with the owner of the key pair (e.g., using public-key certificates). The key information shall retain its association during storage by separating the key information by 'entity,' by application, or by using appropriate metadata for the key information when required. Section 6.2.3 addresses the use of the metadata. An association may need to be maintained between protected key information and the keying material that is used to protect that key information. In addition, keys may require association with other keying material (see Section 6.2.1.6).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02785", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Considerations for Identity Management in Public Safety Mobile Networks say about Appendix D-Summary of Token Requirements? (Part 3) According to Considerations for Identity Management in Public Safety Mobile Networks, Appendix D-Summary of Token Requirements: irement B OR requirement C. In addition, Token A has to satisfy requirement D. Token B has to satisfy either requirement E OR [requirements F AND G]. In addition, Token B has to satisfy requirement H. | Level of Assurance 1 Type Tokens | Level of Assurance 1 Type Tokens | Level of Assurance 1 Type Tokens | Level of Assurance 1 Type Tokens | |-----------------------------------------------|---------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| | Token Description | Requirements | Requirements | Requirements | | Memorized Secret Token (Something you know) | User chosen string of 6 or more characters from a 90 or more character alphabet | 4 or more digit PIN generated randomly | A secret with equivalent strength 13 | | Memorized Secret Token (Something you know) | Failed authentication attempts limited to 100 or fewer in any 30-day period | Failed authentication attempts limited to 100 or fewer in any 30-day period | Failed authentication attempts limited to 100 or fewer in any 30-day period | | Pre-Registered Knowledge Token (Something you | The secret provides at least 14 bits of entropy | The entropy in the secret cannot be directly calculated (e.g.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, identity management, token. Contains security framework guidance for authentication systems. Source: Considerations for Identity Management in Public Safety Mobile Networks."}]}
{"id": "nist_02786", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Information System Security Best Practices for UOCAVA-Supporting Systems say about 4.2.1 Management Access Control? (Part 2) According to Information System Security Best Practices for UOCAVA-Supporting Systems, 4.2.1 Management Access Control: one. Controlling management of servers requires attention to at least three areas: - Minimize the number of users who can manage a computer to the bare minimum needed to reliably maintain the system. This is not as simple as it initially sounds: having too few administrators makes recovering from emergencies difficult because it may be hard to reach anyone who has management authorization, but allowing too many increases the risk that any one might be impersonated by an attacker. - Use strong authentication for every user who is allowed to administer the computer. Use of passwords that might be easily guessed or copied from other servers to which an attacker may have access is not strong enough for servers of high value. - Record all logins to a server in a way that even an administrator cannot easily change. Anyone who can impersonate a user who has administrative privileges can often make changes that are difficult to trace unless reliable audit trails are kept. Access control goes well beyond these three topics, but implementing them greatly reduces exposure to typical attacks on servers and makes such attacks easier to detect and possibly fix.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Information System Security Best Practices for UOCAVA-Supporting Systems."}]}
{"id": "nist_02787", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Practical Combinatorial Testing say about Practical Combinatorial Testing? (Part 1) According to Practical Combinatorial Testing, Practical Combinatorial Testing: Practical Combinatorial Testing \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ number of random tests. Although ACTS pairwise tests provide better 3-way coverage than the random tests, at other interaction strengths and values of t , the random tests are roughly the same or slightly better in combination coverage than ACTS. Recall from Section 7.1 that pairwise combinatorial tests detected slightly fewer events than the equivalent number of random tests. One possible explanation may be that the superior 4-way and 5-way coverage of the random tests allowed detection of more events. Almost paradoxically, an algorithm that produces a larger, sub-optimal covering array may provide better failure detection because the A less optimal (by size) array may provide better failure detection because it includes more interactions at t+1, t+2, etc. larger array is statistically more likely to include t +1, t +2, and higher degree interaction tests as a byproduct of the test generation. Again, however, the less optimal covering array is likely to more closely resemble the random test suite in failure detection. Note also that the number of failures in the SUT can affect the degree to which random testing approaches combinatorial testing effectiveness. For example, suppose the random test set covers 99% of combinations for 4-way interactions, and the SUT contains only one 4-way interaction failure. Then there is a 99% probability that the random tests will contain the 4-way interaction that triggers this failure. However, if the SUT contains m independent failures, then the probability that combinations for all m failures are included in the random test set is .99 m .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Practical Combinatorial Testing."}]}
{"id": "nist_02788", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2010 Annual Report say about NISTIR 7676, Maintaining and Using Key History on Personal Identity Verification (PIV) Cards? According to Computer Security Division 2010 Annual Report, NISTIR 7676, Maintaining and Using Key History on Personal Identity Verification (PIV) Cards: Group: Cryptographic Technology NIST Special Publication 800-73-3, Interfaces for Personal Identity Verification - Part 1: End-Point PIV Card Application Namespace, Data Model and Representation, discusses methods for storing retired Key Management Keys within the Personal Identity Verifi\u00ad cation (PIV) Card Application on a PIV Card. NISTIR 7676 comple\u00ad ments SP 800-73-3 by providing some of the rationale for the design of the mechanism for storing retired Key Management Keys on PIV Cards and by providing suggestions to smart card vendors, PIV Card Issuers, and middleware developers on the use of the Key History mechanism.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2010 Annual Report."}]}
{"id": "nist_02789", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification provide? (Section 20) d be on the Identity Token Usage phase. However, we find that in order to arrive at a meaningful authentication strength metric, we need to examine all three phases because of the following rationale. - The overall authentication strength in authentication use cases deployed in the Identity Token Usage phase is derived from the combination of trust levels in its constitutent authentication mechanisms. The trust level of an authentication mechanism, in turn, is based on the number of trust bindings (embedded in credential objects) it verifies. - The trust in the set of credential objects that are provisioned to the smart identity token during the Identity Token Issuance phase comes from the bindings it embodies and from the overall security of the system processes used in their generation - security for the data repositories holding the enrollment records, trust in attestion authority that is vouching for credential bindings (e.g., Certificate Authorities (CAs) for digital certificates). - The basis for creation of credential objects in turn is the 'Proofed Identity' which is embodied in the set of data records called enrollment records that are created after a successful 'Identity Proofing' process in the Identity Token Eligibility Determination phase. Thus we see that the trust marker or 'Proofed Identity' for the individual being authenticated is established in the Token Eligibility Determination Phase which together with other data in the enrollment records forms the basis for creation of credential objects in the Token Issuance phase. The credential objects by definition embody a 'stamp of authority' or trust binding in each of them. Since the purpose of any authentication mechanism is to 1 We will the two terms interchangeably in this document verify/validate those bindings, any assessment of its strength should involve the set of bindings it verifies as a prime metric.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token. Contains security framework guidance for authentication systems. Source: A Methodology for Developing Authentication Assurance Level Taxonomy for Smart Card-based Identity Verification."}]}
{"id": "nist_02790", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events say about 3.4.1 Risk? (Part 2) According to Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events, 3.4.1 Risk: impact on the organization's reputation . Analyses of the threats, vulnerabilities, and potential impact to an organization give us an understanding of the risk to an organization with respect to DI. NIST SP 800-39, Managing Information Security Risk, focuses on the business aspect of risk, namely at the enterprise level. This understanding is essential for any further risk analysis, risk response/mitigation, and risk monitoring activities. The following summary lists the strategic risk areas we identified and their mitigations: - \uf0a7 Impact on system function: ensuring the availability of accurate data or sustaining an acceptable level of DI reduces the risk of systems' availability being compromised. - \uf0a7 Cost of implementation: implementing asset identification and protection from DI events once and using it across all systems may reduce system continuity costs. - \uf0a7 Compliance with existing industry standards contributes to the industry requirement to maintain a continuity of operations plan. - \uf0a7 Maintenance of reputation and public image helps reduce level and likelihood of impact as well as facilitates the information required for impact reduction. - \uf0a7 Increased focus on DI includes not just loss of confidentiality but also harm from unauthorized alteration of data (per NISTIR 8050). We subsequently translated the risk factors identified to security Functions and Subcategories within the NIST Cybersecurity Framework. In Table 3-1, we mapped the categories to NIST SP 800-53 Rev. 4 controls.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Data Integrity_ Identifying and Protecting Assets Against Ransomware and Other Destructive Events."}]}
{"id": "nist_02791", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Definition according to Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach? Definition: Offload supportive but", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach."}]}
{"id": "nist_02792", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Training & Awareness Course Compendium say about VENDOR:? According to Computer Security Training & Awareness Course Compendium, VENDOR:: Skill Dynamics - An IBM Company One IBM Plaza 19th Floor Chicago, IL 60611 (800) IBM-TEACh (800) 426-8322 This course teaches you the necessity for and the implementation of effective controls in the MVS operating system. You will learn the MVS security-sensitive areas and the associated system and business impact of exposures in these areas. You will learn the proper use and implementation of controls to reduce security risks. Through hands-on use of the MVS system functions, you will gain valuable experience in maintaining effective and consistent system security. Although this course does not address the implementation of any specific security program (RACF\u2122, CA-TOP SECRET\u2122, etc.) the topics discussed will apply to MVS environments in general. *CA-TOP SECRET is a trademark of Computers Associates, Inc. COURSE TITLE: COURSE LENGTH: 1 DAY Practical Approach to Auditing MVS Security", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, top secret. Contains guidance on protecting sensitive government information. Source: Computer Security Training & Awareness Course Compendium."}]}
{"id": "nist_02793", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974 say about Prescription? (Part 3) According to Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974, Prescription: ndomly generated and of sufficient length to avoid compromise. - b. Be changed periodically, preferably every time used. - c. Be protected at least in accordance with the level of data they safeguard. The access control system should be sufficiently flexible to support a variety of constraints and mixes of objects. Users could be checked against terminals, programs, or data. An access list could be attached to any or all of the above depending on the needs of a particular installation. Every access to a given file or device must be capable of being trapped through the access control system in order to give the capability for additional authorization or identification checks. In addition, code words (lock words) should be placed within files to prevent reading of sensitive information. 3. The security system should support separate identification for individual users, terminal stations by location, individual programs or jobs by name and function and data to at least the file level. 4. All unauthorized access and I/O requests must result in termination of job, sounding of an alarm, purging of queues and refusal of service to the offending terminal/station. A maximum of three invalid log-ons or requests for information must be alowed before a given process is terminated. 5. A journal or accounting log must be used to capture information related to log-ons, terminal/ user identification, data requested, files accessed, data created and security violations. This raw data can then be formatted by user written programs to produce meaningful reports. These specs won't guarantee security, but they provide a useful departure point. They also provide a very small subset of what is required. The main point is that they address some of the real needs of contemporary systems.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974."}]}
{"id": "nist_02794", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? (Part 259) Control HA-1: cribing some of its details and user feedback we received -, an analysis of the merits of our tool's UI is beyond the scope of this paper, for it requires entirely different approaches and techniques. What we want here is to show one possible way it can be done. Besides general familiarity with the X.509/PKIX/PKCS standards and PKIs in general, this text assumes the reader has considerable familiarity with the HTTP [1] and HTTPS [2, 3] protocols. ## 4th Annual PKI R&amp;D Workshop -- Proceedings Figure 1: Overall architecture of the client proxy, which runs in the same computer as the browser. The engager changes the browser's proxy settings so that it uses our own local proxy. Before doing that, though, it detects which HTTP and HTTPS proxies the browser was using and configures our dispatchers to use them. This effectively puts us in the middle of the proxy chain. New HTTP requests originated by the browser will pass through our proxy, where our filters may act upon them. In fact, we have two filter chains, one for the outgoing requests and other for the incoming responses; some of them act upon the headers, other upon the bodies. Some features actually require several filters in cooperation to implement. If none of the filters actually consume the request (i.e., take it out of the chain), it reaches the default dispatcher in the end of the chain and it is sent as an HTTP request. The Encryption Domain filterset is a special set of filters that reroutes the requests that match certain criteria to be sent over as HTTPS. The HTTPS dispatcher makes use of the certificate store services (not shown in this picture) to validate the certificates and perform client authentication (with a friendly UI) if the site so requests. <!-- image --> ## 2 OVERALL ARCHITECTURE Our tool, code-named Kapanga, is an executable program that typically (although not necessarily) runs in the same computer as the user's web browser.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02795", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control OS-1100 in Computer Security Training & Awareness Course Compendium? (Part 127) Control OS-1100: Systems | 41 | | Auditing the Data Center for Controls, Efficiency, and Cost-Effectiveness | 68 | | Computer Security & Contingency Planning | 51 | | Continuity of Operations/Disaster Rec.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Training & Awareness Course Compendium."}]}
{"id": "nist_02796", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD) provide? (Section 926) vice\u2014second DHCP request: sensor ] date Tue Sep 3 15:03:10 EDT 2019 sensor ] dhc Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/wlan0/00:13:ef:20:1d:6b Sending on LPF/wlan0/00:13:ef:20:1d:6b Sending on Socket/fallback DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12 DHCPREQUEST of 10.0.41.182 on wlan0 to 255.255.255.255 port 67 DHCPOFFER of 10.0.41.182 from 10.0.41.1 DHCPACK of 10.0.41.182 from 10.0.41.1 bound to 10.0.41.182 -- renewal in 17132 seconds. NIST SP 1800-15D: Securing Small-Business and Home Internet of Things Devices 435 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Test Case Field Description MUD manager\u2014log file showing cached file in use: 2019-09-03 15:03:51,666 | INFO | on-dispatcher-99 | Mud- FileFetcher | 93 - gov.nist.antd.sdnmud-impl - 0.1.0 | Found file in mud cache length = 9548 2019-09-03 15:03:51,666 | INFO | on-dispatcher-99 | Mud- FileFetcher | 93 - gov.nist.antd.sdnmud-impl - 0.1.0 | read 9548 characters MUD file server\u2014log after second fetch (no change in output): sudo -E python mudfile-server.py DoGET /nistmud1 127.0.0.1 - - [03/Sep/2019 15:02:53] \"GET /nistmud1 HTTP/1.1\" 200 - Read 9548 chars DoGET /nistmud1/mudfile-sensor.p7s 127.0.0.1 - - [03/Sep/2019 15:02:55] \"GET /nistmud1/mudfile- sensor.p7s HTTP/1.1\" 200 - Read 3494 chars Overall Results Pass IPv6 is not supported in this implementation.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_02797", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Blockchain for Access Control Systems say about Blockchain for Access Control Systems? According to Blockchain for Access Control Systems, Blockchain for Access Control Systems: Vincent C. Hu This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8403 <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain for Access Control Systems."}]}
{"id": "nist_02798", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments provide? (Section 221) -5 | NIST800 53-VI- NET- CFG- 00318 | Built-in | NSX | Log into vSphere Web Client with credentials authorized for administration. Navigate to Networking and Security >> Firewall . Expand rule sections as necessary to view rules. If there are no rules configured to enforce authorizations, this is a finding. | Procedural | | CCE- 8453 1-3 | NIST800 53-VI- NET- CFG- 00321 | Built-in | NSX | From the vSphere Web Client, go to Administration >> Single Sign-On >> Configuration >> Policies >> Password Policy . View the values of the password format requirements. If Lower-Case Characters is not set to at least 1, this is a finding. | 1 | | CCE- 8453 2-1 | NIST800 53-VI- NET- CFG- 00322 | Built-in | NSX | From the vSphere Web Client, go to Administration >> Single Sign-On >> Configuration >> Policies >> Password Policy . If Upper-Case Characters is not set to at least 1, this is a finding.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, password policy, single sign-on. Contains security framework guidance for authentication systems. Source: Trusted Cloud_ Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments."}]}
{"id": "nist_02799", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities say about D-Day Minus 5? According to Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities, D-Day Minus 5: In response to the U.S. declaration to send troops and materiel to the region, hostile nations vow to take whatever actions are necessary to 'strike a vicious blow against the American imperialists.' They state that any war that the U.S. provokes will also be fought on the American homeland. U.S. intelligence agencies soon detect an increase of cyber attacks against U.S. and threats to carry out terrorist attacks against the U.S. government. Intelligence also indicates that hostile foreign interests within the U.S. are increasingly active and terrorist cells in other countries have been activated to potentially carry out attacks against the U.S., both overseas and within U.S. borders. U.S. government officials suspect that the hostile nations hope to weaken U.S. public support and impede the military's capability to deploy by engaging in actions that might include the use of weapons of mass destruction and cyberterrorism. Nevertheless, the U.S. military continues to deploy to the region.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities."}]}
{"id": "nist_02800", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Product Supplier according to Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI? Product Supplier: Microsoft Coiporation", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI."}]}
{"id": "nist_02801", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Cryptographic Key Generation say about 2.1 Definitions? (Part 8) According to Recommendation for Cryptographic Key Generation, 2.1 Definitions: | Amethod of encrypting and decrypting keys and (possibly) associated data using symmetric-key cryptography; both confidentiality and integrity protection are provided; see SP 800-38F. 6 | | Key-wrapping key | A key used as an input to a key-wrapping method; see SP 800-38F. | | MACkey | A symmetric key used as input to a security function to produce a message authentication code (MAC). | | Message Authentication Code (MAC) | A cryptographic checksum on data that uses an approved security function and a symmetric key to detect both accidental and intentional modifications of data. | | Min-entropy | The min-entropy (in bits) of a random variable X is the largest value m having the property that each observation of X provides at least m bits of information (i.e., the min-entropy of X is the greatest lower bound for the information content of potential observations of X ). The min- entropy of a random variable is a lower bound on its entropy. The precise formulation for min-entropy is - log 2 (max p i ) for a discrete distribution having event probabilities p 1 , ..., p k . Min-entropy is often used as a worst-case measure of the unpredictability of a random variable. | | Module | See Cryptographic module. | | Nonce | A time-varying value that has (at most) an acceptably small chance of repeating. For example, the nonce may be a random value that is generated anew for each use, a timestamp, a sequence number, or some combination of these.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Recommendation for Cryptographic Key Generation."}]}
{"id": "nist_02802", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security of Personal Computer Systems_ A Management Guide say about 7.1.4.2. Personnel Screening? According to Security of Personal Computer Systems_ A Management Guide, 7.1.4.2. Personnel Screening: Many security controls ultimately depend on trust in individuals. Therefore, there should be some process to screen personnel who are authorized to access sensitive information systems. This does not imply, however, that special screening is needed simply because a person will be using a computer system. Most organizations have pre-employment screening procedures and, if needed, security background investigations. If such screening is considered sufficient for the employee's position description, it should be irrelevant whether or not a computer is used as part of the job.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security of Personal Computer Systems_ A Management Guide."}]}
{"id": "nist_02803", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Access Control for SAR Systems say about 2.1 Policy Identification? (Part 1) According to Access Control for SAR Systems, 2.1 Policy Identification: 2.1 Policy Identification The first phase of the policy lifecycle involves the identification of laws, statutes and policies pertinent to granting or denying access to domain resources. The identification of laws, statutes and policies pertinent to granting or denying access to domain resources requires not only intimate knowledge of pertinent federal, state, local, tribal, and domainspecific laws, statutes and policies, but also of domain resources, it's users and actions that users may invoke on those resources. In general, access control policies are motivated by laws, statutes, and policies that ensure the privacy of sensitive information including classified data and personally identifiable information (PII). After pertinent laws, statutes and policies have been identified, work must be conducted to map these laws, statutes and policies to domain-specific policies. The first step in this process entails the mapping of general laws, statutes and policies into Attribute-Based Access Control (ABAC) [Blaze, Brown, Pimlott] rules. An ABAC rule is a triple SAARA , , where SA represents a set of domain subject (i.e., user or process) attributes, RA represents a set of domain resource attributes, and A represents a set of actions that users may invoke on resources. The set SA is defined by a subject attribute data model that defines subject attributes (and their interrelationships) required to render a policy decision (i.e., permit or deny access to a resource). Such attributes may include, for example, the role, rank and operating unit of an employee. The set RA is defined by a resource attribute data model that defines resource attributes (and their interrelationships) required to render a policy decision. Such attributes may include, for example, the fields of a resource database record or the clearance level of the resource (i.e., public, secret, or top secret).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, secret, top secret. Contains guidance on protecting sensitive government information. Source: Access Control for SAR Systems."}]}
{"id": "nist_02804", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines on Active Content and Mobile Code provide? (Section 99) est security advisories from the United States Computer Emergency Readiness Team (US-CERT) and the Computer Emergency Response Team (CERT) Coordination Center, and subscribe to security mailing lists. - GLYPH&lt;c=31,font=/BAADDB+Webdings&gt; Periodically cross-check products against published lists of known vulnerabilities, such as the National Vulnerability Database (NVD), 10 that provide pointers to solution resources and patch information. - GLYPH&lt;c=31,font=/BAADDB+Webdings&gt; Regularly audit systems and networks, quickly remedying any deficits noted. - GLYPH&lt;c=31,font=/BAADDB+Webdings&gt; Know who to contact and what steps to take when discovering evidence of an intrusion. One typical and common sense approach is to improve the security infrastructure incrementally over time. At each step, apply safeguards against the most critical risk items. For example, start with firewalls and gateway servers capable of screening active content and executable email attachments and successfully defending against a high percentage of Internet launched attacks. Later, for additional protection, complement antivirus software with behavioral controls, intrusion detection capabilities, or other technologies. Regular site security audits also help to identify vulnerabilities and appropriate safeguards, and to decide whether the remaining risks warrant further expenditures of time and money. 10 The NVD is hosted by NIST at http://nvd.nist.gov/.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Guidelines on Active Content and Mobile Code."}]}
{"id": "nist_02805", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does CVSS Implementation Guidance provide? (Section 49) ons upon a login, which allows physically proximate attackers to obtain credentials by resubmitting the login form via the back button of a web browser on an unattended workstation after an RT logout. Analysis: Vector: AV:L/AC:L/Au:N/C:P/I:P/A:P Base Score: 4.6 CWE: CWE-310 - Cryptographic Issues | Metric | Value | Explanation | |-------------------|---------|----------------------------------------------------------| | Access Vector | Local | From keyword 'physically proximate' | | Access Complexity | Low | No special conditions exist | | Authentication | None | Not required | | Confidentiality | Partial | Attacker obtains the credentials of the application user | | Integrity | Partial | Attacker obtains the credentials of the application user | | Availability | Partial | Attacker obtains the credentials of the application user | The Bluetooth stack in Microsoft Windows XP SP2 and SP3, and Vista Gold and SP1, allows physically proximate attackers to execute arbitrary code via a large series of Service Discovery Protocol (SDP) packets. From reference link [1], the range of the Bluetooth radio in this context is listed as 0 m to 100 m. Analysis: Vector: AV:A/AC:L/Au:N/C:C/I:C/A:C Base Score: 8.3 CWE: CWE-20 - Improper Input Validation | Metric | Value | Explanation | |-------------------|------------------|--------------------------------------------------------------------------------------------------------------------| | Access Vector | Adjacent Network | From keyword 'physically proximate' and within Bluetooth range. See Additional Considerations .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: CVSS Implementation Guidance."}]}
{"id": "nist_02806", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guide to Secure Web Services? (Part 222) Control ES-1: ----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| | Hamid R. Motahari Nezhad, et al: 'Securing Service-Based Interactions: Issues and Directions' ( IEEE Distributed Systems Online, April 2005) | ndex.jsp?pageID=dso_level1&path=dsonline/topi cs/was/papers&file=motahari.xml&xsl=article.xsl | | Ken Birman, Cornell University: 'The Untrustworthy Web Services Revolution' ( IEEE Computer, Feb. 2006) | To purchase from IEEE Computer Society: 006.73 | | Marek Hatala, et al, Simon Fraser University (Surrey, BC, Canada): 'Federated Security: Lightweight Security Infrastructure for Object Repositories and Web Services' ( Proceedings of the 2005 International Conference on Next Generation Web Services Practices , 2005 [NWeSP'05]) | federated-security.pdf | | Neal Leavitt: 'Are Web Services Finally Ready to Deliver?' ( IEEE Computer, Nov.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Secure Web Services."}]}
{"id": "nist_02807", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain risk according to NIST Engineering Trustworthy Secure Systems According to Engineering Trustworthy Secure Systems, risk: Effect of uncertainty on objectives. [28] Note 1: An effect is a deviation from the expected, positive or negative. A positive effect is also known as an opportunity. Note 2: Objectives can have different aspects (i.e., financial, health and safety, and environmental goals) and can apply at different levels (i.e., strategic, organization-wide, project, product, and process). Note 3: Risk is often characterized by reference to potential events and consequences or a combination of these. Note 4: Risk is often expressed in terms of a combination of the consequences of an event (including changes in circumstances) and the associated likelihood of occurrence. Note 5: Uncertainty is the state, even partial, of deficiency of information related to the understanding or knowledge of an event, its consequence, or likelihood.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Engineering Trustworthy Secure Systems."}]}
{"id": "nist_02808", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Situational Awareness for Electric Utilities provide? (Section 218) administrator password, then click Finish. - In the Project Explorer window, right-click Tofino SAs, and select New Tofino SA. A folder can also be created for the SAs to help organize multiple areas. Figure 2-35 Administrator Password <!-- image --> Figure 2-36 Project Explorer Window <!-- image --> - In the Tofino ID field, enter the MAC address listed on the firewall hardware sticker. Fill out the rest of the fields as necessary, then click Finish. Figure 2-37 Tofino SA/MAC Address <!-- image --> Figure 2-38 Project Explorer <!-- image --> - Right-click on the Assets icon in the Project Explorer frame, then click New Asset. - In the New Asset window, set the name and type of the device and all other fields as necessary, then click Next. Figure 2-39 New Asset <!-- image --> - Fill in the IP address and/or the MAC address fields, then click Finish. - Repeat for all devices on the network. When they are configured, click on the Assets icon in the Project Explorer frame (if it is not already selected). There should be a list of all configured assets. - Under the Project Explorer frame, click the drop-down arrow next to Tofino SAs, then choose the SA created earlier. From there, click Firewall in the Project Explorer frame to display current firewall rules. This should currently be empty. Figure 2-40 Project Explorer Tofino SA Icon <!-- image --> - To create the first rule, click the + Create Rule button above the Tofino SA-Firewall title. Then, ensure the Standard rule radio button is selected, and click Next. - On the next screen, choose the interface for Asset 1. This is where traffic originates before going into the device. Select a source asset and a destination asset from the radio buttons below. Set the direction of the traffic by using the arrow buttons in the middle. When finished, select Next. - In the Asset Rule Profiles window, select the Manually create the firewall rules for the selected assets radio button, then click Next.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Situational Awareness for Electric Utilities."}]}
{"id": "nist_02809", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Public Safety Mobile Application Security Requirements Workshop Summary provide? (Section 27) ction hierarchy for use in determining an application's level of data protection. - \uf0b7 Applications will declare what data they handle. - \uf0b7 Application will declare what data protection they implement. - \uf0b7 App discloses what location information is being provided, whether the GPS/location services of the device needs to be enabled, how location information is being determined (cell ID, GPS, AGPS), and whether 2D or 3D - \uf0b7 Adequate safeguards are in place to protect privacy, confidentiality Public safety mobile applications will have access to and use location information provided by mobile devices to enhance their utility to public safety practitioners. Location information is actually a special subset of the more general topic of mobile application data protection. Location information, however, has the potential to have more immediate and severe implications to first responders. In general, location information provided to mobile applications will either be two- or three-dimensional. There are at least three factors that will influence to what extent public safety should use the location information being provided: accuracy, integrity, and confidentiality. Location information can be derived using various sources and techniques with each providing varying levels of accuracy. The integrity of the location information may need to be protected so that false location information is not provided that interferes with a timely response. Under certain circumstances, location information being generated may need to be kept confidential so as to not endanger public safety personnel. That said; seamless, efficient, and ubiquitous location communication stands to both empower and enrich public safety as they seek to fulfill their mission.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Public Safety Mobile Application Security Requirements Workshop Summary."}]}
{"id": "nist_02810", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2010 Annual Report say about Biometric Standards and Conformity Assessment Activities? (Part 5) According to Computer Security Division 2010 Annual Report, Biometric Standards and Conformity Assessment Activities: need\u00ad ed) so that the suites are available at the time of publication of the standards or soon thereafter. Changes to the architecture leading towards the development of CTA Beta 3.0 are also planned. Such changes may include the re\u00ad development of some of the Graphical User Interfaces to accom\u00ad modate the diverse types of test suites planned (binary as well as tag-based testing) and to improve the usability of the tools. Some of the features also being researched and/or implemented are pro\u00ad viding for full web services support and the development of a test 2 The CTA/CTS Download web page is rics/biocta\\_download.cfm. The web page can be also reached from NIST/ITL Biometric Resource Center http://www.nist.gov/biometrics under ITL Computer Security Division (CSD)/Systems and Emerging Technologies Security Research Group - 'Standards and Related Technical Developments' 3 The released CTSs were developed to test implementations of four pub\u00ad lished American National Standards: ANSI INCITS 378-2004 and 2009 (Finger Minutiae Format for Data Interchange) and ANSI INCITS 381-2004 and 2009 (Information Technology Finger Image-Based Data Interchange Format). 4 This work is sponsored, in part, by DHS/US-VISIT. suite developer's kit to promote third-party development of mod\u00ad ules that can be incorporated into the architecture. Research is also planned on the need for the development of additional test suites for implementations of new biometric technical interface standards being developed internationally. The Biometric Consortium (the Consortium), co-chaired by NIST and the National Security Agency (NSA), serves as a focal point for research, development, testing, evaluation, and application of bio\u00ad metric-based personal identification/verification technology.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Computer Security Division 2010 Annual Report."}]}
{"id": "nist_02811", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Usability and Security Considerations for Public Safety Mobile Authentication provide? (Section 19) ne ..............................................34 | | 6.2 Future Directions........................................................................................... | | 34 | | Appendix A-Acronyms............................................................................................36 Appendix B-References ..........................................................................................38 | | List of Tables | In 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. Identifying methods to facilitate first responders' operations within their specialized environments can shorten response times and allow emergencies to be more effectively managed, hopefully saving more lives in the process. Surely, firefighters must be protected from heat, emergency medical technicians (EMTs) from blood borne pathogens, and law enforcement officers (LEOs) from projectiles - but what other factors exist?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Usability and Security Considerations for Public Safety Mobile Authentication."}]}
{"id": "nist_02812", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Efforts to Standardize Personal Data according to NIST Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974 According to Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974, Efforts to Standardize Personal Data: There are government agencies urging the standardization of codes for personal identification, location, time, personal characteristics, and medical and physical status descriptors. It is obvious that universally applied codes in these areas would aid in the accumulation and interchange of meaningful personal data, and would reduce the cost of building a data bank. However, the key code necessary to concentrate personal data from several sources is some universally accepted system of linking this coded data to an individual. The pragmatic computer systems designer will specify Social Security number as this identifier unless the public is aware of the dangers of the universal use of the number as a key to personal and private data. It must be apparent that the computer systems designer in industry is only following the lead of the computer systems designer in most government agencies where Social Security number has really become Federal Identification Number. ADAPSO recommends that government and industry efforts to standardize the encoding of personal data descriptors for the purpose of information interchange include the question of personal data ownership.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Approaches to Privacy and Security in Computer Systems_ Proceedings of a Conference Held at the National Bureau of Standards March 4-5, 1974."}]}
{"id": "nist_02813", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Assurance Requirements for Linux Application Container Deployments say about 6 Assurance Requirements for Image Integrity Solutions? (Part 1) According to Security Assurance Requirements for Linux Application Container Deployments, 6 Assurance Requirements for Image Integrity Solutions: 6 Assurance Requirements for Image Integrity Solutions The integrity of the container images is of paramount importance since they are converted to running instances, some of which may host mission-critical applications. The image countermeasures covered in the Container Security Guide include recommendations for monitoring images for malware and other vulnerabilities, proper image configuration, separating secrets from image files, and ensuring trust in images through cryptographic signatures and regular updates. The security solutions needed for carrying out these recommendations should include the following assurance requirements: - (a) There should exist a means to create metadata linking each image to its base image. - (b) There should exist a feature to rebuild the image automatically if the linked base image changes [6]. - (c) When any changes are made to the base image or dependent image (e.g., patching a vulnerability), changes should not be made to the running containers. Instead, the corresponding image should be recreated and the container re-launched using the modified image. Thus, a single master, or golden image, is to be maintained for any service. - (d) When employing 'image signing' solutions for digitally signing and uniquely identifying each image, the following requirements should be met [6]: 1. There should be robust key management to minimize the possibility of key compromise. One approach is to have a PKI system that issues a certificate to each developer exclusively for signing the image. The private key associated with this certificate will then be the 'signing key' that is used to sign all container images in a repository. 2. Replay attacks must be mitigated by embedding expiration timestamps in signed container images. Alternatively, a special key can be used to sign the metadata for the repository, ensuring that the images in the repository do not contain stale versions of the image with valid signatures.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, malware. Contains technical security guidance that could inform defensive posture. Source: Security Assurance Requirements for Linux Application Container Deployments."}]}
{"id": "nist_02814", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-5 in Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control? (Part 115) Control PD-5: reporting, and notification are identified and performance criteria are defined. PCCs responsible for hosted payloads should have an agreement on these roles and responsibilities with the host's MOC. | [NIST-SP800-53r5] CA-2, CA-7, PM-14 | | DE.DP-2 : Detection activities comply with all applicable requirements | Organizations should confirm that their detection activities comply with applicable requirements. Organizations with MOCs responsible for hosting third- party payloads should perform detection activities in accordance with pre-defined agreements for hosted payloads.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control."}]}
{"id": "nist_02815", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control TE-1 in Mobile Device Security_ Bring Your Own Device (BYOD)? (Part 82) Control TE-1: | AC-17(2): Protection of Confidentiality and Integrity Using Encryption SC-8: Transmission Confidentiality and Integrity | A.8.2.3: Handling of Assets A.13.1.1: Network Controls A.13.2.1: Information Transfer Policies and Procedures A.13.2.3: Electronic Messaging A.14.1.2: Securing Application Services on Public Networks A.14.1.3: Protecting Application Services Transactions | CSC 13: Data Protection CSC 14: Controlled Access Based on the Need to Know | OV-SPP-002: Cyber Policy and Strategy Planner OV-MGT-002: Communications Security (COMSEC) Manager OV-LGA-002: Privacy Officer/Privacy Compliance Manager | | Specific product used | Function | Applicable NIST Cybersecurity Framework Subcategories | Applicable NIST SP 800-53 Revision 5 Controls | ISO/IEC 27001:2013 | CIS 6 | Applicable NIST SP 800-181 NICE Framework Work Roles (2017) | |-------------------------|------------|-------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| | | | PR.PT-4: Communications and control networks are protected.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, cybersecurity framework, fips. General security reference material without sensitive content. Source: Mobile Device Security_ Bring Your Own Device (BYOD)."}]}
{"id": "nist_02816", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PE-6 in Identity and Access Management for Electric Utilities? (Part 251) Control PE-6: ing the ConneXium Tofino Configurator, right-click Tofino SAs in the Project Explorer pane, and then select Apply. If the project asks you to save, click OK. . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . NIST SP 1800-2C: Identity and Access Management for Electric Utilities 293 Figure 16-17 Apply Configuration Pane T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . In the Apply Configuration pane (Figure 16-17), ensure that your SA is selected in the table at the top, and that the USB Drive radio button is selected. Browse to the top-level directory of your USB drive, and then click Finish. A popup window (Figure 16-18) will notify you of successful completion. Figure 16-18 Loadable USB Drive Popup . NIST SP 1800-2C: Identity and Access Management for Electric Utilities 294 T h i s p u b l i c a t i o n i s a v a i l l a b e f r e e o f c h a r g e f r o m : h t t p : / / d o i . o r g / 1 0 . 6 0 2 8 / N I S T . S P 1 8 0 0 - 2 . . Ensure that the firewall has been powered on and has been running for at least one minute, and then plug the USB device that was used to copy the Tofino configuration into the USB port on the back of the firewall. Press the Save/Load/Reset button twice, setting it to the Load setting (Pressing it once should turn the indicator light to green; pressing it again will change the indicator light from green to amber). After a few seconds, the device will begin displaying lights that move from right to left across the light-emitting diodes (LEDs) on the back, indicating that the configuration is being loaded. Once the lights stop moving from right to left, wait a few seconds, and ensure that the Fault LED does not light up. Remove the USB drive, and place it back into the computer running the ConneXium Tofino Configurator software. Right-click Tofino SAs in the Project Explorer pane, and then select Verify.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Identity and Access Management for Electric Utilities."}]}
{"id": "nist_02817", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Design Alternatives for Computer Network Security say about 3.2.2 Organization of the Table? (Part 4) According to Design Alternatives for Computer Network Security, 3.2.2 Organization of the Table: es not affect its usage. j ; i A flexible organization which meets all of the known requirements for the SC's access control function has been defined by Kaufman (KAU-74) , and is summarized below. This approach has particular merit in that it can efficiently handle both the simple initial usage and more complex future usage in an open-ended manner The basic profile of a requestor (sxibject) would be stored in a block of information which would also include access authorization in terms of (object, capability) pairs. Considerable factoring, and hence compaction, is possible as indicated in Figure 3-2. Item \"a\" in the figure shows an entry which is a direct (object-capability) pair, which might simply represent access to a particular HOST machine. In contrast, the second entry in the access authorization table is a pointer to \"b\" which is an arbitrary capability list for an object which, in this example, is owned by this siabject. The third entry is also a pointer, but in this case to an access group. Another subject is also shown to be a member of this group. The fourth item is another direct representation, and the fifth is a pointer to \"d\"; an access group in which a further level of factoring has been applied, i.e., with several objects sharing the same capability list. The example situation depicted in the figure is intended to illustrate the open-endedness of the approach, rather than suggesting that compaction by means of the various factoring schemes is necessary. We shall discuss the aspects in which factoring both helps and complicates matters in siibsequent sections of this report. A rather subtle issue that must be considered in the design of the SC is whether the access table should be structured by subject or by object, i.e., the factoring could be either: &lt;subject&gt; (set of &lt;object&gt;, &lt;capability&gt; pairs) &lt;object&gt; (set of &lt;subject&gt;, &lt;capability&gt; pairs). or Figure 3-2.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: Design Alternatives for Computer Network Security."}]}
{"id": "nist_02818", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements say about 1.4 Superseded Validation Programs? According to Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements, 1.4 Superseded Validation Programs: This publication supersedes the Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements revision 4. The previous revisions of the program for SCAP 1.0 and 1.1 have been also deprecated. 6 For a complete list of mappings, please refer to [NIST SP 800-126 R3].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements."}]}
{"id": "nist_02819", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Intrusion Detection and Prevention Systems (IDPS) say about 2.1 Uses of IDPS Technologies? (Part 1) According to Guide to Intrusion Detection and Prevention Systems (IDPS), 2.1 Uses of IDPS Technologies: 2.1 Uses of IDPS Technologies IDPSs are primarily focused on identifying possible incidents. For example, an IDPS could detect when an attacker has successfully compromised a system by exploiting a vulnerability in the system. The IDPS could then report the incident to security administrators, who could quickly initiate incident response actions to minimize the damage caused by the incident. 3 The IDPS could also log information that could be used by the incident handlers. 4 Many IDPSs can also be configured to recognize violations of security policies. For example, some IDPSs can be configured with firewall ruleset-like settings, allowing them to identify network traffic that violates the organization's security or acceptable use policies. Also, some IDPSs can monitor file transfers and identify ones that might be suspicious, such as copying a large database onto a user's laptop. Many IDPSs can also identify reconnaissance activity, which may indicate that an attack is imminent. For example, some attack tools and forms of malware, particularly worms, perform reconnaissance activities such as host and port scans to identify targets for subsequent attacks. An IDPS might be able to block reconnaissance and notify security administrators, who can take actions if needed to alter other security controls to prevent related incidents. Because reconnaissance activity is so frequent on the Internet, reconnaissance detection is often performed primarily on protected internal networks. 2 This term is used for the purposes of this publication. It has not been widely used in the security community, and the reason for using it in this publication is strictly brevity, not to replace the well-established 'IDS' and 'IPS' terms. 3 If the IDPS had successfully prevented the attack, security administrators still might want to be notified of the attack. This is particularly important if the target has a known vulnerability that the attack could have exploited.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit, malware. Contains technical security guidance that could inform defensive posture. Source: Guide to Intrusion Detection and Prevention Systems (IDPS)."}]}
{"id": "nist_02820", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Electronic Mail Security say about 6.7 Checklist for Securing Mail Servers and Content? (Part 5) According to Guidelines on Electronic Mail Security, 6.7 Checklist for Securing Mail Servers and Content: to strip suspicious active content from messages | | | Configure lexical analysis if required | | | Take steps to prevent address spoofing, such as blocking emails from external locations using internal 'From' addresses | | | Create a security policy that addresses content filtering | | | Have the security policy reviewed by appropriate legal, privacy, and human resources authorities | | | Add a legal disclaimer to emails, if required | | | Educate users on the dangers of malware and how to minimize those dangers | | | Notify users when an outbreak occurs | | | Block spam-sending servers | | | Configure mail gateways or firewalls to use LDAP lookup to confirm the existence of email recipients | | | Configure mail server to block email from open relay blacklists or DNS blacklists, if required | | | Configure mail server to block email from specific domains, if required | | | Use authenticated mail relay | | | Configure authenticated mail relay on the server | | | Secure access to the mail server | | | Configure mail server to use encrypted authentication | | | Enable Web access to email |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_02821", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identifying and Categorizing Data Types for Public Safety Mobile Applications_ Workshop Report provide? (Section 23) lete loss of an organization's ability to carry out its mission, severe financial loss, and/or catastrophic harm to individuals involving loss of life or serious life threatening injuries. NIST FIPS 199 provides a compact representation for an information type's security categorization [7]: ``` Security Category (SC) information type = {( confidentiality , impact ), ( integrity , impact ), ( availability , impact )} ``` Finally, NIST FIPS 199 describes applying a security categorization to an information system. U.S. law defines an information system as 'a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, or disposition of information' [8]. By this definition, a public safety mobile device is an information system. Applying a security categorization to an information system entails identifying the impact level for each of the cybersecurity objectives-confidentiality, integrity, and availability-for the information system. To do this, an organization must first identify each of the information type categorizations associated with that system. The highest impact level for each security objective becomes the impact level for that objective for the information system.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Identifying and Categorizing Data Types for Public Safety Mobile Applications_ Workshop Report."}]}
{"id": "nist_02822", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Considerations for Identity Management in Public Safety Mobile Networks provide? (Section 54) without the need for external hardware. Like removable hardware security modules, they typically have the ability to securely store cryptographic keys and perform cryptographic operations in hardware. This approach potentially provides unique security features not supported by other approaches, as small, trusted hardware is often presumed to provide a greater level of assurance in their operation. Many modern mobile devices provide some form of embedded hardware token but mobile operating system vendors and hardware manufacturers often restrict access by third-party developers. Therefore, specific approaches will depend on whatever hardware, firmware, and software support is ultimately provided by these parties. Remote device authentication will be the method of authentication mobile devices use to gain access to the NPSBN. Software and hardware tokens can be leveraged for remote device authentication and used in a manner similar to remote user authentication. After provisioning, these devices could then prove its identity to a verifier by proving knowledge of a credential. This approach may require the establishment and management of a public key infrastructure (PKI) and for this, the existing Federal PKI could be leveraged. A greater level of assurance would be achieved if credentials were stored in hardware protected storage locations. A major difference would be the lack of user interaction in providing a password or PIN to unlock a credential for use. It is possible that during an emergency, the NPSBN will not function as intended, possibly due to the NPSBN directly being attacked (e.g., jamming) or some other reason (e.g., flood, terrorist attack). In the instance of the network ceasing to function, devices may still be able to operate by communicating via the cellular tower, without the use of the core network.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, identity management, pki. Contains security framework guidance for authentication systems. Source: Considerations for Identity Management in Public Safety Mobile Networks."}]}
{"id": "nist_02823", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Dramatically Reducing Software Vulnerabilities_ Report to the White House Office of Science and Technology Policy provide? (Section 26) es. Industry requires evidence of the extent of such vulnerabilities, in addition to knowledge in determining which techniques are most effective in developing software with far fewer vulnerabilities. With effective measures that can function as market signals, industry can favor and select low vulnerability software, thus encouraging development of better software [Grigg08]. Additionally, and more critically, industry requires guidance in identifying the best places in code to deploy mitigations or other actions. This evidence comes from measuring, in the broadest sense, or assessing the properties of software. In order to produce the list of approaches, the Office of Science and Technology Policy (OSTP) asked NIST to lead a community-based effort. The report was developed during an eight-month period. Given the compressed time frame, the focus of the report was kept to the criteria described above to highlight promising approaches rather than perform a comprehensive analysis. NIST consulted with multiple experts in the software assurance community including: - Two OSTP-hosted inter-agency roundtables; - Half-day session at the Software and Supply Chain Assurance (SSCA) Summer Forum; - All-day workshop on Software Measures and Metrics to Reduce Security Vulnerabilities; - Two-day workshop on Reducing Software Defects and Vulnerabilities, hosted by the Software Productivity, Sustainability, and Quality (SPSQ) Working Group of the Networking and Information Technology Research and Development (NITRD) Program and - Public comment from 4 to 18 October 2016. The report is organized into two major sections. The first, Section 2, enumerates technical approaches and the second, Section 3, addresses measures. Section 2 has subsections for technical approaches to deal with vulnerabilities in software. These include formal methods, such as sound static program analyses, model checkers and Boolean Satisfiability (SAT) solvers.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Dramatically Reducing Software Vulnerabilities_ Report to the White House Office of Science and Technology Policy."}]}
{"id": "nist_02824", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Automation Support for Security Control Assessments_ Software Asset Management provide? (Section 8) Control Items Affecting Desired and/or Actual State from All Defect Checks in this Volume................................................................................................................G-1 | | Figure 1:SWAM Impact on an Attack Step Model ........................................................................7 | | |------------------------------------------------------------------------------------------------------------------------------------|----------------| | Figure 2: Definition and Discussion of Software File for SWAM................................................10 | | | Figure 3: Definition and Discussion of Software Products for SWAM........................................10 | | | Figure 4: SWAMConcept of Operations (CONOPS)...................................................................16 | | | Figure 5: Primary Roles in Automated Assessment of SWAM....................................................22 | | | Figure 6: Main Steps in Adapting the Plan Template....................................................................24 | | | Figure 7: Sub-Steps to Select Defect Checks to Automate............................................................24 | | | Figure 8: Sub-Steps to Adapt Roles to the Organization...............................................................25 | | | Figure 9: Sub-Steps to Automate Selected Defect Checks............................................................26 | | | List of Tables | List of Tables | | Table 1:SWAM Impact on an Attack Step Model..........................................................................8 | | | Table 2: Traceability among Requirement Levels...........................................................................9 | | | Table 3: Example SWAMActual State Data Requirements .........................................................14 | | | Table 4: Example SWAMDesired State Data Requirements .......................................................15 | | | Table 5: Operational and Managerial Roles for SWAM...............................................................20 | | | Table 6: Mapping of Attack Steps to Security Sub-Capability......................................................74 | | | Table 7: Applicability", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automation Support for Security Control Assessments_ Software Asset Management."}]}
{"id": "nist_02825", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Securing Property Management Systems? (Part 59) Control AM-1: stered guests or sponsors should not be able to access or view sensitive customer data. | | actual results | ACL manages view of permissions of the logged-in users. Users could only view data they were authorized to view within the Solidres PMS. | | disposition | pass | ## 7.1.5 Test Case PMS-04 (Guest Reservation Editable) Table 7-8 contains test case requirements, associated test case, and descriptions of the test scenario for entering a reservation and editing the reservation. Table 7-8 Guest Reservation Editable | Test Case Field | Description | |----------------------------------------------------|---------------------------------------------------------------------------------------------------------------| | requirement tested | (CR 1) creating a guest reservation and having the ability of only an authorized user to edit the reservation | | description | Enter a guest reservation into the PMS. Verify that it is in the PMS and that it is retrievable and editable.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Property Management Systems."}]}
{"id": "nist_02826", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 1.2.3 General Infrastructure Requirements according to NIST Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders According to Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders, 1.2.3 General Infrastructure Requirements: Some general infrastructure elements must be in place to support the components of this build guide. These are assumed to exist in the environment prior to the installation of the architecture components in this guide. The details of how these services are implemented are not directly relevant to the build. - \uf0a7 DNS-All server names are expected to be resolvable in DNS. This is especially important for FIDO functionality, as the application identification (App ID) associated with cryptographic keys is derived from the host name used in application uniform resource locators (URLs). - \uf0a7 Network Time Protocol (NTP)-Time synchronization among servers is important. A clock difference of five minutes or more is sufficient to cause JavaScript Object Notation (JSON) Web Token (JWT) validation to fail, for example. All servers should be configured to synchronize time with a reliable NTP source. - \uf0a7 Certificate Authority (CA)-Hypertext Transfer Protocol Secure (HTTPS) connections should be used throughout the architecture. Transport Layer Security (TLS) certificates are required for all servers in the build. If an in-house CA is used to issue certificates, the root and any intermediate certificates must be provisioned to the trust stores in client mobile devices and servers.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, certificate authority, token. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_02827", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research provide? (Section 77) The EvoSTS returns an OWA access token to the user's browser and it is presented to the Office 365 OWA endpoint. The user is now authenticated into his or her Office 365 mailbox as shown in Figure 59. Figure 59: Office 365 Mailbox Outlook Web Access <!-- image --> The user can now use his or her Derived PIV End Entity Signature Certificate for S/MIME digital signature as shown in Figures 60 through 63. OWA S/MIME 38 requires the use of Internet Explorer 9 or higher, installation of the owasmime.msi ActiveX control available from outlook.office365.com, and the Derived PIV End Entity Signature Certificate described in Section 4.8.2 of this report. 38 Figure 60: OWA S/MIME <!-- image --> Figure 61: OWA S/MIME Digital Signature <!-- image --> Figure 62: Digitally Signed Message <!-- image --> The recipient validates the signed message as shown in Figure 63. Figure 63: Validated Digitally Signed Message <!-- image --> Modern authentication 39 is Microsoft's implementation of the SAML 2.0 and OAuth 2.0 protocols for rich applications (non-browser-based) using the Microsoft Azure Active Directory Authentication Library (ADAL). ADAL is available on different platforms and allows client application developers to authenticate users to both on-premises AD and cloud-based resources. 40 ADAL is provided as an open source implementation. 41 The OAuth-based authentication stack used by new Office applications includes cross-platform support (e.g., iOS, Mac OS X, Android, Windows). The March 2015 update to Office 2013 includes productionready ADAL functionality. With this update, Outlook 2013 can perform X.509 authentication to its Office 365 mailbox. At the time of this report, the associated Office 365 Exchange tenant must be enabled 42 for modern authentication, and the Outlook client must be configured to use modern authentication protocols.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token, sso. Contains security framework guidance for authentication systems. Source: Derived Personal Identity Verification (PIV) Credentials (DPC) Proof of Concept Research."}]}
{"id": "nist_02828", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Discussion according to Security and Privacy Controls for Information Systems and Organizations? Discussion: Before permitting the use of shared or group accounts, organizations consider", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02829", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.3.1 Office 365 Exchange according to NIST Domain Name System-Based Electronic Mail Security According to Domain Name System-Based Electronic Mail Security, 3.3.1 Office 365 Exchange: Server-to-server encryption (Scenario 1) is available on Exchange for Office 365. Office 365 encrypts users' data while it's on Microsoft servers and while it's being transmitted between the user and Microsoft. Office 365 provides controls for end users and administrators to fine tune what kind of encryption is desired to protect files and email communications. Some technical library links for specific topics are as follows: - \uf0a7 Information on encryption using Office 365 Exchange can be found at https://technet.microsoft.com/en-us/library/dn569286.aspx. - \uf0a7 Information regarding the different types of email encryption options in Office 365 including Office Message Encryption (OME), S/MIME, Information Rights Management (IRM) can be found at https://technet.microsoft.com/en-us/library/dn948533.aspx. - \uf0a7 Information regarding definition of rules regarding email message encryption and decryption can be found at https://technet.microsoft.com/en-us/library/dn569289.aspx. - \uf0a7 Information regarding sending, viewing, and replying to encrypted messages can be found at https://technet.microsoft.com/en-us/library/dn569287.aspx. - \uf0a7 Service information for message encryption can be found at https://technet.microsoft.com/enus/library/dn569286.aspx.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domain Name System-Based Electronic Mail Security."}]}
{"id": "nist_02830", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Case Studies in Cyber Supply Chain Risk Management_ Summary of Findings and Recommendations provide? (Section 19) are utilized to prioritize supplier risks. <!-- image --> 6. Industry standards and best practices, such as ISO/IEC 20001 and SOC 2 compliance reports, are used to evaluate supplier cyber risks. 7. NIST CSF assessments are used by the acquirers and suppliers to determine the maturity of C-SCRM practices. 8. Risks of tariffs and data regionalization are evaluated to manage supply chains that span across multiple countries. Most organizations communicate with suppliers on a regular basis via traditional enterprise communication methods, including email, phone, communications platforms (e.g., Skype, Zoom, etc.), and supplier portals (e.g., iSupplier). Organizations also survey their critical suppliers annually to ensure people, data, and policies are maintained and up to date relative to supporting the contracts. These surveys include a variety of cybersecurity practices, such as supplier personnel receiving security training, physical security measures, use of security cameras and adequacy of camera recording storage, IT and network security measures, security organizational data on external networks, and assessment of applicable compliance levels. <!-- image --> Oversight of supplier C-SCRM practices is an important subject to every organization that was interviewed. Topics such as how to best monitor vendor quality against SLAs, company policies, and industry standards primarily drove the conversation. Additionally, organizations were focused on improving their vendors' security practices. 1. Prominence of industry standards and frameworks: Whether organizations looked to international, national, or industry-specific publications, all utilize multiple frameworks to evaluate the quality of their internal and vendor-specific C-SCRM practices. Organizations also frequently supplement these frameworks with legal or certification-based requirements. 2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: csf, fips, security control. General security reference material without sensitive content. Source: Case Studies in Cyber Supply Chain Risk Management_ Summary of Findings and Recommendations."}]}
{"id": "nist_02831", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management say about Appendix A-Acronyms? (Part 2) According to Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management, Appendix A-Acronyms: | AIS | Automated Indicator Sharing | |-------|---------------------------------------------------------------------------| | ALE | Annualized Loss Expectancy | | APT | Advanced Persistent Threat | | AWARE | Agency-Wide Adaptive Risk Enumeration | | BIA | Business Impact Analysis | | CCE | Common Configuration Enumeration | | CDM | Continuous Diagnostics and Mitigation | | CI | Confidence Interval | | CMDB | Configuration Management Database | | CPE | Common Platform Enumeration | | CSRM | Cybersecurity Risk Management | | CSRR | Cybersecurity risk register | | CTI | Cyber Threat Intelligence | | CVE | Common Vulnerabilities and Exposures | | CVSS | Common Vulnerability Scoring System | | DIB | Defense Industrial Base | | DCISE | DoD-Defense Industrial Base Collaborative Information Sharing Environment | | ERM | Enterprise Risk Management | | ERP | Enterprise Risk Profile | | ERR | Enterprise Risk Register | | ETA | Event Tree Analysis | | EV | Expected Value | HVA High-Value Asset IDS Intrusion Detection Systems IEC International Electrotechnical Commission IoC Indicators of Compromise ISAC Information Sharing Analysis Center ISAO Information Sharing and Analysis Organization ITAM Information Technology Asset Management ITL Information Technology Laboratory KPI Key performance indicator", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, intrusion detection. Contains technical security guidance that could inform defensive posture. Source: Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management."}]}
{"id": "nist_02832", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Authority Key Identifier : according to NIST NIST Test Personal Identity Verification (PIV) Cards Version 2 According to NIST Test Personal Identity Verification (PIV) Cards Version 2, Authority Key Identifier :: 77:6E:68:4A:1D:98:AF:46:CD:26:90:96:28:C3:E4:FD:CD:55:79:2C Key Usage : critical Digital Signature", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_02833", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain USER AWARENESS AND TRAINING according to NIST Security of Personal Computer Systems_ A Management Guide According to Security of Personal Computer Systems_ A Management Guide, USER AWARENESS AND TRAINING: Are users provided with adequate training and awareness of organizational information security policies and their individual responsibil ities? In each of the areas discussed in this questionnaire, are users provided adequate training in the performance of required procedures and the use of necessary equipment or systems?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security of Personal Computer Systems_ A Management Guide."}]}
{"id": "nist_02834", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations say about (b) General Provisions -? (Part 3) According to Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations, (b) General Provisions -: ee, revocation or status information access fee, key recovery fee, reimbursement for information desk services, fees for other services such as policy information, refund policy). Publication and Repositories - This subsection contains any applicable policies regarding 1) a key and/or certificate source's obligations, where keys are not locally generated, to publish information regarding its practices, its products (e.g., keys and/or certificates), and 93 E.g., PKI CA, PKI repository, PKI RA, PKI subscriber, key recovery agent (KRA) and/or PKI relying party in public key management and central oversight authority, key centers, multiple-center groups, service agents, and client nodes in the case of symmetric key management. the current status of such products; 2) the frequency of publication; 3) access control on published information (e.g., policies, practice statements, certificates, key and/or certificate status, RKNs); and 4) requirements pertaining to the use of repositories operated by private-sector CAs or by other independent parties. Compliance Audit 94 - This subsection addresses any high-level policies regarding 1) the frequency of compliance audits for CKMS entities, 2) the identity/qualifications of the compliance auditor, 3) the auditor's relationship to the entity being audited, 4) topics covered under the compliance audit, 95 5) actions taken as a result of a deficiency found during a compliance audit, and 6) the dissemination of compliance audit results.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, pki, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 2 \u2013 Best Practices for Key Management Organizations."}]}
{"id": "nist_02835", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2017 NIST_ITL Cybersecurity Program Annual Report say about Personal Identity Verification (PIV)? (Part 1) According to 2017 NIST_ITL Cybersecurity Program Annual Report, Personal Identity Verification (PIV): Personal Identity Verification (PIV) Figure 27: Government Employees Use PIV Cards for Facility Access <!-- image --> In response to Homeland Security Presidential Directive-12 (HSPD-12), Policy for a Common Identification Standard for Federal Employees and Contractors , the following NIST standard was developed, FIPS 201, Personal Identity Verification (PIV) of Federal Employees and Contractors . FIPS 201 was approved by the Secretary of Commerce in February 2005. HSPD-12 called for the creation of a new identity credential for federal employees and contractors. FIPS 201 is the technical specification for both the PIV identity credential and the PIV system that produces, manages, and uses the credential. Within NIST's ITL, this work is a collaborative effort of the CSD and the IAD. CSD activities in FY 2017 directly supported the latest revision of FIPS 201 (i.e., FIPS 2012) by updating the relevant publications associated with FIPS 201-2 and by initiating implementations of the credential on mobile devices. CSD performed the following activities during FY 2017 in support of HSPD-12: - Coordinated with the revision team in the ACD to update SP 800-63, titled The Digital Identity Guidelines , and ensured close alignment with the PIV Standard in areas of enrollment, identity proofing, authentication and credential lifecycle management. - With industry CRADA partners, built sample solutions at the NCCoE to demonstrate the issuance and use of PIV Credentials on mobile devices using commercial technologies. For more information visit https:/ /nccoe.nist.gov/ projects/building-blocks/piv-credentials.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02836", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy say about REAUTHORIZATION? (Part 3) According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy, REAUTHORIZATION: \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ reports, and plans of action and milestones-focused only on specific problems or ongoing issues, or as comprehensive as the initial authorization. The authorizing official signs an updated authorization decision document based on the current risk determination and acceptance of risk to organizational operations and assets, individuals, other organizations, and the Nation. In all situations where there is a decision to reauthorize a system or the common controls inherited by organizational systems, the maximum reuse of authorization information is encouraged to minimize the time and expense associated with the reauthorization effort (subject to organizational reuse policy).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_02837", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services? (Part 209) Control AM-1: | Identify the role of the organization or critical infrastructure in providing PNT services. Organizations using a PNT source to re- broadcast or transmit PNT data must be aware of how changes can impact PNT data and signals downstream. [BE-1, BE-2] Suppliers and third-party testing and certification . Consider relevant conformance testing, certification requirements, and processes. [SC-2] Identify vulnerabilities, including sources of errors, and threats in the PNT supply chain. For example, when PNT services are transferred through multiple parties and locations. [RA-1, RA-3] Assure the total uncertainty remains within industry standards and regulatory requirements. [GV-4] | Suppliers and third-party partners understand their roles and responsibilities. [AT-3] Hardware component authentication such as radio-frequency identification (RFIDs), physically unclonable functions (PUFs), or other markers. [AC-1, AC-6, AC-7] Hardware lifecycle management can include, but not limited to, consideration of the acquisition, integration, deployment, operations and maintenance, repair, and replacement of PNT components and services. [DS-3] | Clarify monitoring and detection responsibilities and support open communication channels among supply chain to analyze and support root cause determination of anomalous PNT data or signal output . [AE- 3] Understand risk impacts among supply chain partners . Policies and procedures, including lessons learned over time, are adequately documented and shared with stakeholders. [AE-4] PNT data alert thresholds are established. [AE-5] Verify PNT device integrity . Identify and document known limitations. [DS-6, DS-8] | Execute contingency procedures and assess functionality of systems relying on complementary PNT services or other third- party services . Notify downstream users of potential PNT data availability and integrity impacts. Record new threats and vulnerabilities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services."}]}
{"id": "nist_02838", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1 say about 5.1 Compliance Checking? (Part 1) According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1, 5.1 Compliance Checking: 5.1 Compliance Checking SCAP content can be used to compare system characteristics and settings against an SCAP-expressed checklist in an automated fashion. This can verify that operating systems and applications comply with security checklists and identify any deviations from those checklists. The SCAP source data stream component that MUST be included for compliance checking is the XCCDF Benchmark, which expresses the checklist. Each rule in the XCCDF Benchmark SHALL reference one of the following: - \uf03c An OVAL compliance definition. This definition SHALL be contained in an OVAL Compliance component, which holds the definitions of the compliance checks used by the checklist. The OVAL Compliance component SHALL have at least one OVAL definition of class compliance, MAY have one or more additional OVAL definitions of classes compliance and/or inventory, and SHALL NOT have any other classes of OVAL definitions. An XCCDF Benchmark's rules MAY reference one or more OVAL compliance definitions in an OVAL Compliance component. - \uf03c An OCIL questionnaire. This questionnaire SHALL be contained in an OCIL Questionnaire component, which holds the questionnaires that collect information that OVAL is not being used to collect, such as posing questions to users or harvesting configuration information from an existing database. An XCCDF Benchmark's rules MAY reference one or more OCIL questionnaires in an OCIL Questionnaire component. - \uf03c An OVAL Patch component. The OVAL Patch component holds definitions for patch compliance checks. These checks may be needed if an organization includes patch verification in its compliance activities. The OVAL Patch component SHALL have at least one OVAL definition of class patch, MAY have one or more additional OVAL definitions of classes compliance and/or inventory, and SHALL NOT have any other classes of OVAL definitions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1."}]}
{"id": "nist_02839", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IS-95 in Guidelines on Mobile Device Forensics? (Part 102) Control IS-95: Table 5: Example Record Structure | Field | Key | Description | |------------------------|-------|---------------------------------------------------------------------------------------------------------------------------------| | Record Type | M | Mobile originated | | Served IMSI | M | IMSI of the calling party | | Served IMEI | C | IMEI of the calling ME, if available | | Served MSISDN | O | The primary MSISDN of the calling party | | Called Number | M | The address of the called party, e.g., the number dialed by the calling subscriber | | Translated Number | O | The called number after digit translation within the MSC(if applicable) | | Connected Number | O | The number of the connected party if different from the Called Number | | Roaming Number | O | The Mobile Station Roaming Number employed to route this connection, if applicable | | Recording Entity | M | The E.164 number of the visitedMSC producing the record | | Incoming TKGP | O | The MSCtrunk group on which the call originated, usually from the BSS | | Outgoing TKGP | O | The trunk group on which the call left theMSC | | Location | M | The identity of the cell in", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Mobile Device Forensics."}]}
{"id": "nist_02840", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is in the implementation of the system according to Security and Privacy Controls for Information Systems and Organizations? in the implementation of the system: [Assignment: organization-defined system components].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02841", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders provide? (Section 196) OS and dependent software, including Java and Tomcat. The database can be installed on the same host as Tomcat, or remotely. Provision a TLS certificate for the server and configure Tomcat to use TLS. - \uf0a7 The configuration for push notifications to support OOB authentication is not required for this build; push notifications would be used when the mobile device is used to authenticate logins or transactions initiated on a separate device. - \uf0a7 Follow the instructions to generate an encryption key and encrypt database credentials in the installation script. Encrypting the push notification credentials is not required, unless that functionality will be used. - \uf0a7 For this lab build, the standalone installation was used. The standalone option uses the PostgreSQL database on the same host as the Authentication Server and also installs the Tutorial application. - \uf0a7 After running the installation script, delete the encryption key ( NNL\\_ENCRYPTION\\_KEY\\_BASE64 ) from nnl-install-conf.sh . - \uf0a7 For this lab build, the default policies and authenticators were used. In a production deployment, policies could be defined to control the authenticator types that could be registered and used to authenticate. - \uf0a7 Provisioning a Facet ID is not necessary for the OOB integration with Nok Nok Labs Passport, as used in the lab. If the Nok Nok Labs SDK were integrated with a custom mobile application, then the Facet ID would need to be configured, and the facets.uaf file would need to be published at a URL where it is accessible to clients. - \uf0a7 Application link/universal link integration (optional)-In the lab, the default setting using an application link under was used. This is acceptable for testing, but in a production deployment, an application link pointing to the IdP's actual domain name would typically be used.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, single sign-on. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_02842", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Secure Web Services provide? (Section 48) Each requirement may have any number of standards that support it. For example, both SSL/TLS and WS-Security provide confidentiality, integrity and authentication support for the messaging dimension, while the accountability requirement of the resource protection dimension does not have any supporting standards. The notion of core services has yet to be completely defined. Traditionally, these are services that can be used by any of the Web services in an organization's SOA. Two examples are the Open Grid Services Architecture (OGSA), developed for the Globus Grid, and the Department of Defense's (DoD's) Net- Centric Enterprise Services (NCES), developed for the Global Information Grid. Both OGSA and NCES provide a set of services available throughout an organization that are commonly used or essential to most Web services, such as discovery, authentication, and authorization. OGSA provides a comprehensive list of what can be offered as core services: service management, service communication, policy services, and security services. Most SOAs use these same categories of core services but may provide differing names: - Service management services : assist in managing a SOA by providing mechanisms to install, maintain, monitor, and troubleshoot Web services. - Service communication services : provide support for various types of communications models between services: queued messaging, publish-subscribe event notification, and distributed logging services. - Policy services : provide a framework for creating, administering, and managing policies for the infrastructure; these policies cover security, resource allocation, and performance. - Security services : provide support for different security models, mechanisms, protocols, and technologies that extend core Web services security protocols to support activities such as authorization, authentication, trust policy enforcement, and credential transformation. 17 Figure 2-10.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Guide to Secure Web Services."}]}
{"id": "nist_02843", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation say about Procedure? According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, Procedure: 1. Verify that there are no published ROAs that cover the route 10.100.0.0/16. 2. AS 65511 originates a BGP route advertisement for 10.100.0.0/16. 3. Verify that the RUT evaluates this route advertisement as not found . 4. Verify that this route is installed in the routing table. 5. AS 65511 publishes an ROA for its address space authorizing a different AS to originate addresses for it: (10.100.0.0/16, 16, AS65510). 6. Verify that the RUT now evaluates the route to 10.100.0.0/16 that AS 65511 originated as invalid . 7. Verify that this route is still in the routing table. For IPv6, use IP address FD10:100:100:1::/64 in place of 10.100.0.0/16.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_02844", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Practical Combinatorial Testing say about 3.3.2 Cost Factors? According to Practical Combinatorial Testing, 3.3.2 Cost Factors: Using 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. Combinatorial testing for input parameters can provide better test coverage at lower cost than conventional tests, and can be extended to high strength coverage to provide much better assurance.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Practical Combinatorial Testing."}]}
{"id": "nist_02845", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Basic Data according to Cell Phone Forensic Tools_ an Overview and Analysis? Basic Data: The following data was found and reported: IMSI, ICCID, Language Preference (LP), Abbreviated Dialing Numbers (ADN), Last Numbers Dialed (LND) and active/deleted SMS messages. (Meet)", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_02846", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SR-4 in Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives? (Part 53) Control SR-4: ovides a sense of completeness as a research agenda, as it progresses from pointed prerequisites (identity), through emergence of patterns, to anticipation of great scale (ecosystem interoperability). ## 7.1 Identity The theme of identity relates to long standing challenges arising from digital representations in cyberspace. The digital aspects of accountability and its consequences make the challenges particularly difficult. Two areas arise: assured links between uncommunicative physical objects and their data records and likewise, linkage of digital identities to human individuals, communicating sensors, and organizational entities. Two aspects of the identity emerging technology field are: 1.) Non-invasive means of marking physical objects without corrupting them (e.g., cyber-physical anchors), 2.) Privacy respecting means allowing humans and organizational entities to assert their identities for accountability. Additionally, identity as linkage to physical objects and human individuals may be very wellknown within an ecosystem but uncertainty may be introduced when mapping across intersecting ecosystems or by other challenges. Further challenges arise when inspecting parts virtually / remotely when uncertainties can be introduced. Consider including probabilistic aspects with identity with potential utilities such as cost functions. Impacts : Traceability is strengthened when an ecosystem provides: 1.) Provable linkage between physical goods and data records, 2.) Consistent, repeatable, and understandable means of establishing and using identity. ## 7.2 Message content standards The theme of message content standards encompasses the form and vocabulary for traceability transactions. What is the minimum set of data elements and the associated message or process context to support a successful traceability project? Can strategies from previous efforts at design criteria, such as an hour-glass model [35] serve as guidance?", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives."}]}
{"id": "nist_02847", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control provide? (Section 91) is is especially relevant to the ground segment. Space assets are high-cost, high-value assets that are inaccessible, have a limited ability to act autonomously, and are reliant on the ground segment. Response and business continuity plans for the ground segment need to be executed in a manner that is consistent with the space segment's ability to operate autonomously and in the case of a congested orbital slot, | [IEC61850-90-12] 5.8, 4.12- 4.14 [NIST-SP800-53r5] CP-1, CP-2, CP-7, CP-10, IR-1, IR- 7, IR-8, IR-9, PE-17 [NIST-SP800-61r2] [NIST-SP800-160V1] 6.5, 6.6, Appendix F.2 | | PR.IP-10 : Response and recovery plans are tested. | Organizations should assess preparedness by testing incident response and recovery plans to verify effectiveness and for training purposes. Organizations should also consider qualification and periodic testing to assess the response and recovery plans as the satellites lose capabilities due to age or changes to space operations that would significantly impact the performance requirements for the ground segment. Organizations should review the results of testing to determine the efficiency and effectiveness of the plans as well as readiness to execute the plans. The results can also be used to inform other Cybersecurity Framework Functions, such as Detect. Testing and verification of recovery plans should be done in a manner that does not impact operations. Consider the use of test environments (refer to PR.DS- 7).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control."}]}
{"id": "nist_02848", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is References according to NIST_SP_800-53r5_Security_Privacy_Controls? References: [OMB A-130], [SP 800-37].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02849", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does NIST_SP_800-37r2_Risk_Management_Framework say about GLOSSARY? (Part 49) According to NIST_SP_800-37r2_Risk_Management_Framework, GLOSSARY: ents. | | | Note 5: System elements and information resources (as defined at 44 U.S.C. Sec. 3502 and in this document) are interchangeable terms as used in this document. | | system development life cycle | 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. | | system privacy officer | Individual with assigned responsibility for maintaining the appropriate operational privacy posture for a system or program. | | systems privacy engineer | Individual assigned responsibility for conducting systems privacy engineering activities. | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | systems privacy engineering | Process that captures and refines privacy requirements and ensures their integration into information technology component products and information systems through purposeful privacy design or configuration. | |------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | systems security engineer | Individual assigned responsibility for conducting systems security engineering activities.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-37r2_Risk_Management_Framework."}]}
{"id": "nist_02850", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain ASSESSMENT OBJECTIVE according to NIST Assessing Security Requirements for Controlled Unclassified Information According to Assessing Security Requirements for Controlled Unclassified Information, ASSESSMENT OBJECTIVE: Determine if: A.03.03.01.ODP[01]: event types selected for logging within the system are defined . A.03.03.01.ODP[02]: the frequency of event types selected for logging are reviewed and updated. A.03.03.01.a: the following event types are specified for logging within the system: &lt;A.03.03.01.ODP[01]: event types&gt; . the event types selected for logging are reviewed A.03.03.01.b[01]: &lt;A.03.03.01.ODP[02]: frequency&gt; . the event types selected for logging are updated A.03.03.01.b[02]: &lt;A.03.03.01.ODP[02]: frequency&gt; .", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02851", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does ISCMA_ An Information Security Continuous Monitoring Program Assessment say about JUDGEMENT VALUES? (Part 2) According to ISCMA_ An Information Security Continuous Monitoring Program Assessment, JUDGEMENT VALUES: wever, the additional granularity facilitates analysis in ISCMAx, as described in Section 4.6. The examples throughout this report will illustrate both the recommended and the alternate judgment sets. In addition, ISCMAx is provided in two configurations: one preconfigured for the recommended judgment set and one preconfigured for the alternate judgment set.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: ISCMA_ An Information Security Continuous Monitoring Program Assessment."}]}
{"id": "nist_02852", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Foundational Cybersecurity Activities for IoT Device Manufacturers provide? (Section 34) curity needs and goals for the IoT device's expected customers and use cases, manufacturers can determine how to address those needs and goals in order to help customers mitigate cybersecurity risks. For each cybersecurity need or goal, the manufacturer can answer this question: which one or more of the following is a suitable means (or combination of means) to achieve the need or goal? - The IoT device can provide the technical means through its device cybersecurity capabilities (for example, by using device cybersecurity capabilities built into the device's operating system, or by having the device's application software provide device cybersecurity capabilities). - Another device related to the IoT device (e.g., an IoT gateway or hub also from the manufacturer, a third-party IoT gateway or hub) can provide the technical means on behalf of the IoT device (e.g., acting as an intermediary between the IoT device and other networks while providing command and control functionality for the IoT device). - Other systems and services that may or may not be acting on behalf of the manufacturer can provide the technical means (e.g., a cloud-based service that securely stores data for each IoT device, internet service providers and other infrastructure providers). - In addition to and support of technical means, non-technical means can also be provided by manufacturers or other organizations and services acting on behalf of the manufacturer (e.g., communication of lifespan and support expectations, disclosure of flaw remediation plans). - The customer can select and implement other technical and non-technical means for mitigating cybersecurity risks. (The customer can also choose to respond to cybersecurity risks in other ways, including accepting or transferring it.) For example, an IoT device may be intended for use in a customer facility with stringent physical security controls in place.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Foundational Cybersecurity Activities for IoT Device Manufacturers."}]}
{"id": "nist_02853", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guidelines on Firewalls and Firewall Policy? (Part 74) Control ES-1: ment function in accordance with the organization's policies and strategies. - GLYPH&lt;c=31,font=/EDBFEN+Webdings&gt; Performance. Solutions provide adequate performance during normal and peak usage. In many cases, the best way to test performance under the load of a prototype implementation is to use simulated traffic generators on a live test network to mimic the actual characteristics of expected traffic as closely as possible. Simulating the loads caused by DoS attacks can also be helpful in assessing firewall performance. Testing should incorporate a variety of applications that will traverse the firewall, especially those that are most likely to be affected by network throughput or latency issues. - GLYPH&lt;c=31,font=/EDBFEN+Webdings&gt; Security of the Implementation. The firewall implementation itself may contain vulnerabilities and weaknesses that attackers could exploit. Organizations with high security needs may want to perform vulnerability assessments against firewall components. - GLYPH&lt;c=31,font=/EDBFEN+Webdings&gt; Component Interoperability. Components of the firewall solution must function together properly. This is of greatest concern when a variety of components from different vendors are used. - GLYPH&lt;c=31,font=/EDBFEN+Webdings&gt; Policy Synchronization. If there are multiple firewalls running synchronized policies or groups of rules, test that the synchronization works in various scenarios (such as if one or more nodes are offline). - GLYPH&lt;c=31,font=/EDBFEN+Webdings&gt; Additional Features. Additional features that will be used by the firewall-such as VPN and antimalware capabilities-should be tested to ensure they are working properly. ## 5.4 Deploy Once testing is complete and all issues have been resolved, the next phase of the firewall planning and implementation model is deployment, which should be done in accordance with organization policies.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit, malware. Contains technical security guidance that could inform defensive posture. Source: Guidelines on Firewalls and Firewall Policy."}]}
{"id": "nist_02854", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 4.3 Policies Based on User Identity according to NIST Guidelines on Firewalls and Firewall Policy According to Guidelines on Firewalls and Firewall Policy, 4.3 Policies Based on User Identity: Traditional packet filtering does not see the identities of the users who are communicating in the traffic traversing the firewall, so firewall technologies without more advanced capabilities cannot have policies that allow or deny access based on those identities. However, many other firewall technologies can see these identities and therefore enact policies based on user authentication. One of the most common ways to enforce user identity policy at a firewall is by using a VPN. Both IPsec VPNs and SSL VPNs have many ways to authenticate users, such as with secrets that are provisioned on a user-by-user basis, with multi-factor authentication (e.g., time-based cryptographic tokens protected with PINs), or with digital certificates controlled by each user. NAC has also become a popular method for firewalls to allow or deny users access to particular network resources. In addition, application firewalls and proxies can allow or deny access to users based on the user authentication within the applications themselves. Firewalls that enforce policies based on user identity should be able to reflect these policies in their logs. That is, it is probably not useful to only log the IP address from which a particular user connected if the user was allowed in by a user-specific policy; it is also important to log the user's identity as well.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, token. Contains security framework guidance for authentication systems. Source: Guidelines on Firewalls and Firewall Policy."}]}
{"id": "nist_02855", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management provide? (Section 59) considering input from subject matter experts helps avoid 'following the herd' to unreasonable conclusions | Following Trends | | Tendency to over-focus on opportunities or issues that come readily to mind because one has recently heard or read about them | Concern that VPN confidentiality is insecure because quantum computing will make modern encryption obsolete and unreliable | Detailed and realistic risk analysis (Section 2.3) helps to evaluate the true probability of threats | Availability | While it is critical that enterprises address potential negative impacts on mission and business objectives, it is equally important (and required for federal agencies) that enterprises also plan for success.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management."}]}
{"id": "nist_02856", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PL-4 in Security and Privacy Controls for Information Systems and Organizations? (Part 2) Control PL-4: acknowledgment portion of the control, may be satisfied by the literacy training and awareness and role-based training programs conducted by organizations if such training includes rules of behavior. Documented acknowledgements for rules of behavior include electronic or physical signatures and electronic agreement check boxes or radio buttons. Related Controls: AC-2, AC-6, AC-8, AC-9, AC-17, AC-18, AC-19, AC-20, AT-2, AT-3, CM-11, IA-2,", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02857", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Proceedings of the Workshop of the Federal Criteria for Information Technology Security say about a. What Should be the Steps to Harmonization?? According to Proceedings of the Workshop of the Federal Criteria for Information Technology Security, a. What Should be the Steps to Harmonization?: Some comments expressed concern about the inherent feasibility of achieving harmonization. It was noted that there are four IT security criteria now in existence, in varying degrees of completion. The concern was how we can move from that posture to a single criteria that can be agreed upon by a large number of nations. A proposal has been made that the CCEB should focus its work on the common core, the toolset, and not on developing or agreeing on profiles.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Proceedings of the Workshop of the Federal Criteria for Information Technology Security."}]}
{"id": "nist_02858", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? (Part 263) Control HA-1: tore has another type of object called attestation signature or simply attestation . It is a signature block on someone else's 1 Some of our users like to call this 'the poor man's smartcard'. We try to tell them this is a particularly nasty misnomer - not only because certain media such as USB 'pen drives' are actually more expensive than smartcards (even including the cost of the reader), but also because they lack the tamper-proofness and crypto capabilities of the latter. certificate made by the private key of a user to indicate that it trusts that certificate (typically a root CA). This signature is detached - that is, it is stored in a separate file in a file format of our own devising; we will have more to say about attestations in section 2.1.1. . - Chaining: after the certificates are loaded from the physical stores, the CSM tries to chain them. First, duplicates are discarded and certificates issued by the same CA are sorted by their notBefore fields and assembled as a doublylinked list. The best current certificate is selected by applying two criteria: a) it is the one with the most recent notBefore and b) it must be still within validity (that is, with the current date/time before its notAfter field). If no certificate satisfies both requirements, we settle for the one that satisfies only (a). After that we build several indices for fast lookup: one keyed by the certificate's SHA1 hash, other by its Subject Key Identifier extension [7] and another by subject DN. This last one has a peculiarity: only the best current certificates make to this index; the future and previous editions don't get there.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02859", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Acknowledgments according to NIST Attribute-based Access Control for Microservices-based Applications using a Service Mesh According to Attribute-based Access Control for Microservices-based Applications using a Service Mesh, Acknowledgments: The 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Attribute-based Access Control for Microservices-based Applications using a Service Mesh."}]}
{"id": "nist_02860", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST Test Personal Identity Verification (PIV) Cards Version 2 provide? (Section 169) CN=Expired Test RSA 2048-bit CA for Test PIV Cards, ou=Test CA, o=Test Certificates 2010, c=US Validity : Not Before: Apr 3 19:56:01 2008 GMT, Not After: Apr 3 19:56:01 2010 GMT Subject : CN=Test E. Cardholder XV, ou=Test Agency, ou=Test Department, o=Test Government, c=US Subject Public Key Info : rsaEncryption, 2048-bit modulus, e=65537 78:85:E1:08:24:11:82:3A:34:41:59:94:D4:80:BF:23:EB:06:C9:1B 19:A6:D2:91:F3:37:A8:F8:BB:F0:6E:02:0B:85:B2:A6:8E:93:BC:AB ldap://smime2.nist.gov/cn=Expired%20Test%20RSA%202048- bit%20CA%20for%20Test%20PIV%20Cards,ou=Test%20CA,o=Test%20Certificates%20 2010,c=US?certificateRevocationList;binary CA Issuers - CA Issuers - ldap://smime2.nist.gov/cn=Expired%20Test%20RSA%202048- bit%20CA%20for%20Test%20PIV%20Cards,ou=Test%20CA,o=Test%20Certificates%20 2010,c=US?cACertificate;binary,crossCertificatePair;binary OCSP - Key Usage : critical Key Encipherment id\\_fpki\\_common\\_hardware email:test.cardholder15@mail.example.com Serial Number : 1508 (0x5e4) Signature Algorithm : ecdsa-with-SHA256 Issuer : CN=Test ECC P-256 CA for Test PIV Cards, ou=Test CA, o=Test Certificates 2010, c=US Validity : Not Before: Sep 25 23:18:12 2008 GMT, Not After: Sep 25 23:18:12 2010 GMT Subject : CN=Test E.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_02861", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems provide? (Section 19) A.' .'iA A-'^ v.K.'^smA V r&gt; &lt;\u2022 &gt;..M w^i .\u2022i..mc&gt;\u00bb 'i*' 1 \u00bbii&lt; i\u00abit\u00abhft iM' You may wish to perform operational testing at your selected backup facility once or twice a year. Each testing session should last for no more than one day and should be cleared in advance with both system managers. Before testing you should consult with your equipment vendor to insure that proper procedures are followed when transporting and reloading your media. Testing shold be performed in the same mode of operation (shared or dedicated) as provided for in the mutual assistance agreement. Operational testing is beneficial because it identifies incompatibilities between the two systems. For this reason, it is important that the system managers at both data processing sites receive advance notice of software and hardware changes. I'.'.\" x * \u2022'\u00bb ry\u00bbr \u2022 -.t) ; or- \\^\u00a35 *;&lt;\u00bb.\u00bb f: S'i'^ ' .*'.v \u2022 . , .i. ' 'ty n '\"&gt; od-'S :Xj5, X\u00bb.H,x,ds.*i*cJ r,,T&gt;J-S'fcqE\u00abiA d,\u00ab.fi 'f.. .\u00bb;'. . 1 \u2022' . , \u00bb,4 a. -pJxijSH'&amp;J . ac. , rlaar'jj\" '\u00ab&lt;Sr ,t i\u00bb 4i'I\u00a3^-.. I .i\u00ab5SER.w,r-\u00bbr i , - PUBUCATION OR REPORT NUMBER NIST.114A U.S. DEPARTMENT OF COMMERCE (REV. 3-89) NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY 1 . NISTIR 4359 2. PERFORMING ORGANIZATION REPORT NUMBER 3. PUBUCATION DATE AUGUST 1990 4. TITLE AND SUBTITLE Domestic Disaster Recovery Plan for PC's, OIS, and Small VS Systems 5. AUTHOR(S) US Department of State 6. PERFORMING ORGANIZATION (IF JOINT OR OTHER THAN NIST, SEE INSTRUCTIONS) U.S. DEPARTMENT OF COMMERCE NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY GAITHERSBURG, MD 20899 7. CONTRACT/ORANT NUMBER 8. TYPE OF REPORT AND PERIOD COVERED NISTIR 9. SPONSORING ORGANIZATION NAME AND COMPLETE ADDRESS (STREET, CITY, STATE, ZIP) Reprinted by permission of the U.S. Department of State, Office of Information Security, Washington, DC 20520 and the Advanced Information Management, Inc. Woodbridge, VA 22192 10.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Domestic Disaster Recovery Plan for PCs, OIS, and Small VS systems."}]}
{"id": "nist_02862", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain VENDOR: according to NIST Computer Security Training & Awareness Course Compendium According to Computer Security Training & Awareness Course Compendium, VENDOR:: Security Engineering Services, Inc. 5005 Bayside Road Chesapeake Beach, MD 20732 Bruce Gabrielson: (301) 855-4565 Participants learn technical rational and requirements that lead to formal management decision making regarding security issues. Topics Covered: Org. Security, Systems Security Engineering Management, Risk Management, Audit Controls, Contingency Planning, Risk Analysis, System Test and Evaluation, System Design, Network Administration, UNIX, Apple System 7, Config. Management, Life Cycle Management, Virus Protection, COMSEC, Control, TEMPEST Control and Vulnerability Assessments COURSE TITLE: Writing Security Plans COURSE LENGTH: 2 DAYS", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Computer Security Training & Awareness Course Compendium."}]}
{"id": "nist_02863", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case say about 4.11.5.1 Environment Setup? According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case, 4.11.5.1 Environment Setup: 1. NamicSoft was installed on a temp. Windows 10 laptop setup on a need-by basis. 2. The guest OS IP information of this server was set as follows: IP address: 192.168.0.11 Gateway: 192.168.0.2 Subnet Mask: 255.255.255.0", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case."}]}
{"id": "nist_02864", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-128 in Status Report on the Third Round of the NIST Post-Quantum Cryptography Standardization Process? (Part 4) Control ES-128: ecurity reductions to the underlying PKEs in the ROM, and non-tight security reductions in the QROM. Making some additional non-standard assumptions, one of the QROM security proofs can be made tight. The CCA security proofs are obtained from the OW-CPA assumption for the PKEs, thus relating the security of the NTRU submission to the original 1996 NTRU design. The submission specification uses both local and non-local cost models for determining the security category of their parameter sets. For a more direct comparison with the other KEM finalists, the assignment of security categories according to the non-local cost model is appropriate. This is what NIST used for NTRU in the figures and tables in this report. The design and parameter choices of NTRU protect against all the attacks known today. In their specification, analysis is provided for the primal and dual lattice attacks. The specification analyzes quantum versions of the above attacks as well but notes that all existing claims of a quantum speedup for lattice reduction algorithms rely on the QuantumRAM model of computation, which the submission describes as sufficiently unrealistic to be irrelevant to the security of NTRU in practice. The NTRU problem was first posed in 1996 and it remains unbroken despite many research advances in lattice attacks over the past few decades. This long security analysis provides confidence in the security of NTRU. Performance. The public key and ciphertext sizes for NTRU are comparable to the other structured lattice KEM candidates, although about 25% larger (see Table 6). NTRU KEMs have very good performance in software, especially on an AVX2 machine (see Figure 1). NTRU key generation is noticeably slower than that of the other two lattice KEM finalists. Significant events since Round 2. After being selected to be a finalist in the third round, NTRU made a few minor changes. This included an updated security analysis, as well as some patches to some reported bugs.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Third Round of the NIST Post-Quantum Cryptography Standardization Process."}]}
{"id": "nist_02865", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EU-73 in Design Alternatives for Computer Network Security? (Part 77) Control EU-73: d can be either dropped or carried along depending on which is more convenient. The other two designs utilized the implicit addressing schemes and either NOP'ed or deleted the command from the string. The latter also compresses the control string, but requires buffering. The implicit command addressing utilizes the address fields of the composite message leader, or nested leaders, (as discussed in Section 3.3.4) to identify which ICD executes which portion of the embedded commands. ## 4.3.3 Control Strings Using the Primitives As previously stated, the control commands (primitives) will be embedded in text strings, which will then cause the appropriate connections to be established via the interpretation of these strings at each ICD along the path (typically in a relay fashion) . We have found that these control strings look very complex, but upon closer inspection, one finds that they conform to a straightforward and static set of macro-like templates which the SC and its ICD could readily utilize to create the connections. ## 4.3.4 Concern for Errors in Control Commands Errors encountered in a control message must be handled with special care since the ICDs at the two ends may be left in different states, and hence may have to reinitialize via the SC. This condition would be similar to that encountered by loss of crypto-sync in a running key scheme; a condition that could otherwise be avoided by using a self-synchronizing method of cryptographic protection (see Section 4.4.1) If a sending ICD has a message buffer, it can hold a copy of a control message until it has successfully reached the recipient, (and retransmit if necessary) similarly, if a receiving ICD has a buffer it can delay executing any commands until the entire control message has been received and error checked. This would require that our conceptual model of an ICD be modified from that of Figure 4-2 to include a storage buffer between the deciphering unit and the control detector.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Design Alternatives for Computer Network Security."}]}
{"id": "nist_02866", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 118) nges in risk tolerance due to changes in the immediacy of mission or business needs, changes in the threat environment, and detection of potentially harmful or adverse events. Related Controls: SI-4. (4) INFORMATION FLOW ENFORCEMENT | FLOW CONTROL OF ENCRYPTED INFORMATION Prevent encrypted information from bypassing [Assignment: organization-defined information flow control mechanisms] by [Selection (one or more): decrypting the information; blocking the flow of the encrypted information; terminating communications sessions attempting to pass encrypted information; [Assignment: organization-defined procedure or method]]. Discussion: Flow control mechanisms include content checking, security policy filters, and data type identifiers. The term encryption is extended to cover encoded data not recognized by filtering mechanisms. Related Controls: SI-4. (5) INFORMATION FLOW ENFORCEMENT | EMBEDDED DATA TYPES Enforce [Assignment: organization-defined limitations] on embedding data types within other data types. Discussion: Embedding data types within other data types may result in reduced flow control effectiveness. Data type embedding includes inserting files as objects within other files and using compressed or archived data types that may include multiple embedded data types. Limitations on data type embedding consider the levels of embedding and prohibit levels of data type embedding that are beyond the capability of the inspection tools. Related Controls: None. (6) INFORMATION FLOW ENFORCEMENT | METADATA Enforce information flow control based on [Assignment: organization-defined metadata]. Discussion: Metadata is information that describes the characteristics of data. Metadata can include structural metadata describing data structures or descriptive metadata describing data content. Enforcement of allowed information flows based on metadata enables simpler and more effective flow control.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: rmf, fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02867", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications say about D.10 Test Results? (Part 2) According to A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications, D.10 Test Results: Table D.1: Illustration of Rejection/Uniformity Failures | Statistical Test | ExcessiveR ejections | Lacks Uniformity | Generator | |---------------------|------------------------|--------------------|----------------------------------| | Frequency | X | X | Modular Exponentiation | | Frequency | X | X | Cubic Congruential | | Frequency | X | X | Quadratic Congruential (Type I) | | Block Frequency | | X | Cubic Congruential | | Block Frequency | X | X | XOR | | Cusum | X | X | Micali-Schnorr | | Cusum | X | X | Modular Exponentiation | | Cusum | X | X | Cubic Congruential | | Cusum | X | X | Quadratic Congruential (Type I) | | Runs | X | | Modular Exponentiation | | Runs | X | X | Cubic Congruential | | Runs | X | | Quadratic Congruential (Type I) | | Rank | X | X | XOR | | Spectral | X | X | Cubic Congruential | | Spectral | | X | Quadratic Congruential (Type II) | | Aperiodic Templates | X | | ANSI X9.17 | | Aperiodic Templates | X | | Micali-Schnorr | | Aperiodic Templates | X | | Modular Exponentiation", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications."}]}
{"id": "nist_02868", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls say about 3.4 Inertia Problem? (Part 2) According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls, 3.4 Inertia Problem: l be no computer security problem; in short, the magic phrase \"distributed processing\" is often viewed as a solution to the computer security problem. Although there are cases where this is true (e.g. replacing a conventional time-shared service bureau with a lot of mini-computers), the major purpose of distributed systems --the ability to widely and selectively share information --requires that a distributed system at a high level of abstraction appear to be a single integrated system. And securely controlling access to and within this single system, whether distributed or not, comes up against the general computer security problem we have been discussing. Distributing processing hardware may remove the problems caused by a desire to share hardware resources, which is what has given rise to current perceptions of the computer security problem, but it does not remove the problem caused by a need to share information and the logical means for accessing it. See section 6.3 for a further discussion. The technology transfer problem can be seen in the fact that even if government procurement specifications were tightened to ask for the kind of security we believe possible with the current state of the art, fewer than fifty people in the country would understand the true implications of what is being asked for, and those fifty are concentrated in less than a half-dozen organizations, none of them in the main-stream development organizations of the major mainframe vendors. This is partly because at the moment most efforts of vendors relating to security are concentrating on the \"mechanisms\" part of the security problem, with very little attention to the \"assurance\" part.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls."}]}
{"id": "nist_02869", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Security Labels for Open Systems_ an Invitational Workshop say about 8. Support of a Fixed Label-Set Association? According to Security Labels for Open Systems_ an Invitational Workshop, 8. Support of a Fixed Label-Set Association: Going up the protocol stack, diverse labelled-fields are provided at the network layer domain access sublayer, and in order to provide uniform labelled-field support a transition must be made in some higher layer. The (L+l)-layer is the lowest such layer. The benefit of providing the mechanism for supporting a fixed-set-labelling facility at as low a layer as possible is that local labelling operations on a per-SDU basis will not be required above it, only on a perconnection basis. In many computers this gives a realistic opportunity for providing a separate process per connection, and therefore of using process separation as the basis for verification of confinement. The mechanism in the layers above the (L+l)-layer is as described above for the support of a fixed-set-labelling (N)-facility by a fixed-set-labelling (N-l) facility. An application association can then similarly be provided from a presentation layer connection.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Labels for Open Systems_ an Invitational Workshop."}]}
{"id": "nist_02870", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to SSL VPNs say about Executive Summary? (Part 2) According to Guide to SSL VPNs, Executive Summary: ingle standard SSL connection to a Web site to securely access multiple network services. The site accessed is typically called a portal because it is a single page that leads to many other resources. The remote user accesses the SSL VPN gateway using any modern Web browser, identifies himself or herself to the gateway using an authentication method supported by the gateway, and is then presented with a Web page that acts as the portal to the other services. - \u0084 SSL Tunnel VPNs. This type of SSL VPN allows a user to use a typical Web browser to securely access multiple network services, including applications and protocols that are not web-based, through a tunnel that is running under SSL. SSL tunnel VPNs require that the Web browser be able to handle active content, which allows them to provide functionality that is not accessible to SSL portal VPNs. Examples of active content include Java, JavaScript, Active X, or Flash applications or plug-ins. This publication discusses the fundamental technologies and features of SSL VPNs. It describes SSL and how it fits within the context of layered network security. It presents a phased approach to SSL VPN planning and implementation that can help in achieving successful SSL VPN deployments. It also compares the SSL VPN technology with IPsec VPNs and other VPN solutions. This information is particularly valuable for helping organizations to determine how best to deploy SSL VPNs within their specific network environments. Implementing the following recommendations should assist in facilitating more efficient and effective SSL VPN use for Federal departments and agencies.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to SSL VPNs."}]}
{"id": "nist_02871", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control FT-128 in Status Report on the Second Round of the NIST Lightweight Cryptography Standardization Process? (Part 133) Control FT-128: Code sizes (in bytes) for the smallest implementations of the primary hash variants on microcontrollers | | ATmega328P | ATmega4809 | SAM D21 | nRF52840 | PIC32MX | ESP8266 | |------------------|--------------|--------------|-----------|------------|-----------|-----------| | SHA-256 | 2284 | 2322 | 944 | 904 | 1576 | 1084 | | ACE | 2790 | 2482 | 1164 | 1216 | 2216 | 1484 | | ASCON | 2164 | 2148 | 1064 | 888 | 1404 | 1124 | | DryGASCON | 4648 | 4596 | 1320 | 1168 | 2136 | 1504 | | Gimli | 1220 | 1228 | 416 | 352 | 628 | 412 | | KNOT | 2128 | 1970 | 636 | 512 | 784 | 572 | | ORANGE | 2882 | 2894 | 1556 | 1456 | 2580 | 1760 | | PHOTON-Beetle | 1006 | 1000 | 3612 | 2420 | 6128 | 4532 | | Saturnin | 2582 | 2664 | 1280 | 1352 | 2100 | 1572 | | SKINNY-HASH | 2800 | 2694 | 2300 | 1896 | 2936 | 2136 | | SPARKLE | 1836 | 1938 | 848 | 752 | 1316 | 960 | | Subterranean 2.0 | 2614 | 2592 | 2364 | 2352 | 3136 | 2624 | | Xoodyak | 1996 | 2028 | 868 | 2676 | 1248 | 1004 | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Table 14.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Second Round of the NIST Lightweight Cryptography Standardization Process."}]}
{"id": "nist_02872", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Information Security Handbook_ A Guide for Managers provide? (Section 110) ning material. 34 See NIST SP 800-55, Security Metrics Guide for Information Technology Systems, and Chapter 7, Performance Measures, of this guide for additional guidance on measurements and metrics. Formal evaluation and feedback mechanisms are critical components of any security awareness and training program. Continuous improvement cannot occur without a good sense of how the existing program is working. In addition, the feedback mechanism must be designed to address objectives initially established for the program. Once the baseline requirements have been solidified, a feedback strategy can be designed and implemented. Various evaluation and feedback mechanisms that can be used to update the awareness and training program plan include surveys, evaluation forms, independent observation, status reports, interviews, focus groups, technology shifts, and/or benchmarking. A feedback strategy should incorporate elements that address quality, scope, deployment method (e.g., Web-based, onsite, offsite), level of difficulty, ease of use, duration of session, relevancy, currency, and suggestions for modification. Metrics are essential to feedback and evaluation. They can be used to: - Measure the effectiveness of the security awareness and training program; - Provide information for many of the data requests that an agency must provide with regard to compliance; and, - Provide an important gauge for demonstrating progress and identifying areas for improvement. It is necessary to ensure that the program, as structured, continues to evolve as new technology and associated security issues emerge. Training needs will shift as new skills and capabilities become necessary to respond to new architectural and technology changes. A change in the organizational mission and/or objectives can also influence ideas on how best to design training solutions and content.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_02873", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Stateless Hash-Based Digital Signature Standard say about 9.3 SLH-DSA Signature Verification? According to Stateless Hash-Based Digital Signature Standard, 9.3 SLH-DSA Signature Verification: As with signature generation, SLH-DSA signature verification (Algorithm 20) begins by computing a message digest (line 8) and then extracting \ud835\udc5a\ud835\udc51 (line 9), \ud835\udc56\ud835\udc51\ud835\udc65 \ud835\udc61\ud835\udc5f\ud835\udc52\ud835\udc52 (lines 10 and 12), and \ud835\udc56\ud835\udc51\ud835\udc65 \ud835\udc59\ud835\udc52\ud835\udc4e\ud835\udc53 (lines 11 and 13) from the digest. A candidate FORS public key is then computed (line 17), and the signature on the FORS key is verified (line 18). If this signature verification succeeds, then the correct FORS public key was computed, and the signature SIG on message \ud835\udc40 is valid.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Stateless Hash-Based Digital Signature Standard."}]}
{"id": "nist_02874", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives say about 8 Conclusions? (Part 2) According to Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives, 8 Conclusions: acy are more likely to initially be settled locally versus supply chain wide, where top-level agreements without organic lower-level support are likely be over-constrained and difficult to achieve. 2. These traceability ecosystems can internally use decentralized information sharing to overcome the restriction of typical bi-lateral business-to-business (B2B) connections (tiers). - a. This trend is observed. - b. The decentralized information sharing technology can range from DLT (Decentralized Ledger Technology) to blockchain. - c. The benefit of DLT is that the ecosystem can operate redundant nodes to add resiliency. - d. However, if the ecosystem needs more decentralization due to not entrusting any one participant with control over the data, then blockchain can be used (ledger + decentralized control). - e. Overcoming bi-lateral connections enables traceability data records to be shared as widely as agreements can be forged. This scope naturally forms an ecosystem and shares a common purpose, common agreement on language, and a common means to exchange data records. 3. These traceability ecosystems will soon start to connect and form a network of ecosystems. - a. This is the trend anticipated in manufacturing supply chains. - b. This trend has been recently observed in global identity networks. - c. A network of traceability ecosystems, together with a means to measure progress and make incremental improvements will grow the network. - d. Cybersecurity measures and perspectives will be influenced by the scale of interoperable ecosystems and redistribution of cyber responsibilities among participants. 4. The emergent growth of networks of ecosystems can be accelerated by larger feedback loops (hypothesis). - a. A feedback loop of observations, lessons learned, pattern derivation, and updated proposed research areas will grow the scope of networks of traceability ecosystems across the manufacturing supply chain. - b.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Blockchain and Related Technologies to Support Manufacturing Supply Chain Traceability_ Needs and Industry Perspectives."}]}
{"id": "nist_02875", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-002 in Guidelines for Smart Grid Cybersecurity? (Part 52) Control IP-002: egory 21 include: \uf0b7 Vendors acting in an (outsourced) operational role to perform troubleshooting and problem resolution (see Logical Interface Categories 1-4, 5-6, or 20, depending upon the role). 71 Figure 2-25 Logical Interface Category 21 2.3.18 Logical Interface Category 22: Interface between security/network/system management consoles and all networks and systems Logical interface category 22 covers the interfaces between security/network/system management consoles and all networks and systems: \uf0b7 Between a security console and network routers, firewalls, computer systems, and network nodes. The main activities performed on this interface include: \uf0b7 Communication infrastructure operations and maintenance; \uf0b7 Security settings and audit log retrieval (if the security audit log is separate from the event logs); \uf0b7 Future real-time monitoring of the security infrastructure; and 72 \uf0b7 Security infrastructure operations and maintenance. Key characteristics of this logical interface category as follows: \uf0b7 The functions performed on this interface are not considered real-time activities. \uf0b7 Some communications carried on this interface may be performed interactively. \uf0b7 The principal driver for urgency on this interface is the need for critical operational/security updates. \uf0b7 These functions are presently performed by a combination of \u2013 Separate remote access to devices, such as by dial-up connection; \u2013 Local access at the device/control system console; and \u2013 Access via the same interface used for real-time communications. Activities outside of the scope of Logical interface category 22 include: \uf0b7 Smart grid transmission and distribution (see Logical Interface Categories 1-4 and 5-6); \uf0b7 Advanced metering (see Logical Interface Category 13); and \uf0b7 Control systems engineering and systems maintenance (see Logical Interface Category 20).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02876", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Situational Awareness for Electric Utilities provide? (Section 245) ``` !Flags,CaseSens-,Overwrite regex.event.name,set.event.deviceVendor,set.event.deviceProduct .*Cyberlens.*,DragosSecurity,CyberLens ``` - Create a .csv file containing the text below, and copy this file to /opt/arcsight/&lt;connector directory&gt;/current/user/agent/acp/categorizer/current/&lt;deviceproduct&gt;/deviceproduct.csv | event. | set.event. | set.event. | set.event. | set.event. | set.event. | set.event. | |----------|--------------|--------------|--------------|--------------|--------------|--------------| | device | category | category | category | category | category | category | | Product | Object | Behavior | Technique | DeviceGroup | Significance | Outcome | CyberLens /Host /Found /Traffic Anomaly /IDS/Network /Informational /attempt This will allow a user to right-click on a URL in an event to spawn OnGuard with the URL passed as a parameter. Figure 2-84 ArcSight Configure <!-- image --> - In the name field, type I CS2-URL, then select the Program Parameters browse button. Figure 2-85 Program Parameters Setup <!-- image --> - Select Event Attributes &gt; Request &gt; Request URL . Figure 2-86 Request URL Configuration <!-- image --> - Select OK. Figure 2-87 Tool URL Verification <!-- image --> - Right-click on a URL in an event, select Tools, and verify that the ICS2-URL tool appears in the menu. - Follow ArcSight \u02bc s instructions for installing a Linux-based syslog SmartConnector. - Copy the custom FlexConnector configuration files to the appropriate locations. - See Sections 6-8 of cyberlens-syslog-configuration-v2\\_3.docx.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Situational Awareness for Electric Utilities."}]}
{"id": "nist_02877", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data according to NIST 2019 NIST_ITL Cybersecurity Program Annual Report According to 2019 NIST_ITL Cybersecurity Program Annual Report, Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data: Virtualization drives much of today's computing, and a basic component of that is the use of hypervisors-the software, firmware, or hardware that creates and runs many virtual machines. Because of the role that hypervisors play in critical technology such as cloud computing, they are often the target of attacks. To help address this need, NIST has developed a methodology to enable forensic analysis on attacks on hypervisors. Two open-source hypervisors-Xen and Kernel-based Virtual Machine (KVM)-were chosen as platforms to illustrate the methodology by analyzing the most recent vulnerability data from NIST's National Vulnerability Database (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, 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 were identified, and techniques required to gather missing evidence were incorporated during subsequent attack runs, essentially performing an iterative process.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST cybersecurity publication covering vulnerability management. Topics: vulnerability, exploit. Contains technical security guidance that could inform defensive posture. Source: 2019 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02878", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Web Transactions_ TLS Server Certificate Management provide? (Section 450) log with a note about the service check date verification, and the installation of the software may continue. F5 recommends reactivating the BIG-IP system license before conducting a software upgrade. Follow these steps to reactivate a BIG-IP system license using the Configuration utility: 1. Navigate to System &gt; License . 2. Click Re-activate . 3. In the Activation Method area, select Automatic (requires outbound connectivity). 4. Click Next . BIG-IP VE licenses are permanently associated with the virtual instance. To move a license, contact F5 Technical Support for assistance. However, with BIG-IP 12.1.3.3 and BIG-IP 13.1 and later, you can move the RegKey without contacting support by revoking the instance's license from tmsh, the Configuration utility, and iControl/REST by using the 'tmsh revoke sys license' command on that virtual instance. This action revokes the license and unlocks the RegKey-enabling the user to activate a new virtual machine. Call F5 Technical Support for assistance if the connection is lost and you want to move the license to the current VE, if hypervisor crashes, or if you can't access the password or network address. BIG-IP software offers two supported methods for backing up and restoring the configuration: user configuration set (UCS) archives and single configuration files. This guide focuses on using the UCS archive only. To create, delete, upload, or download an archive, you must have either administrator or resource administrator role privileges. A UCS archive contains BIG-IP configuration data that can fully restore a BIG-IP system in the event of a failure or return material authorization. Each time you back up the configuration data, the BIG-IP system creates a new UCS archive file in the /var/local/ucs directory. In addition to configuration data, each UCS file contains various configuration files necessary for the BIG-IP system to operate correctly.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Securing Web Transactions_ TLS Server Certificate Management."}]}
{"id": "nist_02879", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for API Protection for Cloud-Native Systems say about 2.3. Broken Authentication? According to Guidelines for API Protection for Cloud-Native Systems, 2.3. Broken Authentication: Authentication is a prerequisite for authorization, particularly two aspects: the authentication system itself is robust, and the application uses the authenticated identities correctly. Risks that an authentication system needs to mitigate include [8]: - Credential Stuffing is a type of brute force attack, where an attacker knows an account's name, and tries to brute force a ton of different passwords to unlock it. (They \"stuff all the credentials they can find\" into the victim system's authorization system in the hopes that something will stick). The attacker is able to carry out this since mitigation features such as rate limits, Captcha are absent. - Brute-force attacks on a single account without mitigations, which is closely related to unrestricted resource consumption (see Sec. 2.4) - Insecure practices, such as weak passwords, passing sensitive data in public channels (e.g., the URL), missing password validation for changes to sensitive account data, and using weak keys or poor algorithms to encrypt user data in transit and at rest - Bad or incorrect token validation, including not validating at all, ignoring expiry, and using insecure signing schemes or weak signing keys With a robust and secure authentication system in place, the application must use those credentials correctly. Risks to mitigate include: - Missing authentication (e.g., tokens can be present but simply not checked), often due to a bug or misconfiguration in the application - 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)", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, token. Contains security framework guidance for authentication systems. Source: Guidelines for API Protection for Cloud-Native Systems."}]}
{"id": "nist_02880", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is CONFIDENTIALITY according to Standards for Security Categorization of Federal Information and Information Systems? CONFIDENTIALITY: Preserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information. [44 U.S.C., SEC. 3542]", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Standards for Security Categorization of Federal Information and Information Systems."}]}
{"id": "nist_02881", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide? (Section 246) SAF Data Services Center (TS-S) Reasonable Modern Programming Techniques Limited System Integrity Measures 4. No User Programming (TS-S-C) Formal Design Specifications System Integrity Measures 5. Limited User Programming (TS-S-C) Proven Design Specifications Verifiable Implementation Limited Covert Path Provisions 6. Full User Programming (TS-S-C-U) Verified Design Automated Test Generation Extended Covert Path Provisions Reasonable Denial of Service Provisions We are mindful that the administrative aspects of the proposed process are formidable. Rough analogies can be found in current procurement practices. It should be noted that the whole process is somewhat akin to what is being done for pollution control. Public policy vaguely establishes a desire for cleaner air, whereas the technical discussions between the government and the automobile manufacturers establish approximately what is feasible. The policy setters, however, set the acceptable levels somewhat higher than industry would wish, and furthermore announce a general plan of tightening the standards over time. The same kind of process is envisioned here. The evaluation matrix is in effect the security standard analogous to the pollution level standard. At first, the entries in it would be fairly low, but as technology matures (mostly the assurance technology) the standards would be tightened. Publication of intention to follow this process, along with the timetable of standards-tightening, would encourage vendor development, provided it is all done in a reasonable, public, and well-informed manner. ' jj f Note: Special thanks and credit to Clark Weissman for most of the material in this section.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls."}]}
{"id": "nist_02882", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Justification according to Security Analysis of First Responder Mobile and Wearable Devices? Justification: Public safety practitioners would likely try to use public safety-grade, ruggedized devices where possible.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security Analysis of First Responder Mobile and Wearable Devices."}]}
{"id": "nist_02883", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard provide? (Section 104) hannel implementation, a multi-chip DES for high speed reasons. The integrated approach of implementing the DES as a CPU hardware device requires a very careful solution to the key management problem. With that in mind, I will define what I call an \"optimum\" solution to key management and key distribution in an integrated CPU and DES facility.* Let us design a network consisting of N devices attached to a CPU. Each terminal has an imbedded, private Device Key (the encryption key to be used with the DES). Each key is different for good security. The question is, \"How can any device talk to any other device if all of the keys are different?\" The solution is to maintain a list of all of the private Device Keys in the memory of the CPU and let the CPU generate a new key for use in protecting the data between any two common devices. *Editor's Note: Dr. Tuchman told a lengthy, humorous story at this point to illustrate his definition of the word \"optimum.\" To prevent this list of keys from being stolen or accidentally lost, we will encrypt this list of keys with another key which we call the Master Key . This key is located only on the DES device and cannot be read by anyone. The following happens during a \"session\" of communications between any two of the devices. Let us say that terminal 2 wants to talk to terminal 8. The private keys for terminals 2 and 8 are both contained in the encryption key list which, of course, is encrypted by the Master Key. The CPU generates an encrypted Session Key from a device that is time-dependent and pseudo-random, such as the system clock. This encrypted Session Key ( defined to be encrypted under the Master Key and never appearing in the CPU in its plain form) as well as the Private Key for terminal 2 and the Private Key for terminal 8, are all sent to the DES device controlled by the CPU.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard."}]}
{"id": "nist_02884", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST Test Personal Identity Verification (PIV) Cards Version 2 provide? (Section 22) ndicates that there are six retired key management keys on the card (two 2048-bit RSA, two ECC Curve P-256, two ECC Curve P-384) but that none of the corresponding certificates are stored on the card. A URL is provided that refers to a file containing all of the retired certificates for key management. Test PIV Card 5 supports secure messaging using cipher suite 7 and also implements the VCI. Test PIV Card 6 only contains those data objects that are listed as mandatory in [SP800-73] (except for the Discovery object and Biometric Information Templates Group Template, which are present on every test card). 4 Test PIV Card 6 includes a PIV Authentication certificate and a Card Authentication certificate but no digital signature certificate or key management certificate. The subject name in the PIV Authentication certificate contains the card's FASC-N rather than the cardholder's name, and the subjectAltName extension in the 3 A few of the retired certificates for key management contain RSA subject public keys and are signed using RSA PKCS #1 v1.5. 4 The BIT Group Template on every test card except Test PIV Card 8 contains no BITs, indicating that on-card biometric comparison is not supported. PIV Authentication certificate only includes the card's FASC- N and UUID. The card's FASC-N indicates that the cardholder is a contractor, and the NACI indicator extension in the PIV Authentication certificate indicates that the cardholder's NACI had not been completed at the time that the certificate was issued. The Printed Information buffer is not present on the card. Test PIV Card 7 represents a legacy PIV Card. Unlike all of the other test cards, the PIV Authentication, digital signature, and key management certificates on Test PIV Card 7 do not include an extended key usage extension. Like Test PIV Card 1, the PIV Authentication certificate on Test PIV Card 7 includes a UPN in the subjectAltName.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: NIST Test Personal Identity Verification (PIV) Cards Version 2."}]}
{"id": "nist_02885", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SR-2 in Security Recommendations for Server-based Hypervisor Platforms? (Part 21) Control SR-2: o ensure memory consistency. During this phase, the exact state of all the processor registers currently operating on the VM are also transferred, and the migrating VM is suspended on the source host. Processor registers at the destination are modified to replicate the state at the source, and the newly migrated VM resumes its operation. Storage migration is provided by a feature that allows admins to move a VM's file system from one storage location to another without downtime. This storage migration can even take place in situations where there is no VM migration. For example, a VM may continue to run on the host server while the files that make up the VM are moved among storage arrays or Logical Unit Numbers (LUNs). In the process described above, the memory and processor-state migration functions are inherent aspects of hypervisor design. The storage migration function is an integral part of storage management and is applicable to both virtualized and non-virtualized infrastructures. The network state is maintained after a VM migration because each VM carries its own unique MAC address, and the migration process places some restrictions on the migration target (e.g., the source and target host should be on the same VLAN). Hence, from the security protection point of view, the only aspects to consider are proper authentication and a secure network path for the migration process. Security Recommendation HY-SR-13: During VM live migration, a secure authentication protocol must be employed; the credentials of the administrator performing the migration are passed only to the destination host; the migration of memory content and processor state takes place over a secure network connection; and a dedicated virtual network segment is used in both source and destination hosts for carrying this traffic.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Security Recommendations for Server-based Hypervisor Platforms."}]}
{"id": "nist_02886", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings? (Part 403) Control HA-1: e procedure, we defi ned the sets E val g;i using a PDS P C i . However, we plan to employ a And-or graph from which the sets E val g;i can be computed for all g using a single fi x point computation. Now we describe the And-or graph construction for a set D of certifi cates. First using the certifi cate set D ; we fi rst defi ne a nondeterministic normalized pushdown system P ; from which we defi ne an equivalent context free grammar G ; which is converted in to an And-Or graph H : The advantages of using the And-Or graph over the PDS model of Jha and Reps [JR02] is that we have the reachability relationships between various principals in one structure from which the required relations can be computed effi ciently. The And-or graph H can be computed directly from C without constructing either of P or G . However, their defi nition gives a better intuition leading to an easy proof of correctness of the algorithm. The given certifi cate system D is expressed as a set of rewriting rules, the name certs correspond to the rules of form K 1 A ! K 2 A 1 A 2 :::A n . The auth certs correspond to rules of the form K / ! K 1 A 1 A 2 ::A n / . Corresponding to each key K we introduce two symbols K / ; K \u00a5 . K # is the augmented set of keys consisting of the original keys and their associated symbols. Given the set D of cert rules, all the rules will be converted to a normalized transition function -of a pushdown system. The pushdown system P we consider is a three tuple ( Q; \u00a1 ; -) : Q is the set of states as given below, \u00a1 is the stack alphabet containing identifi ers and delegation symbols of a SPKI system, -GLYPH&lt;181&gt; Q \u00a3 f \u00a1 [ f \u2020 gg \u00a3 Q \u00a3 f \u00a1 [ f \u2020 gg is the transition function. -can have transitions either of type ( K 1 ; A 1 ; K 2 ; \u2020 ) or ( K 1 ; \u2020; K 2 ; A 1 ) , which means that PDS can go from state K 1 to state K 2 either by popping or pushing a symbol A 1 2 \u00a1 on top of the stack. \u2020 is the empty string character.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, sso. Contains security framework guidance for authentication systems. Source: 4th Annual PKI R&D Workshop _Multiple Paths to Trust_ Proceedings."}]}
{"id": "nist_02887", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does A Data Structure for Integrity Protection with Erasure Capability provide? (Section 7) ions, with extensions to the algorithms above. Many thanks to Lee Badger, Jeff Voas, Sandy Ressler, Dylan Yaga, and Peter Mell for review and discussion of the original paper on this work. Thanks to Peter for suggesting the alternative of hashing a concatenation of block hashes. [1] D Richard Kuhn. A data structure for integrity protection with erasure capability. NIST Cybersecurity Whitepaper , 2018. - [2] Matthias Berberich and Malgorzata Steiner. Blockchain technology and the gdpr-how to reconcile privacy and distributed ledgers. Eur. Data Prot. L. Rev. , 2:422, 2016. - [3] Henry Chang. Blockchain: Disrupting data protection? Privacy Law and Business International Report, November , 2017. - [4] O. Kharif. Is your blockchain doomed? Bloomberg Business Week, Mar. 22 , 2018.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Data Structure for Integrity Protection with Erasure Capability."}]}
{"id": "nist_02888", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Forensic Filtering of Cell Phone Protocols say about Appendix A - Example PCS Filter Log? (Part 6) According to Forensic Filtering of Cell Phone Protocols, Appendix A - Example PCS Filter Log: ``` [02552] FBusFeedSentFrame: unknown request 0 [02552] 1e 00 10 19 00 08 00 03 01 f0 12 00 01 43 1c a1 [03852] FBusFeedRecvFrame: unsupported FBus response (see below) [03852] 1e 10 00 19 00 0c 03 33 01 f0 13 10 04 55 55 55 [03852] 01 40 5f 96 [02464] FBusFeedSentFrame: unknown request 0 [02464] 1e 00 10 39 00 08 00 03 01 f0 12 00 01 44 1c 86 [03852] FBusFeedRecvFrame: unsupported FBus response (see below) [03852] 1e 10 00 39 00 0c 03 60 01 f0 13 14 00 00 00 00 [03852] 01 41 0e e0 [04064] FBusFeedSentFrame: unknown request 0 [04064] 1e 00 10 3e 00 08 00 03 01 f0 12 00 01 45 1c 80 [03852] FBusFeedRecvFrame: unsupported FBus response (see below) [03852] 1e 10 00 3e 00 0c 03 3c 01 f0 13 03 00 00 00 00 [03852] 01 42 0e af [02552] FBusFeedSentFrame: unknown request 0 [02552] 1e 00 10 22 00 08 00 03 01 f0 12 00 01 46 1c 9f [03852] FBusFeedRecvFrame: unsupported FBus response (see below) [03852] 1e 10 00 22 00 0c 03 59 01 f0 13 01 00 55 55 55", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Forensic Filtering of Cell Phone Protocols."}]}
{"id": "nist_02889", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Control according to Security and Privacy Controls for Information Systems and Organizations? Control: Include the following requirements, descriptions, and criteria, explicitly or by reference,", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02890", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Property Management Systems provide? (Section 160) Click Next. 14. Change the communication server service information if desired: <!-- image --> 15. Click Next. 16. Change the schedule service information if desired. <!-- image --> 17. Click Next. 18. Change the message queue service information if desired: <!-- image --> 19. Click Next. 20. Change the web service name if desired. Select Encrypted communication (SSL): <!-- image --> <!-- image --> 22. Click Install. 23. Wait for the installation to complete. 24. Verify that 'Start Dialock 2.0 now' is checked: 25. Click Finish. 26. A web page should open automatically. If not, navigate to <!-- image --> <!-- image --> 27. Log in with the default credentials provided in the installation guide: <!-- image --> 28. Click the box next to the 'Upload license file' to open a file explorer. 29. Locate the license file for dialock2 and click Open: 30. Input the provided license key: <!-- image --> <!-- image --> 31. Click Import: <!-- image --> 32. Click admin in the top right corner of the page: 33. Click Change password. 34. Enter the current password as well as a new password. Confirm the new password: <!-- image --> <!-- image --> 35. Click OK: <!-- image --> 1. Turn on the encoding station. 2. Note the IP address displayed on the device. 3. Connect the encoding station to a network where the displayed IP address is accessible. 4. Open a web browser and navigate to the IP address. <!-- image --> 5. Sign in with the credentials provided in the installation guide: 6. Select Network: <!-- image --> <!-- image --> 7. Check DHCP: 8. Click Apply Changes. 9. The new IP address should be visible on the encoding station device. <!-- image --> 1. First, add the encoder if it has not already been detected. To do this, navigate to Devices &gt; Coding Devices by using the main menu. 2. From there, you will see a menu titled Encoders list.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Property Management Systems."}]}
{"id": "nist_02891", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain ADVERSARY EFFECTS according to NIST Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171, ADVERSARY EFFECTS: See [SP 800-160-2]: [ Preclude (Expunge); Impede (Exert)].", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_02892", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2. Identity Provider Models and Recommendations according to NIST A Credential Reliability and Revocation Model for Federated Identities According to A Credential Reliability and Revocation Model for Federated Identities, 2. Identity Provider Models and Recommendations: For the purpose of this document, the identity provider and associated authentication solutions can be categorized according to the number of parties involved in an authentication event. The two-party model, for example, involves only the service provider and the credential holder (user) in the authentication event. The four-party model, on the far end of the spectrum, involves the credential holder, an independent identity provider, the service provider, and one or more independent attribute providers that vouch for attributes requested by the service provider. These and other models are discussed in this section. Where applicable, recommendations are identified to improve credential revocation.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: A Credential Reliability and Revocation Model for Federated Identities."}]}
{"id": "nist_02893", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Threshold Schemes for Cryptographic Primitives_ Challenges and Opportunities in Standardization and Validation of Threshold Cryptography provide? (Section 40) eal hardware and software, the black-box assumption can break down in several ways. For example, bugs in the implementation can lead to side effects that compromise the secret key, as with Heartbleed. Also, the material and electromagnetic characteristics of the platforms on which the algorithms run can cause side-channel information to leak and allow attackers to recover the secret key. The distinction of ideal versus real implementations can yield useful insights into the assessment of threshold schemes for cryptographic primitives. What are the security advantages and disadvantages of performing separate computations on shares of a key, compared to conventional implementations that use a single secret key? How can threshold cryptography mitigate the potentially disastrous consequences that a coding error or a side-channel leak could have on a conventional implementation? This section considers how a range of applicable scenarios may differently affect a range of tradeoffs between several security properties. These scenarios depend on adversarial goals and capabilities, and various properties of the system model. It is important to be aware that security strengthening and weakening may co-exist. The discussion also preludes the next section, which motivates the need to describe characterizing features of threshold schemes. In a first baseline comparison, a real implementation allows vectors of attack not possible in an ideal black-box. Once these are identified, one asks how to augment conventional implementations, in the real world, to improve security. Particularly, how does a threshold approach affect security, compared to a non-threshold approach? Perhaps security is improved if an attacker is limited to not compromising more than f -out-ofn components within a certain time interval. Also, as explained in Sec. 3.2, a threshold design may make it inherently more difficult to exploit existing compromises (such as noisy leakage) in the set of 'parties'.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Threshold Schemes for Cryptographic Primitives_ Challenges and Opportunities in Standardization and Validation of Threshold Cryptography."}]}
{"id": "nist_02894", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 9.6. 1.2. univ-id according to NIST Secure Data Network Systems (SDNS) Key Management Documents According to Secure Data Network Systems (SDNS) Key Management Documents, 9.6. 1.2. univ-id: This parameter is required on the request primitive. It is passed on the indication primitive. It contains the universal-ID associated with the key material and CRL version number.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: Secure Data Network Systems (SDNS) Key Management Documents."}]}
{"id": "nist_02895", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does National Checklist Program for IT Products_ Guidelines for Checklist Users and Developers provide? (Section 34) ists can reduce what would otherwise be a 'reinvention of the wheel' for IT products that are widely used in the federal government, such as common operating systems, servers, and client applications. The NIST checklist repository (located at ) contains information on automated and non-automated checklists that have been developed and screened to meet the requirements of the NCP. The repository also hosts copies of some checklists, primarily those developed by the federal government, and has pointers to the other checklists' locations. Users can browse checklist descriptions to locate and retrieve a particular checklist using a variety of different fields. A mailing list for the checklist program is available at https://nvd.nist.gov/general/email-list. 5 The Extensible Checklist Configuration Description Format (XCCDF) is an XML-based format for automating tool usage and eliminating interpretation issues. The XCCDF XML format can be used for both technical checklists (e.g., operating systems, software applications, and hardware configurations) and non-technical checklists (e.g., physical security for IT systems). More information on XCCDF is available from NIST Interagency Report (IR) 7275 Revision 4, the Extensible Configuration Checklist Description Format (XCCDF) Version 1.2, which is available for download at https://doi.org/10.6028/NIST.IR.7275r4 Another XML-based format for checklists is the Open Vulnerability and Assessment Language (OVAL), which is used to exchange technical details about how to check for the presence of 6 https://scap.nist.gov/validation/index.html. Specification for vulnerabilities and configuration issues on systems. More information on OVAL is available at https://oval.cisecurity.org.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: National Checklist Program for IT Products_ Guidelines for Checklist Users and Developers."}]}
{"id": "nist_02896", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is System Hardware according to Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI? System Hardware: Unisys U 6000 Series Model: U 6000/60", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI."}]}
{"id": "nist_02897", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Bluetooth Security say about 2.1.1.2 High Speed with Alternate MAC/PHY? According to Guide to Bluetooth Security, 2.1.1.2 High Speed with Alternate MAC/PHY: Introduced in the Bluetooth 3.0 + HS specification, devices can support faster data rates by using Alternate MAC/PHYs (AMP). This is known as Bluetooth high speed technology. In the Bluetooth 3.0 + HS specification, IEEE 802.11-2007 was introduced as the first supported AMP. IEEE 802.11-2007 is a rollup of the amendments IEEE 802.11a through 802.11j. For the 802.11 AMP, IEEE 802.11g PHY support is mandatory, while IEEE 802.11a PHY support is optional. The 802.11 AMP is designed to provide data rates up to 24 Mbps using Orthogonal Frequency-Division Multiplexing (OFDM) modulation. Note that this AMP is IEEE 802.11 compliant but not Wi-Fi compliant. Therefore, Wi-Fi Alliance specification compliance is not required for Bluetooth 3.0 + HS devices.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Bluetooth Security."}]}
{"id": "nist_02898", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Identity and Authentication (IA): according to NIST A Threat Analysis on UOCAVA Voting Systems According to A Threat Analysis on UOCAVA Voting Systems, Identity and Authentication (IA):: Officials should develop technical and procedural mechanisms to identify all users of the election system, including voters, election officials and system administrators. Voter authentication in registration systems is largely done via procedural mechanisms. Individual jurisdictions must determine appropriate voter authentication mechanisms. Voters must provide election officials with an authenticator during the registration phase. For election systems using e-mail ballot return, the most likely authenticator is a voter signature. Authenticators must be securely stored by election officials so that it is available to authenticate future correspondence from a voter. Other systems may use passwords, PINs, or digital signatures. Authentication on election IT systems should be automated and tied to the systems' access control and auditing mechanisms. Systems should identify and authenticate each individual with access to a system, usually through a user name and password. Jurisdictions should develop appropriate policies regarding the use of passwords for authentication, including setting password complexity requirements and expiration times.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication. Contains security framework guidance for authentication systems. Source: A Threat Analysis on UOCAVA Voting Systems."}]}
{"id": "nist_02899", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does 2017 NIST_ITL Cybersecurity Program Annual Report say about Automated Combinatorial Testing? (Part 1) According to 2017 NIST_ITL Cybersecurity Program Annual Report, Automated Combinatorial Testing: Automated Combinatorial Testing Software engineers often encounter failures that result from an unexpected interaction between components. A NIST investigation of actual failures has shown that most failures are triggered by one or two parameters, and progressively fewer by three, four, or more parameters (see Figure 41); this relationship is called the Interaction Rule. These results have important implications for testing software and systems. If all faults in a system can be triggered by a combination of n or fewer parameters, then testing all n -way combinations of parameters with a practical number of tests can provide strong fault detection efficiency. These methods are being applied to software and hardware testing for reliability, safety, and security. CSD's focus is on empirical results and the impact on real-world problems. Project highlights for FY 2017 include the development of a mathematical model that closely replicates the evolution and distribution of t-way failures found in empirical studies; invited lectures at conferences and universities; leading the Sixth International Workshop on Combinatorial Testing, held in conjunction with the Ninth IEEE International Conference on Software Testing; the development of combinatorial test methods specific to text search, with a demonstration of their practical application; and the development of combinatorial test methods specific to cryptographic software that discovered previously unknown faults in AES algorithm implementations. Collaborators include researchers from the University of Texas at Arlington, the University of Texas at Dallas, Loyola University of Maryland, East Carolina University, Duke University, Texas A&amp;M, and the Air Force Institute of Technology.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: 2017 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02900", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 1 \u2013 General say about 5.2 Key Usage? (Part 1) According to Recommendation for Key Management_ Part 1 \u2013 General, 5.2 Key Usage: 5.2 Key Usage In general, a single key shall be used for only one purpose (e.g., encryption, integrity authentication, key wrapping, random bit generation, or digital signatures). There are several reasons for this: 1. The use of the same key for two different cryptographic processes may weaken the security provided by one or both of the processes. 2. Limiting the use of a key limits the damage that could be done if the key is compromised. 3. Some uses of keys interfere with each other. For example, consider a key pair used for both key transport and digital signatures. In this case, the private key is used as both a private key-transport key to decrypt the encrypted keys and as a private signature key to generate digital signatures. It may be necessary to retain the private key used for transport key 50 See FIPS 186 and SP 800-56A 51 See Section 4.2 52 See SP 800-56A and SP 800-56B. 53 See SP 800-90A. 54 See SP 800-90A, SP 800-56A, SP 800-56B, and SP 800-108. 55 See SP 800-132. beyond the cryptoperiod of the corresponding public key in order to decrypt the encrypted keys needed to access encrypted data. The private key used for signature generation shall be destroyed at the expiration of its cryptoperiod to prevent its compromise (see Section 5.3.6). In this example, the longevity requirements for the private key-transport key and the private digital-signature key contradict each other. This principle does not preclude using a single key in cases where the same process can provide multiple services. This is the case, for example, when a digital signature provides integrity authentication and source authentication using a single digital signature or when a single symmetric key can be used to encrypt and authenticate data in a single cryptographic operation (e.g., using an authenticated-encryption operation as opposed to separate encryption and authentication operations).", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, key management. Contains security framework guidance for authentication systems. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02901", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Staging Cybersecurity Risks for Enterprise Risk Management and Governance Oversight say about Table of Contents? (Part 1) According to Staging Cybersecurity Risks for Enterprise Risk Management and Governance Oversight, Table of Contents: Table of Contents | Executive Summary............................................................................................................................1 | |-----------------------------------------------------------------------------------------------------------------------------------------------------| | 1. Introduction...................................................................................................................................3 | | 2. Aggregation and Normalization of Cybersecurity Risk Registers.......................................................7 | | 3. Integration of Cybersecurity Risk into the ERR/ERP .......................................................................11 | | 4. Risk Governance as the Basis for Cybersecurity Risk Management.................................................20 | | 4.2.1. Adjustments to Cybersecurity Program Budget Allocation........................................................26 | | 4.2.2. Adjustments to Risk Appetite and Risk Tolerance......................................................................27 | | 4.2.3. Reviewing Whether Constraints are Overly Stringent ...............................................................28 | | 4.2.4. Adjustments to Priority ..............................................................................................................28 | | 5. Cybersecurity Risk Monitoring, Evaluation, and Adjustment..........................................................30 | | Appendix A. Change Log...................................................................................................................39 | | List of Tables Table 1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Staging Cybersecurity Risks for Enterprise Risk Management and Governance Oversight."}]}
{"id": "nist_02902", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Situational Awareness for Electric Utilities say about Web and Services? (Part 1) According to Situational Awareness for Electric Utilities, Web and Services: Web and Services - Microsoft Internet Information Services (IIS) 8 - Microsoft .NET Framework 4.5 Use Server Manager for installing IIS and .NET Framework, referring to for detailed steps and corresponding screenshots. First install IIS and then install the .NET Framework. Table 2-3 below summarizes the required IIS components and .NET Framework features followed by the screenshots.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Situational Awareness for Electric Utilities."}]}
{"id": "nist_02903", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework say about FR.NEMA-2Aa? According to Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework, FR.NEMA-2Aa: Firmware Upgrade Recovery to Previously Installed Firmware Reference : NEMA SG-AMI 1-2009, Section 3.2.2 'Smart Meter shall recover to the previously installed Firmware \u2026 if unable to complete the Upgrade Process.'", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework."}]}
{"id": "nist_02904", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Common Platform Enumeration_ Dictionary Specification Version 2.3 say about 5. CPE Dictionary Data Model? (Part 2) According to Common Platform Enumeration_ Dictionary Specification Version 2.3, 5. CPE Dictionary Data Model: optional instead of mandatory), and the schema extension contains the CPE Dictionary 2.3 specific elements and attributes. The tables below define the elements of the data model and their properties. Several of the elements allow organizations to supply additional information that is not covered by these properties. However, such information is not part of the official CPE Dictionary data model, and there are no requirements for dictionary users to access or process this information. In the tables below, types prefixed with 'cpe\\_dict:' are from the CPE Dictionary 2.3 XML schema, 'cpe\\_dict\\_ext:' prefixes indicate types from the CPE Dictionary 2.3 XML schema extension, and 'cpe-name' prefixes indicate types from the CPE Naming 2.3 XML schema. These schemas, which are the authoritative XML binding definitions, can be found at and respectively.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Common Platform Enumeration_ Dictionary Specification Version 2.3."}]}
{"id": "nist_02905", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is BRANSTAD according to Report of the Workshop on Cryptography in Support of Computer Security? BRANSTAD: A public key distribution system would reduce the cost of key distribution. His scheme, however, requires an encryption algorithm with very special properties. Diffie suggested an algorithm similar to the square function having an inverse square-root function. One is easy to compute and the other is relatively difficult. He hasn't developed a usable function yet. The DES algorithm does not satisfy the needed criteria.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Workshop on Cryptography in Support of Computer Security."}]}
{"id": "nist_02906", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Related Controls according to Security and Privacy Controls for Information Systems and Organizations? Related Controls: AC-20, CA-5, CA-6, CA-7, PM-9, RA-5, RA-10, SA-11, SC-38, SI-3, SI-12, SR-2, SR-", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02907", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Digital Identity Guidelines provide? (Section 103) te reference.\u201d 69 NIST SP 800-63-4 July 2025 Digital Identity Guidelines digital authentication The process of establishing confidence in user identities that are digitally presented to a system. In previous editions of SP 800-63, this was referred to as \u201celectronic authentication.\u201d digital identity An attribute or set of attributes that uniquely describes a subject within a given context. Digital Identity Acceptance Statement (DIAS) Documents the results of the digital identity risk management process. This includes the impact assessment, initial assurance level selection, and tailoring process. digital signature An asymmetric key operation in which the private key is used to digitally sign data, and the public key is used to verify the signature. Digital signatures provide authenticity protection, integrity protection, and non-repudiation support but not confidentiality or replay attack protection. digital transaction A discrete digital event between a user and a system that supports a business or programmatic purpose. disassociability Enabling the processing of personal information or events without association to individuals or devices beyond the operational requirements of the system. [NISTIR8062] encryption key The cryptographic key used to encrypt a payload. In asymmetric cryptography, the encryption key refers to the public key of the cryptographic key pair. In symmetric cryptography, the encryption key is the symmetric key. endpoint Any device that is used to access a digital identity on a network, such as laptops, desktops, mobile phones, tablets, servers, Internet of Things devices, and virtual environments. enrollment The process through which a CSP/IdP provides a successfully identity-proofed applicant with a subscriber account and binds authenticators to grant persistent access. 70 NIST SP 800-63-4 July 2025 Digital Identity Guidelines entropy The amount of uncertainty that an attacker faces to determine the value of a secret.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Digital Identity Guidelines."}]}
{"id": "nist_02908", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on PDA Forensics say about 6.3.2 Memory Cards? (Part 1) According to Guidelines on PDA Forensics, 6.3.2 Memory Cards: 6.3.2 Memory Cards A wide array of memory cards exists on the market today, ranging from the size of a stamp to that of a matchbook. Removable media storage capacity ranges from 8MB to beyond 2GB. As technological advances are made, such media becomes smaller and offers larger storage densities. Removable media extends the storage capacity of PDAs, allowing individuals to store additional files beyond the device's built-in capacity. Memory cards provide another avenue for sharing data between multiple users that have compatible hardware. Unlike RAM within a device, removable media is non-volatile storage and requires no battery to retain data. Fortunately, such media can be treated similarly to a removable disk drive, and imaged and analyzed using conventional forensic tools with the use of an external media reader. Memory card adapters exist that support an Integrated Development Environment (IDE) interface. Such adapters allow removable media to be treated as a hard disk and used with write blocker software, which ensures that the removable media remains unaltered [Wie02]. Data contained on the media can be imaged and searched, and deleted files recovered. Below is a brief overview of several common storage media in use today that may contain significant information related to an investigation. - \u0084 Compact Flash Cards (CF) - Compact Flash memory is a solid-state disk card with a 50-pin connector, consisting of two parallel rows of 25 pins on one edge of the card. Compact Flash cards are designed for PCMCIA-ATA functionality and compatibility, have a 16-bit data bus, and are used more as a hard drive than as RAM. They use flash memory technology, a non-volatile storage solution that retains its information once power is removed from the card.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on PDA Forensics."}]}
{"id": "nist_02909", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain REPORTS ON COMPUTER SYSTEMS TECHNOLOGY according to NIST Framework for Emergency Response Officials (ERO)_ Authentication and Authorization Infrastructure According to Framework for Emergency Response Officials (ERO)_ Authentication and Authorization Infrastructure, REPORTS ON COMPUTER SYSTEMS TECHNOLOGY: The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL's responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This 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 7601, 18 pages (August 2010) 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.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Framework for Emergency Response Officials (ERO)_ Authentication and Authorization Infrastructure."}]}
{"id": "nist_02910", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guide to Malware Incident Prevention and Handling for Desktops and Laptops say about 2. Understanding Malware Threats? According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops, 2. Understanding Malware Threats: 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. This section provides basic information on various forms of malware. It defines common terminology that is used throughout the rest of the document, and it presents fundamental concepts of malware. It does not attempt to explain how these different types of malware work in detail, but rather it highlights the basic characteristics of each type of malware. This section first discusses attacker tools, which are often delivered to targeted hosts via malware, and malware toolkits, which are used by attackers to construct malware. The rest of the section examines forms of malware: traditional, phishing, web-based malware, and advanced persistent threats.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Malware Incident Prevention and Handling for Desktops and Laptops."}]}
{"id": "nist_02911", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IR-9 in NIST_SP_800-53r5_Security_Privacy_Controls? (Part 3) Control IR-9: sonnel may not have access to the contaminated systems while corrective actions are being taken, which may potentially affect their ability to conduct organizational business. Related Controls: None. (4) INFORMATION SPILLAGE RESPONSE | EXPOSURE TO UNAUTHORIZED PERSONNEL Employ the following controls for personnel exposed to information not within assigned access authorizations: [Assignment: organization-defined controls]. Discussion: Controls include ensuring that personnel who are exposed to spilled information are made aware of the laws, executive orders, directives, regulations, policies, standards, CHAPTER THREE PAGE 160 NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ and guidelines regarding the information and the restrictions imposed based on exposure to such information. Related Controls: None. References: None.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02912", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Encryption according to NIST 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings According to 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings, Encryption: DKIM, X.509 certificates and XKMS provide all the support necessary to support a comprehensive yet completely user friendly email authentication mechanism. Adding support for encryption completes the requirements for secure email as they are traditionally understood. Instead of proposing yet another email message encryption format however we observe that the existing S/MIME 17 and PGP 18 message formats provide almost everything that is needed. While either message format would meet the technical requirements support for both formats is required to meet the political constraints created by the S/MIME vs. PGP standards war. To date this struggle has reached a stalemate, S/MIME dominates deployment but PGP dominates in mindshare. The quickest way to resolve this stalemate is to declare both formats winners and move on.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki. Contains security framework guidance for authentication systems. Source: 5th Annual PKI R&D Workshop _Making PKI Easy to Use_ Proceedings."}]}
{"id": "nist_02913", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain (AUP) Audit Support &amp; Protection according to NIST IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog According to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog, (AUP) Audit Support &amp; Protection: Description: Ability for the device to support and protect audit activities and associated data. Discussion: Organizations will need to use logged information as part of audits to implement security controls and comply with requirements. IoT devices may have to support through features and functions some aspects of that audit process, such as providing access to or transmitting logs when needed by the organization. Related SP 800-53 Rev. 5 Controls: AU-5(5), AU-6, AU-7, AU-9, SI-4 Requirements that may be necessary: 1. Ability to report on its cybersecurity state. 2. Ability to support a self-audit generation process. 3. Ability to run audit scans (automated or otherwise) to provide specific information (e.g., such as that requested for an external process to audit the device). 4. Ability to send requested audit logs to an external audit process or information system (e.g., where its auditing information can be checked to allow for review, analysis, and reporting). 5. Ability to support an alternate auditing process in the event that the primary auditing process fails. 6. Ability to protect the audit information through the use of: - a. Encryption. - b. Digitally signing audit files. - c. Securely sending audit files to another device. - d. Other protections created by the device manufacturer. 7. Ability to prevent any entities from editing audit logs unless the entity is authorized and is responsible for maintaining the audit logs.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog."}]}
{"id": "nist_02914", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Random Bit Generator (RBG) Constructions say about A.1.4. Entropy and Security Strength in This Recommendation? (Part 2) According to Recommendation for Random Bit Generator (RBG) Constructions, A.1.4. Entropy and Security Strength in This Recommendation: case, the security strength of a bitstring produced by the RBG is the minimum of highest\\_strength and the length of the bitstring - that is, security\\_strength = min ( highest\\_strength , length ) . The DRBG within an RBGC construction is instantiated using a bitstring from a randomness source. The randomness source for an RBGC construction will be either the initial randomness source or another RBGC construction. The tree of RBGC constructions will always originate from 40 However, the entropy-source output may be cryptographically processed by an approved conditioning function before being used. an approved initial randomness source that is either a full-entropy source or an RBG2 or RBG3 construction, each of which includes a validated entropy source. In conclusion, entropy sources and properly functioning RBG3 constructions provide output with entropy. RBG1, RBG2, and RBGC constructions provide output with a security strength that depends on the security strength of the RBG instantiation and the length of the output. Likewise, if the entropy source used by an RBG3 construction fails undetectably, the output is then dependent on the DRBG within the construction (i.e., an RBG2(P) construction) to produce output at the highest security strength for the DRBG design. Because of the difference between the use of 'entropy' to describe the output of an entropy source and the use of 'security strength' to describe the output of a DRBG, the term 'randomness' is used as a general term to mean either 'entropy' or 'security strength,' as appropriate. A 'randomness source' is the general term for an entropy source or RBG that provides the randomness used by an RBG.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Random Bit Generator (RBG) Constructions."}]}
{"id": "nist_02915", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation say about Actual Results? According to Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation, Actual Results: Unable to complete certain steps. See comments below.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Protecting the Integrity of Internet Routing_ Border Gateway Protocol (BGP) Route Origin Validation."}]}
{"id": "nist_02916", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Glossary of Computer Security Terminology say about 2) See COMPUTER SECURITY.? (Part 12) According to Glossary of Computer Security Terminology, 2) See COMPUTER SECURITY.: essing systems, other electronic information handling systems, and associated equipment. (NSDD-145; NTISSP 200) - 3) An information system (as defined in Section 6d of the Circular) that is automated. (A-130) automated information systems security automated security monitoring automatic data processing (ADP) system - 1) Measures and controls that protect an AIS against denial ofservice and unauthorized, (accidental or intentional) disclosure, modification or destruction ofAISs and data. AIS security includes consideration of all hardware andlor software functions, characteristics andlor features: operational procedures, accountability procedures, and access controls at the central computer facility, remote computer, and terminal facilities; management constraints; physical structures and devices; and personnel and communications controls needed to provide an acceptable level of risk for the AIS and for the data and information contained in the AIS. It includes the totality ofsecurity safeguards needed to provide an acceptable protection level for an AIS and for data handled by an AIS. (NCSC-TG-004-88) - 2) See COMPUTER SECURITY. - 1) The use of automated procedures to ensure that automation security controls are not circumvented. (AR 380-380) - 2) The use of automated procedures to ensure that the security controls implemented within an ADP system are not circumvented. (FIPS PUB 39) An assembly of computer hardware, firmware, and software, configured for the purpose of calculating, computing, sorting, transmitting, receiving, storing and retrieving data with a minimum of human intervention. (CSC-STD-005-85; DOD 5200.28-STD; DOE 5635.1A) automation security availability - 1) The measures employed to protect automation and the information handled from both hostile and benign threats and to safeguard against unauthorized exploitation through espionage, sabotage, theft, fraud, misappropriation, or misuse.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Glossary of Computer Security Terminology."}]}
{"id": "nist_02917", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case provide? (Section 122) Parr) | Work | 1-800-555-7643 | | Insurance Provider Account # 8858444 | Agent (R. Parr) | Mobile | 240-555-5698 | | Insurance Provider Account # 8858444 | Agent (R. Parr) | Alternate | 240-555-5433 | | Insurance Provider Account # 8858444 | Agent (R. Parr) | Email | r.parr@insuricare.com | The System Recovery Plan must be reviewed and updated after: - the plan executed in response to a cybersecurity incident, - the plan is executed during an incident response or recovery exercise, - any organizational changes, or - any modifications or maintenance to the manufacturing system or its components that may impact this plan. The supervisor is responsible for updating the document in consultation with other personnel, IT and OT contractors and vendors, as required. The System Recovery Plan will be tested each calendar year. System Recovery team members will perform exercises to: - review documented procedures, - validate the effectiveness of the plan, - identify any gaps or weaknesses in its execution, and - update the plan with any outdated or missing information. The following tables document important information to support the recovery of manufacturing system devices. Each device is listed in its own table with relevant information (e.g., hostname, file systems, physical location, backup strategies). The restoration process for each device below is described in Section 3.6.12. For more detailed system information regarding each host, reference the Hardware Inventory.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 \u2013 Discrete-based Manufacturing System Use Case."}]}
{"id": "nist_02918", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Government Smart Card Interoperability Specification, Version 2.1 say about Command Message? According to Government Smart Card Interoperability Specification, Version 2.1, Command Message: | CLA | 0x00 | |------------|-------------------------------------| | INS | 0xC0 | | P1 | 0x00 | | P2 | 0x00 | | L c | Empty | | Data Field | Empty | | L e | Number of bytes to read in response |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Government Smart Card Interoperability Specification, Version 2.1."}]}
{"id": "nist_02919", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Abstract syntax according to A Study of OSI Key Management? Abstract syntax: A description of a data structure that is independent of machine oriented structures and restrictions.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Study of OSI Key Management."}]}
{"id": "nist_02920", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain &lt;check-content-ref&gt; according to NIST Specification for the Extensible Configuration Checklist Description Format (XCCDF) According to Specification for the Extensible Configuration Checklist Description Format (XCCDF), &lt;check-content-ref&gt;: This element points to a benchmark compliance check, in the language or system specified by the check element's system attribute. Exactly one of check-content or check-content-ref must appear in each check element. The href attribute identifies the document, and the optional name attribute may be used to refer to a particular part, element, or component of the document. Content: none Cardinality: 0-1 Parent Elements: check Attributes: href, name Child Elements: none", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Specification for the Extensible Configuration Checklist Description Format (XCCDF)."}]}
{"id": "nist_02921", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI) say about Task 6: Authorization Decision? According to Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI), Task 6: Authorization Decision: The authorization decision task determines if the assessment phase has been satisfactorily completed so that a recommendation concerning the operation of the issuer can be made with assurance. The DAO, working with the Assessor, reviews the contents of the assessment submission package, the identified and uncorrected or un-correctable deficiencies, the potential impacts on each organization using the issuer's services, and the CAP in determining the final risk to the organization(s) and the acceptability of that risk in light of the organization's mission. Subtask 6.1: Review the authorization decision package to see if it is complete and that all applicable issuer controls have been fully assessed using the designated assessment procedures. Responsibility: DAO Guidance: Coverage for all issuer controls and proper adherence to assessment procedures and appropriate assessment methods helps to create confidence in assessment findings and is the main objective of the assessment review. Part of the assessment review also includes understanding the impact of the identified deficiencies on the organization's operations, assets, and individuals. Subtask 6.2: Determine if the risk to the organization's operations, assets, or potentially affected individuals is acceptable.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, sso. Contains security framework guidance for authentication systems. Source: Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)."}]}
{"id": "nist_02922", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 8.1 The difference between CIPSO and RIPSO according to NIST Standard Security Label for GOSIP_ an Invitational Workshop According to Standard Security Label for GOSIP_ an Invitational Workshop, 8.1 The difference between CIPSO and RIPSO: RIPSO, as defined by RFC 1038, consists of two options: the Basic Security Option (BSO) and the Extended Security Option (ESO). The BSO contains the security level and some protection authority flags. The ESO provides a mechanism to include other security related information in the IP packet. Like CIPSO, it provides authorities that interpret the values for each field. Unlike CIPSO, there is no common format for the security label. The format is up to the associated authority. This will require a software change each time a new authority is added. The primary difference between CIPSO and RIPSO is that the 8 possible authority codes in RIPSO are tightly controlled by DCA and the over 4 billion CIPSO authority (DOIs) codes are open to all commercial as well as Federal organizations. Other differences include the fact that RIPSO supports 8 security levels and CIPSO supports 256. In addition, RIPSO requires two options to send a security label and CIPSO requires only 1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Standard Security Label for GOSIP_ an Invitational Workshop."}]}
{"id": "nist_02923", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Assessing Security Requirements for Controlled Unclassified Information say about Interview? According to Assessing Security Requirements for Controlled Unclassified Information, Interview: [SELECT FROM: personnel with responsibilities for defining terms, conditions, and security requirements for the use of external systems; personnel with information security responsibilities; system administrators]", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02924", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2010 Annual Report say about NIST Personal Identity Verification Program (NPIVP)? (Part 1) According to Computer Security Division 2010 Annual Report, NIST Personal Identity Verification Program (NPIVP): NIST Personal Identity Verification Program (NPIVP) The objective of the NIST Personal Identity Verification Program (NPIVP) is to validate Personal Identity Verification (PIV) components for conformance to specifications in FIPS 201 and its companion documents. The two PIV components that come under the scope of NPIVP are PIV Smart Card Application and PIV Middleware. All of the tests under NPVIP are handled by third-party laboratories that are accredited as Cryptographic and Security and Testing (CST) Labora\u00ad tories by the National Voluntary Laboratory Accreditation Program (NVLAP) and are called accredited NPIVP test facilities. As of Septem\u00ad ber 2010, there are nine such facilities. In prior years, CSD published SP 800-85A, PIV Card Application and Middleware Interface Test Guidelines , to facilitate development of PIV Smart Card Application and PIV Middleware that conform to inter\u00ad face specifications in SP 800-73, Interfaces for Personal Identity Verification . We also developed an integrated toolkit called 'PIV Interface Test Runner' for conducting tests on both PIV Card Application and PIV Middleware products, and provided the toolkit to accredited NPIVP test facilities. In FY2010, the third edition of SP 800-73 (numbered as SP 800-73-3), was published. After SP 800-73-3 was finalized, we updated SP 800\u00ad 85A-1, PIV Card Application and Middleware Interface Test Guidelines , to provide test guidelines that align with SP 800-73-3. After a pub\u00ad lic comment period and resolution of received comments, the final publication of SP 800-85A-2 was released in July 2010. With the release of SP 800-73-3, NPIVP identified the necessary up\u00ad dates for the PIV Interface Test Runner to align with SP 800-73-3 and the revised PIV card interface test guidelines in SP 800-85A-2.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2010 Annual Report."}]}
{"id": "nist_02925", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Annual Report 2018_ NIST_ITL Cybersecurity Program say about Enhancing Risk Management? (Part 6) According to Annual Report 2018_ NIST_ITL Cybersecurity Program, Enhancing Risk Management: security accomplishments in FY18 included an update of NIST's recommendations for protecting the confidentiality of controlled, unclassified information (CUI) in non-federal systems and organizations. Safeguarding that CUI is of paramount importance and can directly affect the ability of federal agencies to successfully conduct their assigned missions and business operations. NIST SP 800-171 Revision 1 10 recommends security requirements to those agencies. The FY18 update included editorial changes to select CUI security requirements, additional references and definitions, and an expanded discussion about each CUI requirement. 10/emspace SP 800-171, Rev. 1, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, https:/ /csrc.nist.gov/publications/detail/sp/800-171/rev-1/final", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Annual Report 2018_ NIST_ITL Cybersecurity Program."}]}
{"id": "nist_02926", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 248) authorization process for the system that includes multiple authorizing officials with at least one authorizing official from an organization external to the organization conducting the authorization. Discussion: Assigning multiple authorizing officials, at least one of whom comes from an external organization, to serve as co-authorizing officials for the system increases the level of independence in the risk-based decision-making process. It implements the concepts of separation of duties and dual authorization as applied to the system authorization process. Employing authorizing officials from external organizations to supplement the authorizing official from the organization that owns or hosts the system may be necessary when the external organizations have a vested interest or equities in the outcome of the authorization decision. The inter-organization joint authorization process is relevant and appropriate for connected systems, shared systems or services, and systems with multiple information owners. The authorizing officials from the external organizations are key stakeholders of the system undergoing authorization. Related Controls: AC-6. References: [OMB A-130], [SP 800-37], [SP 800-137]. CA-7 CONTINUOUS MONITORING Control: Develop a system-level continuous monitoring strategy and implement continuous monitoring in accordance with the organization-level continuous monitoring strategy that includes: a. Establishing the following system-level metrics to be monitored: [Assignment: organization- defined system-level metrics]; b. Establishing [Assignment: organization-defined frequencies] for monitoring and [Assignment: organization-defined frequencies] for assessment of control effectiveness; c. Ongoing control assessments in accordance with the continuous monitoring strategy; d. Ongoing monitoring of system and organization-defined metrics in accordance with the continuous monitoring strategy; e.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02927", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information say about B.4.2.2. CAD/RMS Thick Client at the County with IdP at the State Agency -WS-Trust? (Part 1) According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information, B.4.2.2. CAD/RMS Thick Client at the County with IdP at the State Agency -WS-Trust: B.4.2.2. CAD/RMS Thick Client at the County with IdP at the State Agency -WS-Trust In this scenario, we assume that the CAD/RMS client/server system does not support SAML. We also assume that the user authenticates to the CAD/RMS system through some other means (e.g., Kerberos). To authenticate the user to the message switch, the CAD/RMS thick client redirects the user to a URL at the state IdP that triggers an IdP-initiated SAML authentication flow. The IdP responds with a SAML assertion, which the CAD/RMS thick client sends to the CAD/RMS server, which in turn makes a WS-Trust request to the state IdP to obtain a SAML assertion that it can present to the message switch. The CAD/RMS server is not required to create a SAML authentication request or to parse or validate the SAML responses from the IdP. To the CAD/RMS server, the SAML messages themselves are opaque XML documents, and it simply passes them along. This integration requires configuring the state IdP with parameters for the CAD/RMS system as if it were an RP. Further, we assume that the state IdP supports IdP-initiated SSO and has a URL configured to trigger an IdP-initiated login to the CAD/RMS thick client. Both the IdP and the CAD/RMS system must also support WS-Trust for this integration. This architecture is shown in Fig. 21. Fig. 21. Thick client CAD/RMS at county, state IdP (WS-Trust). <!-- image --> The sequence of interactions is as follows: 1. The officer opens the CAD/RMS thick client application, which connects to the CAD/RMS server. The officer authenticates using a non-SAML method, such as Kerberos. The details of this interaction are proprietary and depend on the CAD/RMS application's design. 2. The officer submits a query that must be submitted to the state message switch. To authenticate the officer, the CAD/RMS thick client opens the IdP-initiated SSO URL of the state IdP in the builtin browser on the officer's MDC. 3.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, multi-factor, sso. Contains security framework guidance for authentication systems. Source: Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information."}]}
{"id": "nist_02928", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines say about 5.1.1. Secure Build? (Part 1) According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines, 5.1.1. Secure Build: 5.1.1. Secure Build The following tasks are required to obtain SSC security assurance in the build process: - Specify policies regarding the build, including (a) the use of a secure isolated platform for performing the build and hardening the build servers, (b) the tools that will be used to perform the build, and (c) the authentication/authorization required for the developers performing the build process. - Enforce those build policies using techniques such as an agent and policy enforcement engine. - Ensure the concurrent generation of evidence for build attestation to demonstrate compliance with secure build processes during the time of software delivery. A common technique for facilitating the second task is to wrap commands from a CI tool with capabilities to gather evidence and ultimately create an evidence trail of the entire SDLC [8]. The first type of evidence is from the build system itself, which should be able to confirm that the tools or processes used are in an isolated environment. This provides internal operational assurance. The second type of evidence that should be gathered consists of the hash of the final build artifact, files, libraries, and other materials used in the artifacts and all events. This is then signed by a trusted component of the build framework that is not under the control of the developers using a digital certificate to create the attestation, which provides verifiable proof of the quality of the software to consumers and enables them to verify the quality of that artifact independently from the producer of the software, thus providing consumer assurance. In this context, the artifact is the build generated by a series of CI process steps. In the context of 'concurrent generation of evidence,' the evidence generated should be enabled by a process with a higher level of trust or isolation than the build itself to protect against tampering. The generation of such evidence requires verification within the build as it occurs.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization. Contains security framework guidance for authentication systems. Source: Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines."}]}
{"id": "nist_02929", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Notional Supply Chain Risk Management Practices for Federal Information Systems provide? (Section 57) subject to access by a variety of actors. It is critical to limit such access to only as much as necessary for those actors to perform their role(s) and to monitor that access for supply chain impact. Access control techniques exist that may be useful in providing needed granularity to ensure that only appropriate actors can monitor or change supply chain elements, element processes, organizations, organizational processes, information, communications, and systems covering the comprehensive supply chain. - a) Establish an internal policy for the broad responsibilities of assigning access control to information, systems, supply chain elements, element processes, as well as key personnel and organizational activities as deemed necessary to protect the confidentiality, integrity, and availability of supply chain elements and processes throughout the system/element life cycle. - b) Instantiate general criteria by which access controls are to be applied, the objects of such controls, the initiating and terminating events or conditions under which such controls are applied, and specific access control mechanisms (e.g., automated, manual, or hybrid). - c) Identify the individuals (roles) and organizations with responsibility for the design, development, and implementation of access controls, to include use of information security, operations security, physical security, industrial security, and IA tactics, techniques, procedures, and tools. - d) Define requirements to include access control (both physical and logical) requirements in all written agreements with integrators including: - Responsibilities for assigning access control among all parties; - Mandatory, recommended, and prohibited access control methods; and - Audit plans for access control review. - e) Define, design, specify, and require assigned roles throughout the supply chain and system or element life cycle so that no single role can, intentionally or unintentionally, create adverse consequences.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Notional Supply Chain Risk Management Practices for Federal Information Systems."}]}
{"id": "nist_02930", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Criticality Analysis Process Model_ Prioritizing Systems and Components provide? (Section 142) cially in the ERP system. Their review questions may include: - Where do inputs to a critical process come from? - Where do the outputs of a critical process go? - What information/data is processed? Is that information/data sensitive or categorized? Are there special handling requirements associated with the information/data? - What is required for providing the output in a timely, accurate, and complete manner? - Which subsystem processes must be completed before the next process takes over? - What subsystems/functions/processes are used to ensure that the subsystems perform their roles as required? - What subsystems/functions/processes interact with or connect to a critical subsystem? Using this information, they identify those subsystems and functions which directly perform or support a highly critical process, those which indirectly support a highly critical process, and those which are immaterial to the critical process. The Lead Systems Architect uses this information to modify the draft system diagram developed in C.2 slightly and to highlight key areas of importance. C.4 The Lead Systems Architect works with her team of engineers to document generally the characteristics of each subsystem and how the subsystems should function when operating normally. They then analyze how each subsystem will behave under the following conditions: - A subsystem is given an incomplete input; - A subsystem is given an incorrect input; - A subsystem is given an input at the wrong time or slowly; - An IT/OT subsystem is not given enough power or too much power; - An IT/OT subsystem is given a software/firmware update. They validate their analysis by brainstorming certain scenarios and how the system will be impacted.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Criticality Analysis Process Model_ Prioritizing Systems and Components."}]}
{"id": "nist_02931", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Related Controls according to Security and Privacy Controls for Information Systems and Organizations? Related Controls: AT-2, AT-3, IR-4, IR-6, IR-8, PM-22, PM-26, SA-9, SI-18.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Security and Privacy Controls for Information Systems and Organizations."}]}
{"id": "nist_02932", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SA-1 in NIST_SP_800-53r5_Security_Privacy_Controls? (Part 1) Control SA-1: POLICY AND PROCEDURES Control: a. Develop, document, and disseminate to [Assignment: organization-defined personnel or roles]: 1. [Selection (one or more): Organization-level; Mission/business process-level; System- level] system and services acquisition policy that: (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and 2. Procedures to facilitate the implementation of the system and services acquisition policy and the associated system and services acquisition controls; b. Designate an [Assignment: organization-defined official] to manage the development, documentation, and dissemination of the system and services acquisition policy and procedures; and c. Review and update the current system and services acquisition: 1. Policy [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]; and 2. Procedures [Assignment: organization-defined frequency] and following [Assignment: organization-defined events]. Discussion: System and services acquisition policy and procedures address the controls in the SA family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of system and services acquisition policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02933", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control EP-67 in Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)? (Part 180) Control EP-67: ocol for use with constrained nodes and constrained networks in the Internet of Things. The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation. Parsing the Protocol and Processing URIs: CoAP attempts to narrow the opportunities for introducing network-facing application vulnerabilities by: reducing parser complexity, giving the entire range of encodable values a meaning where possible, and by aggressively reducing | Approved Standard Guidance Available Commercial Availability | | Network Security: Standards that provide security requirements and guidelines on processes and methods for the secure management, operation and use of information, information networks, and their inter-connections. | Network Security: Standards that provide security requirements and guidelines on processes and methods for the secure management, operation and use of information, information networks, and their inter-connections. | Network Security: Standards that provide security requirements and guidelines on processes and methods for the secure management, operation and use of information, information networks, and their inter-connections. | Network Security: Standards that provide security requirements and guidelines on processes and methods for the secure management, operation and use of information, information networks, and their inter-connections.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)."}]}
{"id": "nist_02934", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations say about 1.4.3. Acquisition and Procurement Owners and Operators? According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, 1.4.3. Acquisition and Procurement Owners and Operators: These readers are those with C-SCRM responsibilities as part of their role in the procurement or acquisition function of an enterprise. Acquisition personnel may execute C-SCRM activities as a part of their general responsibilities in the acquisition and procurement life cycle. These personnel will collaborate closely with the enterprise's C-SCRM personnel to execute C-SCRM activities with acquisition and procurement. Recommended reading includes: - Section 1: Introduction - Section 2.1: The Business Case for C-SCRM - Section 2.2: Cybersecurity Risks Throughout the Supply Chain - Section 3.1: C-SCRM in Acquisition - Section 3.3: C-SCRM Awareness and Training - Appendix A: C-SCRM Security Controls - o These readers should pay special attention to requisite controls for supplier contracts and include them in agreements with both primary and sub-tier contractor parties. - Appendix F: Software Supply Chain Security Guidelines", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations."}]}
{"id": "nist_02935", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does NIST_SP_800-53r5_Security_Privacy_Controls provide? (Section 892) e set of points on the boundary of a system, a system component, or an environment where an attacker can try to enter, cause an effect on, or extract data from, that system, component, or environment. Independent review and examination of records and activities to assess the adequacy of system controls, to ensure compliance with established policies and operational procedures. A chronological record of system activities, including records of system accesses and operations performed in a given period. An individual entry in an audit log related to an audited event. A process that manipulates collected audit information and organizes it into a summary format that is more meaningful to analysts. A chronological record that reconstructs and examines the sequence of activities surrounding or leading to a specific operation, procedure, or event in a security-relevant transaction from inception to result. authentication [FIPS 200] Verifying the identity of a user, process, or device, often as a prerequisite to allowing access to resources in a system. APPENDIX A PAGE 395 NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS _________________________________________________________________________________________________ authenticator authenticity Something that the claimant possesses and controls (typically a cryptographic module or password) that is used to authenticate the claimant\u2019s identity. This was previously referred to as a token. The property of being genuine and being able to be verified and trusted; confidence in the validity of a transmission, message, or message originator. See authentication. authorization [CNSSI 4009] Access privileges granted to a user, program, or process or the act of granting those privileges.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, authorization, token. Contains security framework guidance for authentication systems. Source: NIST_SP_800-53r5_Security_Privacy_Controls."}]}
{"id": "nist_02936", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Cryptographic Key Generation say about Recommendation for Cryptographic Key Generation? According to Recommendation for Cryptographic Key Generation, Recommendation for Cryptographic Key Generation: Elaine Barker Allen Roginsky Computer Security Division Information Technology Laboratory Richard Davis National Security Agency This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-133r2 June 2020 <!-- image --> U.S. Department of Commerce Wilbur L. Ross, Jr., Secretary National Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: secret, national security. Contains guidance on protecting sensitive government information. Source: Recommendation for Cryptographic Key Generation."}]}
{"id": "nist_02937", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is FR according to A Framework for Designing Cryptographic Key Management Systems? FR: 8.2 The CKMS design shall specify the physical security controls for protecting each device containing CKMS components.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: A Framework for Designing Cryptographic Key Management Systems."}]}
{"id": "nist_02938", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.2 provide? (Section 40) escribed in [DCXML]. It MAY also have an @href attribute that gives a URL for the referenced resource. References SHOULD be given as Dublin Core descriptions; a bare string MAY be used for simplicity. If a bare string appears, then it is taken to be the string content for a &lt;dc:title&gt; element. For more information, consult [DCES]. Multiple &lt;xccdf:reference&gt; elements MAY appear; a benchmark consumer product MAY concatenate them or put them into a reference list, and MAY choose to number them. XCCDF supports a digital signature mechanism whereby XCCDF document users can validate the integrity, origin, and authenticity of documents. XCCDF provides a means to hold such signatures and a uniform method for applying and validating them [XMLDSIG]. The &lt;xccdf:signature&gt; element MAY hold an enveloped digital signature asserting authorship and allowing verification of the integrity of associated data (e.g., its parent element, other documents, portions of other documents). The signature SHALL apply only after inclusion (i.e., XInclude) processing. The &lt;xccdf:signature&gt; element is OPTIONAL, and it MAY appear as a child of the &lt;xccdf:Benchmark&gt; , &lt;xccdf:Rule&gt; , &lt;xccdf:Group&gt; , &lt;xccdf:Value&gt; , &lt;xccdf:Profile&gt; , &lt;xccdf:TestResult&gt; , or &lt;xccdf:Tailoring&gt; elements. Any digital signature format employed for XCCDF MUST be capable of identifying the signer, storing all information needed to verify the signature (usually a certificate or certificate chain), and detecting any change to the signed content. XCCDF products that support signatures MUST support the W3C XMLSignature standard enveloped signatures, as defined in [XMLDSIG]. If multiple signatures are needed in an XCCDF document, at most one of them MAY be enveloped; all others MUST be detached [XMLDSIG Section 2].", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.2."}]}
{"id": "nist_02939", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2011 Annual Report say about Cryptography for Emerging Technologies and Applications (CETA) Workshop? (Part 1) According to Computer Security Division 2011 Annual Report, Cryptography for Emerging Technologies and Applications (CETA) Workshop: Cryptography for Emerging Technologies and Applications (CETA) Workshop The CETA Workshop will provide an opportunity for industry, research and academia communities, and government sectors to identify cryptographic challenges encountered in their development of emerging technologies and applications, and to learn about NIST's current cryptographic research, activities, programs, and standards development. Technology areas to be addressed include sensor and building networks, mobile devices, smart objects/Internet of things, and cyber physical systems. NIST considered the following trends when organizing the CETA Workshop: the increasing demand for small footprint cryptography for power-constrained devices; the emerging desire, from both providers and consumers, for trustworthy processes supporting secure communications and transactions that maximize integrity and nonrepudiation properties on single end-user devices that access many kinds of services and applications, and the need for individual users that access the same services and applications from multiple platforms; the need for much more agile key management on cyberspace; and the need for usable and reliable public, enterprise-specific, pseudonymous, and anonymous modes of operation from the same end-user device. In preparation for the workshop, NIST called for the submission of abstracts. The abstracts must highlight cryptographic challenges identified during the research and development of emerging technologies and applications. Examples of emerging or evolving technology areas include: - Sensor and building networks; - Mobile devices; - Smart Objects/Internet of Things; and - Cyber physical systems. Examples of cryptographic requirements for emerging sectors might include: performance or resource issues; cryptographic services (such as anonymous or group signatures); or key management challenges.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2011 Annual Report."}]}
{"id": "nist_02940", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Derived Personal Identity Verification (PIV) Credentials provide? (Section 66) explanation of the NIST Cybersecurity Framework Subcategory codes. Note: Some of our components are marked in the version column as not applicable. This is due to the use of SaaS [24] cloud services. Table 3-6 Products and Technologies | Component | Product | Version | Function | Cybersecurity Framework Subcategories | |---------------------------|--------------------------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------| | PKI Certificate Authority | Entrust Data- card Managed PKI | Not appli- cable | Entity that issues an authentica- tion certificate, which is an X.509 public key certificate that has been issued in accordance with the re- quirements of NIST SP 800-157 and the X.509 Certificate Policy for the U.S.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, certificate authority. Contains security framework guidance for authentication systems. Source: Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_02941", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AC-06(05) in Assessing Security Requirements for Controlled Unclassified Information? (Part 76) Control AC-06(05): ents for A.03.12.01: the security requirements for the system and its environment of operation are assessed &lt;A.03.12.01.ODP[01]: frequency&gt; to determine if the requirements have been satisfied. ## ASSESSMENT METHODS AND OBJECTS ## Examine [SELECT FROM: security assessment and monitoring policy and procedures; procedures for security assessment planning; security assessment plan; security assessment report; system security plan; other relevant documents or records] ## Interview [SELECT FROM: personnel with security assessment responsibilities; personnel with information security responsibilities] ## Test [SELECT FROM: mechanisms for supporting security assessments, processes for security assessment plan development, or security assessment reporting] ## REFERENCES Source Assessment Procedure: CA-02 ## 03.12.02 Plan of Action and Milestones ## ASSESSMENT OBJECTIVE ## Determine if: A.03.12.02.a.01: a plan of action and milestones for the system is developed to document the planned remediation actions for correcting weaknesses or deficiencies noted during security assessments. A.03.12.02.a.02: a plan of action and milestones for the system is developed to reduce or eliminate known system vulnerabilities. A.03.12.02.b.01: the existing plan of action and milestones is updated based on the findings from security assessments. A.03.12.02.b.02: the existing plan of action and milestones is updated based on the findings from audits or reviews. A.03.12.02.b.03: the existing plan of action and milestones is updated based on the findings from continuous monitoring activities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Assessing Security Requirements for Controlled Unclassified Information."}]}
{"id": "nist_02942", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-1 in Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters? (Part 22) Control HA-1: lliptic curve K-283 is a Weierstrass curve Ba , b defined over the binary field GF(2 m ) with m = 283 and parameters a = 0 and b = 1. This curve has order h \u22c5 n , where h = 4, and n is a prime number. This curve has domain parameters D = ( m , f ( z ), T , h , n , Type , a , b , G , { Seed , c }), where the Type is 'Koblitz curve,' and the other parameters are defined as follows: ``` T: 6 f ( z ): z 283 + z 12 + z 7 + z 5 + 1 h : 4 n : 388533778445145814183892381364703781328481\\ 1733793061324295874997529815829704422603873 ``` ``` (= 0x1ffffff ffffffff ffffffff ffffffff ffffe9ae 2ed07577 265dff7f 94451e06 1e163c61 ) tr : 7777244870872830999287791970962823977569917 (=(2 m + 1) h \u22c5 n = 0x5947 44be2a23 66880201 aeeb87e7 87a70e7d ) a : 0 (= 0x0000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ) b : 1 (= 0x0000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000001 ) ``` ## Polynomial basis: ``` Gx : 0x503213f 78ca4488 3f1a3b81 62f188e5 53cd265f 23c1567a 16876913 b0c2ac24 58492836 Gy : 0x1ccda38 0f1c9e31 8d90f95d 07e5426f e87e45c0 e8184698 e4596236 4e341161 77dd2259 ``` ## Normal basis: ``` Gx : 0x3ab9593 f8db09fc 188f1d7c 4ac9fcc3 e57fcd3b db15024b 212c7022 9de5fcd9 2eb0ea60 Gy : 0x2118c47 55e7345c d8f603ef 93b98b10 6fe8854f feb9a3b3 04634cc8 3a0e759f 0c2686b1 ``` Seed : n/a (binary Koblitz curve) ## 3.3.1.4. Curve K-409 The elliptic curve K-409 is a Weierstrass curve Ba , b defined over the binary field GF(2 m ) with m = 409 and parameters a = 0 and b = 1. This curve has order h \u22c5 n , where h = 4, and n is a prime number.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters."}]}
{"id": "nist_02943", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Cybersecurity Framework Version 1.1 Manufacturing Profile? (Part 50) Control AM-1: nd Access Control (PR.AC) | PR.AC-3 | Low Impact Establish usage restrictions, connection requirements, implementation guidance, and authorizations for remote access to the manufacturing system. Provide an explicit indication of active remote access connections to users physically present at the devices. Remote access methods include, for example, wireless, dial-up, broadband, Virtual Private Network (VPN) connections, mobile device connections, and communications through external networks. | Reference ISA/IEC 62443-2- 1:2009 4.3.3.6.6 ISA/IEC 62443-3- 3:2013 SR 1.13,2.6 AC-17, AC-19, AC-20 SC-15 AC-17(1)(2)(3)(4) AC-20(1)(2) | | PROTECT | Identity Management, Authentication and Access Control (PR.AC) | PR.AC-3 | Moderate and High Impact remote access only through approved and managed access points. remote access to the manufacturing system and implement cryptographic mechanisms | Reference ISA/IEC 62443-2- 1:2009 4.3.3.6.6 ISA/IEC 62443-3- 3:2013 SR 1.13,2.6 AC-17, AC-19, AC-20 SC-15 AC-17(1)(2)(3)(4) AC-20(1)(2) | | PROTECT | Identity Management, Authentication and Access Control (PR.AC) | PR.AC-3 | Allow Monitor where determined necessary. Allow only authorized use of privileged functions from remote access. Establish agreements and verify security for connections with external systems.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, authorization. Contains security framework guidance for authentication systems. Source: Cybersecurity Framework Version 1.1 Manufacturing Profile."}]}
{"id": "nist_02944", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Specification for the Extensible Configuration Checklist Description Format (XCCDF) say about XCCDF Schema 1.0? (Part 8) According to Specification for the Extensible Configuration Checklist Description Format (XCCDF), XCCDF Schema 1.0: n xml:lang=\"en\"> Metadata for the Benchmark, should be Dublin Core or some other well-specified and accepted metadata format. If Dublin Core, then it will be a sequence of simple Dublin Core elements. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:choice minOccurs=\"1\" maxOccurs=\"1\"> <xsd:any namespace=\"http://purl.org/dc/elements/1.1/\" minOccurs=\"1\" maxOccurs=\"unbounded\"/> <!-- the namespace URI below is from a draft version of the schema designed to support the checklist metadata requirements from NIST special pub 800-70. --> <xsd:any namespace=\"\" processContents=\"skip\" minOccurs=\"1\" maxOccurs=\"unbounded\"/> </xsd:choice> ``` ``` </xsd:sequence> </xsd:complexType> <!-- ************************************************************** --> <!-- ****************** global elements ************************* --> <!-- ************************************************************** --> <xsd:element name=\"status\"> <xsd:annotation> <xsd:documentation xml:lang=\"en\"> The acceptance status of an Item with an optional date attribute that signifies the date of the status change. </xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:extension base=\"cdf:statusType\"> <xsd:attribute name=\"date\" type=\"xsd:date\" use=\"optional\"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> </xsd:element> <xsd:simpleType name=\"statusType\"> <xsd:annotation> <xsd:documentation xml:lang=\"en\"> The possible status codes for an Benchmark or Item to be inherited from the parent element if it is not defined.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Specification for the Extensible Configuration Checklist Description Format (XCCDF)."}]}
{"id": "nist_02945", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control HA-256 in Derived PIV Application and Data Model Test Guidelines? (Part 156) Control HA-256: mandatory tags for the Key History Object are present in the order indicated in Table 19 of [SP800-73], Part 1. 4. From Step 4, the command returns status word '90 00' along with the Security Object. | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| ## 9.1.6 Retired X.509 Certificates for Key Management ## 9.1.6.1 BER-TLV of Retired X.509 Certificates for Key Management | Test Assertion | TA-09.01.06.01 | |----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Purpose | Verifies that the Retired X.509 Certificates for Key Management (if present) conform to the Derived PIV data model requirements.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_02946", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i say about 10.3 Wi-Fi Alliance Product Certification Programs? According to Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i, 10.3 Wi-Fi Alliance Product Certification Programs: The Wi-Fi Alliance has established several certification programs to give consumers of WLAN products assurance that their systems comply with IEEE 802.11 specifications and can interoperate with similar equipment from other vendors. The following certifications are available that indicate product compliance with IEEE 802.11i: - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; Wi-Fi Protected Access (WPA), which includes a subset of the IEEE 802.11i specification that addresses the weaknesses of WEP - GLYPH&lt;c=31,font=/HACNND+Webdings&gt; WPA2, which extends WPA to include the full set of IEEE 802.11i requirements. Federal agencies should procure WPA2 products that have been FIPS-validated; WPA products cannot be FIPS-validated because they do not support FIPS-approved encryption algorithms. WPA and WPA2 have both Personal and Enterprise modes of operation. Organizations that plan to deploy authentication servers as part of an IEEE 802.1X and EAP implementation should procure products with the Enterprise level certification.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i."}]}
{"id": "nist_02947", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.1.1 Network Boot Services according to NIST Validating the Integrity of Computing Devices According to Validating the Integrity of Computing Devices, 2.1.1 Network Boot Services: The following procedures will create an environment that will enable the acceptance testing of computing devices into an enterprise. First, we create CentOS 7, CentOS 8, and WinPE images that will be booted on computing devices via a Preboot Execution Environment (PXE). We then configure the PXE environment to boot the images.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Validating the Integrity of Computing Devices."}]}
{"id": "nist_02948", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for the Secure Deployment of IPv6 provide? (Section 47) Summary..............................................................................................................6-47 | 6-46 | | List of Appendices | List of Appendices | List of Appendices | List of Appendices | | Appendix A- Acronyms and Abbreviations ......................................................................A-1 | Appendix A- Acronyms and Abbreviations ......................................................................A-1 | Appendix A- Acronyms and Abbreviations ......................................................................A-1 | | | Appendix B-References and Other IPv6 Resources .......................................................B-1 | Appendix B-References and Other IPv6 Resources .......................................................B-1 | Appendix B-References and Other IPv6 Resources .......................................................B-1 | | | List of Figures | List of Figures | List of Figures | List of Figures | | Figure 2-1.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for the Secure Deployment of IPv6."}]}
{"id": "nist_02949", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Computer Security Division 2014 Annual Report provide? (Section 217) her with associated virtual network and hardware/software for data storage An IaaS's consumer's total set of interactions with these resources constitute the set of use cases for IaaS cloud service. These use cases have associated security requirements and these requirements are met by protection options enabled by available security solutions/technologies. The purpose of this paper is to analyze these protection options from the viewpoint of: (a) Security functionality they can provide and (b) the architecture that governs their deployment, so that IaaS consumers can decide on the most appropriate security configuration for their VM instances depending upon the profile of the applications running in them. I. Dominguez, D.R. Kuhn, R.N. Kacker, and Y. Lei, 'CCM: A Tool for Measuring Combinatorial Coverage of System State Space' [poster], 2013 ACM / IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM 2013), Baltimore, Maryland, October 10-11, 2013, p. 291. doi: 10.1109/ESEM.2013.44. This poster presents some measures of combinatorial coverage that can be helpful in estimating residual risk related to insufficient testing of rare interactions, and a tool for computing these measures. D. Ferraiolo, S. Gavrila and W. Jansen, 'On the Unification of Access Control and Data Services,' 15th IEEE Conference on Information Reuse and Integration (IRI 2014), San Francisco, California, August 13-15, 2014, pp. 450-457. doi: 10.1109/ IRI.2014.7051924. A primary objective of enterprise computing (via a data center, cloud, etc.) is the controlled delivery of data services (DS). Typical DSs include applications such as email, workflow, and records management, as well as system level features, such as file and access control management.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, sso. Contains security framework guidance for authentication systems. Source: Computer Security Division 2014 Annual Report."}]}
{"id": "nist_02950", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 2.2.3.5 GUI Gateway Installation according to NIST Securing Property Management Systems According to Securing Property Management Systems, 2.2.3.5 GUI Gateway Installation: 1. Ensure that the following packages are installed via $yum install [pkg\\_name], where [pkg\\_name] is: 2. -freerdp-libs 3. -uuid 4. -cairo 5. -libvncserver 6. -libpng12 7. -freerdp-plugins 8. -net-tools 9. -openssh-clients 10. -open-vm-tools <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Property Management Systems."}]}
{"id": "nist_02951", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does General Access Control Guidance for Cloud Systems provide? (Section 11) y and the privacy of services it provides. This document focuses on providing guidance for access control systems that are applicable to an organization's cloud implementation and security management. It does not prescribe the internal cloud access control standards that an organization may need in their enterprise systems or within a community other than the organization itself. The intended audience for this document is an organizational entity that implements access control solutions for sharing information in cloud systems. This document assumes that readers are familiar with the cloud and access (authorization) control systems and have basic knowledge of operating systems, databases, networking, and security. Given the constantly changing nature of the information technology (IT) industry, readers are strongly encouraged to take advantage of other documents-including those listed in this document-for more current and detailed information. The sections and appendix presented in this document are as follows: - Section 1 states the purpose and scope of access control and cloud systems. - Section 2 provides an overview of cloud access control characteristics. - Section 3 discusses guidance for access control systems for IaaS (Infrastructure as a Service). - Section 4 discusses guidance for access control systems for PaaS (Platform as a Service). - Section 5 discusses guidance for access control systems for SaaS (Software as a Service). - Section 6 discusses guidance for access control systems for inter- and intra-cloud operations. - Section 7 concludes the document with future directions. With the support of different service models, cloud systems can provide a wide range of services to its end-users, developers, and system administrators. Cloud systems have been developed over time and conceptualized through a combination of software, hardware components, and virtualization technologies.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authorization. Contains security framework guidance for authentication systems. Source: General Access Control Guidance for Cloud Systems."}]}
{"id": "nist_02952", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 264) ds development process of FIPS and recommendation practices of NIST. At a minimum, a technique outside of this family of 39 See Volume 3, Chapter 8 R&D for a discussion of some of the considerations. 226 techniques should (1) be defined in a publicly available forum, (2) be provided to a community of cryptographers for review and comment for a reasonable duration, (3) be in, or under development in, a standard by a recognized standards-developing organization (SDO). In addition, a case should be made for its use along the lines of resource constraints, unique nature of an application, or new security capabilities not afforded by the FIPS-approved and NIST- recommended techniques. 4.2.1.2 Entropy As discussed earlier in the section there are considerations when dealing with entropy on many constrained devices and systems that can be found throughout the smart grid. There are some possible approaches that can address restricted sources of entropy on individual point devices, they include: \uf0b7 Seeding a Deterministic Random Bit Generator (DRBG) on a device before distribution; any additional entropy produced within the device should be used to reseed it. \uf0b7 Alternatively, a Key Derivation Function (KDF) could derive new keys from a long-term key that the device has been pre-provisioned with. 4.2.1.3 Cryptographic Module Upgradeability Cryptographic algorithms are implemented within cryptographic modules that need to be designed to protect the cryptographic algorithm and keys used in the system. The following needs to be considered when planning the upgradeability of these modules: \uf0b7 Smart grid equipment is often required to have an average life of 20 years, which is much longer than for typical information technology (IT) and communications systems. \uf0b7 Due to reliability requirements for the electrical grid, testing cycles are often longer and more rigorous.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02953", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Contact according to Computer Security Division 2012 Annual Report? Contact: Mr. Quynh Dang quynh.GLYPH(cmap:df00)ang@nist.gov", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2012 Annual Report."}]}
{"id": "nist_02954", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Control Baselines for Information Systems and Organizations say about 2.4 TAILORING CONTROL BASELINES? (Part 1) According to Control Baselines for Information Systems and Organizations, 2.4 TAILORING CONTROL BASELINES: 2.4 TAILORING CONTROL BASELINES After selecting an appropriate control baseline, organizations initiate a tailoring process to align the controls more closely with the specific security and privacy requirements identified by the organization. The tailoring process is part of an organization-wide risk management process that includes framing, assessing, responding to, and monitoring information security and privacy risks. Tailoring decisions are dependent on organizational or system-specific factors. While tailoring decisions are focused on security and privacy considerations, the decisions are typically aligned with other risk-related issues that organizations must routinely address. Risk-related issues such as cost, schedule, and performance are considered in the determination of which controls to employ and how to implement controls in organizational systems and environments of operation. 24 The tailoring process can include but is not limited to the following activities: 25 - Identifying and designating common controls - Applying scoping considerations - Selecting compensating controls - Assigning values to organization-defined control parameters via explicit assignment and selection operations - Supplementing baselines with additional controls and control enhancements - Providing specification information for control implementation Organizations use risk management guidance to facilitate risk-based decision making regarding the applicability of the controls in the baselines. Ultimately, organizations employ the tailoring process to achieve cost-effective solutions that support organizational mission and business needs and provide security and privacy protections commensurate with risk. Organizations have the flexibility to tailor at the organization level for systems in support of a line of business or a mission or business process, at the individual system level, or by using a combination of the two.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Control Baselines for Information Systems and Organizations."}]}
{"id": "nist_02955", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 say about CUI ENHANCED SECURITY REQUIREMENTS? (Part 1) According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171, CUI ENHANCED SECURITY REQUIREMENTS: CUI ENHANCED SECURITY REQUIREMENTS Controlled Unclassified Information has the same value , whether such information is resident in a federal system that belongs to a federal agency or a nonfederal system that belongs to a nonfederal organization. Accordingly, the enhanced security requirements in this publication are consistent with and complementary to the guidelines used by federal agencies to protect CUI. The requirements are only applicable to a nonfederal system or nonfederal organization as mandated by a federal agency in a contract, grant, or other agreement. The APT is extremely dangerous to the national and economic security interests of the United States since organizations are very dependent on systems of all types, including traditional Information Technology (IT) systems, Operational Technology (OT) systems, Internet of Things 6 [32 CFR 2002] was issued on September 14, 2016, and went into effect on November 14, 2016. 7 The definition of a critical program may vary from organization to organization. For example, the Department of Defense defines a critical program as a program which significantly increases capabilities and mission effectiveness or extends the expected effective life of an essential system/capability [DOD ACQ]. 8 See [OMB M-19-03] and [OCIO HVA]. CHAPTER ONE PAGE 2 \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ (IoT) systems, and Industrial IoT (IIoT) systems. The convergence of these types of systems has brought forth a new class of systems known as cyber-physical systems , many of which are in sectors of U.S.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified, cui. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_02956", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guide to Intrusion Detection and Prevention Systems (IDPS) provide? (Section 93) rk traffic and analyzes its wireless networking protocols to identify suspicious activity involving the protocols themselves. This section provides a detailed discussion of wireless IDPS technologies. First, it contains a brief overview of wireless networking, which is background material for understanding the rest of the section. Next, it covers the major components of wireless IDPSs and explains the architectures typically used for deploying the components. It also examines the security capabilities of the technologies in depth, including the methodologies they use to identify and stop suspicious activity. The rest of the section discusses the management capabilities of the technologies, including recommendations for implementation and operation. Wireless networking enables devices with wireless capabilities to use computing resources without being physically connected to a network. The devices simply need to be within a certain distance (known as the range ) of the wireless network infrastructure. A wireless local area network (WLAN) is a group of wireless networking nodes within a limited geographic area that is capable of exchanging data through radio communications. WLANs are typically used by devices within a fairly limited range, such as an office building or corporate campus, and are implemented as extensions to existing wired local area networks (LAN) to provide enhanced user mobility. This section provides a brief introduction to wireless networking. Section 5.1.1 provides an overview of the most commonly used WLAN standards. Section 5.1.2 discusses the fundamental components of WLANs. Finally, Section 5.1.3 briefly examines the major threats against WLANs. This material is intended only to provide a high-level overview of wireless networking as background information for the wireless IDPS material in the rest of the section. 25 Most WLANs use the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of WLAN standards.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guide to Intrusion Detection and Prevention Systems (IDPS)."}]}
{"id": "nist_02957", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Securing Telehealth Remote Patient Monitoring Ecosystem provide? (Section 346) en authorized and unauthorized remote users. o Ability for the IoT device to differentiate between authorized and unauthorized physical device users. \uf0a7 Ability to verify the identity of an IoT device. \uf0a7 Ability to add a unique physical identifier at an external or internal location on the device authorized entities can access. | \uf0a7 Providing details for how to establish unique identification for each IoT device associated with the system and critical system components within which it is used. \uf0a7 Providing communications and documentation detailing how to perform account management activities, using the technical IoT device capabilities, or through supporting systems and/or tools. \uf0a7 Providing the details necessary to establish and implement unique identification for each IoT device associated with the system and critical system components within which it is used. \uf0a7 Providing the details necessary to require unique identifiers for each IoT device | .", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Telehealth Remote Patient Monitoring Ecosystem."}]}
{"id": "nist_02958", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls say about 4.2 Control Measures? (Part 3) According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls, 4.2 Control Measures: or components from the terminal. Where large quantities of media are used with the terminal, provisions should be made for its safe keeping. Most often these provisions will involve lockable cabinets. In general, the control of access to data in the host system will be provided by application and/or system controls. The discussion of such controls is treated in a different report. However, the auditor is cautioned that the selection and adequacy of local controls may be balanced against and must be appropriate to the application and system controls - 4.2.4 Audit Trail : Records must be kept such that the auditor can establish that controls are in place and that they are uniformly and consistently applied. More specifically, records must be kept such that: - o The assignment of responsibility and establishment of access rules consistent with Control Principles can be demonstrated. Normally, it will be possible to make this demonstration from documents kept for other purposes. These documents may include policy statements, standards and guidelines, procedures, program specifications, job descriptions and performance plans. - o Consistent enforcement of access rules can be demonstrated. This may involve the keeping of records specifically for this purpose. Such records might include a log of all attempted accesses distinguishing between those allowed and those disallowed. - o Accountability for service consumption and resource (data, media, terminal, etc.) use can be established. Normally this portion of the audit trail would be composed of system accounting records. - o The presence, or authorized absence or use of media can be demonstrated. This portion of the audit trail will usually be composed of media inventory control records such as the library management system. - o That required approvals and authorizations were given.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls."}]}
{"id": "nist_02959", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy say about SYSTEM DESCRIPTION? (Part 4) According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy, SYSTEM DESCRIPTION: contractor-operated; nonfederal [state and local governments, grantees]); incident response points of contact; authorization date and authorization termination date; and ongoing authorization status. System registration information is updated with the system characterization information (see Task P-18). References: [SP 800-18]; [NIST CSF] (Core [Identify Function]).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: csf, risk management framework, fips. General security reference material without sensitive content. Source: Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy."}]}
{"id": "nist_02960", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is GLUCK according to Report of the Workshop on Cryptography in Support of Computer Security? GLUCK: People must always realize that you must have a secure key in order to distribute other keys.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Report of the Workshop on Cryptography in Support of Computer Security."}]}
{"id": "nist_02961", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control SI-4009 in Computer Security Division 2008 Annual Report? (Part 23) Control SI-4009: communications used in electronic commerce, critical infrastructure, and other application areas. At the core of all products offering cryptographic services is the cryptographic module. Cryptographic modules, which contain cryptographic algorithms, are used in products and systems to provide security services such as confidentiality, integrity, and authentication. Although cryptography is used to provide security, weaknesses such as poor design or weak algorithms can render a product insecure and place highly sensitive information at risk. When protecting their sensitive data, federal government agencies require a minimum level of assurance that cryptographic products meet their security requirements. Also, federal agencies are required to use only tested and validated cryptographic modules. Adequate testing and validation of the cryptographic module and its underlying cryptographic algorithms against established standards is essential to provide security assurance. Our testing-focused activities include validating cryptographic modules and cryptographic algorithm implementations, developing test suites, providing technical support to industry forums, and conducting education, training, and outreach programs. Activities in this area involve collaboration and the facilitation of relationships with other entities. Federal agencies that have collaborated recently with these activities are the Department of State, the Department of Commerce, the Department of Defense, the General Services Administration, the National Aeronautics and Space Administration, the National Security Agency, the Department of Energy, the United States Office of Management and Budget, the Social Security Administration, the United States Postal Service, the Department of Veterans Affairs, the Federal Aviation Administration, and NIST's National Voluntary Laboratory Accreditation Program.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security Division 2008 Annual Report."}]}
{"id": "nist_02962", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders say about 2.2.2.3 Authenticating with the Token? According to Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders, 2.2.2.3 Authenticating with the Token: Now, because the system has a U2F token on file for the user, the user has the option to authenticate. - Click Authenticate (Figure 2-16), and the Google Authenticator application will be activated once more. - Hold the U2F token to your device, and then the authentication will be successful and the SSO flow will continue. Figure 2-16 FIDO U2F Authentication <!-- image -->", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, token, single sign-on. Contains security framework guidance for authentication systems. Source: Mobile Application Single Sign-On_ Improving Authentication for Public Safety First Responders."}]}
{"id": "nist_02963", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is https according to Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)? https: //docs.forescout.com/bundle/connect-module-1-7-rn/page/connect-module-1-7-rn.About-", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_02964", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain DISCUSSION according to NIST Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, DISCUSSION: Audit records can be generated at various levels of abstraction, including at the packet level as information traverses the network. Selecting the appropriate level of abstraction is a critical aspect of an audit logging capability and can facilitate the identification of root causes to problems. The ability to add information generated in audit records is dependent on system functionality to configure the audit record content. Organizations may consider additional information in audit records, including the access control or flow control rules invoked and the individual identities of group account users. Organizations may also consider limiting additional audit record information to only information that is explicitly needed for audit requirements.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}]}
{"id": "nist_02965", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain National Public Safety Broadband Network (NPSBN) according to NIST 2019 NIST_ITL Cybersecurity Program Annual Report According to 2019 NIST_ITL Cybersecurity Program Annual Report, National Public Safety Broadband Network (NPSBN): Federal statutes direct NIST to conduct research and development that support the acceleration and advancement of a nationwide broadband network that will help police, firefighters, emergency medical service professionals, and other public safety officials stay safe and do their jobs. Having a common and reliable National Public Safety Broadband Network (NPSBN) enables these officials to effectively communicate and conduct their missions. In FY 2019, NIST continued to research and advance methods and guidelines for this community, including: - Publication of draft NISTIR 8196, Security Analysis of First Responder Mobile and Wearable Devices, which reviews the current and potential use cases of these mobile and wearable devices by first responders and analyzes them from a cybersecurity perspective [25]. The goals of this analysis were to enable industry to design and produce more secure public safety devices and to assist jurisdictions in identifying security objectives and selecting secure devices. - Collaboration with the NIST Public Safety Communications Research (PSCR) Division's prize challenge. Contestants explored whether mobile Subscriber Identity Module (SIM) cards could be used as storage containers for public safety mobile application credentials. PSCR reached out to providers globally to participate in a competition aimed at improving public safety operations through innovative improvements to SIM card functionality. The goals of this research were to raise awareness of the need for convenient, standards-based, two-factor authentication for emergency responders while demonstrating an innovative approach to authentication that could lead to future innovations. - NCCoE released a second draft of NIST Cybersecurity Practice Guide SP 1800-13, Mobile Application Single Sign-On: Improving Authentication for Public Safety First Responders [26]. This revision of the guide was updated at the request of the public safety community to incorporate iOS version 12.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, single sign-on. Contains security framework guidance for authentication systems. Source: 2019 NIST_ITL Cybersecurity Program Annual Report."}]}
{"id": "nist_02966", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i? (Part 66) Control ES-1: on of cipher suites. The PMK is the cornerstone for a number of security features absent from WEP. Complete robust security is considered to be possible only when all devices in the network use RSNAs. In practice, some networks have a mix of RSNAs and non-RSNA connections. A network that allows the creation of both pre-RSN associations (pre-RSNA) and RSNAs is referred to as a Transition Security Network (TSN). A TSN is intended to be an interim means to provide connectivity while an organization migrates to networks based exclusively on RSNAs. 24 A link layer protocol describes the rules for communication between two entities over a particular communications medium, such as air (wireless networking) or various cable types (wired networking). It defines how these entities are uniquely addressed, how the medium will be shared when more than two entities use it simultaneously, and how to correct for errors in transmission. Link layer protocols are distinguished from network layer protocols, which focus primarily on routing data packets over multiple links, and perhaps over multiple media types. For example, the packets of a network layer protocol such as IP might travel over a number of links from source to destination. Different link layer protocols (e.g., Point-to-Point Protocol [PPP], IEEE 802.11, IEEE 802.16) might govern the transmission of the IP packets over each of the links. Although RSNs may be created for both BSS and IBSS WLANs, this guide only describes the security algorithms and 25 protocols for BSSs. Significant differences between these modes are highlighted.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i."}]}
{"id": "nist_02967", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Profile of the IoT Core Baseline for Consumer IoT Products provide? (Section 14) such as companion application software or backends, will exist 'outside the box 5 ,' but nonetheless are part of the IoT product through the support they provide for the operation of the IoT product. Regardless of these relationships, these additional 3 Some specialty networking/gateway hardware may be purchased by the customer separately, but are, nonetheless needed for the IoT product to work beyond basic features. In most cases where an IoT product requires separately purchased specialty networking/gateway hardware, that hardware will perform specific, consistent tasks in the implementation of an IoT product (e.g., protocol translation). For example, some IoT products require network connections other than conventional Wi-Fi/ethernet, such as Bluetooth, Zigbee, or Z-Wave, which would need a hub or gateway to allow for broader connectivity (i.e., over Wi-Fi and/or ethernet). This hub or gateway may not always be included as part of an IoT product, but, instead, be assumed to be part of the customer's network infrastructure, much like a Wi-Fi- router might be assumed for IoT products that use Wi-Fi. 4 'In the box' components, particularly the IoT device(s) that serves as the product end point can be considered the face of the IoT product since these are what a customer will physically handle, manage, and use. Though other components may be vital to operation of the IoT product (including cybersecurity), the IoT device(s) plays a central role to the IoT product and, in general, is the focus of the operation of the IoT product. 5 Some 'outside the box' components may be entirely remote relative to the customer, while others may be physically present in the customer's environment (e.g., inside their home), but, nonetheless, come separate from the IoT device(s).", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Profile of the IoT Core Baseline for Consumer IoT Products."}]}
{"id": "nist_02968", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases say about B.1.1.3 Intel Platform Firmware Resilience (PFR)? (Part 1) According to Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases, B.1.1.3 Intel Platform Firmware Resilience (PFR): B.1.1.3 Intel Platform Firmware Resilience (PFR) Intel Platform Firmware Resilience (PFR) technology is a platform-level solution that creates an open platform RoT based on a programmable logic device. It is designed to provide firmware resiliency (in accordance with NIST SP 800-193 [4]) and comprehensive protection for various platform firmware components, including BIOS, Server Platform Services Firmware (SPS FW), and BMCs. PFR provides the platform owner with a minimal trusted compute base (TCB) under full platform-owner control. This TCB provides cryptographic authentication and automatic recovery of platform firmware to help guarantee correct platform operation and to return to a known good state in case of a malicious attack or an operator error such as a failed update. NIST SP 800-193 [4] outlines three guiding principles to support the resiliency of platforms against potentially destructive attacks: - Protection: Mechanisms for ensuring that platform firmware code and critical data remain in a state of integrity and are protected from corruption, such as the process for ensuring the authenticity and integrity of firmware updates - Detection: Mechanisms for detecting when platform firmware code and critical data have been corrupted - Recovery: Mechanisms for restoring platform firmware code and critical data to a state of integrity in the event that any such firmware code or critical data is detected to have been corrupted or when forced to recover through an authorized mechanism. Recovery is limited to the ability to recover firmware code and critical data. In addition, NIST SP 800-193 [4] provides guidance on meeting those requirements via three main functions of a Platform Root of Trust: - Root of Trust for Update, which is responsible for authenticating firmware updates and critical data changes to support platform protection capabilities; this includes signature verification of firmware updates as well as rollback protections during update.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases."}]}
{"id": "nist_02969", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Status Report on the Second Round of the SHA-3 Cryptographic Hash Algorithm Competition say about 4.4.2 Performance? According to Status Report on the Second Round of the SHA-3 Cryptographic Hash Algorithm Competition, 4.4.2 Performance: ECHO is a below-average performer in software across most platforms for long messages. When the processor includes AES-NI instructions, the performance is increased significantly. ECHO is a poor performer on software platforms for very short messages. In constrained environments, ECHO has poor performance, with a slightly higher ROM requirement than average and a fairly high RAM requirement. In hardware, ECHO has very poor performance in its throughput-to-area ratio; however, it can make use of embedded resources in FPGAs to reduce the area needed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Status Report on the Second Round of the SHA-3 Cryptographic Hash Algorithm Competition."}]}
{"id": "nist_02970", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Weakness Abstractions according to NIST Hardware Security Failure Scenarios_ Potential Hardware Weaknesses According to Hardware Security Failure Scenarios_ Potential Hardware Weaknesses, Weakness Abstractions: The CWE weaknesses model is composed of four layers of abstraction: pillar (P), class (C), base (B), and variant (V) 1 . The abstraction reflects the extent to which issues are being described in terms of five dimensions: behavior, property, technology, language, and resource. Variant weaknesses are at the most specific level of abstraction and describe at least three dimensions. Base weaknesses are more abstract than variants and more specific than classes; they describe two to three dimensions. Class weaknesses are very abstract and not typically specific about any language or technology; they describe one to two dimensions. Pillar weaknesses are at the highest level of abstraction. In this work, pillars and classes are used to organize the HW security failure scenarios.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Hardware Security Failure Scenarios_ Potential Hardware Weaknesses."}]}
{"id": "nist_02971", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Recommendation for Key Management_ Part 1 \u2013 General say about 4.4 Random Bit Generation? According to Recommendation for Key Management_ Part 1 \u2013 General, 4.4 Random Bit Generation: Random bit generators (RBGs) (also called random number generators (RNGs)) are required for the generation of keying material (e.g., keys and IVs). RBGs generate sequences of random bits (e.g., 010011); technically, RNGs translate those bits into numbers (e.g., 010011 is translated into the number 19). However, the term 'random number generator' (RNG) is commonly used to refer to both concepts. The use of RBGs is discussed in SP 800-175B; approved RBGs are specified in the SP 800-90 series of documents. 29 For example, see FIPS 197 and SP 800-38F. 30 Sometimes, a key pair is generated by a party that is trusted by the key owner rather than by the key owner and then provided to the key owner. 31 See FIPS 186. 32 See SP 800-56A and SP 800-56B.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Recommendation for Key Management_ Part 1 \u2013 General."}]}
{"id": "nist_02972", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does ANSI_NIST-ITL 1-2011 Requirements and Conformance Test Assertions provide? (Section 64) class or above. It can also be used for the 500 ppi class.Record Type-4 shall not be used for anything but the 500 ppi class. Exemplar images shall have a minimum class scanning resolution of 500 ppi. The migration path to higher scanning resolutions for image capturing devices with a native scanning resolution of the 500 ppi class shall be at a rate of 100% of the current native scanning resolution. Capture devices with native scanning resolutions not in step with this migration path shall provide (through subsampling, scaling, or interpolating downward) a nominal resolution that matches the next lower interval in the migration path. For example, a device with native scanning resolution of 47.24 ppmm (1200 ppi) shall provide a class resolution of 39.37 ppmm (1000 ppi). The scanner resolution is specified for Record Types 14, 15, 16, 17, 19 and 20 using Scanned horizontal pixel scale / SHPS (See Section 7.7.8.7) and Scanned vertical pixel scale / SVPS (See Section 7.7.8.8). These Record Types can handle all resolutions, and are thus called variable-resolution image records. Latent images should have a minimum class scanning resolution of 1000 ppi. Record Type-13 specifies resolution using Scanned horizontal pixel scale / SHPS (See Section 7.7.8.7) and Scanned vertical pixel scale / SVPS (See Section 7.7.8.8). Record Type-13 can handle all resolutions, and is thus called a variable-resolution image record. 7.7.6.2.1 Field: Exemplar Scan Resolution Field: Latent Resolution 7.7.6.2.2, 7.7.6.1 {XElm(biom:NativeScanningResolutionValue) in XElm(itl:PackageInformationRecord)} EQ 00.00 2 M 1.011-NSR- Type4 500 ppi Only {1.011} GTE 19.30 AND LTE 20.08 B 2 M Fields- Exemplar Valid Scan Resolutions <Scanning resolutions for Record Types 14,15,16,17,19 and 20 must migrate at a rate of 100% with a minimum of 500 ppi.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: ANSI_NIST-ITL 1-2011 Requirements and Conformance Test Assertions."}]}
{"id": "nist_02973", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Guidelines for Smart Grid Cybersecurity provide? (Section 293) . \uf0b7 Local autonomy: All authentication processes between devices, or between users and devices will be able to operate even if a centralized service over a network is not available at any given time. For example, this is to ensure that if a network connection in a substation becomes unavailable, but a critical operation needs to be accomplished by local personnel, they would not in any way be inhibited from doing so. \uf0b7 Revocation management: The ability to revoke credentials in a system in an ordered manner that ensures that all affected devices and users are notified and can take appropriate actions and adjustments to their configurations. Examples can include handling revoked PKI certificates and ensuring that entities with revoked certificates cannot be authenticated to protected services and functions. \uf0b7 Key material provisioning: The processes and methods used to securely enter key material initially into components and devices of a system, as well as changing key materials during their operation. \uf0b7 Key material destruction: The secure disposal of all key material after its intended use and lifetime, for example, the zeriozation/erasure of CSPs. Making key material unavailable is an acceptable alternative for systems where destruction is not possible. \uf0b7 Credential span of control: The number of organizations, domains, systems or entities controlled or controllable through the use of the key material associated with the credential. This does not explicitly address keys used for purposes other than control nor 241 include asymmetric keys that are indirectly used for control, such as those associated with root or intermediate certification authorities.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, pki, sso. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02974", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 3.6.2 Element-Level Judgment Assistance according to NIST ISCMA_ An Information Security Continuous Monitoring Program Assessment According to ISCMA_ An Information Security Continuous Monitoring Program Assessment, 3.6.2 Element-Level Judgment Assistance: Each element has an associated discussion to assist in making a judgment. The discussion is accessed by clicking on the element's Notes/Help icon shown in Figure 19. An example of the resulting Notes/Help form is displayed in Figure 20, showing the Assessment Procedure for the element, helpful Discussion about the element, the Rationale for the designated risk management level, and input areas for Recommendations and Notes . The Notes input area allows the rationale for judgments or other thoughts and considerations to be recorded. The Recommendations input area allows recommendations for responses to Other than Satisfied judgments to be recorded. Figure 19 - Notes/Help Icon <!-- image --> Note that there are also buttons for Save and Cancel on this form. 13 The colors of the judgments can be tailored. See Section 5.3.1. Figure 20 - Element-Level Judgment Assistance <!-- image -->", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: ISCMA_ An Information Security Continuous Monitoring Program Assessment."}]}
{"id": "nist_02975", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Guidelines on Securing Public Web Servers say about Using Authentication and Encryption Technologies for Web Servers? (Part 3) According to Guidelines on Securing Public Web Servers, Using Authentication and Encryption Technologies for Web Servers: level of client authentication, configure server to require username and password via SSL/TLS | | | For configurations that require a high level of client authentication, configure server to require client certificates via SSL/TLS | | | Ensure weak cipher suites are disabled (see Table 7.1 for the recommended usage of Federal cipher suites) | | | Configure file integrity checker to monitor Web server certificate | | | If only SSL/TLS is to be used in the Web server, ensure access via any TCP port other than 443 is disabled | | | If most traffic to the Web server will be via encrypted SSL/TLS, ensure that appropriate logging and detection mechanisms are employed in the Web server (because network monitoring is ineffective against encrypted SSL/TLS sessions) | | Completed | Action | |-------------|------------------------------------------------------------------------| | | Protect against brute force attacks | | | Use strong authentication if possible | | | Use a delay after failed login attempts | | | Lock out an account after a set number of failed login attempts | | | Enforce a password policy | | | Blacklist IP addresses or domains known to attempt brute force attacks | | | Use", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, password policy. Contains security framework guidance for authentication systems. Source: Guidelines on Securing Public Web Servers."}]}
{"id": "nist_02976", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Derived PIV Application and Data Model Test Guidelines say about 8.2.2.1 Derived PIV Application Data Objects? According to Derived PIV Application and Data Model Test Guidelines, 8.2.2.1 Derived PIV Application Data Objects: | Test Assertion | TA-08.02.02.01 | |------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| | Purpose | Confirms the data objects (along with their access conditions) are implemented by the vendor of the Derived PIV Application per the specification. | | DTR(s) | \u2022 DTR-06.02.02.01 | |----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| | Vendor Documentation | The vendor to provide documentation identifying all the data objects (mandatory and optional) implemented within the Derived PIV Application. |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Derived PIV Application and Data Model Test Guidelines."}]}
{"id": "nist_02977", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Derived Personal Identity Verification (PIV) Credentials say about 5.2.2.1 Initial Issuance? (Part 4) According to Derived Personal Identity Verification (PIV) Credentials, 5.2.2.1 Initial Issuance: xhibits the following security enhancements: - \uf0a7 Software-based screen scraping or malware attacks that attempt to perform a screen capture of the keypad cannot view the actual layout of the numbers. Instead, the entire keypad is blacked out. - \uf0a7 Each time the keypad window is presented, the numeric keypad is randomized. This means the locations used to enter the PIN change every time. An attacker that captures the PIN entry pattern for successful authenticator activation cannot use it for subsequent PIN entries. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ - \uf0a7 Authenticator activation input for the PIN entry is translated and used within the protective hardware. The actual PIN value is not exposed outside the hardware. - \uf0a7 A 'PIN throttling' mechanism tracks the number of incorrect PIN entry attempts, and at specific intervals will refuse additional PIN attempts for a specific period. This feature minimizes brute force attacks on the PIN. - \uf0a7 Keyboard entry of the PIN is not allowed. This feature minimizes keyboard logger attacks. Post-issuance, the Derived PIV Authentication certificate, along with an indication that the user controls the associated private key, is visible through the Windows certificate Microsoft Management Console in the Personal folder as shown below in Figure 5-15. Figure 5-15 Verizon SSP Derived PIV Authentication Certificate <!-- image -->", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authentication, sso. Contains security framework guidance for authentication systems. Source: Derived Personal Identity Verification (PIV) Credentials."}]}
{"id": "nist_02978", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Representation of PIV Chain-of-Trust for Import and Export provide? (Section 21) y names of the PIV cardholder. The &lt;PrimaryIdentifier&gt; element is always included in the PersonalInformationType complex type and appears only once. The data is provided in an xs:string format. This element contains the Secondary Identifier of the subject of the chain-oftrust enrollment record. The Secondary Identifier is defined in [FIPS201] as pre-names or given names of the PIV Cardholder. The &lt;SecondaryIdentifier&gt; element is always included in the PersonalInformationType complex type and occurs only once. The data is provided in an xs:string format. This element contains the Printed Name of the subject of the chain-of-trust enrollment record. The Printed Name is a combination of the card holder's primary and secondary identifiers, as it is to be printed on the PIV Card according to [FIPS201]. The &lt;PrintedName&gt; element is always included in the PersonalInformationType complex type and only occurs once. The data is provided in an xs:string format. This element may contain the Social Security Number of the subject of the chain-of-trust enrollment record. 1 The &lt;SSN&gt; element is optional, and may occur only once if included in the PersonalInformationType complex type. The data is provided in an xs:string format. This element is required, occurs once in the PersonalInformationType complex type and contains a boolean value. If the subject of the chain-of-trust enrollment record is a U.S. Citizen, then the value is set to true. If the subject of the chain-of-trust enrollment record is not a U.S. Citizen, then the value is set to false. The data is provided in an xs:boolean format. If the &lt;IsUSCitizen&gt; element is false, then at least one country is specified in &lt;CitizenshipCountryCode&gt;. This element is required if &lt;IsUSCitizen&gt; is set to false and optional if &lt;IsUSCitizen&gt; is set to true. The element contains the countries of citizenship of the subject of the chain-of-trust enrollment record.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Representation of PIV Chain-of-Trust for Import and Export."}]}
{"id": "nist_02979", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Automated Information System Security Accreditation Guidelines say about 5. LAVA? According to Automated Information System Security Accreditation Guidelines, 5. LAVA: Use LAVA if you checked box D, F or G in Form 1, Item 2 on page 13. Include a LAVA Report in the Accreditation Report for these DPAs instead of Form 2. Obtain the IBM-PC compatible LAVA software from the AISSM. It can be installed on personal computers using Intel 8088, 80286 and 80386 microprocessors. The software requires a minimum of two floppy disk drives or one hard and one floppy disk drive and 512 Kilobytes of memory. It does not require modification for use at different sites. LAVA is a comprehensive method for assessing vulnerabilities and risks. If you are using LAVA, read the manual that comes with the software and follow its instructions. Also, distribute copies of this manual to all persons involved in the risk assessment.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Automated Information System Security Accreditation Guidelines."}]}
{"id": "nist_02980", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings provide? (Section 250) GSI to RSA public/private key pair generation in the GSI, because the time taken to compute a public key using the hash function H 1 in PECF-GSI is negligible given the parameters we have chosen. Furthermore, construction of a public key by hashing an identifier occurs as part of the associated encryption/decryption scheme. - The only long-term secret required by users is a password. This is likely to improve usability and accessibility of grid applications considerably. Moreover, we do not need to worry about revocation of users' public keys, a considerable problem in certificate-based architectures. - Key agreement and delegation in our approach requires much less bandwidth than the GSI. In addition, our delegation technique requires only a single verification. - The computational effort required by the key generation algorithms that we employ is considerably lower than in the GSI. Our lightweight security architecture is more suitable than the GSI for use by devices with limited resources, thereby significantly extending the number of devices that can interact with computational grids and going some way to realising the potential of wireless grids. That said, identity-based and certificateless public key cryptography are relatively new, and thus lack support from standardisation bodies. This may hinder early adoption of our proposal. To meet the requirement of grid applications which do not tolerate key escrow, we proposed the use of certificateless public key cryptography, which enables users to select their own private components. This only resulted in minor changes, in terms of key set-up, to our original architecture. An important security aspect of grid applications which we have not considered in this paper is authorization. A natural extension of this work is to develop novel authorization techniques using properties of identity-based cryptography.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: authorization, pki, sso. Contains security framework guidance for authentication systems. Source: 6th Annual PKI R&D Workshop _Applications-Driven PKI_ Proceedings."}]}
{"id": "nist_02981", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security Division 2008 Annual Report say about Security Configuration Checklists for Commercial IT Products? (Part 3) According to Computer Security Division 2008 Annual Report, Security Configuration Checklists for Commercial IT Products: s for checklist application \u25c6\u25c6 such as the Security Content Automation Protocol (SCAP). Checklists can take many forms, including files that can automatically set or verify security configurations. Having such automated methods has become increasingly important for several reasons, including the complexity of achieving compliance with various laws, Executive Orders, directives, policies, regulations, standards, and guidance; the increasing number of vulnerabilities in information systems; and the growing sophistication of threats against those vulnerabilities. Automation is also needed to ensure that the security controls and configuration settings are applied consistently within an information system, and that the controls and settings can be effectively verified. The SCAP program addresses these needs by enabling standards based security tools to automatically perform configuration checking using NCP checklists. Working closely with government, industry, and academia, CSD encourages the development of automated checklists, particularly those that are compliant or compatible with XCCDF (Extensible Configuration Checklist Description Format) and/or OVAL (Open Vulnerability and Assessment Language). These are widely used for automated checklists-XCCDF primarily for mapping policies and other sets of requirements to high-level technical checks, and OVAL primarily for mapping high-level technical checks to the low-level details of executing those checks on the operating systems or applications being assessed. There are 130 checklists posted on the website; 25 of the checklists are SCAPexpressed and can be used by SCAP-validated software tools. This allows organizations to use checklists obtained from the CSD web site (checklists. nist.gov) for automated security configuration and patching without vendor interaction.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Computer Security Division 2008 Annual Report."}]}
{"id": "nist_02982", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control PD-12 in Information Security Handbook_ A Guide for Managers? (Part 178) Control PD-12: ecurity Categories , June 2004. National Institute of Standards and Technology Special Publication 800-64, Security Considerations in the Information System Development Life Cycle , Rev. 1, June 2004. ## Annex 11.A Agency Information Security Program Assessment Questionnaire Low: \\_\\_\\_\\_\\_\\_\\_ Moderate: \\_\\_\\_\\_\\_\\_\\_\\_ High: \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Number of Systems in each FIPS 199 Impact Level Category Agency System Summary: Purpose of Report: \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Time Period Covered in Report: \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Date of Report: \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Name(s) of Assessors: \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Name of Responsible Individual: \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ Name of Agency: \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ ## Information Security Program Questions Each question should be answered for each level of IT Security maturity. Each column represents an IT Security Maturity Level. For the 'Policy' maturity level, to answer 'Yes,' the topic should be documented in agency policy. For the 'Procedures' maturity level, to answer 'Yes,' the topic should be documented in detailed procedures. For the 'Implemented' maturity level, to answer 'Yes,' the implementation is verified by examining the procedures and program area documentation, and interviewing key personnel to determine that the procedures are implemented. For the 'Tested' maturity level, to answer 'Yes,' documents should be examined and interviews should be conducted to verify that the policies and procedures for the question are implemented and operating as intended and provide the desired level of security.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control, assessment. General security reference material without sensitive content. Source: Information Security Handbook_ A Guide for Managers."}]}
{"id": "nist_02983", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard say about o LU GO O o LU? (Part 1) According to Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard, o LU GO O o LU: o LU GO O o LU", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security and the Data Encryption Standard_ Proceedings of the Conference on Computer Security and the Data Encryption Standard."}]}
{"id": "nist_02984", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Supported Phones according to NIST Cell Phone Forensic Tools_ an Overview and Analysis According to Cell Phone Forensic Tools_ an Overview and Analysis, Supported Phones: Pilot-link communicates with Palm OS handheld devices, such as those manufactured by Palm, Handspring, Handera, TRGPro, and Sony, over a serial connection. Palm OS devices that double as a cell phone do not necessarily work properly with all of the integrated functions provided by Pilot-link. For instance, Pilot-link was only able to acquire individual database files from the PalmOne Treo 600. However, Pilot-link could acquire all data from a Kyocera 7135 Palm OS-based cell phone using pi-getram, pi-getrom, and pilot-xfer -b. Before performing an actual acquisition, the examiner should experiment with Palm OS-based phones to determine whether Pilot-link can acquire the necessary data.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cell Phone Forensic Tools_ an Overview and Analysis."}]}
{"id": "nist_02985", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control ES-1 in Guidelines on Electronic Mail Security? (Part 71) Control ES-1: | Ability to disable unnecessary network services that may be built into the operating system or server software | | | Ability to log appropriate server activities to detect intrusions and attempted intrusions | | | Availability of trained, experienced staff to administer the server and server products | | | Plan the location of the mail server | | | Appropriate physical security protection mechanisms | | | Appropriate environmental controls to maintain the necessary temperature and humidity | | | Backup power source | | | Preparation for known natural disasters | ## This page has been left blank intentionally.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security."}]}
{"id": "nist_02986", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE) say about 2.8.1 Create MobileIron API Account for Appthority Connector? (Part 2) According to Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE), 2.8.1 Create MobileIron API Account for Appthority Connector: Appthority Connector User <!-- image --> - c. In the Assign to Space dialogue: - i. In the Select Space drop-down menu, select Global. - ii. Enable each of the following settings: - iii. Click Save. Figure 2-132 Appthority Connector Space Assignment <!-- image --> <!-- image --> | Device Management > View device page, device details | |----------------------------------------------------------| | Privacy Control > View apps and ibooks in device details | | App Management > Apply and remove application label | | Other Roles > API |", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mobile Device Security_ Corporate-Owned Personally-Enabled (COPE)."}]}
{"id": "nist_02987", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain 9.8 KMSA TO KMSA PROTOCOL according to NIST A Study of OSI Key Management According to A Study of OSI Key Management, 9.8 KMSA TO KMSA PROTOCOL: The KMSA-KMSA protocol specifies the interaction between two KMSAs. The mission of the KMSA-KMSA protocol is to establish the keys and associated attributes needed by the two communicating security protocols, or to update the security association.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: A Study of OSI Key Management."}]}
{"id": "nist_02988", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is Asset Identification according to Specification for Asset Identification 1.1? Asset Identification: The use of attributes and methods to uniquely identify an asset.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Specification for Asset Identification 1.1."}]}
{"id": "nist_02989", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control GP-4 in System and Network Security Acronyms and Abbreviations? (Part 39) Control GP-4: | XKMS | XMLKey Management Specification | | XML | Extensible Markup Language | | XOR | exclusive OR | | XrML | eXtensible Rights Markup Language | | XSD | XML Schema Definition | | XSL | Extensible Stylesheet Language | | XSLT | Extensible Stylesheet Language Transformation | | XSS | cross-site scripting | | ZSK | zone signing key | ## Appendix A-References Sources used in the development of the list of system and network security acronyms and abbreviations in this document include the following: National Institute of Standards and Technology Publications, NIST Computer Security Division Resource Center Web site, http://csrc.nist.gov/ Internet Engineering Task Force (IETF), http://www.ietf.org/ Microsoft Hardware Developer Central, Glossary of Acronyms for PC and Server Technologies, Organization for the Advancement of Structured Information Standards (OASIS), ## Appendix B-Former Acronyms Over time, as organizations, technologies, or other entities change, some acronyms associated with them may lose their definitions and thus no longer be considered acronyms.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: key management, sso. Contains security framework guidance for authentication systems. Source: System and Network Security Acronyms and Abbreviations."}]}
{"id": "nist_02990", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD) say about OSMUD end? (Part 19) According to Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD), OSMUD end: arent Capability Subrequirement(s) of Par- ent Capability to Be Demonstrated (Y-1) Device Identification\u2013The device is detected, and its make and model are identified upon connection to the network. (Y-2) Device Categorization\u2013The device is correctly categorized accord- ing to its type (e.g., phone, printer, computer, watch) upon connection to the network. (Y-1.a) The non-MUD-capable device\u2019s make and model are correctly identified based on some combination of information such as the de- vice\u2019s MAC address, DHCP header information, and lookup in reposito- ries. (Y-2.a) The non-MUD-capable device is correctly categorized based on its make and model. The device make and model were determined using some combination of MAC address, DHCP header information, and lookup in repositories. (Y-1.b) The non-MUD-capable device\u2019s make and model cannot be iden- tified. (Y-2.b) The make and model of the non-MUD-capable device cannot be determined. The non-MUD-capable device is designated as uncatego- rized. Description Verify that upon detection, when possible, the make (i.e., manufacturer) and model of a non-MUD-capable device are identified correctly based NIST SP 1800-15D: Securing Small-Business and Home Internet of Things Devices 202 This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.1800-15 Exercise Field Description on some combination of its MAC address, DHCP header information, and lookup through the Yikes! cloud service; the device is assigned to the correct category; and it is assigned a unique identity. In addition, verify that a non-MUD-capable device whose make and model cannot be determined will be assigned to the \u201cuncategorized\u201d category.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: nist sp, fips, security control. General security reference material without sensitive content. Source: Securing Small-Business and Home Internet of Things (IoT) Devices_ Mitigating Network-Based Attacks Using Manufacturer Usage Description (MUD)."}]}
{"id": "nist_02991", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. Explain Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines according to NIST Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings According to Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings, Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines: Developing Cybersecurity and Privacy Concept Mappings Karen Scarfone Scarfone Cybersecurity Murugiah Souppaya Computer Security Division Information Technology Laboratory Michael Fagan Applied Cybersecurity Division Information Technology Laboratory This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8477 February 2024 <!-- image --> U.S. Department of Commerce Gina M. Raimondo, Secretary National Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology Certain 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 ", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings."}]}
{"id": "nist_02992", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What information does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Section 152) | | | x | SC-30(3) | Concealment and Misdirection Change Processing and Storage Locations | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ TABLE C-14: SYSTEM AND INFORMATION INTEGRITY REQUIREMENT MAPPINGS | SECURITY REQUIREMENTS | SECURITY REQUIREMENTS | Defense-in-Depth Protection Strategy | Defense-in-Depth Protection Strategy | Defense-in-Depth Protection Strategy | NIST SP 800-53 Relevant Security Controls | NIST SP 800-53 Relevant Security Controls | |-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------|---------------------------------------------|-----------------------------------------------------------------------------------| | | | PRA | DLO | CRS | | | | 3.14.1e | Verify the integrity of [ Assignment: organization- defined security critical or essential software ] using root of trust mechanisms or cryptographic signatures.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "high", "explanation": "NIST publication discussing classified information handling. References: classified, controlled unclassified. Contains guidance on protecting sensitive government information. Source: Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171."}]}
{"id": "nist_02993", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control IP-002 in Guidelines for Smart Grid Cybersecurity? (Part 211) Control IP-002: ive for all but the smallest systems. All of this overhead and risk can be multiplied several times if each device is to have several independent security associations, each requiring a different key. Alternatively, techniques like those used by Kerberos can eliminate much of the manual effort and associated cost, but Kerberos cannot provide the high-availability solution when network or power outages prevent either side of the communication link from accessing the key distribution center (KDC). The provisioning of digital certificates can be a much more cost-effective solution, because this does not require the level of coordination posed by symmetric key provisioning. With digital certificates, each device typically only needs one certificate for key establishment, and one key establishment private key that never leaves the device, once installed. Some products generate, store, and use the private key in a FIPS-140 hardware security module (HSM). In systems where the private key never leaves the HSM, higher levels of security with lower associated operational costs are provided. For example, certificate provisioning involves several steps, including the generation of a key pair with suitable entropy, the generation of a certificate signing request (CSR) that is forwarded to a Registration Authority (RA) device, appropriate vetting of the CSR by the RA, and forwarding the CSR (signed by the RA) to the Certificate Authority (CA), which issues the certificate and stores it in a repository and/or sends it back to the subject (i.e., the device authorized to use the private key). CAs need to be secured, RA operators need to be vetted, certificate revocation methods need to be maintained, certificate policies need to be defined, and so on. Operating a PKI for generating and handling certificates can also require a significant amount of overhead and is typically not appropriate for small and some midsized systems.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: pki, certificate authority, sso. Contains security framework guidance for authentication systems. Source: Guidelines for Smart Grid Cybersecurity."}]}
{"id": "nist_02994", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Manufacturing Profile say about Table 3 PROTECT Business Mission Objectives? (Part 1) According to Cybersecurity Framework Manufacturing Profile, Table 3 PROTECT Business Mission Objectives: Table 3 PROTECT Business Mission Objectives", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Cybersecurity Framework Manufacturing Profile."}]}
{"id": "nist_02995", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Computer Security_ Selected Articles say about The Internet Worm? (Part 2) According to Computer Security_ Selected Articles, The Internet Worm: il November 12. The worm's fast and massive infestation was so portentous that the New York Times ran updates on page one for a week. The 'Nail Street [oumal and usa Today gave it front-page coverage. It was the subject of two articles in Science magazine (1, 2). It was covered by the wire services, the news shows, and the talk shows. These accounts said that over 6,000 computers were infested, but later estimates put the actual number between 3,000 and 4,000, about 5% of those attached to the Internet. On November 5 the New York Times broke the storv that the alleged culprit was Robert T. Moms, a Cornell graduate student and son of a weil-known computer security expert who is the chief scientist at the National Computer Security Center. A friend reportedly said that Moms intended no disruption; the worm was supposed to propagate slowiv, but a design error made it unexpectedly prolific. When he realized what was happening. Moms had a inend post on an electronic bulletin board instructions telling how to disable the wormbut no one Peter Dettnin y is Director at the Research Institute tor Advanced Computer Science at the '.ASA Ames Researcit Center could access them because all affected computers were down. As of February 1989, no indictments had been filed as authonties pondered legal questions. Morris himself was silent throughout. The worm's author went to great lengths to confound the discovery and analysis of it, a delaying tactic that permitted the massive infestation. By early December 1988, Eugene Spafford of Purdue (3), Donn Seeiev of", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security_ Selected Articles."}]}
{"id": "nist_02996", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is This publication is available free of charge from according to Cryptographic Algorithms and Key Sizes for Personal Identity Verification? This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-78-5", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Cryptographic Algorithms and Key Sizes for Personal Identity Verification."}]}
{"id": "nist_02997", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure say about 5.2.1. Identity Management, Authentication and Access Control Category? (Part 8) According to Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure, 5.2.1. Identity Management, Authentication and Access Control Category: EVSE-specific protections are warranted due to the unmanned nature of many EVSE installations. This may take the form of tamper-resistant tools (locks, proprietary tools, etc.), access and tamper logging switches/devices, or deactivating ports allowing unauthenticated access or modification of log/configuration data. This could also include physically securing the charge cable connector to prevent tampering or monitoring for tamper evident events and signals. EVSE owners/operators may consider surveilling the EVSE surroundings for unusual behavior. | [NIST Handbook 44] 1.10 G-S.8, 1.10 G- S.8.2, 3.40 S.3.1, 3.40 S.3.3 ISA/IEC 62443-2- 1:D4E1 ORG 3.1, AVAIL 1.1, AVAIL 1.2 OIML D31:2019 6.1.3.2.1, 6.1.3.2.4, OIML G22:2022 4.4.3.2 | | AC-2 | Cloud/Third-Party | Applicable, but no additional Cloud/Third-Party-specific considerations. | [NIST-SP800-53r5] PE-1, PE-2, PE-3, PE-4, PE-5, PE-6, PE-8, PE-9 | | AC-2 | Utility/Building Management System | Applicable, but no additional Utility/Building Management System specific considerations. | ISA/IEC 62443-2- 1:D4E1 ORG 3.1, AVAIL 1.1, AVAIL 1.2 | | AC-3: Remote access is managed. | Ecosystem: Ecosystem members can consider establishing formal access control policies and guidelines that clearly define remote access privileges. Management may take the form of authentication, training, verification prior to access being granted, and automatic timeout threshold implementation. Managing remote access may include authentication and management and audit mechanisms to track, log, and approve access attempts and activities of devices within the ecosystem.", "findings": [{"category": "confidential", "subcategory": "confidential.classified", "severity": "medium", "explanation": "NIST publication on credential and access management. Topics: access control, authentication, identity management. Contains security framework guidance for authentication systems. Source: Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure."}]}
{"id": "nist_02998", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What does Securing Manufacturing Industrial Control Systems_ Behavioral Anomaly Detection say about Table of Contents? (Part 25) According to Securing Manufacturing Industrial Control Systems_ Behavioral Anomaly Detection, Table of Contents: ....................... 79 | | Appendix F. References...................................................................................................... | 82 | | List of Tables | | | Table 2-1 Mapping of Cybersecurity Framework Functions Addressed by BAD Capabilities to the Manufacturing Profile..................................................................................................... Table 3-1 BAD Methods and Security Functions................................................................... | 5 13 | | Table 3-2 Typographic Conventions ......................................................................................", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: cybersecurity framework, fips, security control. General security reference material without sensitive content. Source: Securing Manufacturing Industrial Control Systems_ Behavioral Anomaly Detection."}]}
{"id": "nist_02999", "source": "nist", "source_license": "public_domain", "text": "You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance on cybersecurity controls, risk management, cloud security, and compliance based on NIST publications including the 800 series, FIPS, and related documents. What is control AM-1 in Securing Property Management Systems? (Part 163) Control AM-1: domain information and credentials to be employed by ForeScout CounterACT: <!-- image --> <!-- image --> 6. Input the IP Address range to be provisioned to the wireless network: <!-- image --> 7. Set the enforcement options desired for this deployment. For our lab, Full Enforcement, NAT Detection (Network Address Translation) and Auto Discovery were employed: 8. Start the appliance in the options windows. You can open the options menu by selecting the gear on the right of the screen: <!-- image --> <!-- image --> ## 2.7.4 DNS Enforcement In the options menu, select the drop-down for modules, then select DNS Enforce. In this menu, configure the IP used for the DNS enforcement. It should look like the screenshot below: <!-- image --> ## 2.7.5 Switch Plug-In 1. In the options menu, select the switch menu icon in the left scrolling menu. Here, we are adding our VyOS switch: - Select Add. - Enter the address of the switch. - Select Router-Linux as the vendor: <!-- image --> 2. Enter the authentication credentials of the switch to enable CLI management via the Forescout CounterACT appliance: 3. Verify that Read: IP to MAC Mapping is checked: <!-- image --> <!-- image --> 4. Configure 802.1X per organizational specification: 5. Start and test your switch configuration, selecting start and test respectively: <!-- image --> <!-- image --> ## 2.7.6 Guest Policy The guest policy is defined to control access of a hotel guest when that person is using Guest WiFi according to the authentication results of the hotel guest device. The authentication process determines the access to which the hotel guest device qualifies, then Forescout implements the controls to provide the correct access. It is assumed, due to limitations of the NCCoE lab, that the actual authentication process is completed.", "findings": [{"category": "safe", "subcategory": "safe.documentation", "severity": "info", "explanation": "NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Property Management Systems."}]}