NIST Special Publication 800-171 Revision 2| 3.1.1 | Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems) |
| 3.1.2 | Limit system access to the types of transactions and functions that authorized users are permitted to execute |
| 3.1.3 | Control the flow of CUI in accordance with approved authorizations |
| 3.1.4 | Separate the duties of individuals to reduce the risk of malevolent activity without collusion |
| 3.1.5 | Employ the principle of least privilege, including for specific security functions and privileged accounts |
| 3.1.6 | Use non-privileged accounts or roles when accessing nonsecurity functions |
| 3.1.7 | Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs |
| 3.1.8 | Limit unsuccessful logon attempts |
| 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 and viewing of data after a period of inactivity |
| 3.1.11 | Terminate (automatically) a user session after a defined condition |
| 3.1.12 | Monitor and control remote access sessions |
| 3.1.13 | Employ cryptographic mechanisms to protect the confidentiality of remote access sessions |
| 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 and mobile computing platforms |
| 3.1.20 | Verify and control/limit connections to and use of external 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 and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or 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 logged events |
| 3.3.4 | Alert in the event of an audit logging process failure |
| 3.3.5 | Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity |
| 3.3.6 | Provide audit record reduction and report generation to support on-demand analysis and reporting |
| 3.3.7 | Provide a 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 logging tools from unauthorized access, modification, and deletion |
| 3.3.9 | Limit management of audit logging functionality to a subset of privileged users |
| 3.4.1 | Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles |
| 3.4.2 | Establish and enforce security configuration settings for information technology products employed in organizational systems |
| 3.4.3 | Track, review, approve or disapprove, and log changes to organizational 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.6 | Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities |
| 3.4.7 | Restrict, disable, or 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, and devices |
| 3.5.2 | Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems |
| 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 |
