You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance 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).

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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 – General say about 4.4 Random Bit Generation? According to Recommendation for Key Management_ Part 1 – 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.

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 – General.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance 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) .  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.  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.  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.  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.  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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, 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 -->

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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) | • 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. |

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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: -  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. -  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. \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ -  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. -  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. -  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 -->

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance 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 <PrimaryIdentifier> 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 <SecondaryIdentifier> 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 <PrintedName> 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 <SSN> 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 <IsUSCitizen> element is false, then at least one country is specified in <CitizenshipCountryCode>. This element is required if <IsUSCitizen> is set to false and optional if <IsUSCitizen> is set to true. The element contains the countries of citizenship of the subject of the chain-of-trust enrollment record.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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 ◆◆ 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance 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.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Guidelines on Electronic Mail Security.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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 |

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).


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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–The device is detected, and its make and model are identified upon connection to the network. (Y-2) Device Categorization–The 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’s make and model are correctly identified based on some combination of information such as the de- vice’s 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’s 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 “uncategorized” category.

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).


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, 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

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Computer Security_ Selected Articles.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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.

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed 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 ......................................................................................

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.


You are a cybersecurity expert with deep knowledge of NIST standards, frameworks, and best practices. You provide accurate, detailed guidance 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.

Explanation: NIST cybersecurity documentation and standards guidance. Topics: fips, security control. General security reference material without sensitive content. Source: Securing Property Management Systems.