question
stringlengths 34
206
| context
stringlengths 15
2.29k
| answer
stringlengths 15
2.29k
|
|---|---|---|
Is requirement 3.1.14 in the 2nd Revision of NIST SP 800-171 a basic security requirement or a derived security requirement? | It is a derived security requirement. | Requirement 3.1.14 is a derived security requirement in the Access Control section of the NIST SP 800-171 2nd Revision document. |
What section is requirement 3.1.14 of the NIST SP 800-171 revision 2 document in? | It is located in the Access Control section of the SP 800-171 document. | Requirement 3.1.14 is located in the Access Control section of the NIST SP 800-171 2nd revision document. |
What is requirement 3.1.15 in the 2nd revision of the NIST SP 800 171? | Authorize remote execution of privileged commands and remote access to security-relevant information. | Authorize remote execution of privileged commands and remote access to security-relevant information. |
What section of the NIST SP 800-171 2nd revision has the requirement: Authorize remote execution of privileged commands and remote access to security-relevant information? | Found in the Access Control section of the SP 800-171 document. | That requirement is found in the Access Control section. |
What requirement in the Access Control section of the NIST SP 800-171 2nd revision requires authorization of remote execution of privileged commands? | That requirement is 3.1.15. | That requirement is 3.1.15. |
What requirement in the Access Control section of the NIST SP 800-171 2nd revision requires authorization of remote access to security-relevant information? | That requirement is 3.1.15. | That requirement is 3.1.15. |
What requirement in the Access Control section of the NIST SP 800-171 2nd revision requires authorization of remote execution of privileged commands and remote access to security-relevant information? | That requirement is 3.1.15. | That requirement is 3.1.15. |
Give me more information on requirement 3.1.15 in the NIST SP 800-171 revision 2 document. | A privileged command is a human-initiated (interactively or via a process operating on behalf of the human) command executed on a system involving the control, monitoring, or administration of the system including security functions and associated security-relevant information. Security-
relevant information is any information within the system that can potentially impact the operation of security functions or the provision of security services in a manner that could result in failure to enforce the system security policy or maintain isolation of code and data. Privileged
commands give individuals the ability to execute sensitive, security-critical, or security-relevant system functions. Controlling such access from remote locations helps to ensure that unauthorized individuals are not able to execute such commands freely with the potential to do serious or
catastrophic damage to organizational systems. Note that the ability to affect the integrity of the system is considered security-relevant as that could enable the means to by-pass security functions although not directly impacting the function itself. | A privileged command is a human-initiated (interactively or via a process operating on behalf of the human) command executed on a system involving the control, monitoring, or administration of the system including security functions and associated security-relevant information. Security-
relevant information is any information within the system that can potentially impact the operation of security functions or the provision of security services in a manner that could result in failure to enforce the system security policy or maintain isolation of code and data. Privileged
commands give individuals the ability to execute sensitive, security-critical, or security-relevant system functions. Controlling such access from remote locations helps to ensure that unauthorized individuals are not able to execute such commands freely with the potential to do serious or
catastrophic damage to organizational systems. Note that the ability to affect the integrity of the system is considered security-relevant as that could enable the means to by-pass security functions although not directly impacting the function itself. |
Is requirement 3.1.15 in the 2nd Revision of NIST SP 800-171 a basic security requirement or a derived security requirement? | It is a derived security requirement. | Requirement 3.1.15 is a derived security requirement in the Access Control section of the NIST SP 800-171 2nd Revision document. |
What section is requirement 3.1.15 of the NIST SP 800-171 revision 2 document in? | Found in the Access Control section of the SP 800-171 document. | Requirement 3.1.15 is located in the Access Control section of the NIST SP 800-171 2nd revision document. |
What is requirement 3.1.16 in the 2nd revision of the NIST SP 800 171? | Authorize wireless access prior to allowing such connections. | Authorize wireless access prior to allowing such connections. |
What section of the NIST SP 800-171 2nd revision has the requirement: Authorize wireless access prior to allowing such connections? | Found in the Access Control section of the SP 800-171 document. | That requirement is found in the Access Control section. |
What requirement in the Access Control section of the NIST SP 800-171 2nd revision requires authorization of wireless access prior to allowing a connection? | The requirement is 3.1.16 from the Access Control section of the SP 800-171 | That requirement is 3.1.16. |
Give me more information on requirement 3.1.16 in the NIST SP 800-171 revision 2 document. | Establishing usage restrictions and configuration/connection requirements for wireless access to the system provides criteria for organizations to support wireless access authorization decisions. Such restrictions and requirements reduce the susceptibility to unauthorized access to the system
through wireless technologies. Wireless networks use authentication protocols which provide credential protection and mutual authentication.
[SP 800-97] provide guidance on secure wireless networks. | Establishing usage restrictions and configuration/connection requirements for wireless access to the system provides criteria for organizations to support wireless access authorization decisions. Such restrictions and requirements reduce the susceptibility to unauthorized access to the system
through wireless technologies. Wireless networks use authentication protocols which provide credential protection and mutual authentication.
[SP 800-97] provide guidance on secure wireless networks. |
Is requirement 3.1.16 in the 2nd Revision of NIST SP 800-171 a basic security requirement or a derived security requirement? | It is a derived security requirement. | Requirement 3.1.16 is a derived security requirement in the Access Control section of the NIST SP 800-171 2nd Revision document. |
What section is requirement 3.1.16 of the NIST SP 800-171 revision 2 document in? | Found in the Access Control section of the SP 800-171 document. | Requirement 3.1.16 is located in the Access Control section of the NIST SP 800-171 2nd revision document. |
What SP documents does requirement 3.1.16 reference on providing guidance for secure remote access and virtual private networks? | 3.1.16 references SP 800-97 document Establishing Wireless Robust Security Networks: A Guide to IEEE 802.11i | Access Control requirement 3.1.16 references the SP 800-97 document Establishing Wireless Robust Security Networks: A Guide to IEEE 802.11i |
What is SP 800-97 document titled? | The SP 800-97 is titled Establishing Wireless Robust Security Networks: A Guide to IEEE 802.11i | Establishing Wireless Robust Security Networks: A Guide to IEEE 802.11i |
What is requirement 3.1.17 in the 2nd revision of the NIST SP 800 171? | This requirement is found in section 3.1 called Access Control. The requirement states: Protect wireless access using authentication and encryption. | Protect wireless access using authentication and encryption. |
What section of the NIST SP 800-171 2nd revision has the requirement: Protect wireless access using authentication and encryption? | Found in the Access Control section of the SP 800-171 document. | That requirement is found in the Access Control section. |
What requirement in the Access Control section of the NIST SP 800-171 2nd revision requires protecting wireless access using authentication and encryption? | The requirement is 3.1.17 from the Access Control section of the SP 800-171. | That requirement is 3.1.17. |
Give me more information on requirement 3.1.17 in the NIST SP 800-171 revision 2 document. | Organizations authenticate individuals and devices to help protect wireless access to the system. Special attention is given to the wide variety of devices that are part of the Internet of Things with potential wireless access to organizational systems. See the Cryptographic Standards and Guidelines. | Organizations authenticate individuals and devices to help protect wireless access to the system. Special attention is given to the wide variety of devices that are part of the Internet of Things with potential wireless access to organizational systems. See the Cryptographic Standards and Guidelines. |
Is requirement 3.1.17 in the 2nd Revision of NIST SP 800-171 a basic security requirement or a derived security requirement? | It is a derived security requirement. | Requirement 3.1.17 is a derived security requirement in the Access Control section of the NIST SP 800-171 2nd Revision document. |
What section is requirement 3.1.17 of the NIST SP 800-171 revision 2 document in? | Found in the Access Control section of the SP 800-171 document. | Requirement 3.1.17 is located in the Access Control section of the NIST SP 800-171 2nd revision document. |
What is requirement 3.1.18 in the 2nd revision of the NIST SP 800 171? | Control connection of mobile devices. | Control connection of mobile devices. |
What section of the NIST SP 800-171 2nd revision has the requirement: Control connection of mobile devices? | Found in the Access Control section of the SP 800-171 document. | That requirement is found in the Access Control section. |
What requirement in the Access Control section of the NIST SP 800-171 2nd revision requires controlling the connection of mobile devices? | That requirement is 3.1.18. | That requirement is 3.1.18. |
Give me more information on requirement 3.1.18 in the NIST SP 800-171 revision 2 document. | A mobile device is a computing device that has a small form factor such that it can easily be carried by a single individual; is designed to operate without a physical connection (e.g., wirelessly transmit or receive information); possesses local, non-removable or removable data storage; and
includes a self-contained power source. Mobile devices may also include voice communication capabilities, on-board sensors that allow the device to capture information, or built-in features for synchronizing local data with remote locations. Examples of mobile devices include smart phones, e-readers, and tablets.
Due to the large variety of mobile devices with different technical characteristics and capabilities, organizational restrictions may vary for the different types of devices. Usage restrictions and implementation guidance for mobile devices include: device identification and authentication;
configuration management; implementation of mandatory protective software (e.g., malicious code detection, firewall); scanning devices for malicious code; updating virus protection software;
scanning for critical software updates and patches; conducting primary operating system (and possibly other resident software) integrity checks; and disabling unnecessary hardware (e.g., wireless, infrared). The need to provide adequate security for mobile devices goes beyond this requirement. Many controls for mobile devices are reflected in other CUI security requirements.
[SP 800-124] provides guidance on mobile device security. | A mobile device is a computing device that has a small form factor such that it can easily be carried by a single individual; is designed to operate without a physical connection (e.g., wirelessly transmit or receive information); possesses local, non-removable or removable data storage; and
includes a self-contained power source. Mobile devices may also include voice communication capabilities, on-board sensors that allow the device to capture information, or built-in features for synchronizing local data with remote locations. Examples of mobile devices include smart phones, e-readers, and tablets.
Due to the large variety of mobile devices with different technical characteristics and capabilities, organizational restrictions may vary for the different types of devices. Usage restrictions and implementation guidance for mobile devices include: device identification and authentication;
configuration management; implementation of mandatory protective software (e.g., malicious code detection, firewall); scanning devices for malicious code; updating virus protection software;
scanning for critical software updates and patches; conducting primary operating system (and possibly other resident software) integrity checks; and disabling unnecessary hardware (e.g., wireless, infrared). The need to provide adequate security for mobile devices goes beyond this requirement. Many controls for mobile devices are reflected in other CUI security requirements.
[SP 800-124] provides guidance on mobile device security. |
Is requirement 3.1.18 in the 2nd Revision of NIST SP 800-171 a basic security requirement or a derived security requirement? | It is a derived security requirement. | Requirement 3.1.18 is a derived security requirement in the Access Control section of the NIST SP 800-171 2nd Revision document. |
What section is requirement 3.1.18 of the NIST SP 800-171 revision 2 document in? | Located in the Access Control section of the SP 800-171. | Requirement 3.1.18 is located in the Access Control section of the NIST SP 800-171 2nd revision document. |
What NIST SP document is referenced in implementing requirement 3.1.18 from the NIST SP 800-171 2nd revision document? | The referenced document is the SP 800-124. | NIST SP 800-124 |
What is the name of the NIST SP 800-124 document? | The SP 800-124 is titled Guidelines for Managing the Security of Mobile Devices in the Enterprise. | Guidelines for Managing the Security of Mobile Devices in the Enterprise |
What NIST SP document is referenced in the Access Control requirement that requires controlling the connections of mobile devices? | NIST SP 800-124 - Guidelines for Managing the Security of Mobile Devices in the Enterprise | NIST SP 800-124 - Guidelines for Managing the Security of Mobile Devices in the Enterprise |
What is requirement 3.1.19 in the 2nd revision of the NIST SP 800 171? | Encrypt CUI on mobile devices and mobile computing platforms. | Encrypt CUI on mobile devices and mobile computing platforms. |
What section of the NIST SP 800-171 2nd revision has the requirement: Encrypt CUI on mobile devices and mobile computing platforms? | Found in the Access Control section of the SP 800-171 document. | That requirement is found in the Access Control section. |
What requirement in the Access Control section of the NIST SP 800-171 2nd revision requires encrypting CUI on mobile devices and mobile computing platforms? | That requirement is 3.1.19. | That requirement is 3.1.19. |
Give me more information on requirement 3.1.19 in the NIST SP 800-171 revision 2 document. | Organizations can employ full-device encryption or container-based encryption to protect the confidentiality of CUI on mobile devices and computing platforms. Container-based encryption provides a more fine-grained approach to the encryption of data and information including encrypting selected data structures such as files, records, or fields. See the Cryptographic Standards and Guidelines. | Organizations can employ full-device encryption or container-based encryption to protect the confidentiality of CUI on mobile devices and computing platforms. Container-based encryption provides a more fine-grained approach to the encryption of data and information including encrypting selected data structures such as files, records, or fields. See the Cryptographic Standards and Guidelines. |
Is requirement 3.1.19 in the 2nd Revision of NIST SP 800-171 a basic security requirement or a derived security requirement? | It is a derived security requirement. | Requirement 3.1.19 is a derived security requirement in the Access Control section of the NIST SP 800-171 2nd Revision document. |
What section is requirement 3.1.19 of the NIST SP 800-171 revision 2 document in? | Located in the Access Control section of the SP 800-171. | Requirement 3.1.19 is located in the Access Control section of the NIST SP 800-171 2nd revision document. |
What is requirement 3.1.20 in the 2nd revision of the NIST SP 800 171? | Verify and control/limit connections to and use of external systems. | Verify and control/limit connections to and use of external systems. |
What section of the NIST SP 800-171 2nd revision has the requirement: Verify and control/limit connections to and use of external systems? | Found in the Access Control section of the SP 800-171 document. | That requirement is found in the Access Control section. |
What requirement in the Access Control section of the NIST SP 800-171 2nd revision requires verification and limiting connections to external systems? | That requirement is 3.1.20. | That requirement is 3.1.20. |
What requirement in the Access Control section of the NIST SP 800-171 2nd revision requires verification and limiting use of external systems? | That requirement is 3.1.20. | That requirement is 3.1.20. |
Give me more information on requirement 3.1.20 in the NIST SP 800-171 revision 2 document. | External systems are systems or components of systems for which organizations typically have no direct supervision and authority over the application of security requirements and controls or the determination of the effectiveness of implemented controls on those systems. External systems include personally owned systems, components, or devices and privately-owned computing and communications devices resident in commercial or public facilities. This requirement also addresses the use of external systems for the processing, storage, or transmission of CUI, including accessing cloud services (e.g., infrastructure as a service, platform as a service, or software as a service) from organizational systems.
Organizations establish terms and conditions for the use of external systems in accordance with organizational security policies and procedures. Terms and conditions address as a minimum, the types of applications that can be accessed on organizational systems from external systems. If terms and conditions with the owners of external systems cannot be established, organizations may impose restrictions on organizational personnel using those external systems.
This requirement recognizes that there are circumstances where individuals using external systems (e.g., contractors, coalition partners) need to access organizational systems. In those situations, organizations need confidence that the external systems contain the necessary controls so as not to compromise, damage, or otherwise harm organizational systems. Verification that the required controls have been effectively implemented can be achieved by third-party, independent assessments, attestations, or other means, depending on the assurance or confidence level required by organizations.
Note that while external" typically refers to outside of the organization's direct supervision and authority that is not always the case. Regarding the protection of CUI across an organization the organization may have systems that process CUI and others that do not. And among the systems that process CUI there are likely access restrictions for CUI that apply between systems. Therefore from the perspective of a given system other systems within the organization may be considered "external" to that system." | External systems are systems or components of systems for which organizations typically have no direct supervision and authority over the application of security requirements and controls or the determination of the effectiveness of implemented controls on those systems. External systems include personally owned systems, components, or devices and privately-owned computing and communications devices resident in commercial or public facilities. This requirement also addresses the use of external systems for the processing, storage, or transmission of CUI, including accessing cloud services (e.g., infrastructure as a service, platform as a service, or software as a service) from organizational systems.
Organizations establish terms and conditions for the use of external systems in accordance with organizational security policies and procedures. Terms and conditions address as a minimum, the types of applications that can be accessed on organizational systems from external systems. If terms and conditions with the owners of external systems cannot be established, organizations may impose restrictions on organizational personnel using those external systems.
This requirement recognizes that there are circumstances where individuals using external systems (e.g., contractors, coalition partners) need to access organizational systems. In those situations, organizations need confidence that the external systems contain the necessary controls so as not to compromise, damage, or otherwise harm organizational systems. Verification that the required controls have been effectively implemented can be achieved by third-party, independent assessments, attestations, or other means, depending on the assurance or confidence level required by organizations.
Note that while external" typically refers to outside of the organization's direct supervision and authority that is not always the case. Regarding the protection of CUI across an organization the organization may have systems that process CUI and others that do not. And among the systems that process CUI there are likely access restrictions for CUI that apply between systems. Therefore from the perspective of a given system other systems within the organization may be considered "external" to that system." |
Is requirement 3.1.20 in the 2nd Revision of NIST SP 800-171 a basic security requirement or a derived security requirement? | It is a derived security requirement. | Requirement 3.1.20 is a derived security requirement in the Access Control section of the NIST SP 800-171 2nd Revision document. |
What section is requirement 3.1.20 of the NIST SP 800-171 revision 2 document in? | Located in the Access Control section of the SP 800-171. | Requirement 3.1.20 is located in the Access Control section of the NIST SP 800-171 2nd revision document. |
What is requirement 3.1.21 in the 2nd revision of the NIST SP 800 171? | The requirement 3.1.21 is found in the Access Control section of the SP 800-171. The requirement states: Limit use of portable storage devices on external systems. | Limit use of portable storage devices on external systems. |
What section of the NIST SP 800-171 2nd revision has the requirement: Limit use of portable storage devices on external systems? | Found in the Access Control section of the SP 800-171 document. | That requirement is found in the Access Control section. |
What requirement in the Access Control section of the NIST SP 800-171 2nd revision requires limiting the use of portable storage devices on external systems? | The requirement is 3.1.21 from the Access Control section of the SP 800-171. | That requirement is 3.1.21. |
What requirement in the Access Control section of the NIST SP 800-171 2nd revision requires limiting the use of external hard drives on external systems? | The requirement is 3.1.21 from the Access Control section of the SP 800-171. | That requirement is 3.1.21. |
What requirement in the Access Control section of the NIST SP 800-171 2nd revision requires limiting the use of USBs on external systems? | The requirement is 3.1.21 from the Access Control section of the SP 800-171. | That requirement is 3.1.21. |
Give me more information on requirement 3.1.21 in the NIST SP 800-171 revision 2 document. | Limits on the use of organization-controlled portable storage devices in external systems include complete prohibition of the use of such devices or restrictions on how the devices may be used and under what conditions the devices may be used. Note that while external" typically refers to outside of the organization's direct supervision and authority that is not always the case. Regarding the protection of CUI across an organization the organization may have systems that process CUI and others that do not. Among the systems that process CUI there are likely access restrictions for CUI that apply between systems. Therefore from the perspective of a given system other systems within the organization may be considered "external" to that system." | Limits on the use of organization-controlled portable storage devices in external systems include complete prohibition of the use of such devices or restrictions on how the devices may be used and under what conditions the devices may be used. Note that while external" typically refers to outside of the organization's direct supervision and authority that is not always the case. Regarding the protection of CUI across an organization the organization may have systems that process CUI and others that do not. Among the systems that process CUI there are likely access restrictions for CUI that apply between systems. Therefore from the perspective of a given system other systems within the organization may be considered "external" to that system." |
Is requirement 3.1.21 in the 2nd Revision of NIST SP 800-171 a basic security requirement or a derived security requirement? | It is a derived security requirement. | Requirement 3.1.21 is a derived security requirement in the Access Control section of the NIST SP 800-171 2nd Revision document. |
What section is requirement 3.1.21 of the NIST SP 800-171 revision 2 document in? | It is located in the Access Control section of the SP 800-171 document. | Requirement 3.1.21 is located in the Access Control section of the NIST SP 800-171 2nd revision document. |
What is requirement 3.1.22 in the 2nd revision of the NIST SP 800 171? | Control CUI posted or processed on publicly accessible systems. | Control CUI posted or processed on publicly accessible systems. |
What section of the NIST SP 800-171 2nd revision has the requirement: Control CUI posted or processed on publicly accessible systems? | The requirement is 3.1.21 is found in the Access Control section of the SP 800-171. | That requirement is found in the Access Control section. |
What requirement in the Access Control section of the NIST SP 800-171 2nd revision requires controlling CUI posted or processed on publicly accessible systems? | That requirement is 3.1.22. | That requirement is 3.1.22. |
Give me more information on requirement 3.1.21 in the NIST SP 800-171 revision 2 document. | In accordance with laws, Executive Orders, directives, policies, regulations, or standards, the public is not authorized access to nonpublic information (e.g., information protected under the Privacy Act, CUI, and proprietary information). This requirement addresses systems that are controlled by
the organization and accessible to the public, typically without identification or authentication. Individuals authorized to post CUI onto publicly accessible systems are designated. The content of information is reviewed prior to posting onto publicly accessible systems to ensure that nonpublic information is not included. | In accordance with laws, Executive Orders, directives, policies, regulations, or standards, the public is not authorized access to nonpublic information (e.g., information protected under the Privacy Act, CUI, and proprietary information). This requirement addresses systems that are controlled by
the organization and accessible to the public, typically without identification or authentication. Individuals authorized to post CUI onto publicly accessible systems are designated. The content of information is reviewed prior to posting onto publicly accessible systems to ensure that nonpublic information is not included. |
Is requirement 3.1.22 in the 2nd Revision of NIST SP 800-171 a basic security requirement or a derived security requirement? | It is a derived security requirement. | Requirement 3.1.22 is a derived security requirement in the Access Control section of the NIST SP 800-171 2nd Revision document. |
What section is requirement 3.1.22 of the NIST SP 800-171 revision 2 document in? | It is located in the Access Control section of the SP 800-171 document. | Requirement 3.1.22 is located in the Access Control section of the NIST SP 800-171 2nd revision document. |