Cortex Xpanse does not make a determination regarding compliance with the listed NIST 800-171 controls.
Not all compliance violations can be detected from our scan data. Cortex Xpanse provides an external view of your attack surface. The controls listed below would require data from internal scans or checks against internal controls and processes where Xpanse does not have visibility. Therefore, Xpanse cannot make a determination regarding compliance with these specific controls.
The following controls, organized by control family, are unevaluated by the Expander Compliance Assessment > NIST 800-171 dashboard.
3.1.9 | Provide privacy and security notices consistent with applicable CUI rules. |
3.1.10 | Use session lock with pattern-hiding displays to prevent access/viewing of data after period of inactivity. |
3.1.11 | Terminate (automatically) a user session after a defined condition. |
3.1.14 | Route remote access via managed access control points. |
3.1.15 | Authorize remote execution of privileged commands and remote access to security-relevant information. |
3.1.16 | Authorize wireless access prior to allowing such connections. |
3.1.17 | Protect wireless access using authentication and encryption. |
3.1.18 | Control connection of mobile devices. |
3.1.19 | Encrypt CUI on mobile devices. |
3.1.20 | Verify and control/limit connections to and use of external information systems. |
3.1.21 | Limit use of portable storage devices on external systems. |
3.1.22 | Control CUI posted or processed on publicly accessible systems. |
3.2.1 | Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to the security of those systems. |
3.2.2 | Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities. |
3.2.3 | Provide security awareness training on recognizing and reporting potential indicators of insider threat. |
3.3.1 | Create, protect, and retain information system audit records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful unauthorized system activity. |
3.3.2 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. |
3.3.3 | Review and update events. |
3.3.4 | Alert in the event of an audit process failure. |
3.3.5 | Correlate audit review, analysis, and reporting processes for investigation and response to indications of suspicious, or unusual activity. |
3.3.6 | Provide audit reduction and report generation to support on-demand analysis and reporting. |
3.3.7 | Provide system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records. |
3.3.8 | Protect audit information and audit tools from unauthorized access, modification, and deletion. |
3.3.9 | Limit management of audit functionality to a subset of privileged users. |
3.4.3 | Track, review, approve/ or disapprove, and audit log changes to orgaizational systems. |
3.4.4 | Analyze the security impact of changes prior to implementation. |
3.4.5 | Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems. |
3.4.7 | Restrict, disable, prevent the use of nonessential programs, functions, ports, protocols, and services. |
3.4.8 | Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software. |
3.4.9 | Control and monitor user-installed software. |
3.5.1 | Identify system users, processes acting on behalf of users, devices. |
3.5.3 | Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts. |
3.5.4 | Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts. |
3.5.5 | Prevent reuse of identifiers for a defined period. |
3.5.6 | Disable identifiers after a defined period of inactivity. |
3.5.7 | Enforce a minimum password complexity and change of characters when new passwords are created. |
3.5.8 | Prohibit password reuse for a specified number of generations. |
3.5.9 | Allow temporary password use for system logons with an immediate change to a permanent password. |
3.5.10 | Store and transmit only cryptographically-protected of passwords. |
3.5.11 | Obscure feedback of authentication information. |
3.6.1 | Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities. |
3.6.2 | Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization. |
3.6.3 | Test the organizational incident response capability. |
3.7.1 | Perform maintenance on organizational systems. |
3.7.2 | Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance. |
3.7.3 | Ensure equipment removed for off-site maintenance is sanitized of any CUI. |
3.7.4 | Check media containing diagnostic and test programs for malicious code before the media are used in the organizational systems. |
3.7.5 | Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete. |
3.7.6 | Supervise the maintenance activities of maintenance personnel without required access authorization. |
3.8.1 | Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital. |
3.8.2 | Limit access to CUI on information system media to authorized users. |
3.8.3 | Sanitize or destroy information system media containing CUI before disposal or release for reuse. |
3.8.4 | Mark media with necessary CUI markings and distribution limitations. |
3.8.5 | Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas. |
3.8.6 | Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards. |
3.8.7 | Control the use of removable media on system components. |
3.8.8 | Prohibit the use of portable storage devices when such devices have no identifiable owner. |
3.8.9 | Protect the confidentiality of backup CUI at storage locations. |
3.9.1 | Screen individuals prior to authorizing access to organizational systems containing CUI. |
3.9.2 | Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers. |
3.10.1 | Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals. |
3.10.2 | Protect and monitor the physical facility and support infrastructure for organizational systems. |
3.10.4 | Maintain audit logs of physical access. |
3.10.6 | Enforce safeguarding measures for CUI at alternate work sites. |
3.12.1 | Periodically assess the security controls in organizational systems to determine if the controls are effective in their application. |
3.12.2 | Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems. |
3.12.3 | Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls. |
3.12.4 | Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems. |
3.13.2 | Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. |
3.13.3 | Separate user functionality from information system management functionality. |
3.13.4 | Prevent unauthorized and unintended information transfer via shared system resources. |
3.13.6 | Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). |
3.13.7 | Prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks (i.e., split tunneling). |
3.13.8 | Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards. |
3.13.9 | Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity. |
3.13.11 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. |
3.13.13 | Control and monitor the use of mobile code. |
3.13.14 | Control and monitor the use of Voice over Internet Protocol (VoIP) technologies. |
3.13.15 | Protect the authenticity of communications sessions. |
3.13.16 | Protect the confidentiality of CUI at rest. |
3.14.6 | Monitor organizational systems including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. |